> Thinking about your question, I'm not sure. On one hand, specifics
> are good. On the other hand, it's actually hard to pin down exactly
> what a technical decision is. For example, is an overhaul of the
> website a technical decision? I would argue that it is, since it's an
> "action" being
gard.com]
>> Sent: Tuesday, December 18, 2012 12:38 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] Apache CloudStack Project Bylaws
>>
>> Latest Draft Below - Comments Please!
>>
>> Draft Apache CloudStack Project Bylaws
>>
t: Re: [DISCUSS] Apache CloudStack Project Bylaws
>
> Latest Draft Below - Comments Please!
>
> Draft Apache CloudStack Project Bylaws
>
> 1. Introduction
>
> 1.1. This document defines the bylaws under which the Apache CloudStack
> project
> operates. It defines the r
Latest Draft Below - Comments Please!
Draft Apache CloudStack Project Bylaws
1. Introduction
1.1. This document defines the bylaws under which the Apache CloudStack project
operates. It defines the roles and responsibilities of the project, who may
vote, how voting works, how conflicts are resol
On Sat, Dec 15, 2012 at 11:51 AM, Sebastien Goasguen wrote:
>
> On Dec 14, 2012, at 7:36 PM, Chip Childers wrote:
>
>> On Fri, Dec 14, 2012 at 1:21 PM, Chiradeep Vittal
>> wrote:
>>> On 12/12/12 6:30 PM, "Chip Childers" wrote:
2.1. Users
The most important participants in the pro
On Thu, Dec 13, 2012 at 3:55 PM, Sebastien Goasguen wrote:
3.4.9. Modifying Bylaws
Modifying this document.
Lazy majority of active PMC members
>>>
>>> Do we need to set a timeframe on updating/reviewing bylaws ?
>>>
>>
>> I wasn't suggesting one, but do folks think t
I'm doing another pass at a clean draft (thanks for all the discussion!).
One question came to my mind, while editing. Is the Single
Transferable Vote (STV) process too complex for the PPMC to use for
the chair?
This is the section that I left in from Hadoop's bylaws (I'm removing
the rotation b
Yeah, with PMC members it's a kinda-different ball o' wax.
For committers, not so much.
On Dec 18, 2012, at 10:52 AM, Chip Childers wrote:
> On Mon, Dec 17, 2012 at 2:40 PM, Jim Jagielski wrote:
>>>
> 2.3. Committers
>
> The project's Committers are responsible for the project's t
On Mon, Dec 17, 2012 at 2:40 PM, Jim Jagielski wrote:
>>
2.3. Committers
The project's Committers are responsible for the project's technical
management. Committers have access to all project source control
repositories. Committers may cast binding votes on any technical
>
>
>>> 2.3. Committers
>>>
>>> The project's Committers are responsible for the project's technical
>>> management. Committers have access to all project source control
>>> repositories. Committers may cast binding votes on any technical
>>> discussion regarding the project (or any sub-project).
>
On Sat, Dec 15, 2012 at 11:51 AM, Sebastien Goasguen wrote:
>
> On Dec 14, 2012, at 7:36 PM, Chip Childers wrote:
>
>> On Fri, Dec 14, 2012 at 1:21 PM, Chiradeep Vittal
>> wrote:
>>> On 12/12/12 6:30 PM, "Chip Childers" wrote:
2.1. Users
The most important participants in the pro
On Thu, Dec 13, 2012 at 3:23 PM, Joe Brockmeier wrote:
> On Wed, Dec 12, 2012 at 09:30:45PM -0500, Chip Childers wrote:
>> Hi all,
>>
>> I'd like to start a conversation about our project bylaws. This is
>> something that an Apache project doesn't absolutely require, but I
>> believe that some of
On Dec 14, 2012, at 7:36 PM, Chip Childers wrote:
> On Fri, Dec 14, 2012 at 1:21 PM, Chiradeep Vittal
> wrote:
>> On 12/12/12 6:30 PM, "Chip Childers" wrote:
>>> 2.1. Users
>>>
>>> The most important participants in the project are people who use our
>>> software. Users contribute to the Apac
On Wed, Dec 12, 2012 at 09:30:45PM -0500, Chip Childers wrote:
> Hi all,
>
> I'd like to start a conversation about our project bylaws. This is
> something that an Apache project doesn't absolutely require, but I
> believe that some of the larger TLP's have found it to be valuable.
> 1.3. CloudSt
On Fri, Dec 14, 2012 at 1:21 PM, Chiradeep Vittal
wrote:
> On 12/12/12 6:30 PM, "Chip Childers" wrote:
>>2.1. Users
>>
>>The most important participants in the project are people who use our
>>software. Users contribute to the Apache projects by providing
>>feedback to developers in the form of b
On 12/12/12 6:30 PM, "Chip Childers" wrote:
>Hi all,
>
>I'd like to start a conversation about our project bylaws. This is
>something that an Apache project doesn't absolutely require, but I
>believe that some of the larger TLP's have found it to be valuable.
>More specifically, I would like t
On Fri, Dec 14, 2012 at 12:47 PM, David Nalley wrote:
>>
>> 2.4.2. The chair of the PMC is appointed by the ASF board. The chair
>> is an office holder of the Apache Software Foundation (Vice President,
>> Apache CloudStack) and has primary responsibility to the board for the
>> management of the
>
> 2.4.2. The chair of the PMC is appointed by the ASF board. The chair
> is an office holder of the Apache Software Foundation (Vice President,
> Apache CloudStack) and has primary responsibility to the board for the
> management of the projects within the scope of the CloudStack PMC. The
> chair
On Dec 13, 2012, at 5:19 PM, Chip Childers wrote:
> On Thu, Dec 13, 2012 at 9:58 AM, Sebastien Goasguen wrote:
>> Chip, some thoughts inline.
>>
>> Don't mind the pickiness.
>
> Thanks for the review. Any no, I don't mind the pickiness!
>
>> On Dec 13, 2012, at 3:30 AM, Chip Childers wrote
On Thu, Dec 13, 2012 at 9:58 AM, Sebastien Goasguen wrote:
> Chip, some thoughts inline.
>
> Don't mind the pickiness.
Thanks for the review. Any no, I don't mind the pickiness!
> On Dec 13, 2012, at 3:30 AM, Chip Childers wrote:
>
>> Hi all,
>>
>> I'd like to start a conversation about our pr
Chip, some thoughts inline.
Don't mind the pickiness.
On Dec 13, 2012, at 3:30 AM, Chip Childers wrote:
> Hi all,
>
> I'd like to start a conversation about our project bylaws. This is
> something that an Apache project doesn't absolutely require, but I
> believe that some of the larger TLP's
Hi all,
I'd like to start a conversation about our project bylaws. This is
something that an Apache project doesn't absolutely require, but I
believe that some of the larger TLP's have found it to be valuable.
More specifically, I would like to see us discuss and agree on the
contents of the byla
22 matches
Mail list logo
