Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of runseb@gmail.com designates
 74.125.82.41 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Summary of why where and how development happens matters
From: Sebastien Goasguen <runseb@gmail.com>
In-Reply-To: <20130304160818.GZ88519@USLT-205755.sungardas.corp>
Date: Tue, 5 Mar 2013 04:46:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD03AA95-DA14-4CC9-AA74-506A43D1B2FE@gmail.com>
References: <20130227185128.GX81779@USLT-205755.sungardas.corp>
 <20130228061538.GF2058@cloud-2.local>
 <CAKprHVYHQ1by9DA_BqYT5rU6am4qnEBCKknH9TuJXaoYQkBAMA@mail.gmail.com>
 <20130228063035.GI2058@cloud-2.local>
 <9C992E2C-77E1-4A9C-ABAB-BDFD8F7E214F@basho.com>
 <7A92FF96DF135843B4B608FB576BFC3E012F74C418E9@SJCPMAILBOX01.citrite.net>
 <20130301183718.GD47236@USLT-205755.sungardas.corp>
 <4061CC58-BD3F-4ADD-8C5C-4CB0CBA77DEF@gmail.com>
 <20130304160818.GZ88519@USLT-205755.sungardas.corp>
To: cloudstack-dev@incubator.apache.org


On Mar 4, 2013, at 11:08 AM, Chip Childers <chip.childers@sungard.com> =
wrote:

> On Mon, Mar 04, 2013 at 09:16:36AM -0500, Sebastien Goasguen wrote:
>>=20
>> On Mar 1, 2013, at 1:37 PM, Chip Childers <chip.childers@sungard.com> =
wrote:
>>=20
>>> On Thu, Feb 28, 2013 at 02:38:27PM -0800, Animesh Chaturvedi wrote:
>>>> John, I agree we need to merge in logical chunks sooner rather than =
later that allows for reviews and feedback sooner.=20
>>>>=20
>>>> Chip I can take the first stab at putting this in a wiki but would =
require collaboration with you and Alex  to get it crisp and clear
>>>=20
>>> That would be quite nice of you Animesh!
>>=20
>> I just read it all and there does not seem to be a real conclusion =
especially from David's concerns.
>>=20
>> How do we move forward and ensure that the entire community and =
committers understand how code is developed in the ASF ?
>> Is this thread a mandatory reading for instance ?
>>=20
>> -Sebastien
>=20
> Part of the challenge is that this is a moving target...  who exactly =
is
> "in the community" at any point in time is different as time moves on.
> So we're left with thinking about it in terms of (1) current community
> members being educated, (2) ongoing education and processes, and (3)=20=

> documenting it for the purpose of reference as the community grows / =
evolves.
>=20
> The reason that we decided to push this thread over from private to =
dev,
> was specifically to support (1) and (3).  For (1), we now have a =
public=20
> reference of the discussion, as well as the effects of it having been =
quite
> visible (see all the IP clearance threads / work).  For (2), this is =
the
> responsibility of the community itself (and specifically a
> responsibility of the (P)PMC to keep an eye on things).  We do need to
> continue to work on our processes though...  As for (3), this thread
> plus a wiki page discussing how and why (which Animesh said he'd work
> on) seem to be the best option.
>=20
> Other than the points above, do you have any other thoughts about how =
to
> move forward?  Think I'm missing anything?

I think it's fine, I just don't know how for (3) we will "enforce" =
people reading the wiki or the thread.

>=20
> -chip