21:02:26 <ttx> #startmeeting crossproject
21:02:27 <openstack> Meeting started Tue Mar 31 21:02:26 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02:31 <openstack> The meeting name has been set to 'crossproject'
21:02:32 <adrian_otto> irc://irc.freenode.net:6667/#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-03-31_2100_UTC Our Agneda
21:02:37 <ttx> adrian_otto: don't steal my meeting
21:02:41 <mestery> lol
21:02:43 <mestery> Meeting theft!
21:02:47 <ttx> Our agenda for today:
21:02:52 <ttx> #link http://wiki.openstack.org/Meetings/CrossProjectMeeting
21:03:05 <adrian_otto> uh, wait?
21:03:16 <ttx> adrian_otto: wait what
21:03:16 <fungi> adrian_otto: wrong channel?
21:03:16 <adrian_otto> sorry guys
21:03:22 <morganfainberg> adrian_otto, hi adrian :)
21:03:28 <ttx> #topic PTL election season
21:03:28 <morganfainberg> ttx, o/
21:03:39 <ttx> Adri2000: you can stay here
21:03:46 <ttx> adrian_otto: I mean you
21:03:53 <ttx> Our meeting is more interesting
21:04:00 <ttx> The PTL election season is coming up:
21:04:07 <ttx> #link https://wiki.openstack.org/wiki/PTL_Elections_April_2015
21:04:11 <morganfainberg> that time of year again!
21:04:18 <ttx> If you don't plan to stand for reelection, it's more than time to encourage people in your teams to step up
21:04:36 <ttx> Self-nomination period starts end of week
21:04:42 <ttx> Feel free to reach out to the election officials if you have any questions
21:04:48 <fungi> as before, we'll also want the governance repo tagged so that our tools aren't hitting a master branch moving target
21:05:06 <mikal> 6am UTC is a weird time to start
21:05:06 <ttx> fungi: sure I'll be around
21:05:08 <mikal> Just sayin'
21:05:22 <ttx> damn round planet
21:05:47 <mikal> Why not just midnight?
21:05:49 <fungi> mikal: it's more that i can generate the electorate rolls first thing when i wake up, and 0600 utc is well before i roll out of bed
21:05:49 <mikal> Not that it matters
21:05:51 <ttx> mikal: must carry some US-centricity
21:05:53 <morganfainberg> mikal, i vote 0623UTC ... :P
21:06:05 <morganfainberg> mikal, my vote doesn't matter though
21:06:11 <fungi> and for whatever reason previous elections did 0600 utc
21:06:15 <ttx> ok, no question on that topic ?
21:06:18 <mikal> fungi: ahhh, fair enough
21:06:41 <anteaya> nothing starts at 6 utc
21:06:49 <eglynn> midnight in US mountain time areas that don't do DST?
21:06:56 <anteaya> it was the utc equivalent of pacific time
21:07:07 <fungi> 0600 utc is merely the cut-off for contributions counting you into the electorate
21:07:09 <anteaya> for midnight on the thursday
21:07:20 <anteaya> and for the self-nomination period
21:07:33 <ttx> not that anyone cares anyway
21:07:36 <ttx> #topic Design Summit content
21:07:47 <ttx> OK, time to talk about the Design Summit in Vancouver
21:08:01 <ttx> In theory the content will be set by the newly-elected PTLs, but nothing prevents to start the discussion early
21:08:04 <eglynn> anteaya: PDT is UTC-7:00 surely?
21:08:16 <anteaya> eglynn: we have moved topics
21:08:21 <mestery> ttx: Ack, starting early is well advised!
21:08:21 <ttx> As far as slot allocation is concerned, we don't have that many new projects after all, so we should be able to give everyone what they requested
21:08:40 <ttx> Final slot allocation and proposed slot layout should be available around April 10, once we know the final list of projects to be considered
21:08:49 <eglynn> anteaya: ... yet the timezones stay the same
21:09:06 <ttx> eglynn: I don't think anybody cares what hour the nomination week starts
21:09:30 <ttx> Questions on slot allocation ?
21:09:33 <tchaypo> o/
21:09:36 <bknudson> do we have some idea if everybody wants fishbowl or conference rooms?
21:09:46 <ttx> bknudson: let me see
21:09:47 <bknudson> or are we getting a mix
21:10:06 <ttx> everyone getting what their PTL asked for when I polled them
21:10:17 <ttx> generally a mix
21:10:21 <nikhil_k> ttx: How about cross project ones?
21:10:24 <bknudson> great
21:10:33 <morganfainberg> ttx, good news!
21:10:34 <ttx> cross-project is all fishbowl
21:10:54 <nikhil_k> All remaining slots ? or do we have min, max on that?
21:11:04 <ttx> Currently 133 fishbowls requested, 173 workrooms and 29 half-days
21:11:10 <nikhil_k> Thanks
21:11:35 <eglynn> ttx: what's the story on for scheduling the Friday afternoon?
21:11:37 <ttx> nikhil_k: once the allocation is confirmed we may have scraps to share for the needy
21:11:50 <nikhil_k> That would be great
21:11:55 <ttx> Friday afternoon is contributors meetups
21:12:03 <ttx> like Friday nmorning
21:12:33 <bknudson> is there a feedback session on fri aft?
21:12:36 <eglynn> ttx: any projects who requested half day contrib meetup getting allocated the afternoon slot?
21:12:42 <bknudson> I'd like some info on how the economy is going.
21:12:43 <ttx> bknudson: yes, last slot
21:12:53 <ttx> bknudson: we invited the same speaker
21:12:58 <bknudson> wonderful!
21:13:00 <morganfainberg> ttx, was going to ask about that :P
21:13:01 <ttx> bknudson: the economy is not getting better
21:13:01 <eglynn> I ask because Friday afternoon == graveyard
21:13:04 <david-lyle> can we talk economy in it?
21:13:16 <morganfainberg> ttx, you typed it out before i could ask.
21:13:34 <ttx> eglynn: most projects requested full day
21:13:49 <eglynn> a-ha, k
21:13:50 <anteaya> bknudson: the Canadian economy? straight down
21:14:04 <ttx> eglynn: we might be able to schedule all the single half-day ones in the mornings
21:14:19 <notmyname> what economy are you talking about?
21:14:27 <mestery> eglynn: I share your concern about friday afternoon being a graveyard :)
21:14:27 <eglynn> ttx: excellent, that would be wise I think
21:14:28 <ttx> OK, next subtopic... session proposals
21:14:37 <ttx> notmyname: you missed a historic moment in Paris
21:14:47 <ttx> As far as session proposals go, we let everyone use their own tooling (mostly etherpads)
21:14:49 <notmyname> oh yeah. I heard about it
21:14:57 <ttx> It would be great to reference those in:
21:15:00 <ttx> #link https://wiki.openstack.org/wiki/Design_Summit/Planning
21:15:01 <notmyname> I wouldn't say I missed it, Bon
21:15:03 <notmyname> *bob
21:15:11 <ttx> so if you already have a design summit suggestion etherpad, please add it there
21:15:20 <ttx> so that people can find them
21:15:25 <ttx> One team asked that we make an ODSREG instance (the system we used for session proposals pre-kilo) available to them for session suggestion collection
21:15:35 <ttx> ODSREG code lives at https://git.openstack.org/cgit/openstack-infra/odsreg/ but I guess for those I'll set up team-dedicated instances of the tool
21:15:45 <ttx> It's not totally impossible we'll use ODSREG for suggesting cross-project sessions as well
21:15:55 <ttx> Most other projects seemed happy with etherpads
21:16:19 <mestery> ++ to etherpads
21:16:31 <mtreinish> +1
21:16:37 <ttx> you can also use Google forms, whatever works best for you
21:16:38 <eglynn> googledocs sheets for the win
21:16:47 <eglynn> ... much easier to tally votes
21:17:13 <ttx> eglynn: you do votes ? What kind of a dictatorship do you live in ?
21:17:31 <asalkeld> hah
21:17:42 <eglynn> ttx: we vote, but North Korea stylee ;)
21:17:55 <ttx> ok.. questions on session proposals ?
21:18:01 <mestery> lol
21:18:16 * morganfainberg already setup an etherpad for keystone
21:18:20 <nikhil_k> ttx: more info on the dates to come later?
21:18:22 * morganfainberg is happy w/ etherpads.
21:18:24 <ttx> morganfainberg: please add link
21:18:27 <morganfainberg> already done
21:18:32 <ttx> nikhil_k: dates ?
21:18:47 * morganfainberg also made sure to be the weird project that didn't follow the naming convention for the etherpad :P
21:18:48 <nikhil_k> Until which people can do proposals
21:18:52 <morganfainberg> [not on purpose]
21:19:02 <nikhil_k> ttx: people like to have meetings before slots can be allocated
21:19:12 <ttx> nikhil_k: you can communicate your own. there will be a deadline to fill the schedule, but otherwise you're on your own
21:19:39 <ttx> which brings us to our next subtopic
21:19:45 <nikhil_k> and that deadline to fill the schedule should be close to the main event like the previous time right?
21:19:51 <ttx> yes
21:19:53 <ttx> As far as scheduling goes, we won't use ODSREG this time, mostly because the sched.org constraints changed (we share the sched with the main conference now)
21:19:54 <nikhil_k> thanks
21:20:05 <ttx> So I created a new tool that lets you directly edit a few things on sched in the slots that are allocated to your teams, I'll send you link to a demo soon
21:20:15 <ttx> Code currently lives at https://github.com/ttx/summitsched for the curious
21:20:20 <mestery> ttx: Cool!
21:20:29 <ttx> it's basically a sched proxy
21:20:48 <ttx> since shced has a pretty simple idea of ACLs
21:21:00 <ttx> (stores it in a binary)
21:21:15 <ttx> We still have a decision to make though. Cheddar enforces a number of things, like making sure all sessions on a track are prefixed by the track name, for clarity
21:21:22 * morganfainberg wonders how many ways we can break sched this time :P
21:21:32 <ttx> It also enforces boring titles and descriptions for "work sessions" and the "contributors meetups", in order to make them as unattractive as possible for the general attendance
21:21:41 <ttx> You can see the results at: http://testingsiteforfutureevents2015.sched.org/
21:22:10 <mestery> nice!
21:22:15 <morganfainberg> ttx, i want to go to the "Ops: cake is amazing" session
21:22:20 <asalkeld> with "food not provided in the title" ;)
21:22:23 <ttx> So basically you can give fishbowl sessions a title, but work sessions and contributors meetups have set titles
21:22:43 <ttx> since they have such limited room you don't want everyone to show up because tyou mentioned "docker" in title
21:22:49 <ttx> One question I still had is whether to allow custom descriptions in work sessions. Currently you only can customize a link, which looks like this:
21:22:55 <ttx> http://sched.co/2wp8
21:23:02 <ttx> That may be a bit impractical for design summit attendees (having to click the link to see what the work session is actually about)
21:23:10 <ttx> It's a balance between making it unattractive to conference attendees and making it a pain to design summit attendees
21:23:16 <ttx> So maybe boring title is enough and we should allow custom descriptions for work sessions ? What would be your take ?
21:23:34 <morganfainberg> I'd allow a link to an etherpad, add a boring description "see etherpad for me"
21:23:37 <morganfainberg> "more"*
21:23:39 <asalkeld> maybe a very short description?
21:23:47 <asalkeld> as a reminder
21:23:51 <ttx> morganfainberg: that is what we have for work sessions right now
21:24:04 <SergeyLukjanov> ++ for very short description asalkeld
21:24:11 <tchaypo> FWIW it seems like it should be possible to work around some of this by creating an etherpad for “here are our project’s work sessions” and putting descriptions there
21:24:18 <ttx> generic description looks like  http://sched.co/2wp8
21:24:32 <tchaypo> possible, but slightly annoying
21:24:34 <morganfainberg> ttx, i'm a fan of that. it means that it's easy to change the work session topic if suddenly everyone is busy elsewhere for that topic
21:24:37 <bknudson> the work group titles are hopefully going to have the project name ?
21:24:55 <ttx> that basically means you need to train your teams to click on the etherpads
21:24:56 <morganfainberg> ttx, i'd rather just keep the boring description and the link.
21:25:11 <serg_melikyan> I think it's pretty nice - at the end working session are for contributors and they know what they plan to discuss
21:25:14 <morganfainberg> but i'm not going to vote strongly against a short description
21:25:36 <ttx> so let's do a quick poll
21:26:04 <asalkeld> (was just thinking if you are on a phone, short description is nice)
21:26:10 <openstack> ttx: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
21:26:16 <ttx> #startvote should work sessions have custom descriptions, or just a boring description and a link ? custom, boring, don't care
21:26:17 <openstack> Begin voting on: should work sessions have custom descriptions, or just a boring description and a link ? Valid vote options are custom, boring, don, t, care.
21:26:18 <openstack> Vote using '#vote OPTION'. Only your last vote counts.
21:26:23 <morganfainberg> #vote boring
21:26:30 <eglynn> #vote custom
21:26:33 <david-lyle_> #vote boring
21:26:33 <notmyname> #vote custom
21:26:34 <edleafe> #vote boring
21:26:35 <mestery> #vote boring
21:26:49 <asalkeld> #vote custom
21:26:55 <morganfainberg> actually... if we can just have it default to boring, and allow an override...
21:27:01 <nikhil_k> #vote custom
21:27:02 <morganfainberg> i think that solves the use for everyone
21:27:10 <mestery> morganfainberg: ++
21:27:12 <david-lyle_> morganfainberg, +1
21:27:12 <ttx> hmm, yes.
21:27:17 <ttx> #endvote
21:27:18 <openstack> Voted on "should work sessions have custom descriptions, or just a boring description and a link ?" Results are
21:27:19 <openstack> boring (4): david-lyle_, edleafe, mestery, morganfainberg
21:27:20 <openstack> custom (4): nikhil_k, eglynn, notmyname, asalkeld
21:27:34 <ttx> Let's make it custom, but encourage boring
21:27:34 <mestery> lol
21:27:42 <morganfainberg> ;)
21:27:43 <ttx> you can come with your own flavor of boring
21:27:48 <morganfainberg> i like it!
21:27:48 <asalkeld> haha
21:27:49 <eglynn> I wouldn't like to see "boring" used as a means of realtime rescheduling of sessions
21:27:49 <mestery> A tie ... but it doesn't matter anywya because morganfainberg had a better solution :)
21:28:15 <ttx> the vote was a rhetorical trick
21:28:16 <eglynn> (hard enough to manage the clashes between multiple tracks in parallel)
21:28:24 <morganfainberg> "this is a boring work session, don't come here... we're going to be quiet and not doing performance art... we swear... and definitely not docker"
21:28:32 <eglynn> LOL :)
21:28:37 <david-lyle_> haha
21:28:39 <mestery> No! You said Docker! ;)
21:28:57 <eglynn> open the floodgates!
21:28:59 <bknudson> put a sign that says docker on a room.
21:29:07 <morganfainberg> LOL
21:29:08 <ttx> "10 things you won't believe about Docker"
21:29:16 <sdague> we just need that nfv docker honeypot session
21:29:19 <morganfainberg> ttx, this one amazing trick about docker...
21:29:29 <mestery> "Docker and OpenStack: Better Together!"
21:29:30 * morganfainberg apologizes for derailing
21:29:36 <mestery> lol
21:29:40 <mestery> sdague: lol
21:29:53 <anteaya> sdague: in another building
21:29:57 <ttx> Oh, and Cheddar (the sched proxy) also supports a session showing up in multiple tracks!
21:29:59 <dansmith> I bet those folks are as easy to trap as ... LEMMINGS
21:30:00 * dansmith runs
21:30:13 <ttx> So it has a main track, but you may also make it appear in other tracks
21:30:19 <mikal> dansmith: lol
21:30:23 <morganfainberg> oh thats cool.
21:30:30 <ttx> example at:
21:30:33 <mestery> lol
21:30:58 <ttx> http://sched.co/2vhQ
21:31:07 <ttx> That's an Ops session, but it also appears in swift
21:31:26 <notmyname> nice. swift + cake == awesome
21:31:26 <ttx> so that when your contributor go to: http://testingsiteforfutureevents2015.sched.org/type/design+summit/Swift they still see it
21:31:41 <ttx> That should facilitate multi-project work
21:31:45 * devananda sneaks in, tries to catch up on scrollback
21:32:15 <russellb> devananda: well that's not sneaky at all
21:32:17 <mestery> devananda: Summary is: NFV Docker honeypot!
21:32:20 <ttx> If someone wants to beta-test Cheddar, I can set up access to the demo instance
21:32:33 <ttx> just send me some email so that I remember to do it
21:33:09 <ttx> Alright, any question on design summit ?
21:33:54 <asalkeld> all good, thanks ttx
21:33:59 <ttx> #topic Open discussion & announcements
21:34:06 <ttx> We had 1:1s syncs today in #openstack-relmgr-office, logs at:
21:34:07 <eglynn> ttx: is there a list of the per-project slot allocations anywhere?
21:34:15 <ttx> #link http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-31-08.04.html
21:34:21 <devananda> ttx: i would have voted boring :)
21:34:23 <sdague> ttx: for open discussion, question on string freeze and string freeze exceptions
21:34:41 <ttx> eglynn: not yet, but the google doc I colected answers on is still up
21:34:48 <sdague> when we need to change a string for bugs at this point, what are we supposed to do to alert i18n teams
21:34:53 <eglynn> ttx: a-ha, cool, ta
21:35:05 <nikhil_k> ttx: What seem to be the community plan for the smaller release cycle in L?
21:35:21 <ttx> sdague: so that is a good question
21:35:23 <nikhil_k> to be community's general plan*
21:35:41 <ttx> sdague: we generally do a thread on -dev, but I have no idea if that reaches the right people
21:35:55 <morganfainberg> sdague. we should do a i18nImpact  tag?
21:35:58 <devananda> ttx: i ma have missed it in my skim - is the ops track taking suggestions and/or having project-specific discussions?
21:36:09 <sdague> yeh, this seems like a very non closed loop, as I never have any idea what the i18n progress is
21:36:10 <ttx> Actually, I have no evidence that string freeze exceptions get seen by translators
21:36:12 <morganfainberg> ttx, i use the i18n mailing list.
21:36:24 <morganfainberg> ttx, got a response from andreas about it.
21:36:28 <ttx> I know they appreciate us not gratuitously changing strings after FF, but that's about all the feedback I got
21:36:28 <sdague> morganfainberg: there's a separate mailing list?
21:36:29 <morganfainberg> ttx, so that seems to work.
21:36:31 <morganfainberg> sdague, yes.
21:36:39 * mestery didn't know of the separate ML either
21:36:42 <Rockyg> devananda: there's an etherpad for ops
21:36:52 * morganfainberg has had to do this a few times in the past.
21:36:55 <devananda> Rockyg: link isn't on https://wiki.openstack.org/wiki/Design_Summit/Planning yet :)
21:37:05 * devananda adds ironic to ^
21:37:14 <morganfainberg> openstack-i18n@lists.openstack.org
21:37:28 <sdague> ttx: so it seems like it would be good to get i18n leadership to be banging appropriate drums on -dev list around this
21:37:34 * Rockyg is looking
21:37:38 <barrett1> Here's the etherpad for the Ops topics:   https://etherpad.openstack.org/p/YVR-ops-meetup
21:37:40 <ttx> sdague: yes
21:37:42 <sdague> because otherwise we're just going to fail a lot
21:38:25 <Rockyg> ops summit ether pad:  #link https://etherpad.openstack.org/p/YVR-ops-meetup
21:38:27 <morganfainberg> we tend to be good w/ closes-bug, and docimpact (not as good as closes bug), so maybe a tag in the commit message is the right approach... maybe it's just a bad idea as well.
21:38:31 <ttx> morganfainberg: you seem to know your way around there, care to introduce that topic ?
21:39:04 <ttx> we just ened to make sure the i18n leadership shows up
21:39:12 <morganfainberg> ttx, uhm.. what needs to be introduced? or you mean for a session?
21:39:24 <sdague> morganfainberg: we need to know what to do now
21:39:28 <ttx> no I mean <sdague> ttx: so it seems like it would be good to get i18n leadership to be banging appropriate drums on -dev list around this
21:39:30 <sdague> on -dev
21:39:50 <ttx> morganfainberg: you seem to know who to reach to
21:40:00 <morganfainberg> sdague, i mean i'll bug andraes and send a message to the i18n list :)
21:40:05 <ttx> i18n is a black box to me. To reach it I usually dial fifieldt
21:40:06 <sdague> you even knew there was a list
21:40:18 <sdague> morganfainberg: so I think the point is this needs to be on -dev
21:40:25 <sdague> because few people know that list is a thing
21:40:38 <sdague> so clearly won't be getting info out to the review teams that need it
21:40:41 <morganfainberg> sdague, right, the point is getting them in on the convo.
21:40:46 <ttx> and the current process involved [stringfreeze] on dev list
21:40:55 <morganfainberg> ttx, oh i didn't know that :P
21:40:59 <sdague> ttx: ok, news to me
21:41:03 * morganfainberg did something totally different.
21:41:22 <ttx> well, that is what I replied to people who asked me
21:41:28 <morganfainberg> so i'll try and chase someone (some i18n folks) down and get them to make some noise on -dev about.
21:41:31 <ttx> not sure that qualifies as "process"
21:41:39 <morganfainberg> not guarantees that i'll be successful.
21:41:42 <morganfainberg> but i'll try
21:41:50 <sdague> when we get to these parts of the release I think the [all] emails need to go out with "x is frozen, to get an except do Y"
21:42:05 <morganfainberg> the only way i knew someone read i18n list is because someone responded this time (i think this is the 4th or 5th string freeze i've sent out)
21:42:11 <sdague> because there has been a ton of confusion with code review where everyone's trying to guess the rules
21:42:38 <morganfainberg> sdague, ++ i'll chase some people down and get them to send something to -dev.
21:42:40 <ttx> sdague: but but but difference in culture is good right ?
21:42:44 <sdague> which means they are so inconsistently applied, it's not clear they are useful at all
21:42:54 * sdague walks away slowly
21:42:55 <morganfainberg> sdague, at least we have some direction then.
21:43:35 <sdague> morganfainberg: yep, thanks
21:43:40 <ttx> morganfainberg: thx!
21:43:51 <ttx> nikhil_k: you had a question ?
21:44:22 <nikhil_k> ttx: What seems to be community's general plan for the smaller release cycle in L?
21:44:41 <ttx> nikhil_k: I don't think we'll do a smaller release cycle in L
21:44:50 <ttx> but we'll dsicuss release cycle lengths in Vancouver
21:45:06 <nikhil_k> so not 6 weeks then?
21:45:18 <nikhil_k> There was some proposal for abandoning older PS
21:45:26 * fungi votes for a 6-minute release cycle
21:45:28 <ttx> well, the cycle will still be 6 months. You may release more often though
21:45:35 <bknudson> we'll run out of letters.
21:45:43 <ttx> nikhil_k: don't believe everything you read on MLs
21:45:52 <nikhil_k> I thought the rhythm matches well with our 6 weeks style
21:45:59 * morganfainberg believes everything on the internet
21:46:05 <fungi> i really didn't get the impression that the "release more often but less thoroughly" discussion really went anywhere except in a circle back to describing why we have milestones that aren't releases
21:46:06 <david-lyle> we could use Liberty, Lemming and Lizard
21:46:06 <nikhil_k> ttx: I kinda like that idea :)
21:46:17 <nikhil_k> (of abandoning older PS)
21:46:23 <morganfainberg> david-lyle, and love. don't forget love
21:46:30 <morganfainberg> >.>
21:46:35 <ttx> All you need is Love
21:46:46 <mikal> All I need is a nap
21:47:23 <ttx> nikhil_k: I'll invite you to that session :)
21:47:33 <ttx> OK... Anything else, anyone ?
21:47:59 <morganfainberg> ttx, does that mean we move to semver?
21:48:05 <morganfainberg> ttx, releasing more often that is?
21:48:14 <morganfainberg> or is that just a rabbit hole not worth talking about right now
21:48:16 <nikhil_k> mikal: http://www.tumblr.com/tagged/i-need-a-nap
21:48:17 <david-lyle> where are cross-project session topics being collected?
21:48:20 <ttx> morganfainberg: rabbit hole
21:48:32 <ttx> david-lyle: nowhere yet
21:48:33 <morganfainberg> ttx, sold. happy to merrily go on my way
21:48:37 <nikhil_k> ttx: heh
21:48:45 <ttx> david-lyle: the etherpad ended up a bit messy last time
21:48:52 <ttx> russellb: ^
21:49:05 <russellb> we need to get started on that soon
21:49:11 <ttx> I was wondering if we should not use something less messy, like ODSREG of some google form
21:49:13 <russellb> one problem was that we started kinda late, IIRC
21:49:19 <russellb> ttx: that too, yes
21:49:36 <russellb> submission by completely freeform text is kind of difficult
21:50:00 <ttx> works well for teams brainstorming, not so much for random individuals posting
21:50:02 <david-lyle> how many cross-project tracts concurrently running?
21:50:06 <russellb> yeah
21:50:11 <ttx> let me see
21:50:29 <russellb> is it a cross project day again?
21:50:43 <ttx> 2 sessions in parallel
21:50:47 <ttx> yes, Tuesday
21:50:50 <russellb> ok
21:50:52 <david-lyle> ok
21:50:53 <russellb> ODSREG is fine with me
21:51:04 <ttx> Ops track runs in parallel though
21:51:18 <ttx> so we'll have to choose where to go
21:51:28 <russellb> usually the case ..
21:51:46 <ttx> right
21:51:49 <russellb> let's just add more days!
21:51:53 * russellb headdesks
21:52:05 <russellb> i think i might collapse
21:52:23 <russellb> ok so, cross-project track.  we should do somethign about that.
21:52:27 <ttx> OK, I think we are done for today, unless someone has a last-minute question/topic
21:52:29 <russellb> ttx: ODSREG++
21:52:46 <ttx> russellb: ok, will set up an instance for cross-project
21:52:50 <russellb> awesome
21:52:54 <ttx> notmyname asked for one for swift too
21:53:06 <ttx> notmyname: still interested ?
21:53:11 <notmyname> yes, i think so
21:53:19 <notmyname> I prefer it to etherpads
21:53:33 <ttx> notmyname: some people use Google forms
21:53:48 <ttx> notmyname: maybe discuss with team and let me know what you need
21:53:52 <notmyname> ok
21:54:01 <russellb> would be nice if it was consistent
21:54:02 <russellb> oh well
21:54:37 <ttx> ok, let's close this
21:54:41 <ttx> #endmeeting