From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Using gentoo-announce for more routine decision/ebuild announcements
Date: Sat Nov 3 05:41:01 2001 [thread overview]
Message-ID: <1004791297.12881.4.camel@zoidberg> (raw)
In-Reply-To: <0GM700K8YSV0MB@mxout2.netvision.net.il>
[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]
lör 2001-11-03 klockan 08.58 skrev Dan Armak:
> Hi,
>
> > > 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.
> >
> > However I don't agree with you here. IMHO gentoo-announce should be for
> > _users_, Gentoo-dev is for posting such things as "unified ebuild
> > style".
> >
> > install -> /usr should defenatly be at gentoo-announce.
> >
>
> I think gentoo-announce should be read by both users and developers, but I
> agree that some topics may be better off on gentoo-dev. Something better
> fitting on gentoo-announce might be, "We have a new document on the site
> about the new unified ebuild style". After all, all gentoo users are
> potential ebuild writers.
Yes, it should be read by both. But the information should be for users
(and of course developers are users too so they'll read the information
as users).
> > > 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.
> >
> > Hmm .. I think that all developers should read the cvs logs, it takes
> > about 2 minutes each day to read. I you haven't subscribe to the
> > cvs-list and you'll get a mail with all changes every day.
> I do read the cvs logs. Perhaps a better point would have been that they are
> usually very short and if I see something interesting I have to look it up.
It is short and if you want to look something up you look in gentoo-dev
or emails the guy who made the change.
> > I'd think that 1 mail/day to gentoo-announce would be far to much. This
> > should be a list for people interested in gentoo or users that don't
> > want to follow the discussions, just the decissions.
>
> Well, maybe 1 in two days, but I think that things of medium importance
> should be in as well, not just the big ones like install->/usr. Like
> drobbins's recent announcements of new Portage versions, any major new
> versions of major apps should be announced. We'll see how many messages that
> makes, and if there are too many, we can do more aggressive filtering.
Since this list is for those that want's to stay tuned on what's
happening in the project without having to read the discussions on
gentoo-user/gentoo-dev messages should only be about things that users
might care about.
A new version of Portage would of course fall in this category since
users won't be able to use newer ebuilds without it.
I think that things like "Finally Evolution works, added RC1..." or
"KDE3 is now added to portage, read about it on http://...."
> Also, in case you've missed it, Drobbins quietly agreed to a test period of
> sorts. Send any announcements to the list, it's moderated.
Yeah, I snapped it up on IRC.
Regards,
Mikael Hallendal
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-11-03 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=1004791297.12881.4.camel@zoidberg \
--to=hallski@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