From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] Using gentoo-announce for more routine decision/ebuild announcements
Date: Sun Oct 28 12:12:01 2001 [thread overview]
Message-ID: <0GLX00MHKJYFEZ@mxout2.netvision.net.il> (raw)
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
next reply other threads:[~2001-10-28 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 12:12 Dan Armak [this message]
2001-10-28 12:58 ` [gentoo-dev] Using gentoo-announce for more routine decision/ebuild announcements 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
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=0GLX00MHKJYFEZ@mxout2.netvision.net.il \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@cvs.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