20:00:58 #startmeeting 20:00:58 Meeting started Tue Dec 10 20:00:58 2013 UTC. The chair is vorlon. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:58 Useful Commands: #action #agreed #help #info #idea #link #topic. 20:01:30 #link https://wiki.debconf.org/wiki/DebConf14/Meetings 20:01:37 #topic Roll call 20:01:41 who all is here today? 20:01:44 * gwolf looks from the side only :-} 20:01:45 Steve Langasek 20:01:46 i'm half-here 20:01:49 I expect to be half-here 20:01:50 hi 20:01:53 hi 20:01:53 Hi. 20:02:02 i'm here 20:02:05 between me and gwolf, we'll make up an entirely-here person, perhaps 20:02:22 Patty Langasek 20:02:23 nattie: the scary question is... which kind of person will that be 20:02:53 hello - at work (so hopefully no interruptions) 20:03:04 hi 20:03:17 anyone else? 20:03:26 gwolf: i shudder to think 20:03:33 * vorlon pokes kees 20:04:14 Meh. He'll eventually figure out something's going on. :) 20:04:17 moving along then 20:04:41 fwiw, I mentioned on here before the meeting that http://www.debconf.org/calendars/DebConf-team.ics is no longer updating from svn - probably related to the alioth move 20:05:03 so it's possible some people have missed the meeting because the calendar isn't current. Does someone here have access to fix that? 20:05:29 * Clint pretends to be here. 20:05:30 OdyX: can you update the ics? 20:05:42 hi! 20:05:53 hey, packed room - great 20:06:03 #topic agenda 20:06:11 * kees is in two meetings at the same time, apologies for any latency 20:06:14 does anyone have any last-minute topics to add to today's agenda, before we get started? 20:06:23 (so that we can allow appropriate time at the end) 20:07:11 I have nothing, sorry. 20:07:41 ok. if anyone thinks of something later we can try to discuss if time allows 20:07:50 Can you relink me to where the agenda is? I seem to have browser fail today. 20:07:54 #topic Updates on last month's actions 20:08:00 harmoney: https://wiki.debconf.org/wiki/DebConf14/Meetings 20:08:06 Gracias 20:08:14 so this says "last month's", but we probably want to cover stuff from the last two meetings 20:08:35 (at least the outstanding ones) 20:08:44 vorlon to work with hug to get a first draft budget done ASAP 20:08:47 vorlon to work with hug to get a firmed-up budget by 30 Nov 20:08:52 tmancill to email out the current sponsorship brochure pdf, so people have access while alioth is down 20:08:55 harmoney to follow up on visa team stuff: try to identify a lawyer friend, and get our invitation letter in order 20:08:59 vorlon to draft a "Call for sponsors" blurb today for inclusion on debconf14.debconf.org, email it to rafw + OdyX 20:09:08 so I'm 0 for 3, how about everybody else? :P 20:09:32 I think tmancill did send out the pdf by email - thanks tmancill 20:09:33 I've identified friends, but I don't think any are lawyers, so I'm needing a little more time. 20:09:34 while not on the official TODO list there, I have started discussions with the the PSU network infra people. 20:10:11 harmoney: we need to have something in order by end of year for sure. Do you want to keep this action, or would it be better to give offer it up to somebody else? 20:10:30 vorlon: I can keep it. After my final tonight, I should have plenty of brooding time to devote to it. 20:10:31 wrt the budget, I've spoken briefly with hug, but I have no budget to present yet 20:10:52 hug: can you send me whatever spreadsheet you're using for this so I can start plugging in numbers as I have them? 20:11:11 I'm already late with the budget, I think we want to get this in for DPL approval before EOY 20:11:28 sorry for that, I was a bit too busy last weeks. I'll send you the spreadsheet and you can fill in some numbers and return it to me. 20:11:33 or google docs if that's fine 20:11:44 whatever format you think is bets 20:11:45 best 20:12:03 you have the experience dealing with DC budgeting, not me - I'm happy to follow your lead, just as long there's something I can look at :) 20:12:41 preferable to have it in the VCS rather than Google Docs 20:12:46 and I guess we should have a "call for sponsors" blurb for dc14.dc.o still, even if it's now later than we intended 20:12:50 so I'll carry that action over 20:13:00 #action vorlon to work with hug to get a firmed-up budget ASAP 20:13:09 #action harmoney to follow up on visa team stuff: try to identify a lawyer friend, and get our invitation letter in order 20:13:20 #action vorlon to work with hug to get a firmed-up budget ASAP rafw + OdyX 20:13:26 ok? 20:13:29 ok 20:13:50 pref. vcs? 20:13:58 Do you need to add that to the action? 20:14:12 harmoney: sorry, what do you mean? 20:14:29 vorlon: 12:14 < moray> preferable to have it in the VCS rather than Google Docs 20:14:38 right 20:15:09 that's certainly preferable, but I want whatever hug can give me as soon as he can give it; so if that means using gdocs for a first pass, that's what I'll go with 20:15:20 anyway, implementation detail :) 20:15:29 #topic Confirm current meeting schedule 20:16:11 so last month we tried a Saturday; this month we're trying a Tuesday by mutual agreement of those who made it to the Tuesday meeting 20:16:18 er, made it to the Saturday meeting 20:16:27 heh 20:16:44 tuesdays as a general rule are good for me, even though i'm not really saying much in meetings at the moment 20:16:47 I believe we had tentatively agreed to continue forward with this time slot on Tuesday - it wasn't the one originally on the doodle, but it's the one that seems to work 20:16:47 tue is waaaay better for me 20:17:00 I'm usually happier with Tuesday as well 20:17:14 Tues... during the day can be iffy for me, but I'll do what I can. 20:17:23 anyone here who's specifically here and *unhappy* about Tuesday? :) 20:17:42 (and if you raise your hand, I will grill you about why you were not at the Saturday meeting last month :) 20:18:06 hands up all those not present ;-) 20:18:15 * vorlon grins 20:18:16 * Clint gestures at fil. 20:18:17 even though I'm not here, I'll vote specifically against weekend meeings 20:18:48 so does that make the next meeting Jan 7 or Jan 14? 20:19:01 fwiw i prefer weekdays, tuesday's are fine 20:19:12 I want to note, though, that "During the week" meetings is more complicating when you're looking at 8+ hour time differences in global organization. But, that might just be my concern. :) 20:19:33 is more complicated. Did you know that English is my native language? True story. 20:19:44 I'd prefer Jan14 (Jan7 I'll be flying from Argentina). But then again, I'm not in such a leading role this time around... 20:19:49 harmony: well, it seems that most of the team members retreat to their hacking caves on the weekends so are unavailable regardless of timezone 20:19:53 harmoney: past experience suggests people don't go to regular weekend meetings anyway 20:20:12 if if strictly speaking they are available 20:20:21 (even if) 20:21:11 so the original doodle poll said "second week of each month" 20:21:20 I think we can reasonably interpret this as "second Tuesday of each month" 20:21:23 so Jan 14 20:21:24 fair? 20:21:33 #agreed 20:21:39 yay 20:21:41 * kees nods 20:21:44 #agreed IRC meetings will be the 2nd Tuesday of each month 20:21:57 #agreed next IRC meeting Tuesday, Jan 14 2014 @ 2000 UTC 20:22:18 #action vorlon to populate the calendar with future IRC meetings (and check with OdyX about website sync from svn) 20:22:34 * vorlon waves to dondelelcaro 20:22:47 #topic Venue contract 20:23:49 current status is that we have a draft contract from PSU for the accomodations, which needs some adjustments 20:23:52 no contract yet for the venue 20:24:11 procedural question: who do we need to have eyes on this contract? Just SPI? 20:24:40 I'd say so. Being it in the USA, SPI is our only legal representative 20:24:46 ok 20:25:01 vorlon: Certainly DPL 20:25:06 ISTR for DC13 there were contract discussions on debconf-team - wanted to check whether that was necessary here 20:25:24 bgupta: DPL needs to sign off on the budget, I don't imagine he needs to be involved in reviewing the contract details 20:25:30 bgupta: The DPL does not need to sign the contract, just to approve it 20:25:39 vorlon: normally we stick these things in the VCS, but don't have much formal team sign-off over them 20:25:52 ok, I can do that 20:25:57 bgupta: anyway, there'd be the issue of *which* DPL - though most recent ones have served two terms, it's not a given 20:26:00 which VCS is "the VCS"? 20:26:11 vorlon: debconf-team for contracts etc. 20:27:00 nattie: the budget is approved by the DPL in term when the budget is presented 20:27:05 #action vorlon to upload PSU draft contract to debconf-team git 20:27:38 that is, the budget for DC13 was presented to (and approved by) zack. Most probably, lucas later approved modifications we did to it (although I don't remember exactly...) 20:27:56 I mentioned previously that there was a question about whether we would in the end be eligible for university discounts on the venue 20:28:01 this is still being worked through 20:28:42 at this point, I think we should operate under the assumption that the venue will not be under a discount, and proceed accordingly 20:28:51 then we can have a pleasant surprise later instead of an unpleasant one 20:28:58 makes sense 20:29:00 Absolutely agreed. 20:29:09 +1 20:29:21 ok. I'll be working numbers into the contract accordingly 20:30:36 ummmm. git+ssh://scm.alioth.debian.org/git/debconf-team/debconf-team.git is empty? 20:30:49 vorlon: AFAIK we are still using the svn 20:30:53 its svn. 20:30:57 sigh 20:31:08 what blocks us from migrating? 20:31:34 (https://alioth.debian.org/scm/?group_id=30976 only mentions the git, which is confusing) 20:32:14 ...besides, mishaps as what we had with Alioth recently should make us go as far as possible from a centralized VCS... 20:32:27 right, but I don't think we need to argue about VCSs and migration during this contract point 20:32:29 (and "us" means "everybody in Debian", if not more wide-reaching) 20:32:35 moray: right :) 20:33:00 #topic VCS migration 20:33:08 :P 20:33:21 does this just need somebody on the team to do the work? 20:33:41 if you also migrate -data, it needs an admin to update the webserver, at minimum. 20:33:42 obviously we need MJ Ray here to keep us to the agreed agenda :p 20:34:05 * fil stabs moray 20:34:15 repeatedly 20:34:38 I'll add that if you are migrating from SVN to git, I'd ask that logs/hisotry are also migrated. 20:34:55 relistically only recent logs are typically needed... 20:35:07 but if you are going to migrate those, we should do all 20:35:08 Ganneff: hey, so I was mentioning earlier that the webserver seems to already be unhappy pulling from the new alioth - at least the calendar ics file is broken. Does that need an admin? 20:35:13 anyway 20:35:22 does someone want to volunteer to migrate debconf-team to git? 20:35:23 bgupta: "git svn" makes it quite trivial 20:35:30 vorlon: it needs someone to inform admins, yeah. 20:35:43 Ganneff: can I consider this done with the above? 20:35:44 (and the migration we should look at "between the years" IMO) 20:36:03 im looking 20:36:06 thanks 20:36:23 Ganneff: well, we kind of are between years still, compared to how things will be in a few months 20:36:28 right 20:36:40 I think a straightforward migration could be done quickly 20:36:41 moray: i meant the between the years between christmas and new year, not debconf years 20:36:50 oh, heh 20:36:59 when it came up before, people wanted to do fancier rearranging, splitting, etc. though 20:37:02 that is, the free time zone 20:37:23 * Ganneff against splitting, honestly. at least for -data that would be annoying (speaking as root@) 20:37:26 Kees had important networking stuff. 20:37:29 maybe it's more realistic for us to just to a simple migration and leave fancy ideas for another time 20:37:38 Ganneff: yes, I wasn't really convinced myself 20:37:43 i volunteer to look at migration - end of this month time. 20:37:57 #action Ganneff to look at migrating debconf-team from svn to git at end of year 20:37:58 so this meeting can go on now with real important stuff :) 20:38:00 Ganneff: thanks 20:38:26 (fwiw I think debconf-data is a much bigger problem and wasn't going to push for that right now... but if you think it's feasible, hey, no objections here) 20:38:35 #topic Wine & Cheese party 20:38:51 I put this on the agenda because I hear a rumor that bubulle won't be able to make it to DebConf14 20:39:14 Quoi ? 20:39:15 moray: was that because there was too much big stuff clogging things up? If so, perhaps the first cut should just say all files above size X get put in via git annex so we can drop them later without having to rewrite history 20:39:26 so I think if we want a cheese & wine party, we need to identify someone who will drive it 20:39:37 * harmoney volunteers Clint. 20:39:38 (someone who is not one of the core local organizers) 20:39:49 fil: I don't think it was individual big files, more that people claimed it was useful to do a partial checkout without getting given every year's stuff 20:40:13 yeah, I routinely do partial checkouts of the current svn 20:40:14 fil: and some people, misguidedly in my view, wanted separate access control per year (I think that's an actively bad idea, we should be able to learn from the past) 20:41:01 vorlon: was a venue for it found yet? or should that be part of the (local) job too? 20:41:10 so we get to shuffle past years into their own branches and throw away master once that's done -- no reason not to start though 20:41:31 anyway, not meeting stuff 20:41:44 moray: we have several leads for a venue, but I would like input from the Cheese Delegate on such things 20:42:21 I'd volunteer, but I've been to a C&W party. 20:42:30 vorlon: well, there is an ongoing cheese team that isn't in these meetings much 20:42:32 what's involved? 20:42:43 vorlon: is the alcohol-serving still an issue? 20:42:56 vorlon: so you might get some non-bubulle volunteer(s) if you ask somewhere wider and/or to the right list of people directly 20:43:11 bgupta: I guess you mean you haven't been to one? Maybe that doesn't make you the best positioned to lead it... 20:43:20 I don't think we should block on bubulle to be able to organize it so early on 20:43:25 haven't, yes 20:43:26 moray: ok, who is that cheese team? documented in the wiki for last year? 20:43:34 gwolf: what do you mean? 20:43:38 vorlon: I think the wiki should have it for some years, yes 20:43:41 ...If he (sadly!) is not able to make it... there are lots of cheese-team expert people 20:43:56 so... I don't think there's much need for C&W to be discussed so early on 20:44:01 I'm trying to specifically /not/ block on him - or worse, have things fall through the cracks 20:44:36 vorlon: C&W is a tradition quite well settled. I'm sure we won't miss it. And bubulle will surely help us organize its details even if he's not coming 20:44:37 the point is, all the coordination that would normally have been done with bubulle needs to be done with someone else, so we (local team) need to know who that is 20:44:54 What I wonder is if bubulle might be willing to still lead it remotely? 20:45:13 nvm 20:45:22 dunno 20:45:24 need to get new glasses 20:45:43 bgupta: for the wine? 20:45:50 We usually use plastic, although it's not as good. 20:45:54 does someone want to take the action to follow up with the cheese team? 20:45:59 (trying to avoid giving myself all the actions here) 20:46:04 vorlon: looks updated, have to monitor if it does so in the future. it makes no sense that it didnt. 20:46:09 Clint: alcohol-serving is an issue on campus only 20:46:10 C&W will be on campus correct? IIRC we have to hire Aramark (to be able to have alcohol?), want me to research that? 20:46:29 Ganneff: huh, ok... I wonder if someone else poked it during the meeting without saying 20:46:35 gwold for my eyes. 20:46:40 no. 20:46:41 gturner: no, we definitely *don't* want to deal with the on-campus nonsense 20:46:55 its a git-svn, and that misbehaved for no reason 20:47:05 gturner: the C&W party is an "everybody bring a bottle to share" affair - completely incompatible with the requirement to have a licensed pourer 20:48:05 gturner: we have had to have C&W outside our usual premises several times in the past... (at least once). But that should be no *big* issue. 20:48:26 vorlon: Weather and local law permitting, I have loved it when we have C&W in open spaces (park, garden, ...) 20:48:31 * vorlon nods 20:48:34 park may indeed be an option 20:48:51 but what I want for the moment is someone to care about taking the action item ;) 20:49:01 it would certainly help against excessive smelliness 20:49:04 vorlon: and the action is... Sending a mail to bubulle to check on him? 20:49:09 Local team can certainly hunt down venue, but someone needs to coordinate everything. 20:49:15 vorlon: Thinking that do to venue restrictions, you are mentioning that perhaps someone in portland needs to be leading C&W 20:49:18 gwolf: contacting the cheese team to find out who will drive this 20:49:20 i could do some research, park policies and what not 20:49:27 vorlon: Ok, sign me for it 20:49:51 #action gwolf to follow up with cheese&wine team (from past DC) to identify point of contact for this year 20:49:54 gwolf: thanks 20:50:34 gturner: right, I don't think we need to get those details nailed down yet - I think it's great if you helped coordinate the local side of this, once we know who's calling the shots for the event :) 20:50:49 #topic AOB 20:50:51 additional topic: networking infra update 20:50:59 #topic Networking Infra Update 20:51:01 kees: go! 20:51:04 I owe an email update on networking, but basically, we'll make things work nicely. we may need to provide our own Wifi infrastructure if we want to avoid all th 20:51:07 e craziness with access tied to individual email addresses, captive portals, etc. 20:51:18 bgupta: (any chance you'd be willing to give a sponsorship team update after this?) 20:51:31 it sounds like we can do anything we want with hard-wired networking, but changing the existing wifi is "hard" 20:52:02 in theory, we could also bring in our own ISP, but I'd like to avoid that just because the config overhead hurts me. 20:52:05 I don't have an update atm.. 20:52:06 kees: ok - own-wifi is something we've happily done in the past. And I guess the campus wifi would still be available in the park etc., so people *could* make use of that 20:52:07 kees: we generally had better experience when we just did our own wifi 20:52:23 yeah, I suspect we'll be better with our own wifi. 20:52:38 we'll have public IP space where we want it, that's no problem 20:52:56 (Other than perhaps we need to raise a lot more than we have) 20:52:57 and since all the students will be gone, we should have tons of bandwidth. 20:52:58 kees: the question has been raised a few times about whether we're expected to pay anything for the network drop... my understanding has been that it's included in the venue space. Is that your understanding too? 20:53:29 right, for "simple" things, it sounds like it's included. for anything too crazy, it's just a matter of paying for their time to do it. 20:53:38 I don't get the sense it will be a problem. 20:53:49 ok 20:53:55 one thing to note, however, is the difference between conference space and residence. 20:54:22 residence has both wifi and wired, but the wifi there is the same tied-to-email captive portal stuff 20:54:37 doing our own wifi for the residence seems ... prohibitive 20:54:54 I don't think we need it so much for the residence 20:55:01 that was my hope as well 20:55:02 We are expected to rest at the residence 20:55:05 yeah, agreed 20:55:10 well, not with the "rest" part ;) 20:55:11 ...Network is wanted, but not hard-needed. 20:55:26 there will be campus wifi access at the residence, we just won't control it 20:55:39 right, so we should make sure we maintain expectations for attendees on that part of it. 20:55:42 vorlon: Rephrase. We are supposed to work at the venue rather than at the residence. 20:55:57 kees: sounds good 20:56:01 The residence hall is our planned late-night hacking, though. 20:56:02 .oO(will give people a reason to get out of bed if they cannot get the talks via wifi ;-) ) 20:56:07 Does that affect how we feel about networking there? 20:56:12 that's it from me; I'm still trying to nail down specifics. 20:56:35 harmoney: can we add some wifi for that space, without covering the rest of the residence? 20:56:42 I feel good about networking -- we just need to stay ahead of the curve on getting it designed, implemented, and tested. 20:56:42 harmoney: not really... late-night hacking is usually not a high-bandwidth affair, and if they don't get to do after-hours hardware hacking, well, so be it 20:56:53 harmoney: ah, we won't have late night access to the venue? Hmm... But yes, we can set up a "good network spot", not covering all rooms and stuff 20:57:36 #topic sponsorship 20:57:39 the specific hack lab location we can handle. it's all the bedrooms that will be hard. 20:57:46 kees: Cool beans. 20:57:53 bgupta: even if you can't give us a formal update, I'd like to touch base on sponsorship, however vaguely 20:57:56 since it's an important topic :) 20:58:42 even if it's just to give us platitudes about how everything is on track 20:59:14 how do you feel about progress on contacting past sponsors / Portland local sponsors? 20:59:30 kees: if people care they'll probably set up their own wifi from the wired network (unless we try hard to ban that sort of thing -- I presume the reason not to is that it's too much effort, rather than the locals getting upset) 21:00:38 fil: for the bedrooms, right. people should bring their own WAPs. it's not banned, but we should avoid calling attention to it. :) 21:00:51 well, I guess bgupta may have stepped away from the keyboard... he was never really here, after all 21:01:06 so let's take up the sponsorship discussion out-of-band (possibly on list) 21:01:25 #topic AOB 21:01:28 anything else? 21:01:32 or can we gavel out? 21:02:09 (btw, just sayin', if anyone does have some cycles to spend helping with the sponsorship team, I know they are always eager for more volunteers... sponsorship makes or breaks DebConf) 21:03:12 * gwolf is tempted to gavel out... to find out what does "gavelling" precisely mean) 21:03:46 http://www.youtube.com/watch?v=mC2_Sd2ewYY 21:04:22 #endmeeting