public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Improving Gentoo User Relations
Date: Fri, 07 Apr 2006 13:32:48 +0200	[thread overview]
Message-ID: <1144409568.18008.22.camel@localhost> (raw)
In-Reply-To: <20060407093312.GG25992@gentoo.org>

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

On Fri, 2006-04-07 at 11:33 +0200, Grobian wrote:
> Maybe user-rel should, together with GWN bridge this problem by keeping
> the source of news anonymous?  Just to use it as teasers of what kind of
> things are being done in Gentoo's kitchen?
> Of course this only holds for new projects like in your hypothetical
> example.
GWN has a section "Future Zone" where any Gentoo project can announce
new ideas, roadmaps or previews. It is not used that often, but if
anyone wants some testing of a pre-release version or some user feedback
on ideas ... just tell the GWN :-)


Patrick

-- 
Stand still, and let the rest of the universe move

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

  parent reply	other threads:[~2006-04-07 11:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07  2:30 [gentoo-dev] Improving Gentoo User Relations Christel Dahlskjaer
2006-04-07  2:17 ` [gentoo-dev] How many users? [WAS] " Donnie Berkholz
2006-04-07  3:22   ` Christel Dahlskjaer
2006-04-07  8:51 ` [gentoo-dev] " Christopher O'Neill
2006-04-07  9:07   ` Ciaran McCreesh
2006-04-07  9:33     ` Grobian
2006-04-07  9:49       ` Ciaran McCreesh
2006-04-07 11:32       ` Patrick Lauer [this message]
2006-04-07 14:24         ` Christel Dahlskjaer
2006-04-11 20:55         ` Tamas Sarga
2006-04-07 14:22       ` Christel Dahlskjaer
2006-04-07 14:19     ` Christel Dahlskjaer
2006-04-07 13:35       ` Martin Ehmsen
2006-04-07 14:45         ` Christel Dahlskjaer
2006-04-07 13:43       ` Ciaran McCreesh
2006-04-07 14:57         ` Christel Dahlskjaer
2006-04-08 19:29     ` lnxg33k
2006-04-07  9:33   ` Donnie Berkholz
2006-04-07  9:56     ` Jakub Moc
2006-04-15  8:45       ` Philipp Riegger
2006-04-07 10:37     ` Jonathan Coome
2006-04-07 14:27       ` Christel Dahlskjaer
2006-04-08 21:55       ` Tom Wesley
2006-04-07 14:26     ` Christel Dahlskjaer
2006-04-07 13:20   ` Grant Goodyear
2006-04-07 14:47     ` Christel Dahlskjaer
2006-04-15  9:10       ` Philipp Riegger
2006-04-07 13:51   ` Duncan
2006-04-07 14:14   ` Christel Dahlskjaer
2006-04-07  9:21 ` [gentoo-dev] " Ciaran McCreesh
2006-04-07 14:41   ` Christel Dahlskjaer
2006-04-07 15:15   ` Thomas de Grenier de Latour
2006-04-07 15:42     ` Alec Warner
2006-04-07 15:47       ` Christel Dahlskjaer
2006-04-07 17:01         ` Alexandre Buisse
2006-04-08 15:12         ` Paul de Vrieze
2006-04-08 19:15       ` lnxg33k
2006-04-07 16:48     ` Michael Cummings
2006-04-07 17:47       ` Thomas de Grenier de Latour
2006-04-08 19:07   ` lnxg33k
2006-04-08 22:27     ` Christel Dahlskjaer
2006-04-07 11:32 ` Thomas Cort
2006-04-07 14:43   ` Christel Dahlskjaer
2006-04-17  8:34 ` Volkov Peter
2006-04-17 19:05   ` Curtis Napier

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=1144409568.18008.22.camel@localhost \
    --to=patrick@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