Open Stack

Jonathon,
How is it possible for someone to taint the nomination process?  Are we
not allowed to promote our nominations? In light of the fact that the
process is closed and we can't know how many nominations we had
received, it seems fine to me to encourage nominations.  Have some
unwritten rules been broken, I am completely confused?  Saying someone
"violated the basic principles that hold our community together" is an
extreme statement. Our community does things in the open, by default.
Had we followed our "basic principles" in this nomination process, I
can't help but think we wouldn't be in this situation.


Rick



On 07/29/2012 01:18 AM, Jonathan Bryce wrote:
> The OpenStack Foundation has already attracted over 2,000 Individual Members in a little over a week. It's a very exciting moment for all of us involved in this effort, but also brings responsibility for each Individual and Corporate member.
> 
> We've learned that someone may have violated the basic principles that hold this community together by trying to affect the nominations for the Individual Member elections. This is not what our community stands for, and we do not want to let the actions of one or a few tarnish the reputation of the thousands of individuals who are working to make OpenStack a great place to develop open source software. We are so determined to uphold our values that every member--individual or corporate--agrees to a code of conduct that prohibits abusive behavior and attempts to manipulate our elections.
> 
> Our bylaws and election process have been defined and overseen by very experienced, independent legal counsel, Mark Radcliffe. We are completely committed to ensuring this process is open, fair and legitimate in accordance with our bylaws and Delaware corporate law. To ensure that the process is open, fair and legitimate, we are looking for individuals who would like to volunteer to be inspectors through the duration of the election to certify the outcome along with our counsel. No more than two affiliated members (working for the same company) can be inspectors, and any candidates who wish to run for election are also ineligible to be inspectors. As stated in the bylaws, "Each inspector, before entering upon the discharge of his duties, shall take and sign an oath to faithfully execute the duties of inspector with strict impartiality and according to the best of his ability." This will require a firm time commitment from any volunteers, as they will need to be available at a number
 of points through the process to fulfill their duties in a timely manner. If you are interested in being an inspector, let me know.
> 
> Any complaints or concerns about the election process are taken extremely seriously. Each complaint will be reviewed by our independent counsel and addressed or brought before the full Board at its first meeting as appropriate. To facilitate reporting we have created an email address that is received only by the Foundation's independent counsel for review: electionmonitor at openstack.org
> 
> We are also working on process improvements for nominations and elections--more details on that coming soon. In the meantime, please speak up or contact me or Mark Radcliffe directly if you have any concerns. We have all come a very long way in establishing the OpenStack Foundation--our Foundation--and are right on the threshold of having it up and running. Now is the time for us all to pull together and to make sure we continue to build the kind of inclusive, supportive community that has come so far in the last 2 years.
> 
> Thanks,
> 
> Jonathan
> 210-317-2438
> 
> 
> _______________________________________________
> Foundation mailing list
> Foundation at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/foundation/attachments/20120729/82390625/attachment.pgp>