Open Stack

We have been focused on getting the actual language of the modifications finalized and wanted to ensure that the Board and the Legal Affairs Committee could review all of the proposed revisions. We have made no decisions on how we will present them to the membership.  I am fine with splitting up the changes into different groups and I will make that recommendation to the Board. 

By the way, we have communicated with the Technical Committee and they want the ATC qualifications to apply to contributions to the OpenStack Project (not the Integrated Release).  We will make that change. 

-----Original Message-----
From: Mark McLoughlin [mailto:markmc at redhat.com] 
Sent: Wednesday, September 17, 2014 3:01 AM
To: Joshua McKenty
Cc: aclark at suse.com; eileen.evans at hp.com; defcore-committee at lists.openstack.org; Roay, Leslie
Subject: Re: [OpenStack-DefCore] Updated Bylaws

On Thu, 2014-09-11 at 10:28 -0700, Joshua McKenty wrote:


> My only further concern is to make sure that, despite the convenience, 
> each potential Bylaws change is structured as a separate redline, and 
> voted on individually - both by the board, and by the membership.
> Specifically:
> 
> 
> 1. DefCore-related changes that clarify the meaning of core, and the 
> difference between integrated release and project.
> 2. ATC-related changes that should be considered an amendment to the 
> TC processes.
> 3. Legal Affairs committee changes.
> 4. Election reform (if we end up coming back to this one).
> 5. CLA reform (again, if it comes back in).
> 
> 
> Since I’ve seen scope creep on #2 and #3, I start to get worried about
> 4 and 5 - which would certainly nuke our chances of getting 1 through 
> this window.

Yep, I was thinking the same. We should try to split up the bylaws changes logically (much as developers do with patches) and have the electorate vote on each logical change separately.

If we proposed all bylaws changes via a single vote and it got rejected, we'd have no feedback on which aspects of the changes were most troublesome.

Mark



_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
Please consider the environment before printing this email.

The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster at dlapiper.com. Thank you.