18:59:45 <madduck> #startmeeting
18:59:45 <MeetBot> Meeting started Mon Apr 13 18:59:45 2015 UTC.  The chair is madduck. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:59:45 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:59:56 <madduck> #topic Preamble / last meeting
19:00:05 <madduck> let me say on thing about last meeting and today
19:00:18 <madduck> some of us were at my office while participating in the IRC meeting
19:00:23 <madduck> on top of that, meetbot failed
19:00:35 <madduck> so we don't really have minutes, and it was a tough meeting too, especially for those not locally present
19:00:40 <madduck> we learnt, and apologies anyway
19:00:42 <madduck> today
19:00:46 <madduck> we will collect the pieces
19:00:52 <madduck> marga has asked me to chair
19:00:57 <madduck> #addchair marga
19:01:01 <madduck> #topic role call
19:01:03 <madduck> who's here?
19:01:06 * DLange waves hello
19:01:07 <marga> that's not for last week, but rather 3 weeks ago, last week there was no meeting, as there was no quorum
19:01:08 <jathan> Hallo
19:01:17 * sladen listening
19:01:18 * Zugschlus 
19:01:24 <jathan> I am attending.
19:01:31 <_rene_> hi
19:01:42 <azeem> hi
19:02:16 <madduck> RichiH excuses himself
19:02:27 <madduck> alright, let's move on.
19:02:32 <madduck> #topic visa invitation letters
19:02:32 <hvhaugwitz> hi
19:02:43 * hvhaugwitz partly here
19:03:03 <madduck> the suggestion here is that the Verein creates a Ressort and appoints _rene_ as leader so that he may sign the letters officially, with a German-sounding name
19:03:23 <madduck> if _rene_ is okay with that, I will work with RichiH and/or Ganneff to make it happen this week
19:03:34 <madduck> the letters should go out ASAP, as far as I understand, right n0rman?
19:03:53 <marga> I'm ok with the plan as long as _rene_ acks
19:03:54 <madduck> So _rene_, please say if you see yourself able to print/sign/send 5–10 letters this week?
19:04:55 <madduck> hm
19:04:56 <_rene_> Friday/on the weekend, yes
19:05:10 <madduck> ok, any objections?
19:05:15 <madduck> n0rman: does this sound ok?
19:05:26 <madduck> _rene_ is on the visa team, so this seems sensible
19:05:45 <azeem> +1
19:05:53 * hvhaugwitz aggrees
19:05:56 <Zugschlus> +1
19:06:00 <madduck> #agree _rene_ will become official Verein visa signer this week and the aim is to print/sign/send the outstanding letters this weekend
19:06:04 <madduck> moving on
19:06:09 <madduck> #topic conf dinner
19:06:21 <madduck> while loni was travelling, she asked me to engage
19:06:52 <madduck> we were late (budget) and the guy was a bit angry about it, but it's under control again
19:06:54 <n0rman> sorry, ok to me :) I'll coordinate with _rene_ +'tahnks
19:07:20 <marga> why was he angry?
19:07:33 <madduck> basically there will be free drinks for a longer period and we will buy kegs and boxes of wine and serve to those who pay extra while supplies last
19:07:42 <madduck> marga: because he wanted a commitment by 2015-03-31
19:08:05 <madduck> so we have two things to figure out, and I was hoping nattie would take this on, or someone on her team:
19:08:08 <marga> Regarding choice, the wiki says this will be coded in the badges, I don't like this.
19:08:17 <madduck> that is one of the two things
19:08:23 <madduck> what don't you like?
19:08:36 <DLange> "oh, you have the booze mark as well..."
19:08:43 <marga> Because the choice of one single dinner would be visible for everyone the whole wekk
19:08:54 <madduck> marga: wait…
19:09:08 <madduck> I don't think it's reasonable to expect people to make a choice before arrival
19:09:14 <madduck> so it won't be on their badges
19:09:23 <marga> ok
19:09:25 <madduck> so we either have to create a new set of badges anyway
19:09:34 <madduck> or find some sort of other means to tag visibly
19:09:38 <marga> Ah, if it's a just-for-that-night badge, that's fine
19:09:43 <marga> That's how it was done for DC13
19:09:45 <madduck> and also track who paid for the beer/wine package (e.g. 5€/person)
19:09:56 <madduck> nattie: can we do this for dc15?
19:10:15 <madduck> hand out just-for-the-night badges coding the dinner choice as well as whether the person paid for alcohol?
19:10:16 <maxy> Beer stickers to add to the badge
19:10:34 <madduck> #info we can use stickers to track who paid for alcoholic drinks
19:10:34 <marga> madduck, the exact request would be: upon registering at FD, people are asked about their choice of food + booze payment and then given the appropriate badge?
19:10:39 * DLange notes down more stickers to print :)
19:10:44 <DLange> beer whirl
19:10:48 <madduck> #info dc13 had for-the-night-only badges to identify dinner choices
19:10:59 <Zugschlus> clothespin on the badge. nothing to print, case closed.
19:11:04 <madduck> DLange: we can use some off-the-shelf stickers for this
19:11:24 <madduck> marga: yeah, at least the choice of meal then would be gopod
19:11:28 <madduck> to make sure everyone chooses
19:11:31 <madduck> our only chance really
19:11:38 <madduck> and purchase stickers later, even during the night.
19:11:49 <larjona_m> hi. I'm late and in the mobile.
19:12:10 <madduck> #info make dinner choice when picking up badge if it's okay with front desk and sell stickers for alcoholic beverages, even on the night
19:12:10 <DLange> madduck: we can print enough for a few euros to make them unique and less easy to "accidentially confuse with another on you stuck on the badge"
19:12:13 <marga> #info If possible we would need: upon registering at FD, people are asked about their choice of food + booze payment and then given the appropriate badge.
19:12:31 <marga> nattie, ^ do you think the above is possible/
19:12:42 <madduck> DLange: not sure we need to protect against this attack vector. But if you're in charge, you get to decide ;)
19:13:49 <madduck> . o O (we should have one IRC channel per agenda item so that we could be truly asynchronous)
19:14:05 <madduck> DLange, nattie: ping?
19:14:31 <madduck> . o O (or RTC meetings…)
19:14:47 <madduck> whatever, we can decide this later
19:14:49 <madduck> moving on.
19:15:03 <madduck> #topic floor plans, booths, job fair
19:15:04 <DLange> This should be easy: We print a list of registrants, write their coming and menue choice and booze payment in there
19:15:28 <DLange> and then give them badges and stickers according to choice and payment
19:15:28 <madduck> #topic conf dinner #2
19:15:38 <madduck> DLange: will you procure the stickers?
19:16:17 <DLange> I can sure. This can be done a week before the event. This is no long-lead item at all but I'll make mayself a reminder to not forget.
19:16:20 * hvhaugwitz has to go, sorry...
19:16:27 <madduck> #action DLange to procure the stickers used to identify those who paid for alcohol
19:16:30 <madduck> #topic floor plans, booths, job fair #2
19:16:48 <madduck> DLange: what do we have on this item (which is a prereq for sponsor fulfillment)?
19:17:17 <DLange> I have sent the plans to Zugschlus and he has git access now
19:17:29 <DLange> but afaik he has not yet been at the venue
19:17:34 <Zugschlus> and I am late with my work
19:17:43 <Zugschlus> it is significantly harder to get a helper than I thought
19:17:45 <DLange> thkoch didn't go to HD because of the weather over Easter
19:17:50 <DLange> he went $elesewhere
19:17:54 <DLange> -typo
19:18:14 <DLange> #link https://wiki.debconf.org/wiki/DebConf15/Germany/Venue#Scouting_tasks
19:18:30 <DLange> any ETA Zugschlus?
19:18:38 <thkoch> sorry, but it would have been too hard on my wife ... :-( We still want to go to the venue on one of the next long weekend
19:18:41 <thkoch> s
19:18:54 <Zugschlus> DLange: I hope next week
19:19:12 <Zugschlus> thkoch: keep me posted, we can do things together or at least beersign
19:19:17 <DLange> that would be great, Zugschlus
19:19:52 * Zugschlus closes the lame excuses book for today
19:20:07 <_rene_> Zugschlus: are you then also able to do "how to get there"? I have (bad, crowded) photos here, but.. <insert (lame) excuses here>
19:20:22 <madduck> well, we need to get to sponsors in May, so if you guys can finish this within the next two weeks, that should be enough for DLange, no?
19:20:28 <Zugschlus> _rene_: tell me more about that task
19:20:36 <madduck> Zugschlus, _rene_: it's an item later on
19:20:43 <DLange> madduck: yes, that still works timing-wise
19:20:43 <_rene_> ok
19:20:50 <madduck> ok
19:20:57 <Zugschlus> what has network scouting to do with the sponsors?
19:21:09 <maxy> Do we know how many sponsors want a both right now?
19:21:14 <madduck> #info Weather and other plans spell delays, next plan is to measure the venue and get detailed plans by 2015-04-27
19:21:23 <madduck> maxy: no, we have not engaged until we know what we could offer
19:21:30 <madduck> Zugschlus: good question
19:21:46 <madduck> DLange: you have the plans now, right? Aren't they enough to see what we can offer?
19:21:57 <marga> madduck, I think that's the wrong order of things, but that's the next topic, isn't it?
19:22:06 <DLange> we have plans but no measurements of the spaces
19:22:09 <sladen> there is quiet likely to a pre-existing plan as prepare/delivered to the fire brigade.
19:22:16 <DLange> so we still need to fill these in
19:22:29 <DLange> sladen: we have that and it's in the git
19:22:40 <madduck> DLange: do you *do* need the guys to measure the venue before you can make a plan on booth spaces, right?
19:22:40 <DLange> but again, not to scale, not measured
19:22:43 * sladen nods
19:22:53 <Zugschlus> DLange: the plans do have a Maßstab, dont they?
19:23:06 <DLange> madduck: yes because I otherwise don't know how many tables and chairs fit in
19:23:30 <madduck> #info Figuring out the number of booths we can set up for both showcases and job fair requires measurings
19:23:32 <Zugschlus> DLange: can you give information which rooms you need measured ASAP?
19:23:33 <DLange> Zugschlus: no, they are fire-rescue plans
19:23:54 <DLange> Zugschlus: it's in the wiki, see link above
19:24:01 <madduck> #action Zugschlus thkoch DLange to coordinate and to deliver measurements in two weeks, 2015-04-27
19:24:13 <madduck> can we move on?
19:24:22 <Zugschlus> yes
19:24:32 <DLange> yes
19:24:36 <madduck> #topic sponsor fulfillment
19:24:59 <madduck> Is there someone ready to liaison to sponsors in May?
19:25:12 <madduck> i.e. communicate to them what we offer and engage in further planning?
19:25:26 * MeanderingCode tunes in
19:25:39 <madduck> even without knowing the measurements or numbers, this could be prepared already and ideas collected.
19:25:40 <marga> It's not like I don't have things to do (mainly Bucharest), but if nobody else volunteers, I can do it.
19:25:51 <marga> I think we should have done this already
19:25:52 <DLange> I have the feeling many sponsors expect you to keep the communication going, madduck
19:26:06 * madduck nods to marga, not DLange
19:26:18 <madduck> in some ways, yes, I am probably the primary contact
19:26:40 <madduck> but this doesn't mean I now have to reach out. payments are done, and that was my job
19:27:41 <madduck> but I'll work with marga…
19:27:58 <madduck> #action marga madduck to engage with sponsors regarding fulfillment
19:28:09 <madduck> #topic Open weekend plans / webpage
19:28:21 <madduck> santiago is not here, maxy can you say anything here?
19:28:36 <maxy> Not really.
19:29:07 <maxy> I haven't spoken with santiago about the open weekend.
19:29:26 <madduck> should we put this back on the agenda in two weeks, i.e. will you be able to get onto this between now and then?
19:30:08 <maxy> And I'm not completly sure planning and promotong the openweekend isn't against the content plans.
19:30:36 <maxy> Anyway, I'll bring this to the content table
19:30:47 <madduck> well, i am just talking about structure, not content
19:30:48 <jathan> Related to Openweekend I can help
19:31:15 <jathan> I writed the initial proposals in the Wiki
19:31:33 <jathan> So any need count with me
19:31:36 <madduck> maxy: also, we promised this open weekend thing to people before the content team was formed. Yes, this sucks a bit and maybe should have been done differently, but the solution now can't be that we scratch the idea because the content team doesn't like it.
19:32:04 <madduck> on the upside of things, we didn't promise any specifics, so all we have to do now is move forward and propose a plan…
19:32:38 <maxy> jathan: If the content team aproves it, I'll be happy to organize it with you.
19:33:17 <madduck> maxy: so can we have a final statement from the content team by 2015-04-27 so we can move on?
19:33:38 <jathan> Ok
19:33:45 <maxy> Sorry my previous comment wasn't clear. The issue is not the openweekend but deciding the talks before the content team aproves them.
19:34:06 <madduck> ah, yeah, but as I said: we should define the structure
19:34:09 <madduck> the programme
19:34:10 <madduck> the slots
19:34:32 <jathan> We including me :)
19:34:34 <madduck> "keynote #1" — "lunch" — "workshop #1" — "party"
19:35:10 <madduck> jathan: yes, absolutely. your help will be invaluable! I am sorry it's such a mess, but this is a first time we're trying this, so it's hard to give clear(er) guidance
19:35:13 <maxy> So, apart from the structure and poking people to propose event that fit in the openweekend idea we are stuck till the talks deadline.
19:35:33 <jathan> Thanks Martin.
19:35:39 <madduck> that's fine if maybe we can announce a keynote and 1–2 other events, maxy
19:35:55 <madduck> it needs not be a final programme, but it needs also not appear as if we have no idea of what we're doing.
19:36:44 <madduck> here is hoping that in future years, we'll have a better timeline uniting all the important events (e.g. event submission vs. registration vs. PR) in a better way…
19:36:45 <marga> madduck, alright. Assuming the basic structure is there, how do you want to advertise it?
19:37:15 <jathan> It could be a good idea ask proposals for OpenWeekend schedule by email to all.
19:37:20 <madduck> marga: I think we should discuss this advertising thing in dc-team (!) and reach a decision about registration caps, reservations etc.
19:37:31 <madduck> jathan: please coordinate this with maxy
19:37:32 <jathan> And set a final date
19:37:36 <marga> madduck, ack
19:37:38 <madduck> marga: we have 348 registrations as of tonight.
19:37:43 <jathan> Ok
19:37:52 <madduck> we have 430 beds or so. we are basically mostly full.
19:38:07 <madduck> i mean, not yet
19:38:08 <marga> madduck, I know, this should be discussed in the next global meeting.
19:38:10 <marga> Not here.
19:38:15 <madduck> but getting to the point where we need to figure out a strategy
19:38:18 <marga> But yes, we will need to act on that.
19:38:21 <madduck> ok
19:38:22 <jathan> maxy: can you give your email address please?
19:38:36 <maxy> The schedule is already decided. It can be tweaked, of course but the one in the git seems to please everyone.
19:38:41 <madduck> #info registration activity vs. beds available needs a clear strategy on how to move on before further PR
19:38:58 <jathan> Ok
19:39:02 <madduck> maxy: maybe this could be finalised and announced?
19:39:07 <madduck> (and tagged)
19:39:15 <madduck> anyway, let's move on
19:39:22 <madduck> #topic Getting there webpage
19:39:36 <madduck> _rene_, Zugschlus, thkoch: can you three please coordinate this?
19:39:47 <_rene_> Zugschlus: that was what I was talking about earlier
19:39:52 <madduck> _rene_ has a draft but needs more photos, and thkoch/Zugschlus are going to the venue, so…
19:40:04 <Zugschlus> _rene_: is your draft in the wiki?
19:40:05 <_rene_> nah, I have bad photos
19:40:14 <_rene_> with many people in it :/
19:40:19 <Zugschlus> _rene_: give your bad photos and I'll take better ones
19:40:20 <marga> #action Maxy to send the schedule as finalized (previous topic)
19:40:22 <madduck> maybe thkoch could take this on and be responsible for it, seeing that Zugschlus already gets to measure the venue?
19:41:12 <azeem> I think what we need most right now is more top-level information, like "you probably want to fly into FRA if you're coming from farther away"
19:41:13 <Zugschlus> I can take the pictures on the way there, that's not a big deal
19:41:22 <_rene_> I've no idea why madduck thinks I have a draft, honestly. I have a planned stucture, but...
19:41:37 <madduck> sorry, misunderstanding maybe? I thought you even sent a file to me…
19:41:41 <Zugschlus> FRA or STR are almost equally good railroad-wise
19:41:48 <madduck> anyway, let you people coordinate this, ok?
19:41:55 <_rene_> azeem: we have that. well, not "you want to fly to to FRA" but "there's FRA, STR etc"
19:41:56 <marga> _rene_, I think we are talking about two different getting there pages
19:42:01 <madduck> #info what's needed first is a rough plan, details can be filled in later
19:42:04 <jathan> yes registration activity vs beds available sounds great
19:42:06 <_rene_> yeah
19:42:09 <marga> _rene_, you had the draft for the FRA page
19:42:12 <_rene_> madduck means HD Hbf to hostel
19:42:21 <marga> _rene_, that one should get published ASAP
19:42:22 <Zugschlus> FRA, STR, MUC, CGN, DUS, even HAJ
19:42:34 <madduck> #action _rene_ Zugschlus thkoch to coordinate the creation of photos and webpage to help people find their way, to HD and to the venue.
19:42:41 <marga> _rene_, then there's the other page that needs to get the extra photos
19:42:41 <madduck> let's move to the next topic, ok?
19:42:43 <_rene_> huh?
19:42:48 <_rene_> http://debconf15.debconf.org/travel.xhtml
19:42:53 <_rene_> ok, STR is missing, but...
19:42:54 * madduck waits
19:42:59 <azeem> is that linked from somewhere?
19:43:07 <marga> Yeah, is it linked?
19:43:16 <_rene_> "You can find information on how to travel to Heidelberg and/or the youth hostel here."
19:43:20 <madduck> _rene_: that is the "draft" I meant, no?
19:43:22 <_rene_> in registration.xhtml
19:43:40 <madduck> azeem will later make a tab for it, that's his speciality.
19:43:54 <marga> Ah, well, it's too hidden, I thought it wasn't published
19:44:03 <azeem> maybe we should combine that and "Dates" into "Information"
19:44:04 <azeem> or so
19:44:06 <madduck> #info http://debconf15.debconf.org/travel.xhtml is the draft I was tlaking about
19:44:13 <marga> azeem, sgtm
19:44:16 <madduck> #info http://debconf15.debconf.org/travel.xhtml should be linked from more places
19:44:34 <madduck> let's worry about this once the page is final
19:44:47 <azeem> well, people wanna buy tickets now?
19:44:49 <madduck> we have the action item
19:44:57 <marga> #info We should probably replace  "Dates" with "Information" and have this page linked there (as well as the dates and any other info)
19:45:07 <azeem> we already had inquires and last time I pointed them to the wiki cause I didn
19:45:12 <azeem> didn't know travel.xhtml existed
19:45:24 <madduck> azeem: ok, I am not trying to prevent it, just don't want to spend too much time discussing something here that needs not be discussed between everyone
19:45:43 <madduck> azeem: do you want to s/dates/information and link it etc.?
19:45:56 <_rene_> *sigh*
19:46:03 <azeem> _rene_: ?
19:46:21 <Zugschlus> I have a few improvements to the train part, of course. Is the source of the page in in git?
19:46:29 <azeem> zes
19:46:30 <_rene_> yes
19:46:32 <azeem> yes*
19:46:33 <madduck> Zugschlus: debconf-data/dc15.git/website
19:46:44 <Zugschlus> can I just commit or do you want a pull request
19:46:55 <marga> Zugschlus, just commit
19:47:02 <Zugschlus> k
19:47:27 <_rene_> azeem: not that I said in some meeting loong ago I was commiting it the  day after, but... since then it's there. months, basically.
19:47:44 <_rene_> so *sigh* because apparently noone noticed :)
19:47:53 <marga> _rene_, I guess some people have found it, it just not obvious and we should fix it.
19:47:58 <marga> Anyway, let's move on.
19:48:10 <madduck> #topic day trip
19:48:26 <DLange> again?
19:48:26 <madduck> Any developments here?
19:48:26 <azeem> _rene_: yeah sorry, I really thought you didn't get around to it yet :-/
19:49:11 <madduck> there seemed to be a lot more discussion about ideas in the past weeks
19:49:20 <madduck> but still, nobody wants to actually drive this to completion, eh?
19:49:22 <azeem> madduck: you wanted to secure buses
19:49:40 <madduck> azeem: yes, I am in discussion with bus companies
19:49:49 <azeem> cool
19:49:58 <madduck> it's not easy if you have to tell them that you have no plans. ;/
19:50:19 <azeem> my personal preference would be towards Speyer/Technikmuseum/something on/at the Rhine
19:50:39 <azeem> but I don't know what else is there, like hiking options
19:51:04 <DLange> 7away
19:51:10 <DLange> duh, sorry
19:51:13 <madduck> DLange: wait…
19:51:14 <madduck> t-shirts
19:51:15 <madduck> next.
19:51:18 <madduck> anyway, let's not discuss ideas or preferences here
19:51:27 <DLange> I know, I wanted to remove away status...
19:51:27 <madduck> #info no progress has been made unfortunately
19:51:37 <madduck> #topic T-shirts
19:51:45 <madduck> any news on this? I do have a question…
19:51:53 <DLange> I'm waiting for Valessio to come back with the two designs {nattie,madduck,me} asked for.
19:51:56 <DLange> He pointed at the debconf-wiki page on pre-made T-Shirt designs but no further updates received so far. We also need the logo's incorporated or on the back side in a somewhat appealing setup. Perhaps nattie has more but I haven't spoken to her over Easter.
19:52:01 <DLange> #link https://wiki.debconf.org/wiki/DebConf15/Artwork#T-Shirt
19:52:03 <DLange> At some point I'd need a distribution of T-Shirts sizes for {attendee,staff,video}-registrants so we can do the maths.
19:52:40 <madduck> DLange: nattie might be able to help, but of course we won't get final data until end of june
19:52:49 <madduck> apparently, in the past, moray just guesstimated them.
19:53:21 <DLange> that's most probably quite fine, the distribution should already be rather stable at 350 registrants
19:53:38 <madduck> … who have not reconfirmed™
19:53:40 <marga> Yes, you want to have extra of all sizes as people sometimes change
19:53:44 <madduck> a DebConf special…
19:54:04 <madduck> DLange: but we can definitely increase the total batch
19:54:15 <DLange> you get your size if you register well, you get what's available in any other case :)
19:54:18 <madduck> and sell
19:54:21 <DLange> sure
19:54:36 <madduck> i wanted to propose going for fairtrade shirts
19:54:42 <madduck> won't be doable within budget
19:54:50 <madduck> but given that we are quite well on the way with budget
19:54:54 <madduck> maybe this is something to consider?
19:54:57 <DLange> I wouldn't say that yet
19:55:26 <DLange> once we have the design, we'll get prices and that includes fair/organic options and then we can decide
19:55:39 <madduck> ok, good plan
19:55:49 <madduck> #info once we have the design, we'll get prices and that includes fair/organic options and then we can decide
19:56:03 <jathan> I said in last meeting that I would check options here in Mexico with Yakbek
19:56:14 <jathan> but talking with Nathi
19:56:17 <madduck> #info DLange wants distribtutions to do the maths, should be fairly stable by now
19:56:40 <madduck> #action DLange nattie to coordinate wrt numbers, maybe ask moray
19:56:52 <madduck> #info we can probably go quite well above 500 and sell shirts etc.
19:57:11 <jathan> She told me that Gunnar ex-girlfriend has been helping during some DebConfs with these
19:57:45 <madduck> i really don't think we should be shipping t-shirts from mexico
19:57:55 <jathan> So I wait until Nathi answer
19:57:58 <madduck> can we move on?
19:58:09 <jathan> Oh I see
19:58:13 <jathan> Yes
19:58:14 <DLange> did you ask your question, madduck?
19:58:19 <madduck> DLange: fair trade; yes.
19:58:22 <DLange> ok
19:58:26 <madduck> #topic conf bags
19:58:38 <madduck> DLange: can we assume that this will basically be done with t-shirts?
19:58:41 <DLange> yes
19:58:48 <DLange> also the banners
19:58:54 <madduck> #action DLange / t-shirt team in charge of conf bags and banners at the same time
19:58:58 <madduck> w00t!@
19:59:19 <madduck> alright, then i suggest we leave the rest for the next meeting and decide now how to move on regarding the schedule
19:59:23 <madduck> #topic Next meeting
19:59:38 <madduck> the "official" (ICS) schedule has us meet again next week
19:59:43 <madduck> and then every 2 weeks
20:00:12 <madduck> I think it would make sense to return to this schedule, but there were a few deadlines in the above at 2015-04-27 :/
20:00:37 <madduck> so, suggestion: next meetings: 2015-04-27, 2015-05-04 and then every two weeks?
20:01:10 <marga> I have no issue with meeting next week.
20:01:25 <DLange> ack from my side. I may miss the 27th though (travel). I'll let you know status/info offline before the meeting in that case.
20:01:41 <maxy> I would prefer to go back to the 20, and avoid having the global and local meeting the same day. :)
20:01:42 <madduck> and skip 2015-04-27 and convene 2015-05-04 and then hope that the 2015-04-27 deadline items are definitely done?
20:02:06 * madduck has visions of Douglas Hofstaedter
20:02:11 <DLange> sounds reasonable to me
20:02:31 <DLange> you can poke people between meetings as well
20:02:38 <madduck> maxy: ah, yes, 2015-05-04 is global team meeting, eh?
20:02:57 <azeem> why not just every two weeks from now on?
20:03:00 <madduck> no, -04-27 is global team meeting
20:03:06 <madduck> azeem: therefore ^
20:03:10 <azeem> ah.
20:03:30 <madduck> so next week and then 2015-05-04 and then every two weeks
20:03:56 <madduck> let's do that. and we can always make next week short or cancel it if not necessary
20:04:09 * madduck proposes to \#agree and \#endmeeting
20:04:40 <marga> +1
20:04:46 <DLange> +1
20:04:57 <_rene_> yes :)
20:05:04 <madduck> #agree return to regular meeting schedule, i.e. dc15 local team meetings 2015-04-20 and 2015-05-04 and forthnightly forthwith
20:05:07 <madduck> #link http://www.debconf.org/calendars/DebConf-team.ics
20:05:11 <madduck> #endmeeting