18:32:23 #startmeeting 18:32:23 Meeting started Wed Sep 9 18:32:23 2015 UTC. The chair is tumbleweed. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:32:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:32:33 #link https://wiki.debconf.org/wiki/DebConf16/Meetings/2015-09-09 18:32:34 Agenda 18:33:13 hi MeetBot 18:33:14 tamo and I are having a glass of wine/beer, so we're relaxed and learning wiki and code stuff 18:34:12 #topic tasks page for volunteers 18:35:16 indiebio: are you going to talk about any of this? 18:35:37 is there anything in this agenda that we need to talk about, basically? :) 18:35:40 I can, I wrote it all on the wiki, but sure. stop me when it gets boring 18:35:59 hi 18:36:02 So nkukard suggested a task page (and it was mentioned before) for people to sign up for small takss 18:36:20 uhm, regarding things that need discussion, yes 18:36:45 So, the break-down, from my side: 18:36:46 so, there's a lot on the tasks page that duplicates things canonically sourced elsewhere 18:36:51 (like team contacts) 18:37:14 and the timeline 18:37:22 I would like people to take note and edit as they see fit, the task page, the timeline, sponsors. 18:37:31 The logo and website needs actual discussion 18:37:43 tumbleweed: yes 18:38:05 I designed this for people with no clue abut debian (girl/boy friends, wifes/husbands who get roped in) 18:38:12 one page where they can sign up for stuff 18:38:26 if these tasks are done by existing teammembers, they should put their names down there 18:38:29 if these tasks are done by existing teammembers, they should put their names down there 18:38:58 so I hope that the tasks page and timeline are the go-to page for us during the whole event orga 18:39:09 the reference page for whenever we need to know something - when what needs to be done and who is doing it 18:39:50 why both? Can't we put the tasks in the timeline and then the core team knows which ones need to be done and have no volunteer yet? 18:40:10 ok. Then we must go through it and ensure it's accurately describing current teams, so no team feels usurped 18:40:13 DLange: yeah, I like this idea, and it also makes it easy for late-joiners to know what's current. 18:40:37 we could, I guess, but it gets very big and clumsy... 18:40:44 I don't mind, if someone else wants to take it - I made a start, do with it as you wish 18:40:45 but a single view of things ... usually more helpful than partially redundant views 18:41:09 indiebio: I think it's useful 18:41:11 maybe the wiki isn't the best format, but a timeline-based approach to things that need doing makes a lot of sense IMHO. 18:41:20 tumbleweed: yes. I think we need a whole meeting just for that. I just wanted to draw attention to its existence today 18:41:30 ack, shall we move on, then? 18:41:43 so we can minute that it exists, that people should look at it, and we can sprint it in due course 18:42:16 sure. 18:42:41 #idea people to review the task list, and expand / correct contents 18:42:54 #topic Timeline 18:42:57 we've already touched on this 18:42:59 anything else here 18:43:01 ? 18:43:18 (sorry, I'm not being the fastest chair I can - my computer is bogged down with a pypy build, making iceweasel very unresponsive) 18:43:29 renice :) 18:43:53 that's fine, I think we can move to design, tamo? 18:44:41 #topic Design 18:45:08 So, sub-topic:Logo 18:45:29 We realised during debconf that the logo was never properly 'onboarded' and people felt it was rushed 18:45:52 We just want to make sure, and if needed give one more week for everyone to make final suggestions on the logo. 18:46:12 So, can we ask, is anyone feeling they want the logo tweaked or changed in any way? 18:46:27 especially highvoltage, superfly 18:46:40 tamo has put more options on dropbox 18:47:06 the internet here in the pub is not sterling, but if it's not there yet it will be by tomorrow, and I'll make sure it makes it to git as well 18:47:10 can you paste a publically accessible link ("share")? 18:47:23 link please 18:47:24 I'm fine with it. There's enough that I can keep the general theme when working on different form factors 18:47:47 I think only tamo can share it 18:47:49 DLange: I'll make a note of it and work with tamo on this after the meeting 18:48:06 ack 18:48:31 dropbox link: https://www.dropbox.com/l/G4XntzCDvRTjWPf7tUQBbv 18:48:35 check it works? 18:48:56 indiebio: those are my final suggestions, please see my comments, but everybody is welcome to make their proposals, it's about teh Cape Town font not the actual log. 18:49:19 so just the swirly text, right? 18:49:37 highvoltage, what's your thoughts on the logo, do you want a week to play with it? 18:49:44 tumbleweed: hey tumbleweed I did invite everyone and left it as editable 18:50:02 indiebio: yes, my understanding 18:50:21 indiebio: I don't know that PDF seems to change the only thing everyone seemed to be happy with :) 18:50:33 huh? 18:50:36 tamo: indiebio's liknk is doing the trick 18:51:09 tumbleweed: okidoke cool 18:51:25 so are you happy, highvoltage? 18:51:26 indiebio: you saw the PDF? it has variations of the typeface "Cape Town" is written in. afaik most people were happy with how cape town was written. 18:51:34 highvoltage: sorry not understanding can you explain? 18:51:46 yes, so maybe we don't have to change that then 18:51:58 highvoltage: is there anything you are still unhappy with, about the current logo (besides the process, which has mostly run its course :P ) 18:51:59 but do you want to play with more logo ideas, highvoltage? 18:52:29 well I think the "debconf" font doesn't look at all relevant, it doesn't seem to fit either debian, debconf or cape town 18:52:55 that's just me and I don't want to hold anything up, like I said at debconf I feel no need to drag that out 18:53:24 I agree with highvoltage. And the two fonts always fight each other, no matter which ones you use. 18:53:31 can we give you a wekk deadline to come up with an alternative, at which point we discuss all the options available, and then make a decision on a final logo then? 18:54:00 so if we finalise the logo now, tonight, would you be ok with that, highvoltage, DLAnge? 18:54:13 one other thing, capitalization: isn't it usually written 'DebConf', rather than 'debconf'? 18:54:14 the sooner the better 18:54:18 highvoltage: I feel similarly. But I also do like the logo, and we have to settle on one soon 18:54:23 indiebio: I can post some alternative font suggestions, I'd rather have that by the end of tomorrow than a week from now 18:54:26 I dunno, I like the logo as is. I'd like the 'proper' debian swirl somewhere, but I'm easy 18:54:29 ginggs: either will work, but generally DebConf, yes. debconf is a perl script. 18:54:31 can't say I'm a big fan of the "debconf" font either, but it's workable imho 18:55:01 ok. so can we minute that by end of Friday (for some flexibility) highvoltage will have alternatives, 18:55:04 indiebio: I don't know how else to say it, I repeatedly said at debconf I'm fine if we settle with the current logo 18:55:14 indiebio: rather than saying "come up with alternative" to a bunch of non-designers. Can we rather agree to work together? 18:55:16 and then we discuss that over the weekend, those who want to, and we finalise it by the next weekly meeting 18:55:26 indiebio: i think it can be considered "decided", no? 18:55:31 but I want you to be happy, highvoltage :) 18:55:32 tamo: then I think as indiebio said maybe come up with suggestions and a week is what the deadline is 18:55:37 if tamo is open to feedback and working with someone on design, that could work. I don't think people can be expected to have final proposals by the end of this week 18:55:54 or, of course, we could just decide that we're happy with it now, and move onn 18:56:12 +1 ;) 18:56:14 *finally* at my desk 18:56:17 let's be realistic about what we can accomplish this week 18:56:26 I don't think everying needs to submit proposals, if you want to, you do. 18:56:43 I don't think anyone is going to submit proposals 18:56:48 pushing on doesn't mean it gets better 18:56:49 nobody has indicated that they will 18:56:56 tumbleweed: thata is the problem I am thinking we need the sponsors brochure done, but can't put the wrong logo on it will be inconsistant 18:56:57 it would be best if we decide it's final and move on, but if people are really unhappy and want to redo this, then that is important. 18:57:03 we don't ask tamo to fix highvoltage's code either 18:57:15 tumbleweed: pardon spelling 18:57:16 tamo: absolutely, we have to finalize it fro the brochure and website 18:57:21 so why not collect the feedback and have another design interation... 18:57:34 DLange: no, that would be cruel. 18:57:46 DLange: :) 18:57:55 ok, so is everyone happy that we consider the logo finalised? can we minute that? 18:58:12 speak now and wear your badger proudly 18:58:27 mushroom! mushroom! 18:58:38 I don't understand why I have to be happy about it. I'm prepared to accept it and that's the best I can do. 18:58:38 * superfly is fine with that 18:58:53 highvoltage: :P 18:58:58 indiebio: haha 18:59:06 #agreed our logo design is final 18:59:16 subtopic: website 18:59:17 ok, we'll make you happy from now on, highvoltage. I will try my level best 18:59:57 indiebio: ok so is that sytems go?? re: logo? 19:00:03 so this is website DESIGN, not front end coding or wafer. 19:00:09 tamo sent the banner image through this afternoon. I haven't had a look at it yet, but her wireframes so far are OK 19:00:54 Nothing I cannot put together 19:01:00 ok, and we definitely want input, alternate design ideas of any sort, opinions, bike shedding on this can commence and continue for an amount of time 19:01:03 superfly: yes sorry been up to my eyeballs since I got back!! 19:01:06 (aside from that diamond in the middle of the menu) 19:01:39 highvoltage: what time frame do you suggest for the ideas phase to continue until? 19:01:55 superfly: ok :( but can work around that, banner was just beginning stages must do more design on it 19:01:59 and can we agree on the 'wireframe' layout, the boxes and positions of things, so superfly can start coding it? 19:02:00 maybe? 19:02:30 indiebio: not sure I understand the question, I think tamo's wireframes so far are great and we can work together to evolve that work 19:02:45 so not colours and fonts and stuff, but the initial coding of it? 19:02:49 excellent highvoltage 19:03:04 indiebio: imho superfly could work directly into templatizing it as it evolves so that we could use it in whatever system we'll end up using 19:03:07 indiebio: coding makes no sense without some sort of colours and fonts and stuff 19:03:08 so superfly/people can start work on that, and then we can design the stuff together? 19:03:14 argh 19:03:33 surely it can... back when I websites it could. search and replace colours, no? 19:03:41 indiebio: imho wager is a logical choice for the static site already, and I think if it might end up evolving into more than that then we should treat that as a seperate discussion 19:03:47 indiebio: yes but good to start deciding on colours soon so it can be carried through to all elements of design and marketing etc,etc 19:03:48 I'm trying to find a way to move this forward efficiently but still give people time to design 19:04:03 indiebio: yes, superfly knows CSS :) 19:04:14 indiebio: I think the design will evolve as its implemented 19:04:28 ok highvoltage. i have no idea how any of this works, so how do we proceed? 19:04:33 and it can't take forever 19:04:33 indiebio: it's more than just find and replace colours, it's about layout and UX and meta 19:04:44 superfly: you're right we do need to put that in the bag too re, fonts colour etc 19:04:47 ok, superfly: tamo agreed too :) 19:05:03 indiebio: I suggest we work on wireframes and then mockups 19:05:05 so, meeting time is flying along, what are the next steps with interim deadlines? 19:05:13 brochure. 19:05:17 cool, and deadlines? 19:05:22 madduck: shut up 19:05:31 sorry 19:05:38 indiebio: I need a better idea of what content is going on the site 19:05:50 or should I just copy what past DebConf's have done? 19:05:53 superfly highvoltage we can alwyas organise a meeting time if need be? 19:06:02 tamo: I'd like to do that. 19:06:17 tamo: yep, that would be great 19:06:20 superfly: yeah, past debconfs sounds fine 19:06:23 agreed 19:06:37 superfly: I think there's a general trend to move information from the website to the wiki, to reduce load on website maintainers 19:06:44 we can take the content thing offline 19:06:46 superfly: yes if I can have a week to finish the website content of basic pages then we can meet and go through all? 19:06:50 agree tumbleweed 19:07:00 tamo: we need to do some sort of content matrix 19:07:01 superfly: so, it can be fairly simple :) 19:07:08 so can we minute to have a website meeting in a week? 19:07:08 tumbleweed: great 19:07:18 superfly: I think the main website's content depends a lot on how easy it is to edit 19:07:25 indiebio: yes, I'll get a content matrix together 19:07:25 superfly: content matrix??? 19:07:34 I think can we not discuss this here 19:07:37 if it's XHTML like now, then the tendency would probably be to keep it down to a minimum and use the wiki extensively, like DC15 19:07:37 #agreed website meeting next week 19:07:39 superfly: the backend? 19:07:40 madduck: you said you like .rst 19:07:41 let's take it further in that meeting 19:07:48 and move on to ... madduck: brochure! 19:07:55 if it's .rst or something like that (yes) in Git, then it can be expectec to be maintained a lot better 19:07:57 tamo: negative. let's take it further in another meeting 19:08:19 madduck: wafer supports that, it seems like a logical approach to handling content changes. 19:08:21 madduck: changing the current scripts to take rst from git instead of xhtml is quite the small change 19:08:40 DUDES. no more website talk. 19:08:45 tumbleweed: perfect 19:08:50 next: brochure 19:08:55 superfly: okidoke sounds good! 19:09:02 highvoltage: wafer supports rst in db, not rst in git (sorry indiebio ) 19:09:05 or website talk elsewhere 19:09:18 * indiebio runs away screaming 19:09:30 #topic brochure 19:09:35 let's make that clear 19:09:41 tumbleweed: oh bother. ok we can pic that up again :) 19:11:07 I have updated the meeting wiki of where I am at etc https://wiki.debconf.org/wiki/DebConf16/Meetings/2015-09-09#Brochure 19:11:08 tamo is learning wiki, just hang on :) 19:11:16 oh wow, see :) 19:11:21 haha I am learning!! 19:11:26 #link https://anonscm.debian.org/cgit/debconf-data/dc16.git/plain/Design/Sponsors_Brochure_print_draft_6sept15.pdf 19:12:25 tamo: what do you need from us? 19:12:26 we have put a few more changes on Dropbox waiting for it to download, but as I go along I will save and add etc 19:13:13 pages 1, 2, 4, 9 in that PDF are black for me. Am I missing something? 19:13:17 tumbleweed: there is a draft already that Brian added in Git in the design folder, it would be nice to hear a few comments on it 19:14:08 There is a draft in git/dc16/Design/Sponsors_Brochure_print_draft_6sept15.pdf 19:14:13 it's 13MB at the moment 19:14:16 indiebio: I linked to it already 19:14:19 ah 19:14:24 wait for it to load? 19:14:27 it looks fine to me 19:14:32 tumbleweed: ok can I send you to Dropbox then? 19:14:38 indiebio: what PDF viewer? 19:14:41 no black pages, indiebio? 19:14:46 it is big now, but tamo will flatten the images once it;s final final 19:15:08 indiebio: it's on my local machine, no waiting for loading necessary 19:15:33 no, tumbleweed, there's an updated one, but we haven;t loaded it yet, but nevermind, the 6sept one gives the gist of it 19:16:07 yeah, I also had black pages 19:16:14 i don't know then, tumbleweed. I'll put the next one on git, and dropbox should be synced soon, by tomorrow morning latest 19:16:20 tumbleweed: https://www.dropbox.com/home/DEBCONF2016/MARKETING20MATERIAL 19:16:31 can we minute that everyone look at it, see if they like it (if they care about it, that is)? 19:16:36 tumbleweed: one you pasted from git loaded fine for me in chromium's pdf reader 19:16:48 for those following at home, that is https://www.dropbox.com/sh/wmizkyzieb1i8fh/AAD9k5TrgW3h9KIgpDH_rjxSa?dl=0 19:17:14 guys, I could only arrive now, sorry :( 19:17:15 in the interest of time, can we get back to this tomorrow? 19:17:29 I'read backlog and send comments later 19:17:37 the bottom line is, we (tamo) is working on it, and it should be final by the 14th 19:17:44 it takes long, but it's worth it 19:17:45 tamo: which file in there? "Sposors Brochure more work done.pdf" hasn't uploaded yet 19:17:50 hi tassia :) 19:18:01 tumbleweed: I ahve used Debcon15 images as fillers, for now but need images if other debconf's would like to add some images related to the article 19:18:04 indiebio: so do you need help on content, or is that covered? 19:18:14 what's the source format for that doc? 19:18:19 no, I think it's done, wendar, madduck and co helped. 19:18:23 indiebio, hi ;-), and sorry for disturbing 19:18:30 the content is in final_text_ something something .txt 19:18:33 on git 19:18:36 tumbleweed: 1st draft of where I am at PDF 19:18:47 so unless madduck wants to know more, can we move on? 19:18:50 tassia: hey tassia!! 19:19:28 indiebio: I just want the final version. I don't care about looks (although it looks great), and nor do I think this is something the team needs to care about. We need to get started fundraising though. 19:19:33 sorry if I repeat myself or bgupta 19:19:44 I know madduck. 19:19:49 yes, it doesn't sound like there's much to discuss here 19:19:54 But looks are important too 19:19:59 ok, let's move on 19:20:00 we're mostly getting caught up in finding the PDFs that you're talking about :) 19:20:15 #topic Website content 19:20:15 website: I think we can discuss it all at the website meeting? 19:20:26 have we covered this sufficiently, yet? 19:20:28 The only thing to minute here is that we have decided to go with wafer 19:20:29 tumbleweed: sorry we will have it loaded properly etc :( 19:20:30 * highvoltage will spend some time on content polish where possible/welcome/needed tomorrow 19:20:31 (not summit) 19:21:00 tumbleweed: I'm going to take a look at dc15 and dc14 and make a content matrix, and we can talk about it at the website meeting 19:21:07 righto 19:21:16 #topic contracts 19:21:29 contracts are equally slow and frustrating :(( 19:21:34 indiebio: you asked me for progress? I can't really help here 19:21:39 we need something to show SPI 19:21:41 and the DPL 19:21:47 I emailed Belinda of CMC again, but didn't call her today as promised. will chase up tomorrow 19:21:48 so, this depends on negotiations 19:22:15 I did talk to nkukard and we are moving closer to deciding on a finacial vehicle 19:22:19 instead of dealing with long documents, have you considered a term sheet to capture the main issues? 19:22:32 we are thinking we'd most probablyh register a company 19:22:42 indiebio: can you expand on the reasoning for that? 19:22:43 we just need their contract. and then we can find issues. 19:22:54 nkukard would be better suited to expand... 19:23:10 something about liability I think 19:23:43 I'm really sorry (and vicuously annoyed) that things are going slowly at the moment 19:23:44 I thought the CMC was our finanncial vehicle 19:24:09 uhm, nkukard thinks not. 19:24:20 where are you nkukard? badger, come in, roger 19:24:25 I am here, reading what you saying 19:24:32 i am also not convinced by that. They might provide treasury and payment services, but they hardly will run our conference legally 19:25:09 I want to to see the financial part of the agreement, then I guess a decision must be made how we are to proceed 19:25:12 form a company or not ... etc 19:25:17 yeah, think that was it. but registering a company is apparently neither difficult nor time-consuming, so should be easy-ish (famous last words) 19:25:29 yea, it is really easy 19:25:32 so nkukard, did you see the template Belinda sent a long time ago? 19:25:55 so in terms of meeting, please minute: there's no progress :( 19:26:28 I was looking for it a bit earlier, is it in git? 19:26:45 yes, can we move on to budget and I'll find it so long 19:26:56 if you form a company, keep in mind that you need to tear it down too post-dc16, which can take many months and effort 19:27:20 I've done it before, it's not so hard in SA 19:27:21 the fast companies are for-profit though (just FTR. NFPs takes ages in ZA) 19:27:22 indiebio: before we move along 19:27:30 you said in the agenda that "The DPL said this is not a problem to get from SPI - Stefano please update the team?" 19:27:39 that's not all the DPL said 19:27:53 he also thought the huge upfront deposit was stupid, and asked us to push back on that 19:27:57 nkukard: git/dc16/UCT_Contracting/CMC_Standard_Conference_Management_Agreement_14_feb_2014.doc 19:28:11 I don't know if the current exchange rate means it's actually a good idea, though :P 19:28:11 * nkukard does a git pull on this pc 19:28:30 nkukard: the other reason we were avoiding a company was tax 19:28:33 tumbleweed: yes. so once CMC contract is signed we can move on accommodation contract where this comes into play 19:28:42 indiebio: ok 19:29:00 tumbleweed, you are not going to escape tax 19:29:03 I assume whether we're doing a company or not, we're doing CMC, because it saves us money, and buys us influence 19:29:10 nkukard: CMC seemed to think we would 19:29:13 I spent like 4 hours explaining a few months back 19:29:21 yes tumbleweed 19:29:22 that is why I said I want to see the contract 19:29:23 nkukard: let's discuss this outside the meeting 19:29:29 nkukard: we don't have the final contract, yet 19:29:32 #topic Budgeting 19:29:33 exactly :) 19:30:37 nkukard: so, we're budgeting based on 350. Is that sensible? or do we need a parallel budget for 250 (which we thought was more realistic( 19:30:47 350 is on the upper end of what I'd expect 19:30:53 exactly 19:30:55 tumbleweed: please minute that I contact Belinda from CMC again? 19:30:58 thats the amount we budgeting for as max 19:31:06 anything more and we need to check figures 19:31:13 #action indiebio to contact Belinda from CMC again 19:31:31 I think let's budget for 350 19:31:32 indiebio, you can #action and #info as well 19:31:37 nkukard: your travel sponsorship budget seems amazingly low 19:31:40 oh. thanks marga :) 19:31:58 nkukard: I'd also like to know where do we submit budget amounts? 19:32:09 (like 20 people from the northern hemisphere) 19:32:17 indiebio, ML would be fine I guess 19:32:20 nkukard: how do we go about sourcing the numbers? do you need help on that 19:32:59 tumbleweed, I believe the figures I have for sponsorship were based from a discussion with marga and some others one evening who were discussing sponsorship, it can easily be changed, but thats the figures I got 19:33:07 tumbleweed, nkukard: I'd triple or quadruple that travel budget. 19:33:28 I have no idea what it says, but I'd push for 50k USD normal travel + 10k USD outreach 19:33:31 yeah, we really need to be budgeting a lot there, or we won't have a conference 19:33:46 then the team must submit the figures to me please 19:33:53 I put in what they give me :) 19:34:05 so can I suggest something like a budget sprint or meeting where we can focus on this? 19:34:33 * madduck has dejavu feelings 19:34:34 or we can just let it evolve over time, a bit 19:34:49 what are the timeline/deadlines for budget? 19:34:52 nkukard: are you going to ping the team leaders, to get budgets? 19:35:00 tumbleweed, that is why we have a poker :) 19:35:09 madduck: I'm relieved that you say so 19:35:15 that didn't work too well last year 19:35:25 (asking leaders for budget) 19:35:38 indiebio: shame walked into that one ;) 19:35:51 I am concerned that our team is not big enough for people to have ideas about all the facets that need budget 19:36:04 I suggested to nkukard that we use DC15 as a guide to start... 19:36:10 past budgets are useful for that,yes 19:36:15 madduck: (the quadrupling of travel sponsorship estimate, not the dejavu statement :) ) 19:36:16 but we need a hack session to just think and talk through stuff 19:36:21 highvoltage: yeah 19:36:21 take the DC15 budget and you have 90% of the line items, not? 19:36:26 actually the global team would be great input here!! 19:36:29 indiebio, I did and I discussed this with a number of teams 19:36:34 the numbers I have is a result from that 19:36:39 and no one has said anything after I mailed the ML 19:36:41 marga: right, but it's the way to go. We need to coach the "leaders" or whatever we have to provide those numbers. 19:36:50 marga: this year the teams will hopefully have theexperience from dc15 19:36:52 DLange: that's what he's doing. 19:36:59 I am adjusting with marga's figure snow 19:37:17 marga, your 10k usd is in there already :) 19:37:34 nkukard: for me, I didn't know what was going on... so I would like to be walked through it in a sprint thingie 19:37:38 make it 20, nkukard 19:38:06 we had 11k € for dc15 19:38:19 and had a hard time to use it 19:38:22 but you were in Debian Central. We're going to have to up that 19:38:38 DLange: because we started 6 weeks before the conference. 19:38:48 the 10k were for outreach, which means not-involved-with-Debian people. 19:38:51 ok, I think we need to start moving on 19:38:52 madduck, the 10k was after discussion with the sponsors/diversity team .... I'd prefer their team lead give me figures? 19:38:58 anyways, do we want to caht about this at this meeting, or take it offline? This *is* going to be the next thorny issue 19:38:59 nkukard: can I minute that you'll talk to team leads? 19:39:04 nkukard: sure. Didn't know. 19:39:05 We need to look at trval budget from Nicaragua 19:39:15 yes, that's a good comparison 19:39:54 tumbleweed, must I be responsible for poking people to give me their budgets? 19:40:06 somebody must 19:40:14 it's 21:40 peeps, we need to move on. can we please have a hour loing hack at budget in the near future, nkukard, when it suits you? 19:40:32 I don't mind poking, tumbleweed, nkukard, but I want to know what's going on first. 19:40:34 remember, my time is limited, I do not have any free time, I am traveling until 1st Oct now ... so additional tasks I must do out of the scope of doing the budget I need to plan 19:40:48 ok 19:40:51 This is not as urgent as other things 19:41:02 I can submit a mail weekly to the ML with outstanding items? 19:41:04 would that help? 19:41:08 maybe slightly off-topic, but it there might be some social ways to encourage people to only request travel sponsorship for the amount they need (rather than mostly always applying for full amount), maybe a a slider or similar on the registration form to encourage that (if needed (and yes, I know, that's another discussion)) 19:41:11 nkukard: yes, that's a great start 19:41:16 awesome 19:41:19 that is easy to do :) 19:41:24 #action nkukard to ask team leads for budget proposals 19:41:38 #topic Social/Teambuilding 19:41:40 #info NK will send mail to ML with outstanding items :) 19:41:49 highvoltage: we tried and some people think we failed to do that last year. But yes, it's the right direction. 19:41:50 Ah, an easy item :) 19:42:17 so yes, I intend to be in ZA for the first week or two of Oct, thanks to pyconza 19:42:19 next braai: tumbleweed, when are you here again? 19:42:26 haven't booked flights, yet 19:42:32 so what saturday works for a braai? 19:42:46 10 Oct 19:43:17 so, tumbleweed, dats's set, book the flights. nkukard, tell your better half. 19:43:20 we can shift braai to then, sounds good 19:43:24 and... next item. 19:43:30 * superfly diarises 19:43:32 #info Braai on 10 Oct 19:43:33 indiebio, can you email Natalie? 19:43:40 #topic Sponsors 19:43:51 ok. jeez, nkukard, what;s the going salary for a PA these days? 19:44:21 indiebio: what are you looking for here? people to talk to the sponsors team? 19:44:24 no, sorry, next sub-item: is everyone OK with me using some of the team building budget to organise a recruitment event with Robyn Farah of Arduino-CT? 19:44:54 indiebio, she is the planner for braai's not me :), I just finance them :D 19:45:25 tumbleweed: I want people to take note, and look for potential sponsors, NOT contact them, and let us know please 19:45:28 that's all for now. 19:46:01