From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EYSP9-0005G8-0v for garchives@archives.gentoo.org; Sat, 05 Nov 2005 18:04:39 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA5I2umc016612; Sat, 5 Nov 2005 18:02:56 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA5Hw2mj031011 for ; Sat, 5 Nov 2005 17:58:02 GMT Received: from 82-41-57-20.cable.ubr08.edin.blueyonder.co.uk ([82.41.57.20] helo=snowdrop.home) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1EYSIj-0003PX-Nw for gentoo-dev@lists.gentoo.org; Sat, 05 Nov 2005 17:58:02 +0000 Received: from localhost.home ([127.0.0.1] helo=snowdrop.home) by snowdrop.home with esmtp (Exim 4.54) id 1EYSIe-0008Px-S6 for gentoo-dev@lists.gentoo.org; Sat, 05 Nov 2005 17:57:56 +0000 Date: Sat, 5 Nov 2005 17:57:54 +0000 From: Ciaran McCreesh To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two Message-ID: <20051105175754.64ff0f7b@snowdrop.home> In-Reply-To: <200511052218.14564.jstubbs@gentoo.org> References: <20051105005814.0de0d8ff@snowdrop.home> <200511052218.14564.jstubbs@gentoo.org> X-Mailer: Sylpheed-Claws 1.9.99-rc2 (GTK+ 2.6.10; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Signature_Sat__5_Nov_2005_17_57_54_+0000_Er9v.qHIZYxhnVPM; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 09803eb5-327e-4b13-8dcf-37b33a2fcbf7 X-Archives-Hash: 95db2ccebf2247baeceba594d6b5c5c0 --Signature_Sat__5_Nov_2005_17_57_54_+0000_Er9v.qHIZYxhnVPM Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, 5 Nov 2005 22:18:14 +0900 Jason Stubbs wrote: | > A more reliable way of getting news of critical updates out to | > users is required to avoid repeats of the various recent upgrade | > debacles. |=20 | Examples of the "recent upgrade debacles" aren't needed, but you | should at least state some of the outcomes that occurred, whether it | be unscheduled downtime, data corruption or whatever. I'm trying to avoid throwing in too many unnecessary references, but I guess a couple here would be useful. |=20 | > Preemptive | > =C2=A0 =C2=A0 Users should be told of changes *before* they break the u= ser's | > system, after the damage has already been done. |=20 | s/after/when/ perhaps? This sentence takes a couple of reads... Ring up another one for me hitting . in Vim forgetting that I'd done a daw after the gq} ... | > Quality control | > =C2=A0 =C2=A0 There should be some way to ensure that badly written or | > irrelevant messages are not sent out, for example by inexperienced | > developers, those whose English language skills are below par or | > morons. |=20 | "morons" is not needed either. No, but it's funny! | > The following headers are used for filtering. If none of these | > headers are specified, the news item is displayed for all users. | > Otherwise, the news item is displayed if *at least one* header | > matches. |=20 | It would seem more useful if the headers were sorted into the three | classes first. A news item would then only be displayed if a header | from the class matches or the class is empty. This would allow for | rules such as "net-www/apache is installed and the keyword is either | mips or sparc". Hrm. I'll need to think about that. But it's starting to sound nicer than the and/or/none voodoo I'd removed previously. | Isn't keyword just a generalization of profile? Why have both? Simplicity. | > Thus, all proposed news items must be posted to the ``gentoo-dev`` | > or ``gentoo-core`` mailing list, and ``Cc:``\ed to | > ``pr@gentoo.org`` at least 72 hours before being committed | > (exceptions may be made in exceptional circumstances). Any | > complaints regarding wording or clarity **must** be addressed | > before the news item goes live. |=20 | Why gentoo-core? It's a news item; it's purpose is to be made public. Possible security concerns. Hopefully this will never happen. | Why put this in portage at all? Post sync hooks will likely be | available in 2.0.54. If adding hooks were as easy as adding a file to | a portage config directory, would adding the package that does the | above to the system package set be enough to force this new | information dispersal method on users? Performance. I have a bash script which does the installs that could easily be called by a hook, but it has to call portageq quite a bit. Otherwise a hook would be fine... Possibly it's fine anyway? --=20 Ciaran McCreesh : Gentoo Developer (Anti-XML, anti-newbie conspiracy) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm --Signature_Sat__5_Nov_2005_17_57_54_+0000_Er9v.qHIZYxhnVPM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDbPKk96zL6DUtXhERAjIUAJ9yy5DPVlnFvhToc5W5qQ7urnoymgCg2Ddt 8oxm8uLUnaa7H4U8O2uBtYA= =iyCn -----END PGP SIGNATURE----- --Signature_Sat__5_Nov_2005_17_57_54_+0000_Er9v.qHIZYxhnVPM-- -- gentoo-dev@gentoo.org mailing list