public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Gregory M. Turner" <gmt@malth.us>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] CIA replacement
Date: Mon, 01 Oct 2012 12:57:04 -0700	[thread overview]
Message-ID: <5069F590.2090906@malth.us> (raw)
In-Reply-To: <CAGfcS_mZP47_F1BRfZB=p0oBksi4CW3UBqqYFw_VEuJJeVZMmw@mail.gmail.com>

On 10/1/2012 10:29 AM, Rich Freeman wrote:

>
> Looking at the tracker [1], we need a pre-upload hook (I'm not quite
> sure why), an rsync conversion script, the ability to validate the
> converted tree, and documentation.  There is still an open bug for
> commit signing, and I'm not quite sure why as this was implemented.

a job for gitolite? what does ogo use?

> Am I missing some big concern that just isn't obvious in these bugs?

Things will break.  There will be much wringing of virtual hands. But in 
1 weeks' time, everyone will get over it and find ways to fix whatever 
broke.  There will be one less thing on the big to-do list, and most 
people will be happier overall.

It's one of those "Social Security" type of things it's hard to build a 
clean consensus around /when/ to make a break like this.  I think we 
basically need a headstrong asshole in a position of sufficient 
authority to say, "fuck everyone, we are doing this, here is the 
changeover date."

Too much democracy, tactical planning and consensus-building will almost 
certainly perpetuate the status quo.

Look, Gentoo will probably fall to pieces for a few days.  The 
alternative, IMO, is a huge, elaborate multi-phase plan of some kind, 
like how Microsoft or NASA would do it: armies of 40-somethings toil for 
months or years in cubicles...  Elaborate Gantt charts and process 
diagrams are drawn up and approved by layer after layer of middle 
management.

Gentoo can tolerate a hiccup; it's survived way scarier challenges.  We 
have a huge community of very talented people highly motivated to keep 
this machinery working... there's literally zero chance that Gentoo will 
somehow have it's spirit broken by cvs->git.

In other words, devs -- imo -- just go for it.  Throw caution to the 
wind.  Break some bylaws if need be.  Ignore anyone saying "we're not 
ready."  It'll be easier to get forgiveness than permission, and exactly 
what process issues needed to be smoothed over will frankly only truly 
be clear in the aftermath.

Of course, that's easy for me to say since I'm not the one whose door 
everyone will be beating down when TSHTF.  There are worse things than 
CVS (Visual SourceSafe comes to mind).  But if we don't bite the bullet 
now, we all know we'll be having this discussion again later.

-gmt




  parent reply	other threads:[~2012-10-01 19:58 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01  8:14 [gentoo-dev] CIA replacement Ben de Groot
2012-10-01  9:48 ` [gentoo-dev] " Duncan
2012-10-02  4:40   ` Ben de Groot
2012-10-02  6:32     ` Fabian Groffen
2012-10-03  0:21       ` Jeroen Roovers
2012-10-03  0:25         ` Anthony G. Basile
2012-10-03  1:10         ` Michael Mol
2012-10-03  3:43         ` Ben de Groot
2012-10-03  4:45           ` Jeroen Roovers
2012-10-03 10:02             ` Duncan
2012-10-03 13:05         ` Rafael Goncalves Martins
2012-10-02 15:56     ` Peter Stuge
2012-10-02 16:15       ` Ben de Groot
2012-10-02 16:51         ` Peter Stuge
2012-10-03  3:40           ` Ben de Groot
2012-10-01 11:19 ` [gentoo-dev] " Chí-Thanh Christopher Nguyễn
2012-10-01 15:21 ` Rafael Goncalves Martins
2012-10-01 17:29   ` Rich Freeman
2012-10-01 17:42     ` Michael Mol
2012-10-01 17:54       ` Rich Freeman
2012-10-01 18:08         ` Michael Mol
2012-10-01 18:08     ` Rafael Goncalves Martins
2012-10-01 18:29       ` Rich Freeman
2012-10-01 18:31         ` Diego Elio Pettenò
2012-10-01 18:53         ` Peter Stuge
2012-10-01 19:57     ` Gregory M. Turner [this message]
2012-10-01 20:17       ` Peter Stuge
2012-10-01 20:35         ` Diego Elio Pettenò
2012-10-01 20:54           ` Rich Freeman
2012-10-01 21:00             ` [gentoo-dev] Discussing stuff that is not appropriate to discuss Diego Elio Pettenò
2012-10-01 21:41               ` Peter Stuge
2012-10-01 21:55                 ` Diego Elio Pettenò
2012-10-01 22:21                   ` Peter Stuge
2012-10-01 22:24                     ` Diego Elio Pettenò
2012-10-01 22:53                       ` Peter Stuge
2012-10-01 22:58                         ` Diego Elio Pettenò
2012-10-02  0:51               ` Gregory M. Turner
2012-10-02  0:58                 ` Diego Elio Pettenò
2012-10-02  1:14                   ` Michael Mol
2012-10-02  4:15                   ` [gentoo-dev] CVS -> git, list of where non-infra folk can contribute Brian Harring
2012-10-02  4:58                     ` Ben de Groot
2012-10-02 20:51                       ` Theo Chatzimichos
2012-10-03  3:46                         ` Ben de Groot
2012-10-03  4:58                           ` Jeroen Roovers
2012-10-02 20:20                     ` Gregory M. Turner
2012-10-03  4:14               ` [gentoo-dev] Re: Discussing stuff that is not appropriate to discuss Ryan Hill
2012-10-03 14:35                 ` [gentoo-dev] Regarding the tinderbox logs Diego Elio Pettenò
2012-10-10  8:47                   ` Markos Chandras
2012-10-10 14:41                     ` Diego Elio Pettenò
2012-10-10 15:18                       ` Rich Freeman
2012-10-10 15:28                       ` Markos Chandras
2012-10-01 20:19     ` [gentoo-dev] CIA replacement Dirkjan Ochtman
2012-10-01 20:24       ` Rich Freeman
2012-10-01 17:45   ` Jeff Horelick

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=5069F590.2090906@malth.us \
    --to=gmt@malth.us \
    --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