Sam, I personally would want to keep Rackspace Cloud Builders out until they show a commitment to openness. This is not a judgment of Scott Sanchez, but of his management, who I feel could try to unduly influence the OCI.
I am fine with Nick. I will be at the OWF as well, see you there. Rick On 08/24/2011 04:07 AM, Sam Johnston wrote: > Another point is that Nicolas Barcet <http://nicolas.barcet.com/drupal/> had > previously offered to join the board and serve as a representative in France > and reaffirmed his commitment recently. Assuming the majority of the board > agrees, I'd like to have him appointed in time for Open World > Forum<http://www.openworldforum.org/>in Paris, where I plan to speak > about OCI. > > Scott Sanchez <http://www.linkedin.com/in/scottcsanchez> also expressed an > interest in helping with business involvement, and while I initially thought > it best to steer clear of the commercial side of things (ala the OSI), I > don't think we're going to get far without vendor & buyer support. We want > vendors advertising Open Cloud certification and we want buyers asking for > it in RFIs etc. > > That would take us to 12 (of a maximum 21) — I'd envisaged having 13 or 15 > directors so as to have a stable base and avoid deadlocks so is there anyone > I've missed? Someone from government (e.g. Deb Bryant) and/or education > (e.g. ?) would make a lot of sense I think. > > Sam > +41 78 871 6868 > > On Mon, Aug 22, 2011 at 10:15 PM, Sam Johnston < > sam.johns...@opencloudinitiative.org> wrote: > >> You know I've been thinking about exactly the same issue myself and while >> I'd love to use Atlassian Jira <http://www.atlassian.com/software/jira/>to >> track all these issues (and respond to them in a timely fashion) ala the >> Apache >> Foundation <https://issues.apache.org/jira/secure/Dashboard.jspa>, I >> wonder if it's "open cloud"... especially having migrated from Google Apps >> (Sites) to Drupal — which, while not necessarily "open cloud", is at least >> "open source". >> >> On the specific roles, I see us all as evangelists. Certain roles are >> required by california law but I see us all as peers and representatives of >> the community. As the OCI shouldn't take a position that's not been ratified >> by the community (e.g. the OCP) I don't see a problem with us all expressing >> our personal opinions on the subject, which are, for the most part at least, >> well aligned. >> >> I have to duck off for dinner but let's definitely get the discussion going >> — thanks for taking the initiative Sam. >> >> Sam >> >> On Mon, Aug 22, 2011 at 8:36 PM, Evan Prodromou >> <evan.prodro...@gmail.com>wrote: >> >>> Sam, >>> >>> I totally agree. There's an old saw that the function of a committee is to >>> make subcommittees, but it might actually be useful for us to start dividing >>> up roles for one or more people to attack. >>> >>> Some roles I think that matter: >>> >>> - *Press relations* -- deal with reporters, get the story out >>> - *Certification* -- develop a timeline for certifying compliance with >>> principles (for badge use) >>> - *Website* -- Continue to develop and improve the OCI web site (and >>> blog!) >>> - *Community* -- Set up and manage community resources (mailing lists, >>> bug tracker, others?) >>> >>> Just some off the top of my head. >>> >>> -Evan >>> >> >> >
signature.asc
Description: OpenPGP digital signature
