public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grobian <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: regular project updates
Date: Thu, 5 Jan 2006 17:28:13 +0100	[thread overview]
Message-ID: <20060105162813.GA25581@gentoo.org> (raw)
In-Reply-To: <1136476815.20002.45.camel@localhost>

On 05-01-2006 17:00:15 +0100, Patrick Lauer wrote:
> 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?

The following crossed my mind: what about a Developers release of the
GWN?  I see you guys scouring the planet, MLs and whatever more, but not
all information there is user-friendly, or just a 'good idea' to tell
the users about.  I'd really like to see an aggregation of stuff from
all kinds of sources (perhaps even including CVS/SVN commit messages)
put into a monthly (or bi-weekly?) message sent to -dev for instance.
It should just have some headliners for each project team, such that
those who want be a bit aware of what happens in the whole of gentoo can
read it, and take an active role when interested in some more
information.
I'm thinking of quite dull news, so absolutely not meant to be a
publication like GWN, but just thingis like some commits on the portage
sources that say to fix/implement X, a discussion on project ML Y
working on Z.  Also for instance that Flameeyes has been working on
something with "--as-needed"; just what it is, and why, from planet.
Perhaps even a short note that after +-150 commits the tree has been
upgraded to XOrg-7_rc1 or something... that can be useful information,
even though it does look like spam.
This kind of information is all of the type background noise, hence it
dull, but can be very important for those that are open to it.

I would just be interested in such a thing, because I'd like to read
some few lines per month on projects, but not whole MLs and every dev's
Blog.  Of course it's just shifting the problem of not wanting to read
everything to someone else... but IMHO it does improve communication for
those open to read the "Gentoo Developer Notes" (or something like
that).

Just a thought.  No idea whether you really meant to do something like
this.  Would like you to do it though ;)


-- 
Fabian Groffen
Gentoo/Alt
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-01-05 16:31 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
2006-01-05 16:26 ` Stuart Herbert
2006-01-05 16:28 ` Grobian [this message]
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=20060105162813.GA25581@gentoo.org \
    --to=grobian@gentoo.org \
    --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