20:01:02 #startmeeting 20:01:03 Meeting started Thu Mar 10 20:01:02 2011 UTC. The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:01:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 20:01:32 hello! who all is here? 20:01:36 hi 20:02:07 what's the date for the next election? 20:02:16 o/ 20:02:16 http://wiki.openstack.org/Governance/PPB - agenda is on this page 20:02:35 and is the PPB member list up to date? 20:03:03 http://www.openstack.org/blog/2011/03/openstack-governance-nominations-and-election-process/ - march 21st 20:03:11 joshuamckenty: This will be my last meeting 20:03:20 gotcha 20:03:37 and there are no TPL members yet, right? 20:03:42 (Technical Project Lead) 20:04:02 joshuamckenty: correct 20:04:59 #idea can we suggest new projects post a manifesto similar to the redis manifesto? 20:05:08 #link http://antirez.com/post/redis-manifesto.html 20:05:28 As an extension of item #3.4 20:06:37 and point 2 needs to be specific. What does gather community feedback mean? 20:07:24 good q 20:07:33 i'm thinking along the lines of what eday has been doing with burrow 20:08:10 alsoin 3.4, the use of 'enhance value' does not sound right. 20:08:43 We need a time span for how often (if at all) a project can resubmit for inclusion 20:09:14 do you think the eday type mailing list/wiki process for community feedback works? 20:09:20 joshuamckenty: good point. any suggestions? 20:09:23 yes 20:09:24 6 months? 20:09:26 6 months? 20:09:26 yeah 20:09:41 perhaps 3 months instead? 20:09:46 also for migration from incubation, I would suggest we review those at the design summits 20:09:50 perhaps once per release 20:10:37 well, release cycle is per project as well 20:10:56 PPB review should be consistent, I think once every 3 months is reasonable / generous 20:11:01 ok 20:11:06 joshuamckenty: I like the idea that it is presented at summits 20:11:28 so a project that is not accepted must wait 3 months before resubmission 20:11:57 jbryce: seems reasonable - since not being accepted just means it isn't part of core - it can still integrate deeply 20:11:57 projects in incubation will be reviewed at design summits 20:12:12 should all projects be reviewed at design summits? 20:12:24 I think that's a PPB scheduling question 20:12:28 reviewed by whom? 20:12:42 seems like a good time, but I don't want to turn it into a giant roundtable, it'll become a popularity debate 20:13:21 PPB review, step 4 20:13:28 This should not require RW meetings IMHO 20:14:20 Is there a process for a project to *leave* OpenStack? 20:14:23 Just a weird question 20:14:52 I think that would be by forking it 20:15:17 Well, it still remains in OpenStack as well, technically, at that point. 20:15:30 the name does at least 20:15:37 that is the real question 20:15:54 do we own the name of an existing project after they join 20:15:57 Yeah, that's not covered by this process 20:16:23 The name is owned (by default) by the project founders, correct? Unless someone files trademark 20:16:30 e.g., who own's 'nova'? 20:16:45 I think it is an important question 20:16:57 I know who owns @novacc and novacc.com, and it's not OpenStack 20:17:00 proposals? 20:17:03 joshuamckenty: that is me 20:17:05 ;) 20:17:46 Also it is called OpenStack Compute from the project perspective 20:17:47 I think we need a process for a project to leave and take its name with it. 20:18:00 I still have @novacc passwords, buddy ;) 20:18:12 perhaps we talk about naming separately? 20:18:16 Well, I think maybe the OpenStack name for the project should be distinct 20:18:24 k, separate agenda item? 20:18:28 ya, burrow might become openstack queue if accepted 20:18:32 yes 20:18:49 #todo start discussion around naming and transitions out of openstack for projects 20:19:20 jbyrce, is there a charter doc that would need to be signed by the project 20:19:30 e.g., like the code of conduct doc for members 20:19:52 there is not...that's one of the things i was thinking about as i was putting together the process 20:20:16 we know how we are running nova/swift/compute but we haven't actually codified it anywhere as a coherent set of openstack development processes 20:20:47 there was the original HACKING.txt file 20:21:16 which things are required, which are optional - launchpad, bzr, jenkins, release cycles - those kinds of things 20:21:18 I think we can codify that as we go, minimum PEP8 numbers, minimum test coverage, etc. 20:21:44 the other question that was raised is how does a project split into 2, like pulling volumes and networking out of nova 20:22:24 same criteria applies, right - size of dev team, available technical lead, etc. 20:22:41 Probably a vote from the existing core team on the split? 20:22:48 i made updates to the wiki to try to address the points you all raised (except anything about the design summit) 20:23:12 who initiates? 20:23:30 the existing core team votes to split and the ppb ratifies? 20:23:51 if a project splits, is there an election for PTL? does this add a seat to the PPB? 20:24:08 if it becomes a full project, it would add a seat to the ppb 20:24:35 I think core team votes, and PPB ratifies, yes 20:24:48 And probably the old core team votes for PTL of new project? 20:25:01 oh, and initial core team should be seeded 20:25:05 from previous core team 20:25:29 agree with Josh 20:25:31 maybe just a free pass for those core team members who want to sign on to the new project? 20:26:15 makes sense to me 20:26:51 Anything else on this proposal? 20:26:53 #todo document proposed mechanism for splitting existing project into new projects 20:26:59 Or should we +1 it? 20:27:34 i don't want to vote on it with the majority missing... 20:27:42 i'll send it out for a mailing list vote after the meeting 20:27:53 ah, right 20:28:24 did all of you agree with ewan's thoughts on the standards body? 20:28:40 that it should basically be company specific with no official openstack community sanction? 20:28:45 yeah, with the exception of the OCC 20:29:00 yeah, kinda like how we can talk about what we want to do for nasa, but we can't talk on behalf of nasa 20:29:07 just because they have an awesome testbed of hardware that I think we should use as a community resource for CI 20:29:49 well, we could still do the same thing with OCC 20:30:01 but have a more involvement with multiple parties 20:30:09 whether it be rackspace or citrix or ... 20:30:33 i agree with anotherjesse 20:30:43 as long as the CI environment ends up available with incubated projects, I'm happy with that 20:30:50 ok 20:31:03 /s/with/for/ 20:31:20 ;) 20:31:24 those were the two things i wanted to hit on 20:31:35 do you all have anything else you want to discuss? 20:31:58 election process 20:32:05 jbryce: we might want to link to the project page from the official site 20:32:09 even if just the wiki page 20:32:15 definitely 20:32:19 just want to make sure the announcement of the election results is smoother than last time 20:32:34 it's going to be heavily covered by media, I don't want any more FUD 20:32:42 and that the results are immediately available 20:32:51 yeah, that was the part I was pointing out 20:32:59 yep 20:33:11 i'm pretty sure everyone is on board with that 20:33:32 are you coordinating the election? 20:33:42 stephen spector is, but i've talked to him about it 20:33:49 can you be available on IRC during that process, so there's a single POC for the PPB? 20:33:55 ttx is telling SS how to do it correctly 20:34:15 * joshuamckenty doesn't understand ttx or SS 20:34:18 oh, nm 20:34:26 stephen spector and thierry 20:34:34 dendrobates: not sure they actually have that down yet 20:34:34 :) sorry 20:34:51 civs needs email addresses and most launchpad people don't have their email addresses available 20:35:04 i know that's one thing they're still trying to work through 20:35:09 jbryce: a last count on which seats are up for election? 20:35:13 that was the number one problem last time around too 20:35:36 2 general seats (chuck's seat is up for election + 1 new seat) as well as 1 PTL seat each for nova, swift and glance 20:37:18 dendrobates: any ideas on how to get the right contact info for the elections? 20:37:39 jbryce: we should talk to the launchpad team 20:37:55 ubuntu uses the same site and manages somehow 20:38:09 ttx can talk to them for you 20:38:25 ok 20:38:36 k, I'm good 20:38:59 anything else from anyone? 20:38:59 * soren wanders in 20:39:04 Sorry I'm late. :( 20:39:05 gotta bounce, thanks jbryce 20:39:45 bye all 20:39:52 hi soren! we didn't vote on anything but we did discuss quite a bit 20:40:04 I'll read the scroll back. 20:40:13 Oh, well. 20:40:14 :( 20:40:16 bye rick 20:40:27 #endmeeting