Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two

[Stuart Herbert <stuart@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 2148 bytes --]

On Fri, 2005-11-11 at 18:40 +0100, Marius Mauch wrote:
>   I've already asked a similar question in another mail (in other
> context) without an answer, but how many news items do people believe
> will exist at any given time?

We won't know for certain until people start using it.  I expect that
it'll eventually be used for more than just the
package-upgrade-will-break-your-box type news that we plan on using it
for at first.

For example, there's no real reason why GLSA's couldn't been delivered
via this at some point (although I'd prefer a "You have X amount of
security fixes to apply" type message adding to emerge, and treating
GLSAs as a special case).

> Things that should definitely be changed:
> - Integration with existing systems:
> This definitely should be a requirement for the GLEP to be considered
> final. It doesn't prevent some thing being implemented sooner than
> others, but multi-channel distribution (to use a buzzword) is a
> requirement from where I come from.

One of the key things with successfully delivering a change programme is
to not dilute the change by introducing too many at once.  

If we simultaneously launch emerge --news w/ (f.ex) gatewaying to
gentoo-announce, I believe that it weakens the impact of introducing
emerge --news.  

One of the objectives is to remove confusion from the minds of users
about where to find the news.  If we can start by pointing at one place,
and saying "go there", we can clear up the confusion, and then
afterwards introduce multi-channel distribution when our users "get it",
so to speak.

I'm all for making the news available via www.g.o etc etc as well - I
just think doing it all at the same time will not be the most effective
strategy.

Best regards,
Stu
-- 
Stuart Herbert                                         stuart@gentoo.org
Gentoo Developer                                  http://www.gentoo.org/
                                              http://stu.gnqs.org/diary/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]