19:01:46 #startmeeting 19:01:46 Let the Jenkins meeting commence! 19:01:51 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda 19:02:02 #topic recap of actions 19:02:39 #info https://issues.jenkins-ci.org/browse/MEETING 19:03:00 MEETING-8 is complete 19:03:13 except rtyler hasn't sent in the reimbursement form 19:03:21 please do 19:03:55 orrc: I'm not sure if I heared back from FFI 19:04:00 (wrt MEETING-9) 19:04:16 I haven't heard anything 19:04:47 trying to locate the e-mail 19:05:27 I guess I'll write to Martin Schulze 19:05:42 is he a member of ffis? 19:05:52 or someone whose project is affilated with ffis? 19:06:16 action: kohsuke to ping ffis again 19:06:21 #action kohsuke to ping ffis again 19:06:32 He replied to my first ffis email, so I guess he's involved 19:06:53 other AIs still incomplete 19:07:10 #topic Balancing personal information of JUC attendees vs cost 19:07:42 so I asked Alyssa to produce a summary of the income/expense of JUCs 19:07:44 #info https://docs.google.com/spreadsheet/ccc?key=0ApE2WVyiXL0hdGZSRTZVQmdTN2VnVWdJMWZCNEJqa1E 19:08:24 The context here is that we've been passing attendee contact information to sponsors, and we haven't been explicit about it 19:09:21 So we want to fix this 19:09:26 On that note, we want to apologize that you felt like you were being harassed by JUC sponsors because we shared lead information. You should know that both when sponsors signed up originally, and when we sent attendee details to them, sponsors were urged to “please treat the list gently, maybe send only one follow-up email with useful assets and an Opt In capability, and not to merge people into their main databases.” 19:10:05 OTOH, people talking to sponsors said without those "lead" information, it'd be very difficult to get sponsors at all 19:10:37 Gold sponsors paid $5000 for the privilege of getting contact information – which is $2000 more than Silver sponsors paid, and the contact info is the only difference. I signed these guys up myself, and it was the names they wanted. 19:11:19 The "eventbrite" line is the income from ticket sales 19:11:37 if you compare that with the total expense, it's pretty clear that they don't match up 19:12:10 I believe "F&B" is food&beverages and that actually includes room fee 19:12:44 in case you're not on the Gdoc: $28k of EventBrite income vs $45k of expenses 19:12:52 Alyssa told me that the way it works with these venues is that hotels bundle them into one to make you pay more 19:13:48 So how can we make this better next year? 19:14:06 I think we continue to try to find a venue that's free/cheap like we did in JUC Tokyo, but we haven't found one in San Francisco. 19:14:08 We want to make sure not to upset people in future. Going forward, we’d like the community to agree on what sponsors receive and on how to share (or not share) information. We are also looking into options where people could Opt Out of contact sharing upon registration and also looking into Badge Scanning options for next year (maybe individual QR codes as suggested) . 19:14:36 rtyler: any thoughts? 19:15:08 hare_brain: ? 19:15:21 For me, I understand that I'm probably going to receive solicitations when I register for something. What annoyed me was a particular vendor emailed me several times, *and* called me on my personal phone. Worse, the way they presented themselves was that we had had a conversation at JUC which I absolutely did not. 19:15:50 Yeah, that was my only issue. 19:15:55 Am I reading the spreadsheet correctly, even without Gold Sponsors, SF JUC would have been in the black? 19:15:58 Spam is one thing - cold-calling is another. 19:16:10 So one thing I would suggest is a clearer disclosure about what information would be disclosed. 19:16:18 So next year we definitely want to have an "Opt Out" checkbox when you register (if EventBrite will let us) - with the plea to please understand that sponsors really help out and the contact info makes it worth their while 19:16:29 also we were thinking next year we don't share phone at all? 19:16:36 I gave my personal number under the assumption that it would have been used to contact me about problems with the event. I did not expect that it would be given to a vendor. 19:16:54 quidryan: Yes, I think JUC SF 2012 was in black 19:16:58 our apologies for not being clear aobugt that. 19:17:23 * rtyler shows up 19:17:32 quidryan: but there were 6 gold sponsors so I don't think it was in black if we didn't have any of them 19:17:37 At the end of the day, it's an annoyance, and not a travesty. I wouldn't NOT come to JUC because of this. :) 19:18:08 rtyler: https://docs.google.com/spreadsheet/ccc?key=0ApE2WVyiXL0hdGZSRTZVQmdTN2VnVWdJMWZCNEJqa1E#gid=0 19:18:35 kohsuke, I see line 11, line 13 and maybe line 12 as Gold Sponsors. I don't see 6. 19:18:48 bad url 19:19:07 rtyler: how about https://docs.google.com/spreadsheet/ccc?key=0ApE2WVyiXL0hdGZSRTZVQmdTN2VnVWdJMWZCNEJqa1E 19:19:14 oh the same thing 19:19:19 We did have 6 Gold sponsors. Some we had to negotiate more heavily with than others. 19:19:33 #info http://www.cloudbees.com/jenkins-user-conference-2012-san-francisco.cb for sponsor list 19:19:35 HP, for example, would not have sponsored if we hadn't given them Gold at half price. 19:20:06 * rtyler boggles at NY and Paris 19:20:36 Starting build #2077 for job jenkins_main_trunk (previous build: SUCCESS) 19:21:32 I guess I'm hoping that opt-out + being more explicit about this would be acceptable for future events of this sort 19:21:32 hare_brain: if every company called me like sonatype did, I wouldn't attend 19:22:13 and I guess I'll personally ask LisaWells to tell this episode to future sponsors 19:22:16 rtyler Fair enough. I'll rephrase as "What happened after JUC SF 2012 wouldn't stop me from attending." 19:22:55 I don't think it's in anyone's interest to be perceived like sonatype 19:23:15 Heh. So much for my attempt to keep things anonymous. 19:24:03 Let me move on to the next topic as it's kind of related 19:24:15 #topic Forming the Events subgroup in the community for the purpose of coordinating and running event 19:24:50 there's a couple of related efforts here 19:24:53 so... how do we do this better next year? 19:25:48 LisaWells_: my sense is that opt-out + transparent about what happens to your contact info received reasonable acceptance 19:26:04 what does everyone else think about that? 19:26:13 Not requiring/not sharing phone numbers would be welcome. 19:26:13 * rtyler nods 19:26:56 i don't think Phone was a Required field during registration, fwiw. but next year we won't share that even if provided 19:27:14 Yes, I like that 19:27:20 * kohsuke is phone phobia 19:27:48 LisaWells_: Can I resume talking about the next topic? 19:28:13 I take it as yes 19:28:14 Please :) 19:28:34 kinow is trying to bootstrap the brazilian user community 19:28:53 and independently I'm working with Samsung folks to get one going in Korea as well 19:29:32 I'm also trying to bring more JUC conversations in public, which requires a channel for communication for folks like LisaWells_ and alyssa 19:29:57 so I mentioned this to rtyler a bit but I finally got events@lists.jenkins-ci.org created 19:30:11 http://lists.jenkins-ci.org/mailman/listinfo/jenkins-events 19:30:27 in the past we had event specific list like http://lists.jenkins-ci.org/mailman/listinfo 19:31:03 we are hoping to help the community drive a lot of events, so having a streamlined comm link will be most excellent 19:31:16 but for smaller events and for cross-pollination between different local community, I wanted the project meeting to bless the new list for event related stuff 19:31:29 I think it's a good idea 19:32:13 There are a few more things I thought this list would be a good fir for in https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-November14thMeeting 19:32:49 like doing the CIA program bookkeeping 19:32:51 I think getting the right people on the list that can help new organizers will be useful too 19:33:00 offering advice, etc 19:33:02 exactly 19:33:37 rtyler: who should we invite, aside from you? 19:33:38 Alyssa & I are hoping we can help share knowledge, give ideas, suggest structure that has worked (and not worked :) ), etc 19:33:51 kinow, ndeloof 19:34:03 and some folks from Tokyo 19:34:03 the israeli guys, copenhagen guys 19:34:31 israeli guys = I'll check with JFrog, copenhagen guys = rsandell and Knud 19:35:15 action: kohsuke to write to kinow, ndeloof, JFrog, ikikko, cactusman et al, rsandll and Knud Poulsen to join events (and encourage others they think of to do so the same) 19:35:36 should I do a post about it on jenkins-ci.org? 19:35:52 I think bruno kinoshita would like to join as well 19:35:53 +1 19:36:00 alyssa_: that's kinow 19:36:12 with the encouragement for people to sign up for the list AND start thinking about events for next year 19:36:12 kohsuke: yes 19:36:14 I think so 19:36:20 yes to what LisaWells_ said too 19:36:27 action: kohsuke to announce it on jenkins-ci.org post 19:36:41 I'm going to be swamped with fosdem, but we should start trying to get more things organically organized in 2013 19:36:51 Yes 19:37:26 we've been talking about what we can do to encourage meetups, Jenkins events, etc. any thoughts? 19:37:42 rtyler: wrt FOSDEM, one of the Tokyo people might after all be able to come with your grant 19:37:47 So the aim is to help people organise any sort of Jenkins-related event or talk? 19:37:53 kohsuke: let's chat more about that after :) 19:37:54 yes 19:38:00 orrc: more the event stuff I think 19:38:28 talks too - CIA is another thing that could use some TLC 19:38:47 and could maybe be addressed by Events subgroup? 19:38:47 although a part of the original Jenkins CIA idea was to come up with some reusable slides, so if anyone wants to take it on, I think it'd fit, too 19:40:00 #agreed events@lists.jenkins-ci.org is blessed 19:40:24 shall we move on? 19:40:37 #topic Status of moving Jenkins to java 6 as minimal runtime 19:40:48 I thought we already did this? or was it just for development 19:41:09 No, we haven't done this 19:41:28 ah 19:41:33 * rtyler backs away 19:41:50 My suggestion is to start producing releases with Java6 but without adding tons of Java6 dependencies right away 19:42:10 That gives a chance to anyone not tuning into the last round of e-mail conversations 19:42:16 I'd love to see this happen - but what was the issue olamy was mentioning? 19:42:26 jorgenpt: ^ 19:42:37 What am I looking at? 19:42:45 jorgenpt: /topic 19:42:52 requiring Java6 to run Jenkins master, slave, and Maven builds 19:42:55 wanted to make sure you were in on this to some extent 19:42:58 Okay 19:43:11 Sounds good to me - I'm all for it. :-) 19:43:24 imod: the only issue I'm aware of is that Maven builds now need to run with Java6 19:43:43 ok, so lets do it 19:44:10 yeah, my proposal is to start producing releases with Java6 class files but without adding new dependencies 19:44:38 what kind of dependencies are you thinking about? 19:44:39 if by 1.500 or so we don't hear any major backlash, all Java6 dependencies are good to go 19:44:53 imod: calls to java.util.*, etc 19:45:03 ok 19:45:26 IOW, for a while I think we should be able to back off from Java6 requirement easily 19:46:14 action: kohsuke to send an e-mail to the dev list about the above plan and start acting accordingly 19:46:23 #action kohsuke to send an e-mail to the dev list about the above plan and start acting accordingly 19:46:43 users list as well 19:46:58 #action CC to the users list as well 19:47:00 Yes, one more heads up 19:47:11 I think that's it for today 19:47:15 #topic next meeting 19:47:47 just before xmas? 19:47:48 11/28 19:47:55 wait, what? 19:47:58 Would we call that the last one for the year? 19:48:00 will that be the last of the year? 19:48:00 11/28 19:48:04 heh 19:48:27 I wouldn't mind making 2012.12.05 the last meeting of the year 19:48:38 next week is a total wash as far as I'm concerned :P 19:48:38 is 12/12 (the day after that) some special day? 19:49:01 12/5 would be out of bi-weekly cycle though 19:49:06 it would 19:49:20 the question I meant to ask is more, will we have sufficient business to discuss 19:49:44 I probably won't be able to make 12/5 19:49:47 I'm flying somewhere 19:49:54 you always are 19:50:01 we could just skip to 12/12 then IMO 19:50:19 Well aren't we getting ahead of ourselves? 19:50:26 I don't think we'll have much to talk about if we meet 11/28 19:50:42 Oh, so you're proposing skipping one 19:50:47 yes 19:51:11 Skip straight to 12/12 then? 19:51:13 I'm fine either way 19:51:25 anyone want to talk about events sooner than that? 19:51:40 the mailing list will be good for that :) 19:52:15 #agreed next meeting is in 4 weeks, 12/12 19:52:20 +1 19:52:49 Anything else? 19:53:16 #endmeeting