| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Stuart Herbert wrote: |
| 5 |
> On Tue, 2005-11-01 at 14:51 -0500, Chris Gianelloni wrote: |
| 6 |
> |
| 7 |
>>Did you specifically ask them if it is because we have different news in |
| 8 |
>>different locations? Somehow I think you're obscuring some facts to |
| 9 |
>>make your own argument. |
| 10 |
> |
| 11 |
> |
| 12 |
> That seems an unpleasant accusation to make :( |
| 13 |
> |
| 14 |
> The answer is that I didn't ask them if it was because we have different |
| 15 |
> news in different locations. The question didn't occur to me. |
| 16 |
> |
| 17 |
> |
| 18 |
>>The only problem that we have now with our multiple mediums is that not |
| 19 |
>>all news is on all mediums. We should have the same information going |
| 20 |
>>to all of these and let the user choose which method they like for |
| 21 |
>>getting news. |
| 22 |
> |
| 23 |
> |
| 24 |
> The critical difference between improving our existing mediums, and the |
| 25 |
> emerge --news approach that I've proposed, is that emerge --news is the |
| 26 |
> only approach that actively pushes news out to *all* users, and puts it |
| 27 |
> in a place that is as guaranteed as anything else available to catch |
| 28 |
> their attention. |
| 29 |
> |
| 30 |
> All the other approaches rely on the user going somewhere to get news, |
| 31 |
> whether it's signing up to a mailing list, reading www.g.o, reading the |
| 32 |
> forums, or whatever. Inevitably, this is only going to reach a smaller |
| 33 |
> subsection of our user community. |
| 34 |
> |
| 35 |
> What I care about is that we've taken the right steps to put important |
| 36 |
> information in front of *all* of our users (and our devs!). Even |
| 37 |
> (especially?) the ones who are unable to keep up with the news as it is |
| 38 |
> currently delivered. |
| 39 |
> |
| 40 |
> Making sure our users are well-informed improves the level and quality |
| 41 |
> of service that we provide; it can only enhance our reputation; and it |
| 42 |
> should also cut down on the amount of developer time that goes into |
| 43 |
> post-upgrade support (leaving more time for package maintenance). |
| 44 |
> |
| 45 |
|
| 46 |
One source: http://errata.gentoo.org/ |
| 47 |
|
| 48 |
Push that out to as many alternate sources as you like (RSS feeds, |
| 49 |
summaries in emerge --news, forums post, etc.), but make it known that |
| 50 |
the website is *the* source (your alternate sources should point back to |
| 51 |
it). |
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 54 |
|
| 55 |
iD8DBQFDarUL2QTTR4CNEQARAh0pAKCi7BJpBOkRRT4iiaXUjajwbrjseACfahPV |
| 56 |
R2MVvKhkLfnid1/ADRUZAxk= |
| 57 |
=Oou4 |
| 58 |
-----END PGP SIGNATURE----- |
| 59 |
-- |
| 60 |
gentoo-dev@g.o mailing list |
Archives