public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] Using gentoo-announce for more routine decision/ebuild announcements
@ 2001-10-28 12:12 Dan Armak
  2001-10-28 12:58 ` Daniel Robbins
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Dan Armak @ 2001-10-28 12:12 UTC (permalink / raw
  To: gentoo-dev

Hi all,

This is a followup on the gentoo-ebuild rhide thread, intented to be more 
visible than the original thread.

The gentoo-announce list currently gets a message in a month or two. IMHO 
it's not very useful that way. Why not open it for all developers to send 
announcements of medium and high importance?

This can include various decisions - unified ebuild style, install -> /usr, 
etc. and announcements of important/interesting new ebuilds and major new 
versions of existing ones. 

I for one am tired of reading the cvs logs, and as Azarah says, most of us 
aren't on IRC 24/7 and can't follow all the discussions that take place.

If you think gentoo-announce is important and should stay as-is, we can 
create a new list for this.

In my view the optimal volume would be around 1 message per day, sometimes 2, 
with the messages being short and succint and any discussions taking place on 
a different list (gentoo-dev, -user, or the team lists).

What do you think?

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2001-11-03 12:40 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-28 12:12 [gentoo-dev] Using gentoo-announce for more routine decision/ebuild announcements Dan Armak
2001-10-28 12:58 ` Daniel Robbins
2001-10-30  4:23 ` Dan Armak
2001-11-02 15:34 ` Mikael Hallendal
2001-11-03  1:01   ` Dan Armak
2001-11-03  5:41     ` Mikael Hallendal

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox