18:31:52 #startmeeting 18:31:52 Meeting started Wed Mar 16 18:31:52 2016 UTC. The chair is tumbleweed. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:31:52 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:32:05 phew, just in time 18:32:39 #link Agenda https://storm.debian.net/shared/pg75HcKvGVql2SS_PdlitmnPFMUTTYz4_A6mqT_LeDr 18:32:57 thanks 18:34:13 #topic Registration 18:34:18 #subtopic Timeline 18:34:20 hello! 18:34:28 are subtopics a thing? I never remember 18:34:40 not sure, think not 18:34:42 not on meetbot 18:35:03 yeah, not a thing 18:35:06 onwards! 18:35:06 We don't need to put the subtopic in minutes, only the agree 18:35:06 so i guess #topic Registration - timeline ? 18:35:13 #topic Registration: timeline 18:35:21 woo yay 18:35:31 https://wafertest.debconf.org/dates/ 18:35:59 not to be confused with https://wafertest.debconf.org/dating/ 18:36:02 I put dates without really checking things. i think deadline for registration is too late 18:36:05 heh 18:36:54 Also the CfP deadline, do we have reconfirm? Do we publish also the first debcamp days? And Do we have Open Days? 18:36:57 we have until 6 April to get final numbers to UCT, if we want a full refund 18:37:29 how final are these final numbers? 18:37:42 tumbleweed: OTOH bursaries cannot decide for 6 april, so some people not sponsored will not arrive 18:38:11 nattie: just we need to pay some penalities in case of missmatch 18:38:46 cate: yeah, I get that 18:39:42 nattie: page 5 of accommodation/Commercial\ Groups\ Booking\ Form_15.pdf in git 18:39:45 Now I set it to 3 and half week. We can go to 4 April, so nearly 3 weeks 18:40:04 we only take a 10% hit, and only if we reduce, not if we expand 18:40:07 I'm not sure about arrival days ... 100+ ppl will be there for Sat, 2 July. So why have them slob around for others that are not willing to be there (say) 11am? 18:40:42 DLange: I don't understand the question 18:41:18 tumbleweed: the https://wafertest.debconf.org/dates/ page contains "arrival days" for DebCamp and Debconf on their first days 18:41:27 and makes the second days first days 18:42:30 I don't mind DebCamp but for DebConf ~40..50% of the people will be there at 1am and another (say) 20% will make it for a 10am or 11am welcome session 18:42:36 We can move the arrival day one day earlier. But weekend was open days 18:42:37 so why waste that day? 18:43:00 DLange: sorry, I'm struggling to understand this 18:43:03 yes, so we want CPT students to have something to see Sat 10am 18:43:08 DLange: it says arrival day on 23 june, and 1st day on 24 june 18:43:15 DLange: do you think people will travel friday? 18:43:23 Saturday, 2 July Arrival day for DebConf, first day for sponsored people 18:43:35 DLange: i'm not sure where you're getting this figure of 100 people hanging around? 18:43:36 cate: they will have to unless they are Africans 18:43:37 DLange: I think that means first sponsored night 18:43:52 o/ 18:44:31 quite frankly, people will need to recover from the journey 18:44:43 But my dates are not final. I just put something, so let's decide when it is arrival day (so first sponsored date) nad when we will have opening cerimony 18:44:50 tumbleweed: we should sponsor people that arrive for DebConf Fri evening already and ... what nattie says 18:45:14 DLange: yeah, usually the arrival day is the last day of debcamp 18:45:40 so debconf15 started on the Saturday, right? 18:45:42 * tumbleweed looks at our booking, again 18:45:59 tumbleweed: and when is the departure day in the booking ;-) 18:46:00 first sponsored day for DebConf: Fri, 1 July // first day of DebConf (opening at say 10am) Sat, 2 July (which is also open weekend first day) 18:46:39 ginggs: yes 18:46:40 DLange: we've booked them to arrive 1 July, so we'll have to change that 18:46:43 err 2 July 18:46:44 I find too early 10am to start, you want that we take more than one week holodays 18:47:24 i seem to recall people arriving all through the day, missing the actual opening 18:47:35 the international flights usually land in the morning, and so people should be at UCT by midday. I expect few people to be arriving in the evenings 18:47:52 yeah... the opening ceremony is kind of a nice-to-have in terms of attendance, but sometimes it's not practical to be in time for it 18:47:55 but our actual opening is on the Sunday? 18:47:56 if we want to make an open weekend, we need to open Sat morning. A Debian welcome to DebConf session can always be later, if we want to. 18:48:26 well, the people dealing with the open weekend would presumably be orga who are largely already there for debcamp? 18:48:29 maybe give 2 days for people to arrive? Fri and Sat 18:48:32 (or local?) 18:48:47 ginggs: it was Sat. for DC15 and I recommend to make the same for DC16 18:48:56 DLange: open weekand are not DebConf days usually 18:49:04 tamo: people will arrive whenever they see fit (and the airlines) anyways 18:49:11 cate: isn't that a point for arguing semantics or something? 18:49:14 blergh, I thougght we'd nailed this stuff down months ago :( 18:49:15 this is just about what we plan & communicate 18:49:34 people have been asking if debconf dates were final, so they could book flights 18:49:37 and we've been saying yes 18:49:40 DLange: ok but was thinking registration could be over those 2 days perhaps 18:49:53 tumbleweed: https://wiki.debconf.org/wiki/DebConf16/ is correct and always has been 18:50:08 DLange: ah, that's the bit of information, I'm missing here, then 18:50:11 tamo: let's keep terms straight - registration is the stuff people do beforehand. 18:50:12 nattie: no, so we can have sessions on weeken but open cerimony later 18:50:14 tumbleweed: if you go to - say - SXSW you don't arrive at day 2 either 18:50:34 tumbleweed: I'm going offline, please email if you need stuff. 18:50:37 tamo: (not meant as criticism, just the same as the sponsorship/bursaries thing earlier) 18:50:51 'night indiebio 18:50:56 thanks indiebio 18:51:02 * nattie waves at indiebio 18:51:19 nattie: thanks nattie I was thinking more along the lines of people signing in etc 18:51:44 tamo: yeah, i'm sure there's a term we can come up with. not quite check-in or FD activities but something like that 18:51:49 basically, my department :) 18:51:51 DLange: the way I read https://wiki.debconf.org/wiki/DebConf16/ , debconf16 starts on Sunday 18:52:16 ginggs: if you do not want to take part in the open weekend 18:52:33 ginggs: that was my thought too 18:53:20 were we thinking that the wider open culture / hacking open weekend stuff would be on saturday, and more debian stuff on sunday? 18:54:12 tumbleweed: I thought that the atual Conference with talks etc start on the Sunday 18:54:18 tumbleweed: yeah, that's what I thought, too 18:54:39 do we have an Open Weekend or just a DebianDay on Sunday? 18:54:41 ginggs: the question is whether any of that will happen, without indiebio's involvement 18:54:58 indiebio left? 18:55:32 somewhat 18:55:35 h01ger: you may have noticed she hasn't been very involved, for a few months. She's restricted herself to supporting some areas of debconf 18:55:45 but left the centre stage 18:56:01 ic 18:56:29 so, how do we fix the dates now? 18:56:34 yes 18:56:39 * h01ger finds it hard to follow this years preparation as its very very much irc centric, hardly any mails. (i was thankful for azeem's last mail, btw) 18:56:42 azeem: what is an open weekend? 18:56:43 we've been on the first agenda item for half an hour, we have to pick up the pace 18:57:10 tamo: open weekend is like what we had. basically debian day x2 18:57:23 tamo: http://debconf15.debconf.org/openweekend.xhtml 18:57:26 maybe we can start on Saturday afternoon 18:57:40 (no booths for DC16 though) 18:57:45 nattie: ah ok would that be at teh begining of the conference? 18:57:49 yeah 18:58:23 DLange: thanks makes sense now 18:58:38 https://summit.debconf.org/debconf15/2015-08-15/ <- Saturday, 10am opening ceremony 18:59:05 we can move the opening ceremony to the afternoon, but I'd start the conference in the morning 18:59:21 why? 18:59:26 or we call Sunday "Debian day" and ditch the open weekend 18:59:41 because it's hard to communicate an open weekend is closed 2/3 of Sat 18:59:48 1/2 18:59:51 DLange: I would start it after lunch on the Sat afternoon gives people time to arrive 19:00:13 well, we can still spillover to Saturday morning in case we have too many talks to allocate 19:00:28 but maybe play it low for now 19:00:29 o.k. sounds like a plan 19:00:46 the job fair makes more sense on Saturday afternoon than on Sunday, though IMO 19:00:49 so opening ceremony 14:00 and talks before that if we have a too dense agenda otherwise 19:01:26 then again, maybe Sunday afternoon is just as well for the fair 19:01:39 DLange: sounds good 19:02:25 azeem: Sat worked well for DC15 but then the conference also started on Sat. I fear with the 2pm schedule people will "fly in lazy" and basically arrive for dinner on Sat. 19:02:48 So to protect the sponsor experience, I'd prefer the job fair to be Sun. under these circumstances 19:03:42 DLange: is the Job Fair normally so close to the beginning of the conference or do you have 2? 19:03:43 yeah 19:04:05 I think we have to move on 19:04:06 tamo: last year's job fair was the first ever 19:04:07 why not both? (job fair Ssturday and Sunday) 19:04:16 tamo: just one. The first one ever was at DC15 and then on the first day (Saturday) in the afternoon. 19:04:26 ginggs: too long, sponsors need to man booth 19:04:32 azeem: DLange ah ok I see 19:04:44 IIRC we settled on the dates we did, so that people flying in from the US could leave on friday night, and arrive before things really got under way 19:05:03 well, I think whatever the local team decides should work, but maybe check back with the sponsors team about the job fair 19:05:31 h01ger: yes, working on the list is something that we should be fixing, it's been on my mind 19:05:51 just send mails 19:05:54 I'm partly responsible for less list traffic - I'm hardly keeping up with it, never mind posting... 19:06:14 also irc meeting summaries are good, very good even 19:06:15 cate: the point of Open Weekend was precisely to make it part of DebConf, because we don't have resources to organise separate events, and a DebianDay with few people is just not good enough. 19:06:16 * cate is guilty. 19:07:01 I used to post meeting summaries, but I can't do everything 19:07:05 if someone can volunteer... 19:07:23 seriosuly 19:07:25 we're 40 min sin now 19:07:28 we have meetbot, who's interested can click http://meetbot.debian.net/debconf-team/2016/ . Not that hard. 19:07:30 and haven't made a decsision on the first topic 19:07:32 isn't that what meetbot is for? 19:07:35 we have 9 topics 19:07:42 DLange: meetbot doesnt send emails by itself 19:07:43 tumbleweed: so next topic 19:07:48 ok I can at least volunteer to drive meetbot next time 19:07:57 that would make the meeting notes easy 19:08:04 * h01ger apologies, didnt realize a meeting was taking place… 19:08:05 #chair highvoltage 19:08:05 Current chairs: highvoltage tumbleweed 19:08:16 h01ger: slap :) 19:08:27 tumbleweed: I pushed for proper minutes from the meetings for dc15, but generally the feedback was that meetbot is enough and everything on top a waste of time. 19:08:29 h01ger: you'd known about indiebio if you followed the ML, so don't hang it too high 19:08:32 h01ger: same time every week... 19:08:44 tumbleweed: just that i switched time zones :) 19:08:49 madduck: excellent, because it does wastequite a bit of time, writing summaries 19:08:50 so what's needed to be decided re registration? 19:08:55 h01ger: aha, i'll see you tomorrow :) 19:09:00 also i would have maybe noticed if there were a meeting reminder by mail or meetbot pingall 19:09:03 anyway OT 19:09:11 meetings are early in the AM for me 19:09:15 so, I can't usually do reminders 19:09:20 I'm only just awake and at my desk, in time 19:09:24 tumbleweed: i can do those if needed 19:09:26 but we *must* move on 19:09:51 fixing the dates formally would be nice now. And fixing https://wafertest.debconf.org/dates/ afterwards then (as in after the meeting) 19:09:51 are we happy with the dates on https://wafertest.debconf.org/dates/ ? 19:09:57 no 19:10:22 I recommend: no reconfirmation (we have no time for this) 19:10:47 * h01ger lols 19:10:48 DLange: people who don't get sponsorship will maybe not cencel 19:10:55 and then fix the arrival day for DebConf to be Friday with the Sat. 14:00 opening as we said earlier 19:11:02 no reconfirmation is a bad idea 19:11:05 reconfirmation is useful 19:11:24 those dates transition from debcamp to DebConf with no mention of debian day / weekend though 19:11:27 far more people register than actually come 19:11:43 but we're too late for this. Who registers now has to pay after beginning of April or we (as in DebConf) pay the fee 19:11:52 let's talk about why reconfirmation is useful 19:11:56 people haven't booked tickets yet 19:12:03 because they haven't been able to apply for sponsorship, etc 19:12:21 DLange: if there is no reconfirmation you will order more beds and more food than you need -> you waste money 19:12:27 reconfirmation can be a useful way to get final dates out of people 19:12:40 I don't know how hard it is to get people to reconfirm, though? 19:12:56 h01ger: no, we underbook and who's late may not get a space if UCT fills up (which is unlikely though) 19:12:57 its not hard at all 19:13:02 DC13 had 14 day reconfirmation, so I think we have time 19:13:30 cate: we need to pay the venue or cancel beds 45 days before DebCamp 19:13:54 So we book, we odn't sponsor people and we need to pay venue and food extra? 19:14:20 DLange: no reconfirmation doesn't mean that people will not cancel from DebConf, just they don't tell us 19:14:24 yes, we could as well have sponsored them in that szenario 19:14:27 #info Notice period to venue is 45 days before DebCamp. We need good numbers to work with by then 19:14:34 * nattie agrees with cate 19:14:58 cate: which is why madduck has said for month there should be a fee 19:15:12 a fee for what? 19:15:13 not only madduck 19:15:22 for registering for accom and not turning up 19:15:26 any registration fee to make people show up 19:15:29 We are late on opening registration, so things don't go as programmed 19:15:43 right, so now we need to adjust 19:15:48 we will be billing people for accom, if they aren't being sponsored 19:15:59 maybe we really need reconfirmation from sponsored attndees? 19:16:20 We could hide the reconfirmation on dates, and think it later 19:16:21 and that means getting as good data as possible to the venue within three weeks and then who's later may have an issue 19:16:24 h01ger: the idea is: registration costs X (which can be waived, of course) and the money is refundable on site, for vouchers, swag, towards the bill, or paid out in cash. 19:17:04 people who will not show up will not pay fees 19:17:06 tumbleweed: maybe we need fine print saying that sponsored people who don't show up will be invoiced in full? 19:17:32 Does madduck volunteer to track payments with SPI? and to help people without a credit card? 19:17:38 perhaps everyone can be charged a deposit for accommodation? 19:17:50 you need the money up front, madduck. It's not about sanctioning people but about making them think, plan and communicate 19:17:52 madduck: I think we forgot about that plan somewhere along the way, yes 19:17:56 and then those that arrive and are sponsored can be refunded 19:18:00 cate: there are providers for this. 19:18:01 in all honesty I think that discussion is big and would be better suited for outside this meeting 19:18:06 yeah 19:18:09 well, it really boils down to what h01ger said: so far we never invoived people who didn't show up at all AFAIK 19:18:10 we're not going to get through this meeting 19:18:14 reconfirmation is much easier 19:18:15 sponsored people are expected to pay for their own transport 19:18:22 if start doing that, it should be *very clear* 19:18:23 (and then get a refund) 19:18:26 +we 19:18:27 ginggs: that is essentially the same as the idea with charging for registration. 19:18:36 azeem: yeah, it's too late for such a big change, I think 19:18:38 Sponsored people not showing up will have penalities. just last year someone mixed the badges on final day, so we need to reconstruct them 19:18:53 can I action a discussion for how payment will work for no-showers, or if it's a good idea for DebConf at all? 19:18:58 cate: do you have a list of people who abused our financial aid programme in the past? 19:18:59 also, reconfirmation is a way for people to say they are (not) coming. this is needed, with fee or without. 19:19:15 a fee gives no advantage whatsoever, but yet increases the work and will piss people off. 19:19:18 I think I agree with h01ger, it's too late this year to start experiments 19:19:40 it's too late to do as every year 19:19:47 madduck: we tracked them (the non-sponsored people with no-show. but I remember only one in dc12 which were no show in dc11 so sponsorship was denied 19:19:58 so maybe a discussion should be scheduled now for Montréal 19:20:02 we want people to be happy. 19:20:15 h01ger: if we have to pay a fee, it's only fair to pass it on 19:20:25 but I'd like to table this discussion 19:20:30 and move on 19:20:34 +1 on that 19:20:37 #topic Registration - Form feedback 19:20:47 https://titanpad.com/DC16-registration-form-feedback from line 190 19:21:00 #action Schedule a meeting to discuss no-shows and what their responsibilities/penalties would be. 19:21:12 tumbleweed: if there is no reconfirmation, how should people tell there are not coming? that fee is in a fact just a poorly designed reconfirmation system which is painful for everyone. us and them. 19:21:15 no new questions if not really necessary, just check inclusiveness and clearness 19:21:18 h01ger: we've moved on 19:21:19 s#tumbleweed# 19:21:52 tumbleweed: and forgot to finish the "timeline" subject? ;) 19:22:08 h01ger: we can't there is'n time to finish this discussion and, get to everything else on the agenda 19:22:11 as said earlier, we need the invoice address for UCT as well (they need to have it on file for credit card payments in the no card present case) 19:22:13 I should have moved us on half an hour ago 19:22:20 h01ger: tumbleweed will do an executive decision about dates. 19:22:47 no, we can discuss it after the meeting 19:22:50 but we cant't derail the meeting with it 19:22:58 tumbleweed: I tried the registration form last night, it's very nice already 19:22:59 now, can we all please go back to the topic 19:23:00 DLange: the billing address is already there, or you mean other billing address? 19:23:20 line 306 19:23:25 cate: no the same, just not only for prof and corp attendees but also for non-sponsored people in general 19:23:45 ah, so to increase the visibility cases? 19:24:18 yes, too, I'd move it up to after the radio buttons where you select the attendee level 19:24:19 DLange: ah, have they told us they need the address? 19:24:31 I didn't see any such discussion 19:25:08 tumbleweed: they have it in their form 19:25:35 OK 19:25:58 anything else here? 19:26:25 next topic before we have other questions ;-) 19:26:37 #topic Registration - Inoframition for attendees 19:26:39 grr 19:26:42 tyop 19:26:52 smirk 19:26:59 oh, sorry sirmk 19:27:02 cate: I started working through your titanpad this morning, but haven't got very far 19:27:12 * TyopFiary blesses tumbleweed 19:27:14 DLange: do you have the links on titanpad? 19:27:27 https://titanpad.com/DC16-registration-text-editing-session 19:27:32 #link https://titanpad.com/DC16-registration-text-editing-session 19:28:15 DLange: links are automatically picked up, even without #link fyi 19:28:45 madduck: thy 19:28:52 (what is #link for then?) 19:28:55 nafc 19:29:05 well, we all just need to have a look through that afterwards? 19:29:12 So there were some question on when, how people will pay conference fee, accommodation, bed sheets, and food organisation 19:29:26 yeah 19:29:30 so for those attendee info pages, I want to convert a whole bunch of things we would've put on the wiki for web pages so that it's all on one place 19:29:56 The rest should be standard, but please check 19:29:59 not sure how that would fit in with tamo's design ideas so perhaps some extra design would be needed or maybe we can re-use some existing layouts 19:30:07 that makes total sense. But it's fine if that happens -say- until next weekend 19:30:18 I could have sworn bedding was available for vacation bookings of the residences. We must ask them 19:30:25 I've been meaning to get in touch with tamo again, will do tomorrow or friday 19:30:47 highvoltage: sure we can def relook it to fit in with the info 19:31:14 tumbleweed: as far as I know bedding is included? 19:31:34 #action confirm status of bedding with uct accomodation 19:31:36 tumbleweed: we can double check that though 19:31:51 tumbleweed: if it is not what then? 19:32:09 tamo: yeah, good question 19:32:21 tamo: put it on the packing list for people and/or offer a cheap buying option on-site 19:32:39 it's shitty to have to buy bedding, we'd want hire I guess 19:32:54 this is winter, you want to be warm, too 19:32:57 DLange: sure will do, we could also look into cheap bedding 19:33:15 couldn't hire 200 of these in Germany, but we'll see 19:33:16 is anyone taking this action item? 19:33:19 or buy / donate to charity perhaps (might make people feel better about having to pay for temporary bedding) 19:33:20 it's no dealbreaker now 19:33:23 tumbleweed: hire def but pep stores have cheap stuff! haha 19:34:17 tumbleweed: like the option of giving it to charity they def could use it, but maybe UCT would buy it from us? 19:34:41 let's talk to them before we have this discussion, otherwise it isn't very useful 19:34:44 let's cross that bridge if and when we get there, should be quick to check what the actual status of bedding is. 19:34:55 highvoltage++. Let's move on. 19:34:56 tumbleweed: lets find out first I'll send an email to Kristen tomorrow to find out 19:35:06 tamo: thanks 19:35:07 tamo: could you cross check the food part? 19:35:27 cate: what do you mean? 19:35:29 the food part of https://titanpad.com/DC16-registration-text-editing-session that is 19:35:55 we can have Debian duvets made 19:36:03 who wouldn't buy one of those? 19:36:04 yeah, I was already on next subsubtopic 19:36:38 #topic Registration: opening 19:36:42 when we're ready? 19:36:47 it sounds like we have lots of details to get through 19:36:56 tumbleweed: cate you mean the breakfast? No not yet but on my list for this week 19:37:22 tamo: I really don't know. It was done today by DLange, but he had also some questions 19:37:35 tumbleweed: I'd open tomorrow. What gets fixed by when you wake up tomorrow is fixed, the rest we do during the next day or two. 19:37:39 cate: ok 19:37:54 We need something sensible, we can adjust/expand later 19:38:13 DLange: I wake up early tomorrow :) 19:38:28 right, so we say R300 for food and give the details on a wiki page when we have it 19:38:31 OK, so we aren't seeing any blockers, yet 19:38:41 ginggs: :) that would be cool 19:38:48 I'm sure we're going to get feedback from early signups 19:38:53 the form is done once you move up the invoice field so we can go with it 19:39:01 I can do that now 19:39:08 ginggs: I like the way you think 19:39:23 and then we need the export and further fixing of the support pages within a very short timeframe 19:39:25 the next agenda item links to a private sandstorm grain 19:39:30 tumbleweed: we forgot about conference fee. Do we pay at the site? 19:39:37 cate: we're working it out 19:39:41 ah ok 19:39:49 cate: I think we'll be able to do it by e-mail between registration and arrival 19:40:02 #topic Registration - announcement 19:40:08 can anyone post a public link? 19:40:12 or should we just move on? 19:40:40 https://storm.debian.net/shared/XwJVKQxdy-FzWvu_0Y9cVOtt50pKp7I2-i7nIMGf_4v 19:41:15 Because we have no new question on the form, we can already open (IMHO) and just prepare final text befor to announce 19:41:20 OK this depends on us getting our dates in a row 19:41:25 (so does opening registration :P ) 19:41:57 I should update the deadline in the announce 19:42:16 But than I think we should put the thing to larjona and publicity, right? 19:42:41 yep 19:42:50 and we must also advertise it within south africa (and africa) 19:42:54 indiebio had some ideas here 19:42:57 cate: would you like that to be an action or are you noting that for yourself? 19:43:59 tumbleweed: who would your target market be in the advertising? 19:44:08 highvoltage: an action, but I would not like to put the ball on larjona if she doesn't agree 19:44:46 tamo: geeks, debian users - basically, just the tech scene 19:46:17 so let's see with larjona, or we will find tomorrow an alternate way 19:46:53 tumbleweed: ok so would you want technical collages and universities as well as companies maybe someone could research and put a list together 19:46:53 #action larjona (or cate) to get the registration announcement out 19:48:07 tamo: discuss that with the press team? 19:48:08 tamo: we could also get in touch with Yvonne who was in Heidelberg who knows about reaching African women 19:48:17 tamo: for debian day/weekend we want as many people as possible who might be interested in Debian. For DebCamp we certainly don't want randoms to show up that want to be entertained, it's strictly for people who want to use that time to work on debian 19:48:31 (anyone correct me if I'm wrong about debconf) 19:48:36 (I mean debcamp) 19:48:36 nattie: yup sure we are still in contact almost every month 19:48:44 tamo: awesome! 19:49:01 tumbleweed: sure 19:49:06 highvoltage: you are reminding me that maybe debcamp is a little too prominent in the registration form 19:49:09 highvoltage: completely correct 19:49:10 but we can talk about that, later 19:49:18 highvoltage: sounds about right. i mean, there will also be orga people about doing stuff, but that's the same 19:49:47 moving on 19:49:55 #topic Call for Papers 19:50:12 wendar said we should be good to open submissions immediately 19:50:19 tumbleweed: not really, but debcamp should certainly not be marketed at the general public 19:50:22 do we have a call for papers in progress? 19:51:08 What is the deadline for CfP? We will announce together with registration? or one day delay? 19:51:21 no reason not to announce it with registration 19:51:31 (to my mind?) 19:52:24 just for visibility. Some time we did together, so we can also do it this year 19:53:04 tumbleweed: we have the text for the CFP ready 19:53:43 gotta link, wendar? 19:54:19 https://titanpad.com/1YVOp0C6vG 19:54:46 It's in email, larjona asked for it 19:54:49 if the cfp is ready to go, why not just send it now? 19:54:54 long, so I think we need to mails 19:55:02 two 19:55:17 madduck: because talk submission isn't open? :) 19:55:36 but that's not dependent on registration, right? 19:55:43 nope, it isn't 19:55:58 madduck: tumbleweed and I have just been getting the talk submission form ready to open this week 19:56:05 just saying, turn it on before you send the mail 19:56:12 I'd send that 2-3 days after reg opening but because - as cate said - it's long 19:56:13 madduck: i.e. it wasn't ready yet when I sent out the CFP text, that was just a step on the way 19:56:33 wendar: great. 19:56:37 but it is very well written so it will be great as a communications tool 19:56:40 thank you. 19:56:45 We can certainly mention that talk submissions are open when we launch registration, or vice versa. 19:57:06 yes, sounds good 19:57:10 yea I agree 19:57:42 ok, on 19:57:48