Gentoo Archives: gentoo-dev

From: kloeri@g.o
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two
Date: Sat, 05 Nov 2005 11:51:18
Message-Id: 20051105114729.GB14844@kloeri
In Reply to: Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two by Grobian
1 On Sat, Nov 05, 2005 at 12:29:28PM +0100, Grobian wrote:
2 > kloeri@g.o wrote:
3 > >You must not have read the [#forums-whining]_ reference as that makes it
4 > >quite clear that existing methods isn't adequate. Even if you think the
5 > >apache maintainers made lots of mistakes you can't really fault us for
6 > >not trying to get the news of config changes out to all users.
7 >
8 > I haven't, that's correct. However, a reference should be a source for
9 > additional information. A small exerpt or recap of that thread is not
10 > in the GLEP. Also, [#forums-whining]_ was not referenced in the quoted
11 > part, the reference only follows later on.
12 >
13 > Going into answering your question, the thread suggests for instance an
14 > RSS-feed with this info. Also the GLEP mentions 5 distinct sources, of
15 > which I personally think at least two will be effective for a certain
16 > group of people.
17 >
18 > That last thing was what I was aiming at. For some it might work quite
19 > well if the apache2 upgrade stuff (as sent out on gentoo-dev) was
20 > communicated through gentoo-announce. Hence my doubts on whether "[they
21 > are not] particularly effective" is a general statement that applies to
22 > any situation.
23 >
24 If we were only aiming at a certain group of people there would be no
25 need to change anything. The apache announcements reached lots of users
26 but still left a large chunk of users in the dark. Moving the news to
27 -announce or some RSS feed wouldn't change anything as the basic problem
28 with these methods is that people have to actively search out important
29 news instead of news getting pushed to them.
30
31 Regards,
32 Bryan Østergaard
33 --
34 gentoo-dev@g.o mailing list

Replies