public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Allen Brooker <gmane@allenjb.me.uk>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project]  Re: Improving developer/user communication
Date: Sat, 21 Jul 2007 17:59:37 +0100	[thread overview]
Message-ID: <f7te1h$vrr$1@sea.gmane.org> (raw)
In-Reply-To: <f7tcq6$t1h$1@sea.gmane.org>

Allen Brooker wrote:
> Donnie Berkholz wrote:
>> Allen Brooker wrote:
>>> Could we create a very-low-traffic, developer-posts-only list that is
>>> used for announcing important package changes? The list could also be
>>> used for other announcements (not sure exactly what - events where
>>> Gentoo devs will be, regional meets, other things). If people feel that
>>> using the same list for other announcements too would create too much
>>> traffic, consider creating multiple lists, which would allow people to
>>> subscribe to only the types of messages that they want to see.
>> Just made it at the same time as this one: gentoo-dev-announce. We're
>> still working out the policy.
>>
>> Thanks,
>> Donnie
>>
> According to http://www.gentoo.org/main/en/lists.xml (and my impression
> from the name) that list appears to be for developer-targeted announcements.
> 
> What I was thinking was something along the lines of some of the
> post-install messages (not all of them, just the important ones that
> might actually (appear to) break things - eg. glibc upgrade - "you can't
> downgrade"; gcc upgrade - "follow the guide here; coreutils upgrade -
> "some locations have changed - run 'hash -r' to clear the cache"; etc.)
> and other user-targeted messages to be sent to a list.
> 
> Allen
> 
I've also just been reminded about GLEP 42 [1] - What's the current
status and what are the hold-ups, if any? How can they be overcome?

Allen

[1] http://www.gentoo.org/main/en/lists.xml

-- 
gentoo-project@gentoo.org mailing list



  parent reply	other threads:[~2007-07-21 17:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 23:42 [gentoo-project] Improving developer/user communication George Prowse
2007-07-20  0:49 ` lnxg33k
2007-07-21  8:20 ` Marijn Schouten (hkBst)
2007-07-21 11:00   ` George Prowse
2007-07-21 14:43   ` lnxg33k
2007-07-21 16:02 ` [gentoo-project] " Allen Brooker
2007-07-21 16:27   ` Donnie Berkholz
2007-07-21 16:38     ` Allen Brooker
2007-07-21 16:50       ` Allen Brooker
2007-07-21 16:59       ` Allen Brooker [this message]
2007-07-21 19:42         ` Alec Warner
2007-07-23 16:40           ` Marius Mauch
2007-07-23 18:56             ` Ciaran McCreesh
2007-07-24  2:21               ` Marius Mauch
2007-07-24  2:54                 ` Ciaran McCreesh
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23  8:43 Steve Long

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='f7te1h$vrr$1@sea.gmane.org' \
    --to=gmane@allenjb.me.uk \
    --cc=gentoo-project@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