public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Gentoo Wiki Project
Date: Fri, 9 Apr 2010 18:49:52 +0530	[thread overview]
Message-ID: <x2r8b4c83ad1004090619k79d93a9cx60fe073e1b4ff97d@mail.gmail.com> (raw)
In-Reply-To: <n2pe117dbb91004090602t61fff7d1w9a42b517ddf158b2@mail.gmail.com>

On Fri, Apr 9, 2010 at 6:32 PM, Ben de Groot <yngwin@gentoo.org> wrote:
> On 9 April 2010 14:35, Maciej Mrozowski <reavertm@gmail.com> wrote:
>> See? This is the problem. Every time comes an initiative to introduce official
>> Gentoo infra hosted Gentoo Wiki (yes, the one that won't loose randomly all
>> its contents) - there's lack of interest of cooperation from already existing
>> unofficial Gentoo-related Wiki admins.
>
> You are quite wrong here, as Guy was one of the first to volunteer for
> the official wiki project. It is the bickering about its status that
> apparently has demotivated him.
>

I think at this point you've got the opinions of everyone, and pretty
much everyone's needs have been stated. Any more discussion will only
distract you and use up time and energy. I say ignore all further
discussion on this thread unless you feel it's *really* important.
Everything else not from the team is just bikeshedding I think :)

-- 
~Nirbheek Chauhan

Gentoo GNOME+Mozilla Team



  reply	other threads:[~2010-04-09 13:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 18:12 [gentoo-dev] [RFC] Gentoo Wiki Project Ben de Groot
2010-04-05 18:52 ` Nathan Zachary
2010-04-05 19:00 ` Alex Legler
2010-04-05 19:15 ` Markos Chandras
2010-04-05 21:37   ` Zeerak Mustafa Waseem
2010-04-05 19:45     ` Sylvain Alain
2010-04-06  2:27 ` Ravi Pinjala
2010-04-06  5:16 ` Stuart Longland
2010-04-06 13:00   ` Ben de Groot
2010-04-06 15:12     ` Zeerak Mustafa Waseem
2010-04-08 19:51 ` [gentoo-dev] " Ryan Hill
2010-04-08 20:13   ` Ben de Groot
2010-04-08 20:56     ` Ryan Hill
2010-04-08 21:37       ` Sylvain Alain
2010-04-08 22:55         ` Ryan Hill
2010-04-09  0:38           ` Sylvain Alain
2010-04-09 11:26             ` Guy Fontaine
2010-04-09 12:35               ` Maciej Mrozowski
2010-04-09 13:02                 ` Ben de Groot
2010-04-09 13:19                   ` Nirbheek Chauhan [this message]
2010-04-09 12:38               ` Ben de Groot
2010-04-09 17:02                 ` George Prowse
2010-04-09 17:24                   ` Zeerak Mustafa Waseem
2010-04-09 17:32                     ` AllenJB
2010-04-09 17:52                       ` Ben de Groot
2010-04-09 18:52                         ` Mike Pagano
2010-04-09 17:48                     ` George Prowse
2010-04-09  2:42   ` Patrick Nagel
2010-04-09  6:34     ` Duncan
2010-04-12 10:28       ` Roy Bamford
2010-04-12 11:32         ` Ben de Groot
2010-04-12 13:13           ` George Prowse
2010-04-12 13:17             ` Arun Raghavan
2010-04-12 13:19               ` George Prowse
2010-04-12 13:22                 ` Arun Raghavan
2010-04-12 13:41                   ` George Prowse
2010-04-12 14:01                   ` Ben de Groot
2010-04-12 16:47                     ` Dale
2010-04-12 18:10                       ` Duncan
2010-04-12 17:59             ` Duncan

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=x2r8b4c83ad1004090619k79d93a9cx60fe073e1b4ff97d@mail.gmail.com \
    --to=nirbheek@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