incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: [VOTE] Project Bylaws
Date Thu, 03 Jan 2013 19:04:34 GMT
On Thu, Jan 3, 2013 at 1:52 PM, Rohit Yadav <rohit.yadav@citrix.com> wrote:
> +1
>
> Some comments:
>
>>2.4.1.2. Deciding what is distributed as products of the Apache CloudStack
> project.
>>2.4.1.1. Fostering, supporting and growing the project's community.
>>2.4.1.4. Speaking on behalf of the project.
>
> Should committers also participate in the above?
>

2.4.1.2. and 2.4.1.4. have to do with the legal role of the PMC within
the foundation.

2.4.1.1. - Absolutely, all community members should help foster and
support the community as a whole.  The reason it's listed as a
responsibility of the PMC is that it's such a critical responsibility
for that group.  Apache projects are communities first and foremost,
that just happen to have gathered around a shared software development
activity.  The PMC is accountable for ensuring that the community is
healthy.

>>3. Veteos
> Who can Veto? Timeframe when a veto is challenged?
>

The "who" is anyone that can cast a binding vote on an issue.
Further, veto's are only applicable for "lazy consensus" style formal
votes or technical decisions.

I'm not sure I get your timeframe question though...

> Regards.
>
>
> On 03-Jan-2013, at 6:58 AM, Chip Childers <chip.childers@sungard.com<mailto:chip.childers@sungard.com>>
wrote:
>
> On Thu, Jan 3, 2013 at 9:47 AM, Wido den Hollander <wido@widodh.nl<mailto:wido@widodh.nl>>
wrote:
> On 01/02/2013 09:52 PM, Chip Childers wrote:
>
> One quick follow up.
>
> If we approve the bylaw draft, I'll publish it to the website.
> However, the document comes from the perspective of CloudStack being a
> top level project (graduated from the incubator).  I'd likely include
> a header note indicating this issue.  My preference is to approach the
> process this way, so that we don't have to do an amendment process
> during / after a potential / eventual graduation.
>
>
> Not to be picky, but shouldn't this be changed then?
>
>
> "3.1.1. Decisions regarding the project are made by votes on the primary
> project
>
> development mailing list (cloudstack-dev@incubator.apache.org<mailto:cloudstack-dev@incubator.apache.org>)."
>
>
> If you are writing like we are graduated should we keep the incubator
> address there? Just to prevent this bylaws being copied and we being haunted
> by this e-mail address still being present in there.
>
> Other then that: +1 (binding)
>
> Wido
>
> -chip
>
>
>
>
> Agreed.  I'll make that change in the wiki version.  Unless anyone
> objects, I don't think this change represents a reason to restart the
> vote.
>

Mime
View raw message