Hi josh, just read the blog post you referenced. I now understand why you and I have had (and continue to have) "interesting" discussions, as we view the world through different prisms. Diversity of opinion and the ability to rationally discuss is what will make the OpenStack community stronger J.
Regarding Scalr. this submission brings into focus some issues that we have not addressed to date regarding project submission. With an existing open source project I think the diligence needs to be more than language, test coverage, and CI approach (although these are critical elements to consider). I also believe we need to understand the dynamic of the existing proposed project, as this will be a merge of an existing community into the OpenStack community and ecosystem. How is the project managed, what is the governance, how active are outside community members, how "compatible" is the project with existing/planned OpenStack processes, etc. this is why I think it is essential that the project advocate attend the PPB meeting when the project is being evaluated. I believe that test coverage, CI, QA integration, etc. are some of the focus areas as a project becomes "incubated" from "related". If the project is willing to adopt the "OpenStack Way" tm part of the definition of being incubated is that the OpenStack resources (release management, packaging, tooling/build and qa automation) are available to help recast the project. It is much easier to have a project adopt new conventions and workflow than it is to fix a "bad" or non-existent open source community. The Scalr submission also raises another meta-OpenStack project question: at this particular point in time what do we consider the "envelope" of OpenStack, in terms of project focus'? The core projects to date are all classic IaaS, is the timing right to introduce PaaS elements into the mix? I believe that some of the "related" projects (such as RedDwarf, Donabe, Atlas, etc.) can be considered either PaaS offerings or PaaS-elements. As the projects mature and some of them apply to be "incubated" we should have an agreed to position as to what is within the OpenStack charter and what is clearly not. John From: Joshua McKenty [mailto:[email protected]] Sent: Tuesday, June 14, 2011 5:08 AM To: Jay Pipes Cc: John Purrier; [email protected] Subject: Re: [Openstack-poc] Meeting tomorrow I won't be able to make the POC meeting today (I'm on a plane, unfortunately), but I wanted to weigh in with my thoughts on the two projects proposed for incubation. I blogged briefly about it here: http://www.cognition.ca/2011/06/what-it-means-to-be-openstack.html Which, as you can imagine, is a +1 for dashboard and a -1 for Scalr as a whole. (With all apologies to Sebastian). I'm happy to consider the Scalr guest agent (in python) as a standalone submission, but I think we'd need to see test coverage and CI environments first. Would love to weigh in on django arguments if they come up, maybe Jesse can circulate the NASA Trade Study I wrote on the subject. Thanks all. Joshua McKenty Piston Cloud Computing, Inc. (650) 283-6846 [email protected] On 2011-06-13, at 7:19 PM, Jay Pipes wrote: On Mon, Jun 13, 2011 at 2:09 PM, John Purrier <[email protected]> wrote: Jay, what is your concern with PHP? Mainly that the rest of OpenStack projects are written in Python. Hey, I used to program in PHP; I don't have anything against the language in particular. But if all the other projects in OpenStack are Python, it's a bit difficult for me to welcome a PHP project as a core project or even incubated... Just my 2 cents, jay _______________________________________________ Mailing list: https://launchpad.net/~openstack-poc Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack-poc Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
