19:30:00 #startmeeting 19:30:00 Meeting started Mon Sep 29 19:30:00 2014 UTC. The chair is marga. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:30:00 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:30:00 . 19:30:09 marga++ 19:30:11 Hi all. If you haven't already, please have a look at the agenda, it includes background information on the subjects that we expect to touch during the meeting: 19:30:19 #link https://wiki.debconf.org/wiki/DebConf15/Germany/Minutes/2014-09-29#Agenda 19:30:24 Can we do a very quick roster call? Everyone that's here, please say "hallo" (or equivalent) 19:30:29 hallo 19:30:33 hallo 19:30:33 miau 19:30:41 hi 19:30:43 moin 19:30:44 <_rene_> 'n abend :) 19:30:50 marga: pingall? 19:30:51 * gwolf confirms _not_ to be here :( 19:30:51 mahlzeyt! 19:30:53 Hallo 19:30:57 * gwolf is leaving _now_ 19:31:01 enjoy the meeting! 19:31:06 hi, I'm half here ;-) 19:31:09 hi 19:31:16 I'll try to follow 19:31:23 RichiH, I thought meetbot would do it, but it was done half an hour ago... And most people seem to be here. 19:31:26 Hi 19:31:35 During the meeting, if you think we need to add a new urgent topic or we need to go back to previous topics, please send me privmsg. 19:31:55 #topic Status Updates 19:32:00 We have quite a bunch of items from the previous meeting. The purpose of this section is to follow up on them. Please be ready to provide your updates. Use the #info command if appropriate. 19:32:12 #topic Status Updates - Verein 19:32:14 madduck, RichiH ? 19:32:30 awaiting non-profit status 19:32:33 nothing new 19:32:36 i got a confirmation letter from the district court 19:32:40 hallo (late!) 19:32:49 meaning we are registered 19:32:52 RichiH, what does that mean? 19:33:02 marga: meaning we won against the lady ;) 19:33:06 marga: just the official confirmation that they are, in fact, done 19:33:12 #info Verein is registered, we are awaiting non-profit status 19:33:18 it basically repeats our bylaws and registration letter 19:33:19 ETA for the non-profit? 19:33:29 another week, maybe two 19:33:34 in my experience, they are pretty fast 19:33:46 #info we should have news about this in one or two weeks 19:33:54 as an aside, madduck is working on ironing out tax details 19:34:05 else, there's nothing of value to add 19:34:09 #topic Status Updates - Website 19:34:12 #info The poll regarding background was quite close, but the white background won. The change has already been made, along with some fixes, including fixing the logo background 19:34:27 <_rene_> thanks :) 19:34:31 it's still flickering when dark contrast is selected, valessio is on it 19:34:37 It would be nice to have a "news" box with links to the DebConf blog somewhere in the website, but for that we would need a "webmaster" 19:34:38 flickering on page change 19:34:48 Yes 19:34:53 we should just have the blog on the front page, no?> 19:34:58 <_rene_> yes 19:35:03 like in the last years? 19:35:04 Uhm... Always? 19:35:05 blog is cheap and easy content, yes 19:35:09 ok. 19:35:11 <_rene_> we should simply activate the rss 19:35:13 marga: for some time 19:35:13 Who takes that? 19:35:18 anyway, we can do this without infrastructure people 19:35:25 once we have actual content, we move the blog to news 19:35:27 <_rene_> which I commented out for the initial version as there was only dc14 content there by then 19:35:31 on the sidebar 19:35:40 there's various RSS feeds to choose from, though? 19:35:52 _rene_, are you able to do this now? (i.e. laptop issues) 19:36:02 azeem: there is a dc15-only blog IIRC 19:36:09 oh no, there isn't 19:36:11 that was the point 19:36:14 anyway, dc14 is done 19:36:16 <_rene_> yeah, IRCing from the new one now 19:36:21 so only final report left 19:36:21 Ok. 19:36:28 _rene_, so, can you handle this? 19:36:46 it would be weird if a blog post about the DC14 final report showed up, IMO 19:36:49 <_rene_> enabling of the rss? yes, probably. should just uncomment it 19:36:52 but maybe it's not a big issue 19:36:55 azeem: we can frame it as dc15 19:37:00 <_rene_> do we have larjona s blog post already? 19:37:02 each subdir should have an rss on blog, so there should be a dc15 only one 19:37:04 yes 19:37:13 http://blog.debconf.org/blog/debconf15/index.rss11 19:37:13 #action _rene_ will handle re-adding the rss (dc15 only) to the website 19:37:15 there 19:37:26 Ganneff: is that one syndicated on Planet Debian as well? 19:37:32 there it has the main 19:37:36 _rene_: Ganneff is right: http://blog.debconf.org/blog/debconf15/index.rss 19:37:38 (which includes all subdirs) 19:37:51 so basically yes, its on planet 19:37:54 Ok, awesome 19:38:06 <_rene_> ok, so I'll reclone now and do it probably tomorrow 19:38:12 #topic Status Updates - Impressum 19:38:14 #info madduck has added a link (Imprint) with the legal data required by German Law 19:38:18 Why is it in English? Shouldn't it be in German? 19:38:36 should there be a german version of the website? 19:38:42 I mean in general 19:38:44 <_rene_> it's an english website? we just made sure it has one 19:38:58 which website? 19:39:00 i think it's fine. 19:39:08 In general, I wouldn't think we need a German version of the website 19:39:13 n0rman: debconf15.debconf.org 19:39:21 But for following German law, I'd expect it needs to be in English 19:39:37 In any case, if I'm the only one that thinks this, then we can move on and consider this done. 19:39:40 marga: the server is IIRC not hosted in .de 19:39:46 so this is optional anyway 19:39:49 <_rene_> yep 19:39:52 we're done, let them come and complain 19:39:52 its in the UK 19:39:55 <_rene_> just for safety 19:39:55 and then we can handle it still 19:39:58 ok 19:40:00 #topic Status Updates - CCC / FrOsCon 19:40:12 conny, rhalina, sur5r: Any News? 19:40:20 marga: not really 19:40:31 no, haven't heard anything 19:40:42 Ok... :-/ 19:40:45 #info No news 19:40:49 conny is not attending today (sick) but I don't thing she has any news 19:40:52 As far as I know the date for the Camp is still not set. 19:40:55 do we know when CCC camp will be announced? 19:41:07 I mean the dates, usually 19:41:28 If I remember correctly end of the year - but I'm not sure 19:41:33 ok 19:41:36 but it varries 19:41:39 azeem: I doubt there will be real news before the Congress from what I heard from the Orga 19:41:44 aye 19:42:01 #info Probably no news for quite a while 19:42:03 #topic Status Updates - Brochure translations 19:42:07 rhalina, Is this done? What's missing? 19:42:18 The first draft is done 19:42:45 yeah, great work 19:42:45 What still needs to be done? 19:42:54 we definitely need someone with "distance" to read this over 19:42:56 Conny said she will rework tomorrow to have everything in the same style (i'll help) and we can expect to have a final version to be proof read on wednesday 19:43:06 azeem has been checking the quotes with their sources 19:43:09 * azeem has contacted the two people who provided quotes who are native germans, and got their translated quotes authorised 19:43:23 #info First draft ready, needs people to proof-read 19:43:25 I'm not sure we should translate the one from Bytemark hosting (or the others) 19:43:26 but the rest needs a good look and possibly some fixups. 19:43:44 azeem: yeah, neither… 19:43:45 thats clear 19:43:46 Do we have volunteers for the proofreading? 19:43:57 if you translate em, have the english in small print besides 19:44:00 well, the Bytemark quote got translated already 19:44:00 marga: ideally someone who has not worked on this. 19:44:01 I don't think we should translate them 19:44:13 azeem: we don't need to take the translation 19:44:22 *nod* 19:44:40 Repeat: one or two people that volunteer for proof reading? 19:44:45 I /might/ be able to proofread the translation, but I'd prefer somebody else volunteer 19:44:45 we just divided the pages between us - so not harm done if we exclude a translation 19:45:03 last meeting a bunch of people volunteered for proofreading 19:45:09 but i don't remember wo 19:45:09 i can read over it. is it in git? 19:45:15 * RichiH too 19:45:18 Ganneff: yes 19:45:18 Ok, thanks 19:45:20 (ping me when its ready for it) 19:45:23 aye 19:45:23 same 19:45:26 what I noticed is that at least towards the end some spaces are missing cause the lines in the de.po don't end with ' "' 19:45:29 #action Ganneff and RichiH to proofread once it's ready. 19:45:39 azeem: jupp i saw that as well 19:45:43 but thats easily fixed 19:45:45 * and1bm can proof read too 19:45:46 yeah 19:45:49 Thanks for the great work on this... Moving on. 19:45:51 #topic Status Updates - Fundraising announcements 19:45:57 bgupta: I believe this is done, right? 19:46:00 yes 19:46:09 and1bm: ok i'll ping you too 19:46:11 madduck, do you have a link handy? 19:46:12 also a note in the dc15 blog post 19:46:24 #link https://lists.debian.org/debian-devel-announce/2014/09/msg00003.html 19:46:27 danke 19:46:34 #topic Status Updates - Budget 19:46:36 rhalina: OK 19:46:38 madduck, hug: ? 19:46:54 so the basic model is done, hug has yet to review it 19:47:04 but in general, what we need next is numbers for the assumptions 19:47:08 how much do we have to fundraise? 19:47:13 oh, ok 19:47:15 azeem: too early to say 19:47:20 #info madduck created a spreadsheet to model possible scenarios. Hug still needs to review assumptions. 19:47:21 how many people do we expect each night? 19:47:25 no 19:47:27 marga 19:47:34 the assumptions are not there yet 19:47:42 ah, ok. what does he need to review? 19:47:44 we need to come up with them and I think we should have a meeting for that 19:47:52 that i translated the contract into Calc ;) 19:48:00 we can just keep going though 19:48:14 so there are a bunch of variables in there 19:48:24 and those need to be forecast 19:48:27 #info *Correction* Hug to review the Contract-to-ods translation, we need a meeting to review assumptions 19:48:42 Alright. madduck can you handle calling a meeting for this? 19:48:49 yes. 19:48:58 madduck: Is that in the dc15 git ? 19:48:59 #action madduck to call a meeting specifically for that 19:49:38 maxy: yes, I sent you the URI in the response to your poke 19:49:39 #topic Status Updates - DayTrip / Conference Dinner 19:49:46 rhalina, any news on this? 19:50:59 ... 19:51:18 Alright then... Moving on... 19:51:20 #topic Final Report for DC14 19:51:21 manuel answered my poke about this, but he was sick, so he didn't do much. 19:51:29 #link https://wiki.debconf.org/wiki/DebConf14/FinalReport 19:51:36 #info Most sections are taken, but we need a global coordinator and we need to set a deadline for text submission and for publication 19:52:06 * azeem has updated the talks section with some content from ana's report 19:52:06 We need the feedbacks 19:52:27 still need to update one subsection though and send to the talks team for review and TODO fixups 19:52:40 maxy: you mean the blog posts? 19:52:49 did we collect a few" 19:52:52 ?* 19:52:54 i've been poking CarlFK for video (no response), nattie for the sections she claimed (she said last weekend), and harmoney for hers (no response) 19:53:06 azeem: there was just a dc14 blog post with a lot of links 19:53:06 eh, like 20 19:53:11 I have asked the chairs to review the feedback@dc.o situation, but I don't think this blocks the FR in any way 19:53:12 https://wiki.debconf.org/wiki/DebConf14/FinalReport/Links 19:53:21 #link http://blog.debconf.org/blog/debconf14/wrap-up.dc 19:53:25 Indeed 19:53:36 This is my task, I intend to do this this week. 19:53:39 none of the feedback we received is good for the FR 19:53:40 maxy: do you mean we should have a "Feedback" section in the report? 19:53:53 I tend to agree with madduck 19:53:56 certainly not a blocker 19:54:06 azeem, no, he meant the feedback from feedback@dc.o, but I don't think we will use that. 19:54:21 maybe we (or whoever feels responsible) could discuss whether we should just dump whole blog posts, or edit them 19:54:27 i.e. take paragraphs or parts of them 19:54:36 madduck: I have v2 of my report about done. waiting on one last review in the next 12 hours and I'll send it in as is reviewed or not 19:54:41 for the attendee's impression section 19:54:45 azeem: No, I mean the mails sent to feedback@debconf.org. It makes little sense to ask for impressions if we are not using those. 19:54:45 What I want is someone in charge of coordinating the whole FR, setting deadlines for content and for editting. 19:54:52 CarlFK: super, thanks! 19:54:56 marga: sorry 19:55:01 wireless broke dowb 19:55:03 *down 19:55:05 maxy: well, we asked for feedback and we will evaluate it 19:55:11 but I don't think it should go into the report 19:55:28 v1 will go to harmoney for feedbacky things 19:55:29 we should send a summary to -team at some point, though I guess 19:56:29 Can we appoint someone to be in charge of the whole? 19:56:49 #action madduck to add feedback@dc.o handling to next agenda 19:57:05 marga: the whole feedback@dc.o? 19:57:08 or the final report? 19:57:13 The final report 19:57:20 azeem, are you in charge? 19:57:26 *sigh*, ok 19:57:30 ok :) 19:57:33 azeem: I will help you. 19:57:40 though I am not sure how much time I can spend the next two weeks 19:57:55 #agreed azeem and madduck to share coordinating the FR as a whole 19:57:58 Deadlines? 19:58:02 We need deadlines 19:58:04 azeem, madduck: i can help too, a least poking people :) 19:58:11 Deadline for submission and deadline for publication 19:58:15 publication end of October 19:58:26 Submission 15th? 19:58:30 submission: the night before…? ;)( 19:58:37 marga: sounds ok 19:58:50 as we can still negotiate with people directly 19:58:57 #agreed Deadline for submissions Oct 15th, for publication Oct 30th. 19:59:00 Caroll: … would you be willing to start the "credits" page? 19:59:34 madduck, yep... well, I'll need some help, but I can start and ask when the time comes 19:59:50 #agreed Caroll to start working on the credits page 19:59:50 Caroll: use last year's as template, and sure, ask anytime 19:59:51 what's most important for the credits page IMO is to reach out to the teams (talks, video etc.) to get a good list of people 19:59:57 but the wiki page should be a good start 20:00:04 madduck, ok, thanks 20:00:08 #topic Airline Partnerships 20:00:11 Caroll, how's this going? What can we do to help? 20:00:39 marga, no responses at all 20:00:53 I'll do one more round of emails/contact forms 20:01:01 the lufthansa info on thw wiki page sounds interesting 20:01:04 and I'll try to call them too 20:01:27 #info No progress yet. Needs more poking 20:01:32 they really want to do "official airline"? and what exactly does that mean 20:01:37 Ganneff, yep! Lufthansa has partnership with united too, would be the best option 20:01:42 yes. 20:01:59 im asking as i was trying to get to someone from inside LH, but not yet gotten very far 20:02:12 so if there is already something established thats good (dont know), then i could drop that 20:02:28 but if it is still unclear, i continue. 20:02:33 in the website they ask to be the only official partner... I think we shouldn't have any other partnership 20:02:33 Ganneff: can't help to push internally, as well 20:02:52 maybe contact the people Caroll's got contact with so they see internal support 20:02:55 RichiH: it "cant help"? 20:03:07 Ganneff: multiple paths can be really bad… 20:03:07 Ganneff, I would appreciate if you could help getting some intern contact there :) 20:03:23 so you need to coordinate with each other… ;) 20:03:25 Caroll: can you tell me who you are in contact with (off meeting) 20:03:36 Ganneff, sure :) 20:03:46 #agreed Ganneff and Caroll to coordinate talking with LH 20:03:47 Ganneff, I'll send you a email 20:04:03 #topic PR (website, social media) 20:04:05 larjona has created a page with some ideas for promoting DebConf in general: 20:04:05 its a long shot on my side anyways, as im far away from any people doing sponsoring, but im trying to use the networks inside lh 20:04:09 #link https://wiki.debconf.org/wiki/DebConf15/Germany/PromotionIdeas 20:04:11 Caroll: thx 20:04:33 I believe she's looking for more people to help her out. 20:04:46 larjona, anything else to say about this? 20:04:55 i think this is a fantastic start by larjona 20:05:01 Yep 20:05:03 yes :) I've sent email to debconf-team too http://lists.debconf.org/lurker/message/20140929.185252.783e003c.en.html 20:05:05 we should *all* keep in mind that we have a PR team 20:05:09 whether we are part or not 20:05:17 half of the work is providing ideas 20:05:21 we should certainly microblog new sponsors 20:05:27 content and actual publication is the second half of the story 20:05:35 agreed 20:05:38 Should we? I was unsure about that one, but it does sound like a good idea. 20:05:38 (and reblog their corporate accounts if they mention sponsoring DC on it) 20:05:39 (azeem) 20:05:49 I suggest looking at PGConf.eu 20:05:51 's twitter 20:05:54 marga: other conferences are *a lot* more active 20:06:08 https://twitter.com/pgconfeu 20:06:11 i would even suggest adding twitter/g+/facebook links to our webpage and get more engaged 20:06:17 Ok, I don't disagree :) 20:06:18 there are ways to do this without being tracked 20:06:35 well, their sponsoring is a while ago, it was about registration recently 20:06:37 i.e. you click to load the actual tracker^W link 20:06:54 I have the feeling that some people would not agree... 20:06:58 point being: larjona (and I for @debconf) can do all the microblogging 20:07:02 I think this shold be discussed in the ML 20:07:06 especially with the help of deb-publicity 20:07:13 but we need to get impulses from *everyone* 20:07:28 it puts non-free and bad services on our frontpage -> not going to go down well 20:07:30 tassia: sure, I know. But this is probably a worthwhile idea. 20:07:40 Ganneff, ++ 20:07:45 Ganneff, it doesn't need to be twitter 20:07:46 let's not discuss this here 20:07:51 * _rene_ disagrees with twitter/g+/facebook links on the website, too 20:07:52 this needs further discussion, in the ML 20:07:55 if its free services -> sure way. 20:08:01 and yes, ML 20:08:03 We can post officially in the free networks, and *people* in the other ones repeat/retweet etc 20:08:14 right 20:08:30 #agreed services to be used and how to use them require a bit more discussion on the ML 20:08:38 madduck: is there an actual benefit to using social networks, social or not? 20:08:44 but yah, we can move this to ml 20:08:49 what we can do is use pump.io and syndicate to twitter 20:08:50 Ok, next topic 20:08:58 marga: also make sure we keep in the minutes that *everyone* brings in the stories 20:09:13 #plea … ;) 20:09:18 #idea Everyone should try to bring in content 20:09:32 #topic General schedule format 20:09:33 There's been quite some discussion about this. 20:09:34 now we just need a way to track that stuff 20:09:37 we will come up with a plan 20:09:41 #info The idea of shorter talks has been pretty much accepted, provided we still leave the option for longer ones, which was always the intention. 20:09:50 #info Food times are set by the Hostel and we can't actually move them. Breakfast 7-10, Lunch 12:30-14, Dinner 18:30-20:30 20:10:01 lunch to 14:30 20:10:01 madduck, correct? 20:10:07 should i check? 20:10:15 madduck, I thought you already had? 20:10:33 12–14 is what we agreed in the contract, but that's changeable 20:10:42 they just can't push dinner later 20:10:45 ok. 20:10:47 because the shifts end 20:10:56 and they need enough time between meals for cleaning 20:11:10 #info Lunch was agreed from 12-14, but can be moved. Dinner can't be moved 20:11:27 7–10, 12:30–14:30, 18:30–20:30 is current status with HD IIRC 20:11:59 Now, on the rest of stuff there's more to discuss. I'll list the points that still require discussion one by one, so that we try to agree on stuff: 20:12:01 1) Announcements + Keynote + Talks in the morning. Proposals: 20:12:05 A) 9:45 + 10:00 + 1.5h (finishes at 12:30) 20:12:11 B) 10:05 + 10:15 + 1 h (finishes at 12:15) 20:12:24 Are there other proposals regarding this? Comments? Others? 20:12:41 BTW, there's a dump of this in https://titanpad.com/dc15-schedule 20:12:42 do we really need to decide it now? 20:13:01 tassia, we need to decide it at some point. It doesn't need to be now 20:13:09 it should be before scheduling, but thats far away 20:13:13 But if we decide it now, then it's decided and we can move on to other stuff. 20:13:17 I mean, maybe people from talks team would like to participate in this decision 20:13:39 there is the debconf-team thread 20:13:39 tassia: traditionally, they got slots and then had to work around them, but I agree with you 20:13:45 marga, the problem of having already too many decided things is that people who arrive later will have already a script to follow 20:13:52 I think we should come up with a dc15 proposal 20:13:59 and then run it by the talks/scheduling team 20:14:19 madduck: really usually there was a discussion both ways 20:14:22 <_rene_> tassia: but that is the case for any decision we do :) 20:14:36 this is also not a hard decision which can in no way changed later, if needs be, we could be flexible I guess 20:14:40 yes, if it is not urgent, I'd let it just as a recommendation, not a decision 20:14:42 Indeed, if we are going to wait for more people to join, then we are not going to use this time at all. 20:14:49 i have a question to maxy about A) 20:15:03 cate: okay, then we should do that 20:15:18 maxy: in those 1.5h, what do we do? three short slots? two long slots? 20:15:20 well, do we assume the talks team is not reading -team? 20:15:31 azeem: I think it's important to reach out explicitly 20:15:33 madduck: At least one short slot 20:15:34 1 long 1 short? 20:15:41 madduck, that's up to the talks team. But it would either be 3 short or 1 long + 1 short 20:15:53 okay. hadn't thought of that. busy day ;) 20:15:54 azeem, not everyone followd all the messages 20:16:17 the talks team ... we are plenty early right now for "the talks team", most people havent wrapped their head around "dc14 is over" at this time, let alone deciding on scheduling issues for the next conf so far away 20:16:20 IMHO it is good to decide if we will have short slots, but than we must wait to see if there is more request on short or on normal slots. 20:16:31 marga: I think we should not overlap announcements and breakfast, for purely psychologivcal reasons 20:16:40 if it is something that should be discusses within a team, and is not urgent, I don't see why we need to decide now 20:16:55 I think we can just come up with a proposal nowish 20:16:58 marga: (though I agree with your point…) 20:17:01 madduck, I don't think it will make a difference. 20:17:02 arent we lacking the information on what people will submitt for scheduling? (even slot length)? 20:17:09 but we can always discuss, and even have a soft decision, but always letting the team decide at the end 20:17:14 as we used up 46 of our 60 minutes, maybe we can bounce this to the ML once more? perhaps with an explicit poke towards to the talk team 20:17:23 marga: psychologically, having it at 9:45 before breakfast ends makes it way more optional than having it non-overlapping, no? 20:17:39 that sounds like a feature 20:18:05 rhalina: the talks team will have X slots available and to accomodate as many events as possible, they might tell someone that they can have the slot if they are willing to do it in 20 mins 20:18:18 bremner: not if we want people to listen to our announcements. 20:18:26 that's the whole point, an asset to organisers. 20:18:38 I think in that case non-overlaping is important 20:18:39 RichiH, it already got stale on the ML, and now we are losing time discussing if we should discuss... 20:19:06 marga: how about a concrete proposal to the mailing list, for feedback from the talks team? 20:19:07 madduck, the problem is that moving everything later, "eats" time from the schedule. 20:19:21 bremner, there's been a bunch of proposals 20:19:31 how about breakfast till 9:45? 20:19:34 We need to agree first before making a proposal 20:19:34 marga: we are talking about one 20 minute slot right now 20:19:36 marga: yes. so choose (as a group) one? 20:19:37 azeem: doable… 20:19:39