14:29:49 #startmeeting 14:29:49 Meeting started Thu Jan 4 14:29:49 2018 UTC. The chair is czchen. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:49 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:59 #topic roll call 14:30:11 hola! 14:30:12 Say hi if you are in meeting 14:30:16 hi 14:30:17 hi 14:30:20 hi 14:30:24 OwO/ 14:30:31 hi 14:30:36 Hi. I'll be on a bus in a couple minutes, but I'll try to participate as much as possible. 14:30:45 oh hey taowa 14:30:46 Don't forget to update meeting agenda https://storm.debian.net/grain/uNF6W7gzmxGQHshgb5yCBS/ 14:31:00 hi 14:31:21 0/ 14:31:21 ohai 14:31:26 czchen: could you repost that link with the deb.li address please? 14:31:31 * Clint grunts. 14:31:44 hi 14:31:54 Anyone has deb.li address? I don't have it right now 14:32:13 deb.li/3OYuV 14:32:16 Found it 14:32:31 http://deb.li/il9wc 14:32:40 oh, maybe there are two 14:33:05 Looks like the same one 14:33:08 the first one was in the topic before the meeting 14:33:49 hi 14:33:58 paulliu: are you there? 14:34:08 Hi ... Greetings from Curitiba Brazil 14:34:22 o/ 14:34:33 +1 from Curitiba here 14:34:46 #topic Submissions of DC19 candidatures 14:35:00 +1 Brazil here :P 14:35:29 What is the status of DC19 bid? 14:35:46 Curitiba BID is read. 14:36:09 lenharo means ready 14:36:12 https://wiki.debconf.org/wiki/DebConf19 I think we only have Curitiba, Brazil now? 14:36:32 Bratislava bid is semi-ready (as in: many things are ready, but some need more work, and the team needs more than one person) 14:36:35 yeah. i think Bratislava is effectively doing a dry run? 14:36:39 o/ 14:36:47 yes 14:37:02 updated the wiki page 14:37:14 but we should do the evaluation dance, at least for form's sake 14:37:27 and so that andrewsh gets feedback for a subsequent bid attempt 14:37:32 (at his request) 14:37:33 yes please :) 14:37:41 fantastic 14:38:44 nattie: How to process evaluation? 14:39:30 updated the wiki page once again 14:40:15 Any question so far? 14:40:53 czchen: In general: public phase: questions on mailing list, then a IRC meeting with questions (optional) and a final IRC meeting with question and evaluation of main points (maybe the final decision is taken in an additional meeting, if some data is still missing). 14:41:16 cate: thanks 14:41:49 When to we need to decide the date for those events? 14:41:58 but: one person should take care to do (or make sure other do) such check list, deadlines. And committee (+ ev. other helper) should be ready for the final question and meeting 14:42:07 the decision tends to be made around mid-february 14:42:09 czchen: hi 14:42:19 though we could do it earlier this year if people would like 14:42:50 anyone from DebCOnf committee? 14:43:06 I'm +1 for that, unless Bratislava needs more time to prepare their dry run bid 14:43:40 if anything, I will add more info tomorrow/during the weekend, so this is fine 14:43:46 but if we know it's curitiba for 2019, I would rather make it official as soon as possible to give them the maximum amount of time 14:43:50 i've just poked the committee memnber i know best 14:43:54 +1 14:44:04 I don't think there's much more we can do atm except filling in blanks at the wiki and/or replying to questions 14:44:13 hello, sorry, RL got me 14:44:17 (and updating the wiki according to the replies) 14:44:37 nattie: you could have done in public. It is important also for tw and bid, to remember who is part of committee 14:44:58 hi 14:45:02 tumbleweed: tl;dr, curitiba is officially bidding, bratislava is doing a dry run only 14:45:33 no other bids have emerged 14:45:53 i think the big item is to schedule the official decision meeting 14:46:06 even if it's substantially earlier than usual since the conclusion is mostly foregone 14:46:15 tumbleweed: some suggestions/question is whether we should make the announcement a bit earlier if possible, while still providing useful feedback to bratislava 14:47:54 Do we need to decide date right now? 14:48:15 lucas: are you around? 14:48:15 czchen: as soon as possible 14:49:06 We need to have the confirmation from sun and from moon about the eclipse in South America ;-) 14:49:21 cate: nerd ;) 14:49:25 hah, please don't start that again :) 14:49:31 No idea how to decide the date, earlier than mid-Feb. Jan 25 or Feb 1 ? 14:49:51 not Feb 1, people will be busy at FOSDEM 14:49:56 Jan 25 would certainly be great for me 14:50:04 Jan 25 works for me too 14:50:05 highvoltage: thaks for the catch up 14:50:10 sorry, IRL is still being a pain 14:50:29 it's long enough to be a dignified timespan 14:50:39 any objections to Jan 25? 14:51:05 Jan 25 is okay for me. I think there will be a lot of people for FOSDEM here? 14:51:26 highvoltage: I am 14:51:39 medicalwei[m]: yes, people will be at FOSDEM the following weekend (3/4 Feb) 14:51:39 it would probably have to be early enough to accomodate the curitiba folk, can I suggest 12:00 UTC for the 25th? 14:51:56 jan 30 to feb 3 we have an event here too 14:51:58 25th is the middle of LCA for me 14:52:02 lucas: tl;dr, we're trying to find a date for the bid decision for dc19 14:52:19 (dunno how that will fit timezone wise) 14:52:35 highvoltage: right. no constraints on my side around those dates except FOSDEM 14:52:49 it's a thursday lunchtime for europe, and would be very early in the morning for curitiba folk 14:52:57 lucas: nattie, tumbleweed and I will be at fosdem too, so you're safe for that :) 14:53:15 for Curitiba i think the best time for meetings is the same as this one, its on our lunch time and it makes it easier for those who work 14:53:26 nattie: oh right, where's my brain, it would have to be around 19:00 UTC then, I suppose 14:53:36 but it is not a big problem to make it at morning too 14:53:48 so that's 14:30 UTC 14:53:53 yeah 14:54:28 I know DLange is traveling, but from what I understand it should be fine if we find a stand-in 14:54:29 18:30 at FOSDEM bar is a good time for a beer and a meeting 14:54:36 nattie: here now is 12:55 (-2 from UTC because we are in summer time) 14:54:36 highvoltage: do we need to decide this *now*, or can we do a quick doodle? 14:55:27 doodle or dudle :) 14:55:29 lucas: depends how quick the doodle is, but it would be nice to have that date at least set this week. before fosdem would be great. 14:56:26 (highvoltage is computing) 14:56:49 tumbleweed: when are you leaving for sydney? 14:57:00 I think we has agreed on Jan 25 right? Only need to decide time 14:57:22 czchen: it will be hard for tumbleweed to make that, which is enough reason for us to look at another date 14:57:35 highvoltage: 12th 14:57:49 tumbleweed: yikes, that's early 14:57:51 25 seems to be good for us 14:57:51 I may be able to make it, depending on hours 14:58:05 but something that suits brazil, europe, and australia is always a scheduling headache 14:58:15 what time would the regular 14:30 timeslot be in the LCA city? 14:58:21 tumbleweed: 14:30 is 01:30 in Sydney 14:58:26 that's actually doable 14:58:26 oyyyyyyy 14:58:29 ah ok 14:58:31 jan 25 is the meeting to decide the BID19, right? 14:58:34 shall we go with that then 14:58:34 I mean, not great, but doable :P 14:58:55 tumbleweed: yeah it's either you or not great for everybody else 14:59:01 yep 14:59:26 BID = Big Important Decision 14:59:41 :) 14:59:41 or: 14:59:43 lucas: I'm not against a doodle but I think we could reach consensus for 14:30 UTC on 2018-01-25 right now, which would be nice 14:59:49 BID = Brazilian International DebConf 15:00:09 Actually I would be okay to -2 but that's not good for Curitiba neither... 15:00:31 for Curitiba is good too 15:00:37 i think it's only tumbleweed who will be at LCA out of us? 15:00:43 14:30 = 12:30 in Curitiba 15:00:59 * andrewsh proposes Almdudler instead of a doodle 15:01:03 well, we can do -2 i guess, its not as good as 14:30 UTC but it looks better for the others. I feel like other brazilians have to ack this 15:01:12 How about 12:30? 15:01:16 let's stick with 14:30 15:01:25 ok for me 15:01:25 it's easy to remember 15:01:54 and there's only one person who will be in a somewhat incompatible timezone, whereas it's fine for everyone else 15:02:16 So do we have conclusion on 2018-01-25 14:30 UTC for DC19 official decision meeting? 15:02:17 ack for 2018-01-25 14:30 UTC? 15:02:34 yes 15:02:43 * lenharo ack for 2018-01-25 14:30 UTC 15:02:43 can we get an #agreed :) 15:02:46 Ack. 15:02:54 I'd like to see at least tumbleweed and lucas give a +1 15:03:02 (and bid teams) 15:03:13 ack 15:03:15 ack 15:03:15 (and OdyX but I know his busy) 15:03:29 I'm teaching at that time, but I should be able to pay attention to the meeeting at the same time 15:03:31 ack 15:03:32 acl 15:03:34 +1 15:03:43 s/l/k 15:03:43 (so ack) 15:03:59 great, then it's set 15:03:59 #agreed We will have DC19 official decision meeting at 2018-01-25 14:30 UTC 15:04:28 #topic Sponsorship 15:05:33 We has sent sponsorship mail for most of the sponsors without Debian-Contact. It is time to contact Debian-Contact to see if they want to send sponsorship mail or we shall do it. 15:05:39 I have a question aboud BID19, sorry 15:06:39 nattie: shall I send a mail about dc19 bid meeting to -committee and -team or are you on it? 15:06:40 phls_brazil: could you raise that at the end under "AOB" please? 15:06:47 highvoltage: could you please? 15:06:51 nattie: will do 15:07:05 thanks :) 15:07:07 nattie: sure, I wait 15:07:13 thank you 15:08:12 Could we use fundraising? (it is not only aboud getting sponsors, and we had already question of people asking for sponsorship (aka bursaries) 15:09:05 yeah, can we agree to rename that process fundraising? 15:09:39 tumbleweed: Will you help to contact sponsor for DC18, as you are listed as Debian-Contact for certain sponsors? 15:09:52 Ok for me since that decreases confusion. 15:10:06 nattie: rename to ? 15:10:20 czchen: from sponsorship to fundraising 15:10:26 czchen: the sponsors I'm listed for are probably south africa specific 15:10:37 Sponsorship (for getting money from companies and government funds) -> Fundraising 15:10:46 I see 15:10:54 but I also am not a member of the sponsorship team, so I don't even know who those are. Please coordinate that with me in the sponsorship channel / privately 15:11:16 tumbleweed: No problem 15:12:48 i think we have three in favour and no objections. can we #agreed the renaming? 15:13:22 #agreed to rename sponsorship to fundraising 15:14:32 sponsor are asking how to process, do we just send the payment methods so that they can send money to OCF.tw / SPI ? 15:14:58 i believe so 15:14:59 Or is there any other process we need to do before providing these information? 15:15:06 okay, thanks 15:15:22 we need to talk to OCF about how they'll hold our funds i guess, unless that's already been cleared? 15:15:38 czchen: as I told you yesterday, we need to invoice them ourselves for SPI 15:16:25 We've discussed that before, they can invoice companies (before/after payment) or receive donations 15:16:32 nattie: OCF provides us the ledger for Debian 15:16:49 medicalwei[m]: Is that for OCF or SPI? 15:16:51 invoice before payment seems best, i think. any other opinions on that? 15:16:58 czchen: that's OCF 15:17:29 OCF. Refering to the email from Singing 15:17:54 We also need to confirm how we do it in SPI, since some sponsors might favor SPI for tax deduction 15:19:23 SPI already has a process established 15:19:33 czchen: ask Hydroxide or schultmc. Usually you can do a invoice, and they will notify you when payment are received 15:19:37 they've done this for us before several times 15:19:55 Thanks for the information 15:19:55 cate: zobel would also know 15:20:04 czchen: ^^ 15:20:57 anything else for fundraising? 15:20:57 I think olasd could also help understanding the procedures with SPI. Poor olasd ;-) 15:21:05 #info Hydroxide or schultmc knows about process of receiving funds in SPI. 15:21:53 the chief advice for fundraising is: get on with it :) 15:21:59 #info and zobel 15:22:40 #topic Visa 15:22:54 who's on visa this year? 15:23:39 abdelq according to https://wiki.debconf.org/wiki/DebConf18/TeamRoles 15:23:47 * medicalwei[m] holds a ROC (Taiwan) passport. Doesn't need a visa. 15:23:50 interesting... 15:23:58 medicalwei[m]: i meant, who's on the visa team 15:24:28 Oh 15:24:38 I guess we don't have visa team right now? 15:24:53 medicalwei[m]: oh wow, I didn't realise you'd even need that 15:25:07 right. It needs lead of a really local person (to sign invitation letters) 15:25:27 cate: i think OCF are proposing to actually issue the invitation letters, but we need to provide the data for them 15:25:32 cate, I think OCF should handle signing 15:25:33 as to who is getting invited, etc 15:25:53 I seem to remember that some countries had special requeirements too (e.g. stamps) 15:25:57 because OCF is a legal entity which should be easier for Taiwanese government. 15:26:05 So anyone could be in the team. Time to wake again n0rman? ;-) 15:26:47 medicalwei[m]: it is mostly on our part to check if people are true attendees or just people who look for a easy way to get a visa 15:26:58 So we need provide the information about invitation letter to OCF so that OCF can issue it? 15:27:10 So the process is like, visa team and reg team decide who should get invitations, and let OCF handle the rest 15:27:34 There's a template for invitation letter already, sent by OCF people 15:27:35 czchen: yes. they've given us a template. we adjust the text to make it applicable to Debconf, and also tell OCF who needs a letter 15:27:58 about what people should be invited. And usually we have two invitation letters: one specific for ourcontributors, one one for people we think are true attendees (and we deny for others) 15:28:53 contributors, and non-contributor attendees (possibly sponsors is in this category?) 15:29:42 medicalwei[m]: I suppose it will mainly be people who are applying for a visa 15:29:45 medicalwei[m]: if we give them free food and accommodation (so the attendees should no further provide information about funds), previous attendences, 15:30:12 So right now we need to form the visa team and they will review if we want to send invitation letter or not for specific person, right? 15:30:51 Yes 15:31:39 If some members are part of registration make collecting information easier. In any case not a lot of work 15:31:54 https://www.roc-taiwan.org/za_en/post/4658.html mentions an ARC, I suppose OCF will know what this is? 15:33:01 I can join visa team, but I am not sure how to see if people are true attendees or not 15:33:28 czchen: I can help on that (and so on visa team) 15:33:36 highvoltage: We can ask OCF about https://www.roc-taiwan.org/za_en/post/4658.html 15:33:43 czchen: great 15:33:53 #action czchen will ask OCF.tw about https://www.roc-taiwan.org/za_en/post/4658.html 15:34:10 czchen: remember, visa works together with registration on that matter 15:34:20 about determining legitimate attendees 15:35:22 nattie: thanks 15:35:40 you're welcome 15:35:56 How to get access to visa@debconf.org ? 15:36:07 czchen: ah, I just learned that ARC stands for Alien Resident Certificate, so it's just an ID, so I suppose OCF would use their registration data (probably on their letterhead) for the invite letters, but I'll leave that to you :) 15:37:33 Anything else? 15:37:36 czchen: request it in #debconf-infra or file a RT ticket with DSA if you don't get a response 15:37:48 tumbleweed: thanks 15:37:58 we should probably check who all is on that alias, anyway 15:38:07 OCF can use their own entity ID in case of that 15:39:10 Who shall be on visa@debconf.org? Do we have the list? 15:40:31 Have to check with DSA people 15:41:16 yeah 15:41:46 we can sort that out after the meeting 15:42:00 okay, anything else? 15:42:23 #topic Website update 15:42:25 visa seems all done for the moment 15:42:26 ok 15:42:50 medicalwei[m]: Any update for website? 15:42:53 * tumbleweed is busy hacking on the registration system 15:43:01 Theme for wafer is ready (without any further examinations) 15:43:03 well, I was hacking full-speed during CCC but now I'm caught up in work 15:43:10 but weekend soon 15:43:25 I hope to get what I've got done, then 15:43:39 and get a replacement for wafertest.debconf.org up 15:43:56 https://screenshots.firefox.com/YA27VMQ8aCBMMC1f/localhost 15:44:28 Looks greate 15:45:35 Anything else for website? 15:46:04 not from me, yet 15:46:15 I hope to be able to have a conversation abuot what we need in the registration form, soon 15:46:30 #topic DC17 Status Update 15:46:36 tumbleweed: dunno, the person who deals with that is horrible, i hear... 15:46:36 I should claim for updating the timeline again... always forgot about this 15:46:40 0/ 15:46:45 yo pollo 15:46:54 The dc17 website is now static 15:46:59 yay 15:47:14 Still waiting on SPI to finish accounting for dc17 15:47:33 Poked them a couple of times, no answer 15:48:04 We had a meeting last week to work on the dc17 final report, about 25% of it is done 15:48:15 I guess that's it 15:48:47 #topic DSA Migration 15:49:19 I told ganeff I would push this 15:49:23 I think this is to discuss migrating to salsa.debian.org ? 15:49:44 Yes, our git stuffs 15:49:50 The idea would be to put all of our got repos in a group 15:50:00 Each team gets a subgroup 15:50:06 But that's different topic imho 15:50:20 Each subgroup gets a subsubgroup for the legacy stuff 15:50:46 And permissions are given on subgroups and not on the group to keep things sane 15:51:21 Oh, is there another topic for the git migration? 15:51:30 pollo: Any timeline for this migration? When do we need to push to salsa instead of alioth? 15:51:57 Asap, ganeff seemed eager to do it and only wanted our approval 15:52:00 Not yet... 15:52:23 I don't see why we can't migrate now 15:52:26 yeah 15:52:30 moving git repos around isn't exactly invasive 15:52:38 as long as you don't end up with different thnigs on each master 15:52:58 speaking as salsa admin: I thnink chances for a reset are near zero. From my perspective you can start migrating at any time 15:53:39 Does anyone has objections on the structure or the migration? 15:53:45 No problem for me 15:53:58 not at all, 100% for it! 15:54:07 But the problem of synchronizing Salsa and Alioth is a problem for now... 15:54:11 to prevent having 2 different masters... 15:54:25 maybe stop write access on alioth first 15:54:27 medicalwei[m]: simply stop using alioth? 15:54:36 then delete it after it's on salsa 15:54:49 well that's one way to go 15:55:06 use the alioth redirector service I announce later the day 15:55:31 that will at least make http(s) requests going to salsa. 15:55:34 we are using alioth to minidebconf curitiba site. Is it will be migrate too? 15:55:44 chmod -R -w on old repos? (or delete / move them) 15:55:59 tumbleweed: add a hook with a message 15:56:19 yeah, that's probably better 15:56:21 is minidebconf a sub group? 15:56:35 but anyway, Ganneff said he'd do the migration, so presumably he'll do one of the above 15:57:34 phls_brazil: sure, if Ganneff misses something just ping him 15:57:40 cat /git/pkg-postgresql/postgresql-common.git/hooks/pre-receive on alioth for an example 15:57:44 Can we get an #agree? 15:57:54 +1 15:58:10 yes 15:58:15 agree on "Ganneff will do the migration" ? 15:58:22 sure 15:59:02 #agreed Ganneff will do the migration from alioth to salsa 15:59:28 #topic Miscellaneous 15:59:39 next meeting time? 16:00:01 my question about bid :-) 16:00:19 question is? 16:00:55 if I understood correctly, Brazil is running alone, right? Is it possible Brazil not be choosen? And what will happen in this case? 16:01:15 We will look better possibilities ;-) 16:01:45 There is time for plan B and plan C. 16:02:18 But most probable negative outcome could be some restriction on venue/budget or some requirements to take into considerations 16:02:56 phls_brazil: technically Brazil will be competing against Bratislava in the bid meeting 16:03:09 in the unlikely case Brazil falls out (I hope not!) I can put triple energy into turning the dry run into damp run into wet run 16:03:39 so basically, Bratislava is the very remote backup plan, but we need to follow the process 16:03:42 phls_brazil: and as far as I can tell Curitiba's bid is really good, I think it would take something really big and bad for Curitiba's bid to be rejected. 16:03:42 highvoltage: just Bratislava is less well-prepared :) 16:03:50 that's why were doing the evaluation and decision-meeting dance 16:04:57 we're 98% certain that it's Curitiba, but it would look very bad if we ignored the 2% chance and skipped the correct procedure 16:05:09 (probably even more than 98% actually, but you know what i mean, right?) 16:05:28 sure, the procedure is important 16:06:15 it would've been nice to have at least one solid bid against curitiba, the last few years it seemed that competition was really tough every year 16:06:20 (which is great for debconf) 16:06:43 I don't know if it's *that* important, but it's also a good check that the bid is actually ready 16:06:55 *nods* 16:07:02 And in any case, we should be sure that Curitiba meet the Debian standards (openess, inclusivness), debian can affort it, etc. Really there is also the possibility ode Debian "NOTA" None of the above. I doesn't think it is the case this year 16:07:25 yeah a lot could have changed since last year, so it's good to at least confirm that everything that was true last time still is now 16:07:59 the effect we tryied last year was very important to us to understand the procedura. With all questions were done 16:08:54 it was also a very close race 16:09:22 which shows that the bid is at the very least about on par with an already winning bid 16:10:05 So I don't think you will fall out of bid before a solid competitor shows up 16:10:54 yeah, last year was difficult. I voted tw because new continent was a big advantage, but br teams seemed larger and more experienced on orga. [this argument could be used still for australia and antartica... so for dc20...] 16:11:25 * pollo votes for penguins 16:11:27 And since Asia is big, possible for India too. 16:11:56 * medicalwei[m] votes for kangaroos :3 16:12:26 you won't believe how many times people have told me that they want to come to south africa to see the kangaroos 16:12:43 [australia, new zeland, some part of france and other islands] 16:12:47 Yes, i think we are more prepared now too to run. I think last year was good to us to know how the BID works 16:12:55 highvoltage: at least they can see penguins 16:13:13 I think we can discuss next meeting time, Jan 19 ? 16:13:22 [Tahiti] 16:13:38 +1 16:14:03 any objection about Jan 19 as our next meeting time? 16:14:11 it is ok 16:14:11 no objection here 16:14:15 wait 16:14:17 Jan 18 16:14:18 that's a Friday, correct? 16:14:20 <_rene_> sigh. so again nothing affordable? :-( 16:14:28 Opps, wrong date 16:14:35 czchen: i do object. do you mean the 18th? 16:14:37 Shall be Jan 18 16:14:38 :) 16:14:42 Jan 19 then Jan 26 for DC19 big 16:14:45 s/big/bid 16:14:47 it'll be a birthday party for Q 16:14:59 * valessio[m] if DC19 is in Brazil, DC21 is very likely to happen in Cuba. 16:15:09 I don't realize it passes midnight 16:15:12 OOPS... 16:15:27 Jan 18 then Jan 25 for DC19 bid 16:15:30 any objection about Jan 18? 16:15:36 no from me 16:15:41 s/no/not 16:15:52 no objection to the 18th :) 16:15:58 Okay for me 16:16:16 #agreed next meeting time Jan 18, 2018 14:30 UTC 16:16:21 anything else? 16:17:24 #endmeeting