public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Joseph Warner <warnera6@egr.msu.edu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: regular project updates
Date: Thu, 05 Jan 2006 11:14:19 -0500	[thread overview]
Message-ID: <43BD45DB.3070200@egr.msu.edu> (raw)
In-Reply-To: <1136476815.20002.45.camel@localhost>



Patrick Lauer wrote:
> Hi all,
> 
> as the debate about the future direction of Gentoo continues it's
> getting more and more obvious to me that there's a lack of information
> skewing the debate. It seems that while most devs (and users) have a
> good idea what's happening in "their" projects it's quite difficult to
> see what is happening in other projects.
> 
> So - as GWN monkey - I'm offering my services as aggregator for project
> updates. Maybe someone from the doc project wants to help to get this
> information put on the website so that it's visible?
> 
> I suggest project updates every 6 months (which roughly is the same
> timeframe as releases)
> Maybe this helps people get a "global vision" of where Gentoo is and
> where it's going.
> 
> Any feedback appreciated :-)
> 
> wkr,
> Patrick 

I would prefer quarterly, but anything is better than the present.
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-01-05 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 16:00 [gentoo-dev] RFC: regular project updates Patrick Lauer
2006-01-05 16:14 ` Alec Joseph Warner [this message]
2006-01-05 16:26 ` Stuart Herbert
2006-01-05 16:28 ` Grobian
2006-01-05 16:41   ` Ciaran McCreesh
2006-01-05 16:49     ` Grobian
2006-01-05 16:57     ` Patrick Lauer
2006-01-05 16:54 ` Chris Gianelloni
2006-01-05 19:10   ` Donnie Berkholz
2006-01-05 19:52 ` Lares Moreau
2006-01-05 20:18 ` Jan Kundrát
2006-01-05 20:32   ` Jan Kundrát

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43BD45DB.3070200@egr.msu.edu \
    --to=warnera6@egr.msu.edu \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox