Re: [Openstack-poc] [OpenStack Foundation] Technical Committee: reserved seats for PTLs (or not)

2012-06-22 Thread Joe Heck
On Jun 22, 2012, at 11:53 AM, Justin Santa Barbara wrote: > In my mind, the PTL is responsible for moving their individual OpenStack > sub-project forward. The technical committee is responsible for OpenStack as > a whole, and making sure that the individual projects are advancing OpenStack >

Re: [Openstack-poc] [OpenStack Foundation] Technical Committee: reserved seats for PTLs (or not)

2012-06-22 Thread Joe Heck
On Jun 20, 2012, at 3:18 AM, Thierry Carrez wrote: > The current PPB had a discussion yesterday on the bylaws for the > Foundation Technical Committee ("TC"), mainly around whether PTLs should > get reserved seats on the TC. > > I would like to summarize the options and extend the discussion to th

Re: [Openstack-poc] Thoughts on client library releasing

2012-06-18 Thread Joe Heck
Monty - Thierry stated it as an assumption last PPB meeting, but I'd like it to be explicit that we have at least a tag on each client library release that we make so that it's possible to distribute a version of the clients. -joe On Jun 18, 2012, at 2:11 PM, Monty Taylor wrote: > We're tryi

Re: [Openstack-poc] openstack-common bug spam

2012-05-08 Thread Joe Heck
None from me. On May 8, 2012, at 7:07 AM, Mark McLoughlin wrote: > Hey, > > I see this list gets a bunch of bug spam because the POC team is listed > as a driver for the openstack-common library: > > https://launchpad.net/~openstack-common-drivers/+members#active > > The doesn't make much sen

Re: [Openstack-poc] 3rd Party APIs

2012-05-07 Thread Joe Heck
On May 7, 2012, at 7:45 AM, Thierry Carrez wrote: >> "COMMUNITY" >> >> >> Everything else - additional APIs that map to the OpenStack kernel, >> proprietary plugins that provide services or functionality to core pieces >> (like Keystone and Quantum plugins, Volume drivers) actually

Re: [Openstack-poc] 3rd Party APIs

2012-05-06 Thread Joe Heck
The reason I said "c" and not "b" is because there may be something in the future that we see that really, really needs to belong in the kernel of an OpenStack system. By choosing "B", categorically it seemed like an assertion that none of these 3rd party APIs (or plugins or whatever) could *e

Re: [Openstack-poc] 3rd Party APIs

2012-05-05 Thread Joe Heck
Back the original - I like the idea of Vish's option "C" - but that's assuming a lot around what we mean about being "core". We're complicating this discussion every time someone uses the word "official", either trying to inject a new "middle state" of something that's not core, but that has so

Re: [Openstack-poc] Meeting tomorrow

2012-04-09 Thread Joe Heck
Either On Apr 9, 2012, at 10:30 AM, Jonathan Bryce wrote: > We have 2 requests to use openstack.org for community-related technical > projects: one for satellite projects and one as the package name for a java > library. Would you all prefer to discuss tomorrow at 3:00 PM CDT/20:00 UTC or > ov