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 1EXl3E-00001p-7O for garchives@archives.gentoo.org; Thu, 03 Nov 2005 19:47:08 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA3Jj6aT000867; Thu, 3 Nov 2005 19:45:06 GMT Received: from mail.gnqs.org (myrddraal.demon.co.uk [62.49.28.63]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA3Jeo0p008702 for ; Thu, 3 Nov 2005 19:40:50 GMT Received: from mogheiden.gnqs.org ([192.168.0.20]) by mail.gnqs.org with esmtp (Exim 4.54) id 1EXkx6-0000Fl-NA for gentoo-dev@lists.gentoo.org; Thu, 03 Nov 2005 19:40:49 +0000 Subject: Re: [gentoo-dev] Re: GLEP 42 (Was: Getting Important Updates To Users) From: Stuart Herbert To: gentoo-dev@lists.gentoo.org In-Reply-To: <1130874713.26789.194.camel@cgianelloni.nuvox.net> References: <200511010836.29453.chriswhite@gentoo.org> <46059ce10510311541s6bf5bb1csc19d330ef714a3d4@mail.gmail.com> <46059ce10510311552m4d6cb06eje22d7c31651c8a3c@mail.gmail.com> <20051101075631.GB18490@superlupo.rechner> <1130873554.8565.2.camel@mogheiden.gnqs.org> <1130874713.26789.194.camel@cgianelloni.nuvox.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-L6t4QyzNjPdvsNhk8hEj" Organization: Gentoo Linux Project Date: Thu, 03 Nov 2005 19:40:29 +0000 Message-Id: <1131046829.8530.45.camel@mogheiden.gnqs.org> 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 X-Mailer: Evolution 2.2.3 X-Spam_score: -2.8 X-Spam_score_int: -27 X-Spam_bar: -- X-Spam_report: Spam detection software, running on the system "demandred.gnqs.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Tue, 2005-11-01 at 14:51 -0500, Chris Gianelloni wrote: > Did you specifically ask them if it is because we have different news in > different locations? Somehow I think you're obscuring some facts to > make your own argument. [...] Content analysis details: (-2.8 points, 7.5 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.8 ALL_TRUSTED Did not pass through any untrusted hosts X-Archives-Salt: 3d44efa7-7280-4aa9-9bad-1c4b4e079961 X-Archives-Hash: 18c9e908cd0331a9c615d6d4c3d0a35c --=-L6t4QyzNjPdvsNhk8hEj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2005-11-01 at 14:51 -0500, Chris Gianelloni wrote: > Did you specifically ask them if it is because we have different news in > different locations? Somehow I think you're obscuring some facts to > make your own argument. That seems an unpleasant accusation to make :( The answer is that I didn't ask them if it was because we have different news in different locations. The question didn't occur to me. > The only problem that we have now with our multiple mediums is that not > all news is on all mediums. We should have the same information going > to all of these and let the user choose which method they like for > getting news. The critical difference between improving our existing mediums, and the emerge --news approach that I've proposed, is that emerge --news is the only approach that actively pushes news out to *all* users, and puts it in a place that is as guaranteed as anything else available to catch their attention. All the other approaches rely on the user going somewhere to get news, whether it's signing up to a mailing list, reading www.g.o, reading the forums, or whatever. Inevitably, this is only going to reach a smaller subsection of our user community. What I care about is that we've taken the right steps to put important information in front of *all* of our users (and our devs!). Even (especially?) the ones who are unable to keep up with the news as it is currently delivered. Making sure our users are well-informed improves the level and quality of service that we provide; it can only enhance our reputation; and it should also cut down on the amount of developer time that goes into post-upgrade support (leaving more time for package maintenance). Best regards, Stu --=20 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 =3D 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C -- --=-L6t4QyzNjPdvsNhk8hEj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDametDC+AuvmvxXwRAnhsAJ9aNsmq4iyWGbLx5OOnaSUDi22Z9QCeLCQV ZQuhYzq43jJgiPngz7UcAEE= =LP6I -----END PGP SIGNATURE----- --=-L6t4QyzNjPdvsNhk8hEj-- -- gentoo-dev@gentoo.org mailing list