On Mon, 2005-11-07 at 09:27 -0700, Duncan wrote: > They shouldn't /have/ to, but the option is there. Those who care about > security and care about getting a heads-up on "major" changes of this > nature, will find several opportunities to be notified of them.
That's not the point behind the push for this approach. I kicked this off in my blog article because we've used those opportunities to notify users, and it didn't work well enough. We've had users and Gentoo developers alike who didn't know about the changes. Add 'php' to your away logging, and sit in #gentoo-dev and #gentoo-apache for a week or so, and make a count of the number of users and devs who still don't know about the (delayed) PHP5 changes. From my point of view, as a Gentoo developer pushing large service-affecting changes out to users, our existing mechanisms are at least a partial failure when it comes to getting the news out. If you want a timely example, take a look at this week's GWN's description of this debate, and see for yourself how it matches the changes I've blogged about ;-) > The announce list is one. By your own admission, you're on the announce list, and but you didn't know about the Apache changes. Imagine how many other users were in the same situation. Imagine how many other users never signed up to the announce list in the first place. We can sit here all day and blame those users for their actions, or lack thereof. Or, we can do better, and pro-actively put the news right in front of them. Even game systems like Steam already do this :) > I'm just not sure how much > I'd /personally/ prioritize it, given that there are plenty of information > sources for those that care, already. Take a moment to re-examine the argument from the viewpoint that the existing information sources are not getting the news out to the people that matter - our devs and our users. From that point of view, this work is worth making a high priority. Best regards, Stu -- Stuart Herbert [EMAIL PROTECTED] 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 --
signature.asc
Description: This is a digitally signed message part
