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 <[email protected]>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 >
