public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Council manifesto of sping
Date: Tue, 22 Jun 2010 04:37:52 +0200	[thread overview]
Message-ID: <4C202200.5010008@gentoo.org> (raw)
In-Reply-To: <20100622014611.GA24755@hrair>

On 06/22/10 03:46, Brian Harring wrote:
> Your proposed solutions in your manifesto is to just throw out the 
> manifest bits that need completion, in the process ignoring the 
> infrastructural and security reasons for their existance.  Same goes 
> for ignoring the commit hooks chunk for rsync generation (after all, 
> we can't just tell every gentoo user that "by the way, we're no longer 
> going to update rsync").

The Git migration is taking us 2 years already because it's taken too
far.  We need to look at what's really needed of that now.

I'll speak to Robin before I go into further details here.


> I'd be a bit less critical of your offer here and the manifesto 
> presented, if it was actually factual and at least a partially 
> accurate understanding of the issues outstanding.

I read that as a pretty hard accusation.
Are you referring to the Git migration or the manifesto as a whole?
Please make clear where exactly my manifesto is not factual.


> At the very least, I suggest you actually have a chat w/ Robin 
> directly and get caught up on what the issues are rather than making 
> claims about his work that are pretty far off base.

Earlier today I wrote to him asking for his number to be able to call
him tomorrow.


> Also please note Arun's actual question was "what have you done to 
> help", not "what skills do you have".  There is difference- one I'm 
> guessing that is being lost in the language barrier.

I am aware of that difference.



Sebastian



  reply	other threads:[~2010-06-22  2:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 19:56 [gentoo-dev] Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-19 21:06 ` [gentoo-dev] Manifesto for council election Tony "Chainsaw" Vroon
2010-06-20 11:19 ` [gentoo-dev] My Council manifest Petteri Räty
2010-06-20 13:47 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-21 16:33 ` [gentoo-dev] Council manifesto of sping Sebastian Pipping
2010-06-21 18:20   ` Petteri Räty
2010-06-21 21:07     ` Sebastian Pipping
2010-06-21 19:25   ` Arun Raghavan
2010-06-21 21:36     ` Sebastian Pipping
2010-06-22  1:46       ` Brian Harring
2010-06-22  2:37         ` Sebastian Pipping [this message]
2010-06-22  5:13       ` Arun Raghavan
2010-06-22 10:02         ` [gentoo-dev] " Duncan
2010-06-22 10:24           ` Arun Raghavan
2010-06-30  0:45         ` [gentoo-dev] " Sebastian Pipping
2010-07-02 14:23           ` Arun Raghavan
2010-07-02 15:50             ` Sebastian Pipping
2010-07-02 17:30               ` Nirbheek Chauhan
2010-06-22  5:15       ` Arun Raghavan
2010-06-22  2:37   ` Alec Warner
2010-06-21 19:10 ` [gentoo-dev] My council manifesto Mark Loeser
2010-06-21 19:15   ` Arun Raghavan
2010-06-21 19:27     ` Mark Loeser
2010-06-21 19:30       ` Arun Raghavan
2010-06-21 21:19 ` [gentoo-dev] Gentoo Council 2010/2011 - Voting Mike Frysinger
2010-07-02 22:32 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting - Reminder Roy Bamford

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=4C202200.5010008@gentoo.org \
    --to=sping@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