public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: GLEP 42 (Was: Getting Important Updates To Users)
Date: Tue, 01 Nov 2005 09:32:49 -0500	[thread overview]
Message-ID: <1130855570.26789.173.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20051101075631.GB18490@superlupo.rechner>

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

On Tue, 2005-11-01 at 08:56 +0100, Wernfried Haas wrote:
> On Mon, Oct 31, 2005 at 06:52:04PM -0500, Dan Meltzer wrote:
> > 1) Why post to forums.g.o if its on www, why would one check forums
> > instead of www.
> Redundancy - to get the attention of those folks that for whatever
> reason visit the forums and not www.gentoo.org in a specific time
> interval. The more places you cover, the more likely people will see it
> somewhere. We've been doing that with GLSAs for quite a while now.

Exactly.

While I agree that we need a single source where users can get their
information, I feel that the *user* should be able to choose their
source.  If that is the gentoo-announce mailing list, or www.gentoo.org,
or the forums, it doesn't matter.  The same information should be
duplicated.

Make them *all* a definitive source.  We don't need to check all of them
if any one of them gives all of the information needed.

As for subscriber counts or whatever, if by adding the information to
gentoo-announce (or the forums or wherever), we reach 10 more users that
we wouldn't have reached before, then I consider it a success.  The idea
is to reach as many users as possible here.  To me, that means
duplicating the information everywhere.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

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

  reply	other threads:[~2005-11-01 14:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 23:36 [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users) Chris White
2005-10-31 23:41 ` [gentoo-dev] " Dan Meltzer
2005-10-31 23:52   ` Dan Meltzer
2005-11-01  7:56     ` Wernfried Haas
2005-11-01 14:32       ` Chris Gianelloni [this message]
2005-11-01 19:32       ` Stuart Herbert
2005-11-01 19:51         ` Chris Gianelloni
2005-11-03 19:40           ` Stuart Herbert
2005-11-04  1:10             ` Nathan L. Adams
2005-11-04  8:22               ` Sami Näätänen
2005-11-04 14:26               ` Xavier Neys
2005-11-04 16:44                 ` Jason Stubbs
2005-11-04 18:53                   ` Alec Joseph Warner
2005-11-05  5:08                     ` Jason Stubbs
2005-11-05  5:34                       ` Alec Warner
2005-11-07 10:11                         ` Paul de Vrieze
2005-11-07 12:37                           ` Jason Stubbs
2005-11-07 16:06                             ` Grant Goodyear
2005-11-07 16:44                               ` Jason Stubbs
2005-11-07 16:43                             ` Stuart Herbert
2005-11-05  9:58                       ` [gentoo-dev] " Duncan
2005-11-05 12:54                       ` [gentoo-dev] " Michiel de Bruijne
2005-11-06 19:32                       ` R Hill
2005-11-01 19:53         ` Mike Williams
2005-10-31 23:46 ` [gentoo-dev] " Brian Harring
2005-11-01 10:51   ` Jason Stubbs
2005-11-01  0:42 ` Ciaran McCreesh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1130855570.26789.173.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox