20:07:23 <jmckenty> #startmeeting
20:07:24 <openstack> Meeting started Tue Feb 28 20:07:23 2012 UTC.  The chair is jmckenty. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:07:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic.
20:07:28 <devcamcar_> yep
20:07:56 <jmckenty> #topic GlobalBugSquash Day
20:08:06 <jmckenty> That was the topic, right?
20:08:31 <vijayendra> yes
20:08:53 <notmyname> from ewan "Is this something that the PPB could / should co-ordinate? "
20:09:12 <jmckenty> Is lauren ever on IRC?
20:09:38 <pvo> I feel this is almost project specific
20:09:40 <devcamcar_> yea not sure what ppb has to do with it?
20:09:42 <ttx> The people organizing it should coordinate it. Not sure what we can bring in
20:09:52 <jmckenty> Fair enough.
20:09:55 <ttx> except saying "You shalt use a wiki page"
20:10:14 <jmckenty> I'll make sure Lloyd updates things on that wiki page
20:10:25 <jmckenty> Anyone else on that topic?
20:10:26 <ttx> We can definitely spread the word, personally.
20:10:59 <notmyname> is it a "pre-inherited" function of the ppb since the foundation says it's going to be responsible for promoting projects?
20:11:18 <jmckenty> Well, the best promotion mechanisms we have are
20:11:25 <jmckenty> the meetup sites, the openstack blog
20:11:32 <jmckenty> and maybe the planet?
20:11:47 <jmckenty> who's got the knobs on the @openstack account - stefano?
20:11:51 <ttx> is there a link to the event somewhere we could tweet about ?
20:12:01 <jmckenty> Just tweet the meetup link
20:12:16 <jmckenty> http://www.meetup.com/openstack/events/52682572/
20:12:22 <mtaylor> notmyname: ++
20:12:34 <jmckenty> or http://www.meetup.com/openstack/events/52682022/
20:13:02 <jmckenty> notmyname: okay, so the PPB can direct Stefano to write something on the blog and tweet it?
20:13:20 * jmckenty thinks that notmyname just volunteered to write something
20:13:30 <jk0> sorry I'm late, out sick today
20:13:32 <jmckenty> #link http://www.meetup.com/openstack/events/52682022/
20:13:35 <ttx> notmyname: the foundation says the PPB/TC will be responsible for promoting projects and promoting events ?
20:13:39 <jmckenty> #link http://www.meetup.com/openstack/events/52682572/
20:13:44 <notmyname> I'm just asking :-) we could do anything from announcing it to actually corrdinating it
20:13:46 * mtaylor likes voting to make Stefano do things - likes voting to make notmyname do things even more
20:14:22 <ttx> My understanding is taht the foundation will be, not the PPB2/TC
20:14:29 <jmckenty> #idea notmyname to direct Stefano to blog and tweet about GlobalHackDay
20:14:39 <ttx> reed: ^
20:14:48 <ttx> reed==Stefano
20:14:55 <jmckenty> ah, thanks
20:15:01 <reed> jmckenty, Lloyd has an account there too
20:15:09 <jmckenty> Handy
20:15:23 <notmyname> reed: can you write something about a global hack day? if you have questions, ask jmckenty
20:15:27 <notmyname> jmckenty: done :-)
20:15:30 <jmckenty> :)
20:15:33 <jmckenty> next topic?
20:15:41 <vijayendra> #link http://www.meetup.com/openstack/events/52682572/
20:15:41 <jmckenty> ProjectTestingInterface
20:15:46 <jmckenty> #topic http://wiki.openstack.org/ProjectTestingInterface
20:15:49 <jmckenty> #link http://wiki.openstack.org/ProjectTestingInterface
20:16:05 <reed> #info anybody can request an account on the blog and post there
20:16:06 <jmckenty> mtaylor: you want to walk us through this?
20:16:20 <mtaylor> main thing here is, I've been doing things to get our explosive number of projects aligned on some basic things so that we can template all of that in jenkins better
20:16:58 <mtaylor> and mainly just wanted to put the overall plan in front of folks so that they could hit it with sticks
20:17:06 <mtaylor> it breaks down like this:
20:17:44 <mtaylor> we want to, on every project, do a set of things: run tests, check pep8, generate testing coverage, generate source tarballs, generate docs and import translation strings
20:18:09 <mtaylor> we don't do all of those things on all of the projects yet, translations being the big one where infrastructure was way behind
20:18:48 <mtaylor> the patches I've been pushing have been making sure that for each of those things we want done, the command line interface for it in a clean repo is the same
20:19:02 <jmckenty> mtaylor: would this be a decent place to also deal with .mailmap ?
20:19:12 <mtaylor> yes. I think so
20:19:28 <jmckenty> e.g., since we're testing for Authors file validity, I'd like to be able to resolve multiple email addresses
20:19:34 <mtaylor> I've got some text down further on the page which talks about Authors and Changelog files ... I should highlight that a bit more I think
20:19:38 <jmckenty> yeah
20:19:50 <zns> mtaylor: Do you have a template project that can be used as a reference for existing projects or starting point for new projects?
20:20:00 <jmckenty> Does babel have lazy consensus?
20:20:13 <jmckenty> e.g., is that in use across a few of these projects already?
20:20:25 <jmckenty> or just nova
20:20:28 <mtaylor> zns: almost
20:20:45 <mtaylor> jmckenty: swift also had babel support in tree
20:20:52 <jmckenty> ah, cool
20:20:53 <mtaylor> and I just sent glance a patch to start using it
20:21:02 * notmyname would like to change some of the overloaded uses for the authors file, but that's probably not a discussion for this meeting
20:21:39 <mtaylor> also, even more exciting, I think with the new babel code we might actually start installing and consuming our translated messages (this was not actually happening before)
20:21:48 <jmckenty> So is there any explicit relationship between this proposal and devstack?
20:22:14 <mtaylor> not really - although once we get it in, it might make some of the devstack tasks easier? not sure
20:22:30 <jmckenty> I'd also like to see a fix to capitalization of Authors files
20:22:36 <jmckenty> AUTHORS vs authors vs Authors
20:22:45 <anotherjesse> mtaylor: ya, devstack replicates some stuff in projects because each one was doing stuff different
20:22:55 <jk0> jmckenty: +1
20:22:55 <mtaylor> if there are ways in which project consistency like this would help devstack, I'd be happy to put those on my todo list
20:23:07 <mtaylor> jmckenty: +1
20:23:12 <jaypipes> ++
20:23:20 <mtaylor> shall we do Authors ?
20:23:28 <jaypipes> low priority, but yes IMHO
20:23:31 <devcamcar_> AUTHORS
20:23:37 <notmyname> AUTHORS
20:23:38 <jmckenty> devcamcar: ++
20:23:42 <mtaylor> ++
20:23:51 <devcamcar_> match readme and other supplemental files
20:23:59 <pvo> ++
20:24:00 <jmckenty> LICENSE as well, yes?
20:24:02 <notmyname> but my concerns are bigger than what it's called :-)
20:24:09 <devcamcar_> yep
20:24:19 <mtaylor> notmyname: well yes. but capitalizing it is a start :)
20:24:23 <devcamcar_> yea needs housekeeping
20:25:04 <jmckenty> So any strong objections to mtaylor 's proposal?
20:25:31 <jmckenty> vishy: did you have a look around for babel alternatives? I just don't want to have to argue it later
20:25:34 <anotherjesse> we've had a lot of progress with common config with people just proposing stuff
20:25:39 <anotherjesse> as in merge proposals
20:25:44 <zns> I love how the tools folder just automagically gets updated in sync with other projects. I wouldn't mind more scaffolding like that to meet this goal...
20:26:03 <anotherjesse> so - mtaylor I proposing the projects things like authors will actually get things done :)
20:26:23 <mtaylor> yup. it's on my todo list now
20:26:43 <jmckenty> Does this need a vote? I think it rocks.
20:26:50 <heckj> mtaylor: do you have a link for babel? Not familiar with it...
20:27:00 <mtaylor> jmckenty: the only other thing I found for babel that had setuptools integration was distutilsextra, which broke other things
20:27:10 <mtaylor> heckj: http://babel.edgewall.org/
20:27:13 <mtaylor> #link http://babel.edgewall.org/
20:27:24 <jmckenty> anyone for voting?...
20:27:31 <mtaylor> lemme say q quick word about babel ...
20:27:34 <heckj> mtaylor: thanks!
20:27:34 <mtaylor> just so there isn't confusion
20:27:52 <mtaylor> it's essentially just for manageing the translation strings and merging - it's still built on top of gettext
20:28:08 <ttx> (and LP Translations)
20:28:11 <mtaylor> and the translations themselves are still sent to launchpad and imported from (although I do have jenkins jobs now to do that bit)
20:28:36 <mtaylor> so, for the most part, almost no-one should really ever have to know much about it, unless something goes horribly wrong :)
20:28:51 <jmckenty> So there's no additional steps for localizers?
20:28:58 <mtaylor> I'm also copying the way we're using it from Sphinx, who use it for their in-code translations
20:29:02 <mtaylor> jmckenty: shouldn't be
20:29:08 <jmckenty> cool.
20:29:22 <jmckenty> Last call for additional comments about ProjectTestingInterface?
20:29:38 <jmckenty> ...
20:29:49 <jmckenty> #topic Satellite CI Environment
20:30:06 <mtaylor> I'm verbose today
20:30:23 <jmckenty> rock it
20:30:24 <jaypipes> $> monty-talk -vvv
20:30:41 <mtaylor> quick story here is - we're spinning up a second copy of the OpenStack CI infrastructure that we'd like to offer to satellite projects should they wish to use it
20:31:01 <devcamcar_> awesome
20:31:03 <jmckenty> Define a satellite project?
20:31:04 <mtaylor> essentially a place for folks to stick anything openstack related should they wish to follow a similar process to openstack
20:31:08 <jmckenty> clients?
20:31:17 <jmckenty> PaaS projects?
20:31:19 <ttx> mtaylor: would anything half-official move from the current Ci setup to that satellite setup ?
20:31:22 <mtaylor> jmckenty: anything that wouldn't be a core or incubation candidate
20:31:28 <jaypipes> Toaster as a Service.
20:31:37 <mtaylor> ttx: I think once it's baked, we should probably consider that, yes
20:31:52 <jmckenty> mtaylor: that seems like the main reason to do it
20:31:59 <jmckenty> How much gear do you have?
20:32:08 <mtaylor> jmckenty: I've got a whole free cloud :)
20:32:11 <jmckenty> Will we need a merit-based application process?
20:32:14 <jmckenty> nice!
20:32:36 <jmckenty> Seems like a darn good idea.
20:32:37 <mtaylor> actually- one of the goals is that adding a project to the system can be done via submitting a merge request to gerrit
20:32:37 <jmckenty> Timeline?
20:32:49 <mtaylor> system should be up and going in the next couple of days
20:33:04 <mtaylor> gerrit-based new projects may take a few more weeks (we'll have to write some more puppet magic)
20:33:04 <jmckenty> awesome
20:33:12 <jmckenty> notmyname: can get reed to write up something
20:33:14 <mtaylor> and I think reddwarf is going to hop on board
20:33:22 <ttx> mtaylor: did anyone work on a project directory / forge setup like was discussed at the Essex design summit ?
20:33:38 <mtaylor> ttx: not to my knowledge
20:33:49 <reed> ttx, it's a long story
20:33:49 <jmckenty> I've gotta drop offline (arg)
20:34:01 <jmckenty> mtaylor: this rocks, anything to decide?
20:34:10 <ttx> jmckenty: don't forget to #endmeeting at some point
20:34:16 <ttx> (only you can)
20:34:17 <mtaylor> jmckenty: basically, I've got some legal folks who would like the ppb to say they think its neat
20:34:19 <mrmartin> ttx: i plan to work on a project dir
20:34:39 <mtaylor> jmckenty: so if people don't mind voting to let me donate some stuff, that would be swell
20:34:41 <reed> ttx, I did, jay did too and Chris Bohannon too... no visible results though
20:35:02 <reed> mrmartin, great, please keep me in the loop
20:35:20 <ttx> I think we need to nail the reputation / catalog thing before we open the satellite gerrit too wide
20:35:24 <mtaylor> mrmartin, reed, ttx: I'll also ask and see if I can get some resources allocated to that
20:35:33 <mtaylor> ttx: the catalog part
20:37:47 <ttx> jmckenty: still around ?
20:37:58 <jmckenty> yup
20:38:07 <pvo> gotta end the meeting, if we're done
20:38:27 <notmyname> do we need to "officiall" help mtaylor?
20:38:30 <jmckenty> #endmeeting