19:01:13 #startmeeting 19:01:13 Meeting started Wed Sep 23 19:01:13 2015 UTC. The chair is tumbleweed. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:01:14 duh 19:01:32 agenda: https://debconf16-capetown.titanpad.com/2 19:01:35 can we do a rollcall? 19:01:40 o/ 19:01:53 o/ 19:01:54 o/ 19:02:02 \o 19:02:13 o/ 19:02:30 half here 19:02:33 o/ 19:02:44 I'm here 19:02:47 o/ 19:03:50 \/\/\/\/o 19:03:51 tumbleweed: could you ping all all people again? And maybe make chair also indiebio 19:03:56 #chair indiebio 19:03:56 Current chairs: indiebio tumbleweed 19:04:02 cate: I can, but she'll still ask me to do things :P 19:04:06 I'm happy not to do meetbot stuffs. it breaks my brain 19:04:15 indiebio: it's really not hard 19:04:18 * highvoltage o/ 19:04:20 . 19:04:40 blegh 19:04:44 ok, it's been 5 mins 19:04:46 let's move on 19:04:51 ok, what was I saying... 19:04:58 DLange and nkukard has submitted apologies 19:05:07 #topic General 19:05:19 indiebio: I'm not quite sure what to call that topic 19:05:27 you're looking for a poker? 19:05:44 I'm looking for TLC :) 19:06:02 I don't want it to be a bikeshed, but marga did mention that one poker is too few 19:06:15 I don't mind doing a lot of poking and the stuff I've been doing 19:06:24 but if it gets hot and heavy I struggle 19:07:04 so I would like to know who to go to and say 'I'm not getting what I want with this person' 19:07:10 I think there are a bunch of us who are here to help 19:07:14 * indiebio is trying hard to work in a lot of innuendo here 19:07:27 so maybe the team-leads could work here. 19:07:31 indiebio: I'm happy to help with that kind of thing 19:07:38 IMHO now you can do the lonely poker, and next year when things got complex a new call will be done 19:07:57 cate: haha 19:07:59 This is not the period where we will find the most of volunteers 19:08:01 but anyways, I had a hard week, we can think about this more as time goes on, it seems OK for the moment 19:08:13 we don't have to spend time on this now 19:08:34 OK 19:08:40 braai 10 oct 19:08:41 so a #info looking for an additional poker ? 19:08:50 yup 19:08:58 #chair cate 19:08:58 Current chairs: cate indiebio tumbleweed 19:09:08 as it gets to the end I am sure more people will start volunteering 19:09:14 Second item: for the locals and the teleporters, there's a braai at Nigel's place on 10 October. I'll send an email once I have the address again from his wife. 19:09:18 yes, it's going to be quiet for the next few months 19:09:32 #info Diarise: braai at Nigel's place on 10 October. 19:09:41 what is braai? 19:09:47 we'll make geek jokes on IRC for you lot 19:09:52 tassia: it's a barbeque 19:10:00 but we get annoyed when people call it that ;) 19:10:01 tassia: it's a south african barbeque 19:10:15 nice, thanks 19:10:21 We'll do a S'effrican phrase book for you, don't worry :) 19:10:36 indiebio, ;-) 19:10:43 braai = afrikaans = funny dutch 19:10:52 ok, next, let's move through this quickly 19:11:18 indiebio: timeline? 19:11:36 I'm slightly concerned that people will sink time into that, and then it gets ignored by everyone 19:11:37 Timeline: How do you all feel if we take the next few meetings to flesh out the Timeline on a team/task group basis over the next few meetings? 19:11:55 indiebio: good idea! 19:11:56 would it not be valuable even only as a planning exercise? 19:12:20 I think it would 19:12:43 we can start with the things we sortof know already - registration deadlines e.g. 19:13:09 indiebio: gets every one time to settle into the hum drum and more serious deadlines can be set? 19:13:16 anyways, it is on the agenda and we can take it as it comes... 19:13:19 next item? 19:13:22 indiebio: +1 19:13:38 #info start working on the timleine over the next few meetings 19:14:01 #link https://wiki.debconf.org/wiki/DebConf16/Meetings/template 19:14:06 ok, and then just quickly there's a draft meeting template, if anyone's interested 19:14:14 it's also a living thing, we can adapt it as time goes on 19:14:33 my thinking is to get this as comfortable and familiar as possible so it really is a go-to place for people to find out what's going on 19:14:36 and on that note, 19:14:53 please note that these meetings will happen every week, regardless of if there's maybe not much to discuss 19:15:00 just so everyone can check in if they feel the need 19:15:04 indiebio: cool that looks awesome 19:15:29 tumbleweed, can you note to send a specific call to dc-team for the timeline review? 19:16:18 indiebio: did you want to start with the important timeline bits in meetings, first? 19:16:59 Yes, I think most important things (registration, CfP) should be done first, and then thing that depends on that 19:17:00 not sure I follow the question, tumbleweed... but I was thinking we can take a 'big team'/task group per week and work through all their requirements. 19:17:12 Is the DebConf dates now really finals? 19:17:23 indiebio: what I'm saying is not send the email tassia proposes, yet 19:17:26 99% cate, we *still* need to sign the contract 19:17:32 cate: they're as final as they were at dc15 19:17:46 which is to say nothing is signed 19:18:02 tumbleweed: no, more of a conversation at this stage... 19:18:13 * edrz here now. 19:18:17 cate: we have changed a few especially for Print deadlines etc, so a few might change. 19:18:38 tumbleweed, the call would be just to let people know that the timeline will be discussed 19:18:49 just to make sure people are following 19:19:08 tassia, tumbleweed: once everyone have had their say on their bits, we can send the mail and get people to *properly* talk about them 19:19:24 but sure, these will be sent to -team in weekly meeting agendas - tassia 19:19:39 #topic Task Groups Status Report 19:19:43 indiebio? 19:19:44 so what I'm saying is, for a start, the teams only care about their own times 19:19:52 and then after that they talk to each other? 19:19:59 tassia: indiebio already sent a varsion some weeks ago, but not much comments 19:20:03 about how their times affect each other? 19:20:21 so they in their own space know what they need before they get pulled to all sides by the wider orga 19:20:43 ok, well, I don't know, I don't have the experience, so... 19:21:05 I think people who look at it won't only be looking at their own corner 19:21:09 but let's move on 19:21:14 yes 19:21:15 move on 19:21:18 indiebio: Task Groups Status Report 19:21:41 so in future, we'll have loads of reports here, and the titanpad is looking nicely already 19:21:57 but for now there's not *that* much going on, but let's give it a shot 19:22:13 can someone from content team give a status report? 19:22:57 I doubt there's someone from the content team following here. 19:23:09 e.g., we had that email from a potential sponsor - Enricho. Does content team have info on "speaking (topics, deadlines, type of talk) " 19:23:11 I didn't see any in the roll call 19:23:12 indiebio: (Ideally I would suggest you should get status reports going to the mailing list before meetings, so that meetings can just deal with open questions/problems.) 19:23:21 I see, thanks moray 19:23:29 moray: +1 19:23:38 so we can use this as an example to learn how this was done in the past - so thanks moray 19:23:45 indiebio: I'm not content team formally (intend to incorporate, but not lead) 19:24:00 indiebio, regarding that, the sponsor needs to hear that: 1) only Platinum speakers are assured a talk 2) They can submit talks for consideration of the content team, but they may or may not be chosen depending on merit 19:24:01 But well... topics and types of talk are the same as always, in general lines 19:24:02 moray - how long in advance is this asked for? 19:24:11 ...deadlines shall appear :) 19:24:17 noted gwolf 19:24:28 indiebio: well, it's varied between years how things worked, but that's the most efficient approach if you can persuade teams to do it :) even just "before the start of the meeting" is a lot better than during the meeting 19:24:32 I can give him the month, if not the exact date, yes? 19:24:45 "early next year" 19:25:11 also, I would really like these on the website ASAP... 19:25:18 setting someone up to ping when things are ready is more useful than trying to promise a date now 19:25:22 Yeah, we should agree on a timeline. 19:25:45 though yes, for internal purposes an expected timeline would be useful already 19:25:52 #info Ideally get status reports going to the mailing list before meetings, so that meetings can just deal with open questions/problems. 19:26:44 indiebio: what if you did topics in sections? 19:26:48 ah, so moray, this links to what cate said about cleaning up and refreshing the emails. Ganneff, did you mean to send me a blank email? 19:27:45 indiebio: probably it is encrypted 19:27:54 aaaaah 19:28:03 ok. I'll deal with it tomorrow then. 19:28:39 indiebio: move to the next team? 19:28:46 yup, thanks 19:28:56 participant assistance 19:29:05 about potential sponsor, we can send dc14 report and dc15 sponsorship brochure so they get an idea, and tell them that we are currently finishing the design for dc16 sponsorship campaign, anf get bac… 19:29:06 …k to them asap 19:29:15 #info Talks: set someone up to ping when things are ready is more useful than trying to promise a date now 19:29:50 We don't have the sponsorship brochure yet 19:29:53 larjona_m: why not just set a deadline that next week all is "in the bag" and send it teh following weeK? 19:29:56 tamo_ is working on that. 19:30:11 larjona_m: better to send the real deal 19:30:22 I was thinking just to ack receipt and tell them more info is coming next week 19:30:22 Ah, sorry, I misunderstood. Yes, we don't want to send last year's brochure 19:30:37 indiebio, yes. But you can tell him about the talk part 19:30:40 indiebio, gwolf, cate: maybe larjona can help us set up a sandstorm instance to replace titanpad 19:30:47 sure 19:31:03 marga: yes done, gone to second round and being sent on Fri if not sooner, people to hash out on the weekend 19:31:07 So, answer asap 'thanks for your interest, will send the details next week'. no answer in more than one week is bad 19:31:16 cool. will do 19:31:25 larjona_m: than sounds good 19:31:28 *that 19:31:31 madduck yes I'll help 19:31:38 #info indiebio to send ack email to Enricho sponsor 19:31:55 without h IIRC 19:32:32 is there anything in particular we want to talk about in Participant assistance team? 19:32:38 no, probably too soon 19:32:42 I added about visa 19:32:43 'k 19:32:50 noted, thanks cate 19:32:52 cate, nattie: just be aware that south africa's visa policies are getting sillier 19:33:00 we'll especially have to help anyone planning to bring children 19:33:01 do we have a timeline for the registration process already? 19:33:05 I think you need to find soon someone to check requirement and then to sign 19:33:08 I think that for both talks and registration we want to agree on a timeline SOON 19:33:11 madduck: see earlier discussions about timelines 19:33:16 ok 19:33:17 madduck: we have a draft that I adapted from marga's emails. 19:33:22 madduck: def with kids! 19:33:26 sorry, i just came back. 19:33:29 we need to get consensus from Participant assistance team... 19:33:36 indiebio: on what? 19:33:41 so I think we can do that in the week after next's meeting 19:33:59 consensus on the draft timeline from a thread from a while ago 19:34:00 I don't know what anyone is talking about, any more 19:34:04 lol 19:34:17 it's under control, tumbleweed, for the moment 19:34:32 consensus on the draft timeline with regards to registration deadlines from a thread from a while ago 19:34:40 indiebio: I'm pretty much ignoring list mail, sorry 19:34:50 I think the registration opening is mainly choosed by wafer / local team. registration needs some week before that to finalize questions 19:34:56 indiebio: you mean that they're ready to roll with marga's proposal? 19:35:00 no man 19:35:22 look at the timeline: https://debconf15.debconf.org/wiki/DebConf16/Timeline 19:35:51 actually, can we make this registration stuff it's own meeting? 19:35:56 in two weeks? 19:36:11 indiebio, the timeline? 19:36:16 Or what "registration stuff"? 19:36:17 * tumbleweed is amused that indiebio uses a different hostname for the debconf wiki every time 19:36:27 yes marga, the timeline as it relates to PArticipant assistance 19:36:32 do I? 19:36:42 indiebio: canonical hostname is wiki.debconf.org (that's what the certificate is for) 19:36:45 Whatever the case, yes, at this point in time I think it's better to have separate meetings per subject. 19:36:49 so when registration opens, etc 19:36:49 https: should always be followed by //wiki 19:37:04 indiebio, but the timeline meeting should be about both registration and talks 19:37:08 I just copy what's in the browser 19:37:11 And possibly other important milestones 19:37:14 yes marga, agreed. 19:37:19 indiebio: the question is how you got there :P 19:37:23 but I'm digressing 19:37:31 (or somebody could fix the debconf ssl disaster) 19:37:31 * gwolf is not thrilled about the visa news :-P 19:37:36 so can we action a meeting in about two weeks (depending availability) for content and participant assistance teams? 19:37:57 gwolf: it seems the minister for home affairs is trying to make a name for himself, by enacting stupid policies 19:37:58 jcristau: (right, that would be a better solution than telling people to ignore the results that their search engine gives them) 19:38:04 indiebio: and wafer people 19:38:06 for timeline, with required participation from representatives of PA and content 19:38:13 indiebio: PA team is part of it, but so is infra and content and pretty much everyone else, so this (the timeline) is really a decision that needs to be made globally (e.g. by the dc16 team), after checking with everyone, but with a certain level of assertion. 19:38:32 well, it's on https://debconf15.debconf.org/wiki/DebConf16/Timeline 19:38:41 but that gives everyone a certificate error 19:38:49 where https://wiki.debconf.org/wiki/DebConf16/Timeline doesn't 19:38:50 so have a look and spend two weeks bikeshedding and then we bash it out in two weeks, yes? 19:38:50 indiebio: I'm (probably) fine for that, but I really only know bursaries 19:38:55 (assuming they trust the debconf CA) 19:38:58 maybe it would help to send an email to dc-team, indiebio, announcing the timeline we're going to go by, once it's confirmed with all teams. 19:38:59 You realize we are now meta discussing about a URL? 19:39:10 marga: I tried to stop doing that, sorry 19:39:11 that's what I was suggesting, yes, madduck 19:39:42 tumbleweed: action yourself to help me fix my meta URL stuff and then stop talking about it 19:39:42 madduck: this was all discussed earlier 19:39:49 please stop derialling the meeting everyone 19:39:51 (including me) 19:39:57 ok, so can we action the timeline meeting for two weeks? 19:40:13 indiebio: I thought we agreed to dsicuss the timeline over the next two meetings, already 19:40:18 yes, globally, but we need to be sure main team are represented 19:40:36 #agreed We will have a timeline meeting in about 2 weeks, requiring participation of PA, Content, Infra and any other interested parties. 19:40:38 that's what I said about making a specific call on dc-team 19:40:39 tumbleweed: i am sorry. 19:40:40 but what about visa ? Do we have volunteers? 19:40:48 we'll find them 19:41:11 like the website chat, we have two weeks to find all the stuff we need to make the meeting in two weeks a successful one 19:41:13 #agreed We will have a timeline meeting in about 2 weeks, requiring participation of PA, Content, Infra and any other interested parties 19:41:14 So, no more from my side of -pa 19:41:17 [thanks marga] 19:41:20 thanks cate 19:41:24 ok, moving on 19:41:54 Facilities team 19:42:03 doubt there's anything to discuss here, yet? 19:42:27 we're hoping to get the final contract early next week. 19:42:35 that's all to discuss here for now 19:42:39 next topic 19:42:41 no, just waiting on uct cmc 19:43:12 they're kicking us out in 10 minutes, so this meeting will finish on time! 19:43:38 Social activities team - the notes there we'll take to the timeline meeting 19:43:46 in that case, I propose we read through the notes here 19:43:48 Same for Design 19:43:50 in the titanpad 19:43:54 and discuss anything we need to 19:44:01 without walking through each item together 19:44:10 excellent, that's what titanpad is there for :) 19:44:27 The one thing to note, for those interested, is that there is a Fundraising meeting: Saturday 16:00 UTC (I think - noon EST). - bgupta 19:44:58 ok, infrastructure team: where in the the world is RicheH these days? 19:45:10 RichiH 19:45:22 yes, him :) 19:45:23 I guess recovering from DC15? 19:45:31 titanpad is bad 19:45:33 who's getting kicked out of where? 19:45:41 for mobile-attendants 19:45:51 edrz: from the restaurant we are at 19:46:23 ok, so that's all from my side, any other things to discuss? 19:46:30 oh. I didn't realise you were physically gathered together. 19:46:47 only me and tamo 19:46:54 us semi-geeks stick together 19:47:04 usually with alcohol to help, but sadly not tonight 19:47:10 next week meeting time 19:47:15 #topic next meeting 19:47:21 same time next week? 19:47:22 * indiebio is too normal for geeks and too geek for normal. /o\ 19:47:30 edrz: yup makes it quite entertaining ;) 19:47:31 i thought we alternate? 19:47:37 is everyone happy with the time? 19:47:47 next meeting is about web presence, right? 19:47:50 indiebio: what is normal, anyway? 19:48:01 or that is an additional meeting? 19:48:04 somewhere we decided alternate is too much effort, madduck, but it may still be a good idea 19:48:13 me not very happy but I can try to be happy 19:48:23 Meeting everyweek is exhausting 19:48:36 marga: we discussed alternating 19:48:37 cate: I was thinking it could replace this one, with perhaps a time shift to help the relevant people, and maybe 10 minutes for the other items... 19:48:58 indiebio: will you announce the timeline meeting on the list? 19:49:06 yeah, it's also hardly necessary at this stage. I think it'd be better to have tasks, meet every 3–4 weeks, and in between keep poking each other. 19:49:06 madduck: but the proposed only other slot didn't make much difference availability 19:49:07 marga: we don't need to always physically be there, which is why I try the agenda and minutes to be so complete... 19:49:08 I'd prefer it to be 1h earlier 19:49:09 sorry madduck, not marga 19:49:18 gwolf: me too. 19:49:19 (and intend to be more active on the webpresence meeting) 19:49:39 can we try an hour earlier next week? 19:49:42 oh, wait - which day will it be? Wednesday next week? 19:49:43 indiebio: yeah, I am not complaining and next time I join late, I'll behave even better so that tumbleweed doesn't have to tell me to read backlog ;) 19:49:53 yes, if that works for you gwolf? 19:49:54 If so, I won't be online 19:49:56 :-P 19:50:19 it looks like 1800 might actually be better (if one reads ? as ✔) 19:50:20 I have to give a talk ~100Km South from here, and be back in due time for my class :( 19:50:48 I think I'll check in with the website people and communicate the meeting from there. 19:51:19 ok, we're getting kicked out. 19:51:21 yes. i think not everyone is here right now. 19:51:29 #endmeenting 19:51:32 other chairs do what you must 19:51:33 indiebio: yup we have ameeting on Mon 19:51:37 #endmeeting