17:59:44 #startmeeting DebConf Team Meeting 2020-06-08 17:59:44 Meeting started Mon Jun 8 17:59:44 2020 UTC. The chair is tumbleweed. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:54 #link Agenda: https://deb.li/dc20meet 18:00:10 # topic roll call 18:00:13 #topic roll call 18:00:14 hello 18:00:23 o/ 18:00:25 anyone want to chair? I grabbed it to avoid 5 minutes of avoidance 18:00:26 * DLange calls a roll 18:00:40 present 18:00:41 hi 18:00:47 hello 18:00:58 Hey 18:01:09 hi 18:01:13 ohai 18:01:15 Hi! 18:01:46 o/ karina 18:02:19 #topic summary of last week 18:02:23 #info DC20 Israel decided to be cancelled as a physical conference 18:02:23 #info Registration closed, grapevines communication via dc20.dc.o website, registration@ emails, irc, telegram etc. 18:02:27 #info Heads-up have been given to some sponsors 18:02:29 #info Kosovo team confirmed both DC21 and DC22 possible for them and secured team-wise 18:02:33 #info India team confirmed both DC22 and DC23 possible for them 18:02:35 #info Video team confirmed support for DebConf20 online around the original DC20 dates (~end of August) 18:02:39 #info No formal communication yet as waiting for Israel team to confirm whether DC21 is possible in Haifa. Maybe Wednesday? 18:02:52 #topic Israel Status for 2021 18:03:10 We haven't heard yet, I think we continue to wait? Not much more to say here 18:03:30 tzafrir: said earlier today they should have a position on Wed 18:03:37 s/:// 18:04:14 Yes. I think there is not too much point in hurrying confirmations from the university 18:04:19 Generally we're in touch with the university for a spot for next year. 18:04:38 I would like to not hold off communication with out community indefinitely 18:04:42 Even without a formal response. What level of confidence do we have? 18:04:52 should we establish a deadline/plan? 18:05:00 I guess they are under even more stress than we are... Everybody hopes for "normality" by this time next year, but I'd perfectly understand if they are hesitant to commit this early, even informally 18:05:02 Yeah, we should be putting out some communication to registered attendees, and the community at large 18:05:04 well, we have sponsors asking 18:05:13 so we need to say something tomorrow 18:05:37 DLange: Sponsors will also understand if we say "we are expecting confirmation, but this is our plan and status so far" 18:05:51 Everybody understands our world is not the same world we had when we started planning 18:06:48 gwolf: you are invited to work on the sponsor communication, if you want to 18:07:15 DLange: If you need some hands, I can do a bit there. I've always avoided that area 18:07:17 Given the hairball this discussion turned into last week, I'm tempted to postpone re-visiting it until after the meeting 18:07:32 But I'm more than willing to tell sponsors to have their money back if the terms are not what they want 18:07:38 I mean... it's just logic IMO 18:07:43 can someone #save ? I'm a little late and I have no backlog :( 18:07:49 #save 18:08:31 OK, moving on 18:08:36 #topic Move online / postpone entirely 18:08:44 This is the big question we have in front of us 18:08:53 I think most of us would like some sort of event to happen 18:09:22 Shall we just assume we're doing it online and move on? 18:09:31 Yes. And I think most of us are willing to do some work for it 18:09:32 yes from me 18:09:45 We had a sub-question here about any local physical parts 18:09:51 So, can we do an informal show of hands? 18:09:57 I think the video team committed like that and that is the team with most of the work 18:10:00 gwolf: for? 18:10:13 for online vs nothing, presumably 18:10:13 well, in case there is doubt for doing this 18:10:32 well... you can't stop the people from wanting to do an online event from doing so 18:10:36 and they do want to do so 18:10:41 I think 75% of respondents to the survey are a clear vote from the (potential) attendees 18:10:47 and by them I mean a bunch of us already in the room :) 18:11:02 * gwolf agrees 18:11:09 OK, so nobody is arguing against it 18:11:10 show of hands called off 18:11:20 * gwolf wanted to see fil ;-) 18:11:26 #agreed debconf20 will happen online 18:11:49 #topic reaching out to DC20 sponsors 18:12:02 DLange: is the team needing help with this? 18:12:19 or is it more that you're blocked on firm statements to make to sponsors? 18:12:46 not beyond a clear message what we do with online (seems sorted), DC 21 (<-urgent) and then DC 22, DC 23 fall into place 18:13:03 (these teams committed upfront to be flexible) 18:13:39 +1 for having DC21 information 18:14:03 How many days do you think DebConf20 online will be like? 18:14:13 (guestimate is fine) 18:14:16 we're still working on that, i think 18:14:18 we have an agenda item for that later 18:14:26 so, moving on 18:14:30 ballpark figure probably +/- 6-8 days 18:14:30 o.k., just record the question please 18:14:36 DLange: I know I am not part of the sponsors team -- But still, I don't believe it's _urgent_ to commit to a specific way of holding it 18:14:39 We _cannot_ 18:15:04 #info sponsorship team needs to know the length of debconf20 online (even if dates aren't final) 18:15:12 IMO we can and should reach out to sponsors, and tell them "we are _trying our best_ to hold DC21 just like it should have been this year" 18:15:22 But there will be uncertainty™ 18:15:30 +1 18:16:01 #topic What happens to the bids for Haifa, Kosovo, and Kochi? 18:16:16 I think all 3 teams have agreed to the idea of moving their bids forward one year 18:16:22 correct 18:16:27 a suggestion when talk with Haifa sponsosrs: tell them we can keep them for DC20 online and DC21. 2 events for 1 price 18:17:27 We'd still be needing confirmation from venues that these are actually doable 18:17:30 dates may change, etc. 18:17:35 if they decide to keep money with debian, they will sponsor DC20 onlne + DC21 next year 18:18:07 we just need to know about tax things if we keep things across tax years 18:18:07 yep, may be a bit of a premium but we're thinking along those lines (offer sponsor packages to retain the original DC21 funds where possible) 18:18:27 should I go back to the previous topic? 18:18:38 nah 18:18:49 we need the info, the rest is not that hard 18:18:57 is there anything else to decide wrt Haifa, Kosovo, and Kochi? 18:19:01 yeha. It's still far in the future 18:19:28 terceiro: we can't until we know what Haifa can / cannot do? 18:19:50 tumbleweed's summary above is accurate and as much as we currently know 18:20:10 #agreed the 3 teams have agreed to keep the same order, but shift them up one year. Things may change later, of course 18:20:16 yes I'm asking whether there is anything left for us to decide during this meeting 18:20:37 doesn't seem so 18:20:42 terceiro: probably at least to send out an updated CfP 18:21:05 all 3 teams: I hope you'll keep us informed, over the months, as to how thnigs are going with your team and bid, etc. 18:21:07 highvoltage: that's a separate topic 18:21:14 #topic Nomenclature for the online debcoonf 18:21:27 terceiro: ah I see what you meant 18:21:33 I quote from the agenda: 18:21:34 The fundraising team would prefer to keep DebConf21 for the event in 2021. So we can call the Online DebConf "DebConf20 online" or we should skip a number. Rationale: Communicating DebConfXX in 20(XX+1) is hard and makes things always look like typos / negligent editing. 18:21:49 yeah, LGTM. The alignment on years is nice to have 18:22:01 DebConf20 Online is OK for me 18:22:51 #agreed 2020's online DebConf will be called: DebConf 20 Online (or similar). And be followed by DebConf21 in 2021 18:23:08 #topic DebConf20 Online Preparations - Team 18:23:10 lovely! 18:23:16 OK, on to the main meat of the agenda today 18:23:24 (I've been pushing for speed because there's a lot to cover) 18:23:26 O N L I N E :) 18:23:52 What teams do we need? Who will staff them? 18:24:00 The core is probably content and video 18:24:24 Also needing registration, community team, sponsors 18:25:33 * nattie will deal with registration, as usual 18:26:05 you have the helpers you'll need? 18:26:06 I'm not sure I understand the need for registration? 18:26:18 pollo: to respond to people mailing questions 18:26:28 ack 18:26:32 there will be lots of them 18:26:36 do we need to do registration itself at all? 18:26:43 tumbleweed: yes, i think so. i'll talk to people 18:26:45 if we're going to have shirts, we probably do 18:26:47 and I assume we're always happy for people to give us money from their employers to "attend"? 18:27:00 ah right, yes 18:27:05 yeah, we can take their $ 18:27:11 tumbleweed: shirts sounds like a shipping nightmare 18:27:21 * tumbleweed imagines a cook-it-yourself conference dinner 18:27:39 pollo: if you partner with a t-shirt priting company that does online orders, they should be set up for that 18:27:54 I'm all for a cooking-with-pollo conference dinner 18:28:25 pollo: another reason why a good local team network would be nice, if we had a strong network of those everywhere we could ship in bulk to those who could distribute locally 18:28:48 yeah there are a gazillion drop-ship t-shirt companies 18:29:14 and that becomes a sponsor perk 18:29:39 (that motivates for money this year, not just moving their sponsorship to next year) 18:29:55 should we double check that each team has enough people? 18:30:03 Yeah, so registration seems about covered 18:30:03 (against the meeting agenda) 18:30:13 Video 18:30:27 pollo, paddatrapper, olasd, I assume you're all in if you're here? 18:30:39 tumbleweed: yup 18:30:43 o/ 18:31:06 pollo: We will also need some sort of registration for proposals to be submitted / commented / improved 18:31:17 #agreed registartion will be done by the usual nattie+helpers team 18:31:25 with typos 18:31:46 tumbleweed: plausibly 18:32:00 not 100% committed yet 18:32:01 allegedly 18:32:08 :) 18:32:35 tumbleweed: yep 18:32:57 #agreed video has at least a core team of paddatrapper, highvoltage, pollo, olasd (not 100%), tumbleweed 18:33:10 Content 18:33:18 * gwolf raises hand 18:33:29 I'd prefer _not_ to lead Content 18:33:37 But I'll very happily be a part of the team 18:33:40 pinging azeem here too just in case he's reading elsewhere atm 18:33:58 (and can be persuaded to lead if all others are busy as well) 18:34:22 I'm in as well 18:34:59 nobody wanting to lead, though? :) 18:35:07 typical debconf team problem 18:35:38 #agreed content has a team of at least gwolf and terceiro. No leader yet 18:35:55 tumbleweed: We will do it the Latin American way then 18:35:57 Seems like this is an area where some of the DC21/22/23 teams could contribute 18:35:58 if they get along and don't have too many difficult decisions to make then a leader is less necessary 18:35:58 * gwolf relaxes a bit 18:37:10 * tzafrir would like to join the content team 18:37:27 * gwolf hands over a Latin American passport to tzafrir 18:37:37 #undo 18:37:37 Removing item from minutes: 18:37:43 i cam help with content, if it necessary. 18:37:56 #agreed content has a team of at least gwolf, terceiro, tzafrir, and lenharo. No leader yet 18:38:11 OK, that's starting to look a little better, thanks :) 18:38:27 Community Team: I guess without the physical component, we don't need a debconf community team, just use the team itself? 18:38:48 maybe we'd want to set up people with moderation powers, in discussion with them 18:39:20 if we're redirecting folks to IRC, it would be a good idea to have ppl with mod powers imo 18:39:43 * gwolf agrees 18:39:48 yeah 18:40:03 we do have a OFTC team that gets mod powers on debconf channels 18:40:40 So, we should probably discuss this with the community team once we have a clearer idea of the format 18:40:52 Sponsors Team: DLange + anisa? 18:41:22 #agreed Reach out to community team. Build a moderators team for DebConf IRC channels / jitsi etc. 18:41:22 yeah, I'm happy to help fundraise for DebConf20 Online 18:41:44 Me too 18:41:54 need more than that? 18:42:06 we have our usual suspects 18:42:14 Future DebConf teams: I suggest at least one of your gets involved in the sponsorship team if you aren't already 18:42:21 but the money needed for Online (so far) seems rather limited 18:42:26 You'll need to know how it works, later 18:42:52 #agreed sponsorship team will be DLange, anisa, and the usual suspects 18:42:55 yeah, Enkelena, srud when you read backlog, please think about fundraising early ^ 18:43:05 Right, but it can also be used to gather money for Debian (and/or future DebConfs) 18:43:23 we don't do Debian fundraising for $reasons 18:43:33 #topic Website, Logo, etc. 18:43:35 * gwolf understands. 18:44:03 I took a hack at moving the dc20 website to online debconf: https://wafertest.debconf.org/ 18:44:08 (thanks terceiro too) 18:44:14 it still needs work 18:44:31 well we skipped the website team :) 18:44:33 But basically, that's just the simplest possible tweaks. Ideally I think we need a logo, and some DC20-specific design 18:44:40 Good point! 18:44:51 who wants to join the dc20 website team? :) 18:45:02 the sponsor situation might have to be cleared too before the website is put in prod 18:45:09 pollo: right. That's the main blocker 18:45:50 (but I can see ways to avoid making that a blocker). Until we announce the change we can probably get away with stale sponsor lists 18:45:53 at least that doesn't block from improving the dc20o site 18:46:01 or suppress them all until they confirm that they want to sponsor dc20 online etc. 18:46:03 and the current site can link to the new site prominently in the meantime 18:46:16 my aim here is to replace the current site 18:46:20 FTR: we're discussing packages 18:46:33 and fork off the current version to debconf21.debconf.org 18:46:38 so may be DC21 sponsors can be DC20o sponsors for a small premium 18:46:38 yeah I thought that you might be concerned that sponsors won't be up for a short time and that that might bother them 18:46:54 DLange: pay 10% extra and get two DCs! 18:47:02 exactly, highvoltage 18:47:09 * highvoltage imagines DLange balmer pitch 18:47:16 DLange: so, should we remove sponsors and JFDI release these changes? 18:47:33 Developer, Developers, Developers (notice the uppercase D) :-) 18:47:58 tumbleweed: can we wait until Wed once we have info from the Israeli team? 18:47:58 DLange: I was thinking more "reversi" https://www.youtube.com/watch?v=EtuDS0ntaJY 18:48:05 DLange: OK 18:48:06 But back to the original topic here: Shall we put out a call for designs? 18:48:16 again, I suspect DLange doesn't want announcements until wednesday 18:48:26 Because if that is positive, I'd keep the existing sponsors for now and clean up after the first round of feedback 18:48:28 we're not going to have long to get designs and make a selection... 18:48:32 tumbleweed: yes! 18:48:46 rememeber we needed to mangle the DB for that last time, tumbleweed? 18:48:47 I'm sure a bunch of folk will have great ideas 18:49:05 So may be we can improve the sponsor load process to remove not-loaded ones? 18:49:22 or just delete them all and re-load them 18:49:30 that would be fine 18:49:31 but yes, we can improve things there 18:50:10 DLange: do you have concerns about asking for designs now? 18:50:17 no, not at all 18:50:31 OK 18:50:40 Anyone want to organise the call for designs? 18:50:53 it needs to be clear what is possible and what's not 18:51:18 last year we had an excelent designer propose things that we not easily implementable in wafer :) 18:51:29 the design was great, but not viable 18:52:12 although we have had some pretty radical designs in the past (e.g. debconf16). So there is scope for crazyness, in the right places 18:53:01 OK, I don't see any volunteers. terceiro: let's work this out after the meeting 18:53:10 k 18:53:16 * pollo wants a shirt with "Debconf @ Home" , s/@/Debian logo/ 18:53:16 #agreed we should do a call for designs 18:53:46 #agreed debconf website team appears to be tumbleweed and terceiro as usual 18:53:55 #topic Schedule 18:54:01 Big questions here 18:54:05 When in the year do we want to do this 18:54:07 How long 18:54:10 What format 18:54:11 etc. 18:54:35 I think we can decide the period, and leave the exact format TBD? 18:54:47 Can it be on a work day? 18:55:18 tumbleweed: sorry been distracted by IRC, I'll at least make some MRs for content 18:55:22 as late as possible, 2 days of sprints/BoF + 3-4 days of more regular confs 18:55:45 I was imagining that we'd probably do something like DebConf14, without a debcamp before hand, but with fewer talks each day, and some hacking time between 18:55:56 (also, that can be friendly to a wide range of time zones) 18:56:04 #agreed highvoltage will help with website content 18:56:08 yes, that would be nice 18:56:21 the two days of "debcamp" before minidebconf online was actually nice. both for testing things, and for seeing people 18:56:36 i have a question to the end of this topic 18:56:40 yeah, using the dc14 schedule shape for the actual conf days is a good idea IMO 18:56:41 on the first day a bunch of people joined and then conversation would flare up for a few minutes when new people joined later on. 18:56:55 on the second day we watched talks from the libre graphics conference together and that was great 18:56:57 pollo: Noted 18:57:10 I think there's usefulness and fun things to explore for an online minidebcamp 18:57:23 ... and it's useful for ironing out wrinkles in the stack 18:57:23 we're definitely going to need some testing for video stuff 18:57:25 s/mini// 18:57:39 probably ramping up in the day or two before things start is good, yes 18:57:57 olasd: heh, if it's just 2 days before the online debconf... is it a minidebcamp or a debcamp? 18:58:00 tzafrir: I'd imagine we do some things in the week, and some on weekends 18:58:06 video stuff will definitely need testing wayyyy before a potential camp though 18:58:09 (I don't think we need/want 7 days for sure) 18:58:13 (and of course your weekends are different) 18:58:18 I think having a few separate days for sprints would help justify folks being paid to attend 18:58:47 maybe talk days with gaps between for sprint days? 18:59:12 that would also work, I just don't think mixing both during the same day is a great idea 18:59:25 I like the daytrip 'break' IRL DebConfs because once or twice I just needed it to sleep 18:59:41 I'm guessing many people would attend without taking time off from work. But yes, a sprint is a perfect reason to take that time 19:00:03 I was wondering if it might be good to have 3 days of DebConf, a break day with lighter activities and then 3 days again (not to dismiss other ideas mentioned so far, just spitballing) 19:00:12 I recommend making few great days over more mediocre days 19:00:25 (content, organization, "events" wise) 19:01:28 how long are the days going to be? if they are spread out over 24 hours maybe having less days is better 19:01:38 this feels like an infinitely-paintable bikeshed 19:01:48 I think a lot of this depends on the quantity of submissions 19:01:59 (and for valhalla's question, what timezones they are in) 19:02:09 (and not a very useful use of synchronous meeting time) 19:02:13 I think we should agree on a basic set of parameters, and decide on the exact format later 19:02:22 maybe we start with a vague shape of the conference an drefine later when we have submissions? 19:02:40 although we probably need to set dates 19:03:04 olasd: yeah. This is where it is nice to have a bid team that gets to make the decision 19:03:18 content team: can we put this on you? (with video input) 19:03:23 sure 19:03:36 maybe we could open to have some special slots, to people talk in his/her own language. 19:03:40 phls mentioned a good idea if we get talks from different timezones 19:03:47 yes :-) 19:03:50 as in, a sufficient amount of talks from different timezones 19:04:00 #agreed content team to define a schedule 19:04:08 So, next question here. When do we hold it? 19:04:11 aim for the same dates? 19:04:23 you could split the local teams in 3-4 groups of people who can manage the talks in their timezone so that there's essentially shifts 19:04:37 tumbleweed: I wonder how well august will work for fully remote attendance 19:04:39 the main problem I see with 24h confs is it's going to be hard on the videoteam to find volunteers to cover all shifts and there is the chance of something going down while key people are sleeping 19:04:43 If DC20 take place from 10h to 18h UTC, it will finish at 15h to us (Brasil). So, I'm thinking about organize portuguese talks at night here (19h - 22h = 22h - 01h UTC) on the same days, getting ride on "DC20 mobilizion". 19:04:49 phls: so maybe you should also join content team in that case 19:05:14 I think it would be great to have events in all timezones. Not just coving EU work hours 19:05:56 different languages can put work on other teams (content, website etc.) 19:06:09 but if they're up for it, that could be nice 19:06:24 olasd: what are your concerns for August? People taking holidays? 19:06:26 Different languages can have different rooms 19:06:35 language miniconfs essentially 19:07:00 Do you see any kind of problem on having portuguese talks? 19:07:02 tumbleweed: essentially, yes. but that's a very EU-centric concern 19:07:08 tzafrir, i like this idea 19:07:32 olasd: what's the alternative? October? 19:07:57 tumbleweed, site could be only in english. just put in the schedule, info about language. 19:07:57 choosing a date that will work for absolutely everyone... talk about an infinite bikeshed colour choosing :) 19:07:58 i'm planing to these talks even we don't use DC infra video 19:08:09 phls: I think if you do this, you should think carefully about whether it's part of the conference or something separate, on the same days 19:08:23 if it's part of the conference, all of the teams probably end up being involved 19:08:34 so the processes need to be the same for content submission, video, etc. 19:08:38 imho more languages could be very nice and something worth experimenting with 19:08:44 and you'd need pt_BR speakers on all of those teams 19:08:50 tumbleweed, yes, I agree. If we can deal with infra video for our talks, would be great (and I prefer it) 19:09:27 I guess there are people who have already resevered vacations / days off from work at the original haifa dates 19:09:45 yeah, probably 19:09:45 *reserved 19:09:45 that assumes the conference will run in European work hours, and we did not decide that yet 19:09:53 I mean the "main" conference 19:10:03 I would assume it covers the timezones of all speakers 19:10:07 * gwolf is back, sorry for missing part of the bikeshed... 19:10:09 the few people who really can't make it can catch up on video too. by then a large percentage of people will still be stuck home anyway 19:10:28 I think we can try to do something similar to what we did for the MDCO 19:10:29 debconf doesn't have great video catch-up 19:10:32 (re:schedule) 19:10:38 I mean, our video usually takes a couple of days to be posted 19:10:42 we can do shifts for video team 19:10:48 ...Ask speakers as part of the submission their scheduling preferences 19:11:01 tumbleweed: well if someone can't make it in real-time that's really the only option that's left 19:11:06 (ideally in an automatable way, as I do expect more than 10 talks to be submitted!) 19:11:14 and... have the schedule try to adapt to it! 19:11:21 tumbleweed: video catch-up shouldn't be too hard to implement considering we're dumping streams too 19:11:28 gwolf: yes we can have different talk types for each timezone window 19:11:38 That way, if most speakers are European, the schedule will be more Europe-friendly, as MDCO was... yes... 19:11:38 we don't even need to write any code for that 19:11:41 olasd: yeah 19:11:59 ...That's a bit unfortunate for us non-Europeans - But it's better for people to be awake (and available!) at the time of their talk 19:12:14 I don't know if we're coming out of this bike-shed with any decisions 19:12:15 (keep in mind we will have people at DebConf while at {work,family,foobar} 19:12:28 tumbleweed: we're not 19:12:30 Nobody has argued strongly for changing the time of year 19:12:32 can we please just pick dates/ 19:12:34 Or for keeping it 19:12:35 Do you think there's any point in attempting sort of after-hours activities? (didn't really work in MDCO)? 19:12:39 and then decide everything else later 19:12:41 we cannot take over a person's time 19:12:43 gwolf: well there's an incentive for you to chase some speakers in your timezone and get them to submit CfPs :) 19:13:01 tzafrir: what do you mean? we didn't have after hours activities for MDCO 19:13:02 tumbleweed: my concern was a gut feeling; but there's not much stuff to back it up 19:13:09 highvoltage: yes :-] And even to try to organize something what lenharo/terceiro are suggesting 19:13:14 olasd: yeah. And there are no counter-proposals... 19:13:18 for me, original haifa dates works!! 19:13:23 So, shall we have an infromal vote on the original dates? 19:13:24 +1 19:13:25 tumbleweed: yeah, *shrug* 19:13:45 sure 19:13:54 Maybe more specifically: DebConf original dates 19:14:06 yeah but with flexibility based on proposals and what the content team suggests 19:14:10 I get the feeling that there will be less content than usual, and we won't have a week of DebCamp 19:14:14 tumbleweed: which were? 19:14:24 Although Debcamp begins at the Debian birthday. 19:14:35 DebCamp: 16-22 August, DebConf :23-29 August 19:14:37 if we keep the original dates will we have enough talk proposals to cover ~6 days of DC? 19:14:38 Yes, I don't really think we should expect much of a DebCamp 19:15:00 anisa: we can but hope 19:15:11 And I also think we will probably have less talks than usual - but that can be offset by not needing to have as much parallel tracks as usual 19:15:14 We can always turn days into sprint days or just end the conference earlier 19:15:26 tumbleweed: we manage to get content for three tracks usually; 19:15:35 that would not be a nice message, tumbleweed 19:15:35 I don't think we /need/ that much for an online event 19:15:56 gwolf: I think we can make DebCamp interesting based on what we found in MDCO 19:15:57 may be just aim shorter and extend a day if we get run over by good talk proposals? 19:16:20 So, something like 22-30 August? 19:16:26 (That's Saturday -> Sunday) 19:16:32 DLange: You should work in PR ;-) 19:16:39 That would make us look great 19:16:48 will we have paralelas talks? 19:17:02 phls: that depends on how many we get, surely 19:17:03 depends on the amount of submissions 19:17:11 ok 19:17:54 Are we agreed? Is that too long? 19:18:14 I'd prefer to have the least possible parallel tracks 19:18:20 that can be the *max* duration 19:18:22 but we will probably have some 19:18:24 (I'm taking a moment to process if that's ok) 19:18:30 and we dance around those dates 19:18:42 terceiro: yeah, that works for me 19:19:02 we can always insert "day trip" days in between to keep the same range 19:19:03 tumbleweed: what's that then, debcamp + debconf 8 days? 19:19:15 day trip/sprints/etc 19:19:20 it's 8 days of online debconf. Whatever the actual days end up being can be decided later 19:19:26 ok cool +1 19:19:28