21:01:01 <ttx> #startmeeting project
21:01:01 <openstack> Meeting started Tue Oct  7 21:01:01 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:05 <openstack> The meeting name has been set to 'project'
21:01:05 <dolphm> o/
21:01:08 <ttx> Our agenda for today:
21:01:12 <ttx> #link http://wiki.openstack.org/Meetings/ProjectMeeting
21:01:17 <ttx> 9 days to final release
21:01:24 <ttx> #topic News from the 1:1 sync points
21:01:26 <mikal> Hi
21:01:30 <ttx> Here is the log(s):
21:01:35 <ttx> #link http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-10-07-08.28.html
21:01:50 <ttx> All projects published their RC1 last week or over the weekend, Sahara just respinned RC2
21:01:58 <ttx> Keystone, Glance, Nova, Cinder and Ceilometer have an RC2 window opened now
21:02:11 <ttx> #topic Other program news
21:02:17 <ttx> Any other program with a quick announcement ?
21:02:19 <mestery> ttx: Neutron as well?
21:02:25 <mestery> Or we're talking tomorrow, I forget.
21:02:42 <ttx> mestery: we haven't opened an RC2 window yet.
21:02:46 <ttx> tomorrow :)
21:02:50 <mestery> ttx: Ack
21:02:51 <mestery> :)
21:03:35 <ttx> ok, let's move on to other topics, if someone has announcements, can shout in the middle
21:03:40 <ttx> #topic Refreshing translations on proposed/juno
21:03:51 <ttx> Translations should generally be refreshed if/when we respin a RC, so that we release relatively-fresh ones
21:04:03 <ttx> But the trick is we can't just backport translations from master, as they may or may not apply to proposed/juno
21:04:12 <ttx> So to generate the change we need to run the commands specified at:
21:04:17 <ttx> https://review.openstack.org/#/c/126569/
21:04:23 <ttx> dolphm: do you have them in some runnable script ?
21:04:37 <ttx> dolphm: and do you confirm those commands are the right ones ?
21:05:50 <ttx> dolphm: and do you actually need a transifex account to run them?
21:05:51 <dolphm> ttx: i do not, beyond what's in the commit message above
21:06:04 <dolphm> ttx: and no, it turns out you don't need an account for the subset of the commands pasted there
21:06:12 <dolphm> it only depends on the local codebase
21:06:42 <ttx> eglynn: maybe try to reproduce those commands and post a change for ceilometer ?
21:06:55 <eglynn> ttx: sure thing, will do
21:06:58 <dolphm> eglynn: ping me if you need a hand
21:07:03 <eglynn> dolphm: thanks
21:07:05 <dolphm> applies to anyone else as well ^
21:07:27 <mikal> I assume you want us all to give that a try if we have a rc2
21:07:29 <ttx> if you have an RC2 warning up, and you're getting close to publishing ity, we'll push such a change
21:07:36 <ttx> mikal: yes
21:07:39 <dolphm> AJaeger is in #openstack-infra and can surely help as well
21:07:47 <ttx> so if you have questions about it, ask them now
21:08:00 <ttx> mikal: but we shouldn't push the change too early
21:08:05 <ttx> the later, the fresher
21:08:16 <mikal> ttx: so noted
21:08:42 <ttx> also all RC1s had relatively fresh translations anyway, so if a project just promotes RC1 to release, that's fine too
21:08:52 <ttx> any question on that ?
21:09:07 <dolphm> just ensure you're on the proposed/juno branch when you're running the above, else you're just competing with openstack proposal bot
21:09:19 <ttx> and HE ALWAYS WINS
21:09:20 <dolphm> and not really helping rc2 :)
21:09:49 <ttx> ok, if no question, then next topic
21:09:54 <ttx> #topic taskflow>=0.5.0 juno requirements bump ? or not ?
21:10:02 <ttx> Taskflow was updated recently to 0.5.0 with several bugfixes
21:10:11 <ttx> That makes me wonder if we should bump requirements to >=0.5.0 in master and in proposed/juno
21:10:13 <jgriffith> ttx: my vote is no
21:10:18 <ttx> Cinder is the only project consuming it
21:10:30 <jgriffith> ttx: looks like that bug is specific to six.moves and multiple threads
21:10:37 <ttx> so your conservative vote prevails
21:11:18 <ttx> jgriffith: I'm fine with not bumping, as this could put distros in some painful situation
21:11:23 <ttx> and in theory we freezed
21:11:28 <jgriffith> ttx: sounds good
21:11:36 <jgriffith> ttx: I'm pretty much convinced we're safe here
21:11:37 <ttx> harlowja_: does that make sense ?
21:11:57 * harlowja_ reading
21:12:16 <harlowja_> i think we are ok, eventlet is saving us on that one i think (for better or worse)
21:12:25 <ttx> harlowja_: hah, :)
21:12:27 <harlowja_> anyone using real threads + six.moves will likely sometimes see weird stuff
21:12:34 <ttx> alright then.
21:12:47 <ttx> harlowja_: we don't prevent anyone from running 0.5.0 fwiw
21:12:58 <ttx> it's just that we don't force those on 0.4.0 to update
21:13:15 <harlowja_> ya
21:13:18 <ttx> #topic Cross-project workshops at the Design Summit
21:13:31 <ttx> Like in ATL, the first day of Design Summit (Tuesday) will be dedicated to cross-project workshops
21:13:36 <harlowja_> totally fair, dimsum_ compiled http://paste.openstack.org/show/119087/ (which shows other areas in openstack that use six.moves), hopefully the patch to six will get accepted to avoid all these potential issues
21:13:38 <ttx> (in addition to incubated projects and a few other things)
21:13:45 <ttx> Current plan is to have two or three running at the same time
21:13:55 <ttx> for a total of 18 40-min slots, like this:
21:14:00 <ttx> http://kilodesignsummit.sched.org/type/cross-project+workshops
21:14:08 * nikhil_k joins in
21:14:09 <ttx> Suggestions are open at:
21:14:13 * dhellmann apologizes for being late
21:14:15 <ttx> https://etherpad.openstack.org/p/kilo-crossproject-summit-topics
21:14:24 <ttx> Some topics will obviously use 2 slots
21:14:52 <ttx> Some people wanted to have only 2 running in parallel, some others wanted to keep as much space as we had in ATL
21:14:58 <ttx> so this is a middle ground :)
21:15:45 <ttx> We'll get people from the newly-elected TC to work on building the schedule there
21:16:01 <ttx> but if it's like in ATL, it should be pretty consensual
21:16:02 <annegentle> ttx: I do want docs topics in there since we don't have another slot
21:16:08 <ttx> annegentle: indeed
21:16:13 <ttx> annegentle: file away
21:16:29 <annegentle> ttx: just put one on scaling in the etherpad
21:16:37 <ttx> Questions on that topic ?
21:17:18 <annegentle> can you explain pods more (after you're done with cross project topic?)
21:17:35 <ttx> Note that as far as scheduling goes, we'll use an ODSREG instance like we use to, but will just edit the content of the sessions once they are picked, rather than use it for CFP
21:17:40 <mestery> annegentle: +1 to more info on pods
21:17:48 <ttx> so it will be used by PTLs or their monkey only
21:17:56 <ttx> OK, pods.
21:18:06 <ttx> So we'll have a number of tables. They may be square this time
21:18:08 <eglynn> ODSREG?
21:18:16 <ttx> in two spaces, slightly separate from the dev loungs
21:18:20 * mestery liked circle tables. :)
21:18:29 <ttx> eglynn: the software atht was running on summit.o.o before
21:18:35 <ttx> openstack-infra/odsreg
21:18:40 <eglynn> ttx: -ha, got it
21:19:02 <ttx> mestery: but we reuse some of those tables to build the "meetups" space on Friday :)
21:19:16 <mikal> And some teams have a meetup day right?
21:19:21 <mikal> So are probably not as interested in pods?
21:19:36 <ttx> some programs will have dedicated pods (incubated, docs, oslo)
21:19:44 <ttx> since they don't have a meetup
21:19:51 <ttx> everyone else shares a number of tables
21:20:03 <ttx> we'll have signs, so wyou can claim an empty space as yours
21:20:11 <ttx> and people should be able to find you
21:20:37 <ttx> obviously if people are just using the table to work on something else, we might have to ask them to move
21:21:00 <annegentle> ttx: yup, ok
21:21:12 <ttx> there should be something like one pod for two programs
21:21:14 * annegentle is glad we're not the only ones without a meetup day
21:21:21 <ttx> + all the dedicated ones.
21:22:02 <ttx> annegentle: you can consider your pod as a always(running meetup :)
21:22:19 <ttx> Other questions on that ?
21:22:22 * dimsum_ peeks
21:22:27 <annegentle> ayup ttx :)
21:22:31 <dhellmann> how far away are the pods from everything else this time?
21:22:46 <ttx> pods are very close to the session rooms
21:22:53 <ttx> so may be less clam
21:22:55 <ttx> calm*
21:23:10 <dhellmann> that should be ok, I think we'll use them more for oslo if that's the case
21:23:44 <ttx> As far as scheduling goes, we'd like to have the schedule all set at least one week before summit start
21:24:00 <ttx> so that means we'll have to start making up the schedule soon after release
21:24:14 <ttx> and plan to have the meetings to pick the sessions then
21:24:46 <ttx> I'll be in touch with PTLs on the process to enter the session contents in the schedule
21:25:07 <ttx> (or their summit scheduling liaison)
21:25:16 <ttx> #topic Open discussion
21:25:18 <mestery> ttx: Excellent, thanks!
21:25:23 <ttx> dhellmann: you had something to mention iirc
21:25:27 <dhellmann> yes,
21:25:43 <dhellmann> we need each project to set up a liaison for working with oslo again this cycle
21:26:05 <dhellmann> I didn't want to assume our current volunteers would sign up for a second time, so I went ahead and wiped the wiki page
21:26:21 <dhellmann> https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons#Liaisons_for_Oslo_Integration
21:26:22 <ttx> fwiw we'll do the same for release management. By default the liaison would be the PTL, but you may want to assign someone else
21:26:34 <eglynn> dhellmann: when you need the liaison nominations by?
21:26:40 <ttx> and expect the security team to ask for a main security liaison as well
21:26:52 <dhellmann> I'd like to have the roster filled before the summit so I can make sure they all know which sessions we need them in
21:26:54 <mtreinish> I'm planning to do the same thing with QA as well
21:26:58 * mestery likes the formalization of the liasion program.
21:27:00 <ttx> and stable team
21:27:01 <ttx> etc
21:27:08 <eglynn> cool
21:27:15 <asalkeld> can't this be on one wiki page?
21:27:22 <mestery> asalkeld: ++
21:27:25 <dhellmann> asalkeld: we could probably do that
21:27:26 <ttx> dhellmann: i've been wondering if there was value in showing all liaisons on the same page, or on separate pages
21:27:29 <asalkeld> (all the different cross project stuff)
21:27:37 <dhellmann> yeah, one big table would work
21:27:44 <dhellmann> I'll set that page up and mail the link to the list
21:27:51 <ttx> dhellmann: col, thx
21:27:56 <ttx> cool*
21:28:08 <asalkeld> nice, thx
21:28:24 <dhellmann> asalkeld: good idea -- I didn't realize everyone else was going to definitely do the same thing this time around
21:29:16 <ttx> dhellmann: the VMT had a team of security contacts, but we always ended up with the same person... so better for that person to be THE liaison
21:29:35 <ttx> the default person to ping
21:29:47 <dhellmann> I also want to reiterate that now that we've graduated a bunch of the low level libraries, moving to them should be a priority for all projects in kilo -- we've deleted the incubated version of that code from the master branch of the incubator
21:29:49 <ttx> rather than nobody stepping up
21:30:13 <dhellmann> ttx: makes sense, do we have that list somewhere that I can reproduce on this new page?
21:30:49 <mestery> dhellmann: Agree on the new graduated libraries.
21:30:58 <ttx> dhellmann: depends on the format, but if you list them in separate secvtions, maybe simpler to wait for each area to call for them ?
21:31:11 <dhellmann> mestery: we had a lot of good uptake during juno, but I want to make sure we carry that forward and finish
21:31:19 <mestery> dhellmann: Agreed
21:31:19 <mikal> dhellmann: it would be interesting to be able to generate a report of wqhat orphaned code we have out there
21:31:20 <ttx> I don't want to assume there will be infra liaisons is infra doesn't call for them formally
21:31:31 <dhellmann> ttx: makes sense -- one section per cross-project concern, with a table formatted like the on on the oslo page?
21:31:37 <mikal> dhellmann: something which could be mailed out to openstack-dev periodically perhaps
21:31:41 <ttx> dhellmann: sounds good
21:31:57 <dhellmann> mikal: I will be working on that between now and k-1
21:32:02 <mikal> Cool
21:32:09 <mtreinish> dhellmann, ttx: like https://wiki.openstack.org/wiki/QA/ProjectLiaisons ?
21:32:14 <dhellmann> mikal: but that's also something I hope to delegate to the liaisons :-)
21:32:49 <dhellmann> mtreinish: yep, I'll move yours, too if you like. I was going to call the new page CrossProjectLiaisons and leave it at the top level of the wiki
21:33:15 <mtreinish> dhellmann: sure, thanks
21:34:19 <ttx> ok.. anything else, anyone ?
21:34:51 <ttx> alright then.
21:34:53 <ttx> #endmeeting