19:00:20 #startmeeting 19:00:20 Let the Jenkins meeting commence! 19:00:21 all my jenkins time was spent in the hour writing stupid blog posts :( 19:00:31 rtyler: ha ha ha 19:00:35 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda 19:00:43 #chair abayer hare_brain rtyler 19:00:43 Current chairs: abayer hare_brain rtyler 19:00:55 #topic recap of actions 19:01:14 #info http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-02-08-19.03.log.html 19:01:16 eedri: recommendation is to book Marriott hotel ..same venue as the conference 19:01:18 heh, beat me to it 19:01:37 I think KK already got started on the artifactory thing 19:01:48 he's definitely already submitted the puppet manifests to set up the cname 19:02:04 ndeloof: "ndeloof jieryn to confirm cloudbees foss requirements for sponsor logo" 19:02:24 in the mean time, jieryn what's the good word from cafepress? 19:02:27 can I pls get some votes on this https://skitch.com/alytong/8dwka/jenkinsinparis-crv-1.pdf-1-page 19:02:46 alyssa_: not right now 19:02:48 test message 19:02:48 project meeting 19:02:52 alyssa_, we've started our project meeting. Can you hold on that until we're done? 19:03:00 * rtyler pokes jieryn harder 19:03:14 sorry..am a newbie 19:03:21 hoy people, wouldn't it be useful to have a jenkins plugin to add openvas testing for applications ? (just a thought) 19:03:31 @rtyler: CloudBees marketing is here for the JUC agenda item. Will you let us know when appropriate to speak up? Thanks! We are all newbies at this. :) 19:03:33 DarkRift: we're in a project meeting, hold that thought :) 19:03:40 heidig: can do 19:03:44 Thx 19:03:48 hare_brain: can you chair abayer and myself please? 19:03:54 rtyler: "ndeloof to confirm cloudbees foss requirements for sponsor logo" 19:04:00 rtyler I did 19:04:02 rtyler: we're chaired. 19:04:13 ah, must have missed it 19:04:31 ndeloof: that was an action item from our last project meeting, I honestly don't remember the context though 19:04:41 cloudbees ok for sponsoring jenkins-ci with a "standard" logo on sponsors widget 19:04:55 -> jenkins.ci.cloudbees.com 19:05:03 used for building some of the ci jobs 19:05:20 plan was to move selenium tests there i thing 19:05:31 ndeloof: Yeah, that was the thought. 19:05:46 account is up, 19:05:58 ndeloof: could I ask you to file a ticket for me to add the logo, and include the logo on the ticket? 19:06:02 foss "requirements" have been relaxed for jenkins-ci 19:06:06 heh 19:06:34 so that you don't have to put the "powered by cloudbees" logo on home 19:06:42 logo on sponsor list is ok 19:06:48 will create a jira for that 19:06:54 OK, so to recap: Take advantage of CloudBees infrastructure for some J-on-J jobs, and in return, we put CloudBees logo in the sponsored widget. 19:07:07 +1 19:07:11 #action ndeloof to file a ticket for rtyler to get a standard CB logo on the "sponsors" block on www.jenkins-ci.org 19:07:39 #agreed Take advantage of CloudBees infrastructure for some J-on-J jobs, and in return, we put CloudBees logo in the sponsored widget 19:07:48 #action ndeloof will need to work with abayer and jieryn to figure out what jobs should go on Dev@Cloud and what stays on J-on-J 19:07:55 +1 again 19:08:08 something we can figure out later, shall we move to the first agenda item? 19:08:13 Yup. 19:08:23 #topic Proposal: Move away from Drupal to a Git repository powered by Jekyll for the community site 19:08:33 This one's pretty much all you, rtyler. =) 19:08:35 this is my schtick, let me enumerate the pross and cons 19:09:09 Drupal is great, but I think we could greatly benefit by a more simple statically generated site that we can manage with our typical GitHub infrastructure 19:09:17 this will allow more authors and more content to be more easily published 19:09:29 Easy is always good. 19:09:32 I've done a couple Drupal -> Jekyll conversions and it's pretty straight-forward 19:09:47 I would honestly rather go this route, than figuring out a good ACL scheme for Drupal with our LDAP 19:10:11 I can spend the time to get a working dump "online" without affecting normal operations 19:10:13 Works for me - but admittedly, I defer to you on all thing site-ish. 19:10:23 right, I want to change that up a little more ;) 19:10:30 This is not for the wiki, but for jenkins-ci.org itself? 19:10:35 www, yes 19:10:53 this would also make things like ndeloof's logo action item a simple pull request by somebody that is not me 19:10:56 :) 19:10:57 How would the changelogs and releases get updated? 19:11:21 that's some simple PHP garbage on the host anyways 19:11:30 we can still run that, it'd have to likely stay out of the tree I htink 19:12:04 Or we could set up a job to update static pages with the changelog/releases stuff, I'd imagine. 19:12:07 #info need to be mindful of how changelogs are generated and sourced in the current site 19:12:37 sounds like a good plan 19:12:45 nobody's screamed in terror, so I think i'll start tinkering with it and see what I can come up with 19:12:56 Definitely worth pursuing at the very least. 19:12:57 i want everybody that was at FOSDEM to be capable of also writing news updates for the project ;) 19:13:13 #action rtyler to generate a prototype jekyll www site 19:13:20 hmm, not sure if want that :) 19:13:20 hey, I get this odd error that htmlpublisher fails to copy workspace/build/api to other folder (https://gist.github.com/1886697), any ideas what could be the possible reasons to this 19:13:23 we'll skip over the board thing for now? 19:13:26 +1 19:13:31 iAsterisk: give us a few minutes, we're in a project meeting right now 19:13:33 rtyler: I'd actually like to start talking about that. 19:13:40 oh alrighty 19:13:47 #topic It's been a year, should we elect a new board, how/when/etc? 19:14:02 let's talk about it! 19:14:03 #info So, we've had the same board for a year. Which has been ok, but we should really have elections. 19:14:19 #info Question is - how do we elect new board members? How do we decide who can vote? 19:15:03 abayer: same thing as voting about rename hudson-> jenkins? 19:15:07 Even more fundamental to that, does the structure of the board need to be changed? 19:15:09 I'm the one who proposed the eligibility criteria for the rename vote last year, but that was ad hoc - just looking at the members list of the mailing lists as of a point in time. 19:15:22 But I'm not sure whether that's really viable at this point. 19:15:29 it's a lot more people 19:15:31 :) 19:15:47 we don't have the concept of a "member" in the same way some other projects have 19:15:52 hare_brain: That too. I'd like to propose bumping it up to 5 people, so that we can get more people centrally involved. 19:16:08 I think the current board should vote 19:16:19 #info One model to follow might be the openSUSE structure, e.g. http://en.opensuse.org/openSUSE:Board_election 19:16:23 #idea Increase size of board to 5 people, instead of current 3. 19:16:26 imod: But then we could just vote for ourselves forever! =) 19:16:40 true, but we need to start somewhere 19:17:05 rtyler: Ah, an open period for "registering" to vote...nice. 19:17:31 #idea Before elections, have an open period to allow people to register to vote. 19:17:52 I think registration can still be sign up for the dev or user mailing list? 19:17:57 I mean, lets face it KK and styler are set for sure - everything else is not gone work - I think 19:18:17 #info managing the rename vote was a pain - making sure voters were on the mailing lists by the set time, etc. 19:18:23 imod: rtyler refuses to be on the board, actually. =) 19:18:42 is there some assumption about who *shouldn't* be allowed to vote? 19:18:46 that was not what i meant! 19:19:20 abyer: I think you should be in too! 19:20:11 hare_brain: I'd really prefer a smaller, easier to verify electorate. That OpenSUSE model seemed pretty reasonable to me - though I'd probably want a lower bar for "registering" than they require for OpenSUSE membership, just 'cos I think pure users need to be represented as well. 19:20:21 i.e., not just "contributors". 19:20:33 OK. 19:21:24 abayer: I refused last year 19:21:27 might not this year 19:21:29 I'm hungry for power 19:21:35 Ah, well, then we're dooooomed. 19:21:41 Then I think that the current board should hash out a proposal for how elections would work, then review/ratify at a future project meeting. 19:21:46 Then we can set a date for elections. 19:21:53 that sounds good to me 19:22:35 #action abayer kohsuke hare_brain to write up a proposal for board elections, then bring it to future project meeting for review/ratification. 19:22:47 +1 19:23:15 moving on! 19:23:19 #topic JUC promotion ideas 19:23:20 #idea Proposal should include nomination process, how to handle board member resignations, tenure 19:23:23 ah shit 19:23:36 It's fine. I'm done. 19:23:45 heidig: wake up! 19:23:58 Thanks! KK invited myself, Alyssa and Lisa to the meeting to talk (or type!) about JUC. We are really pumped to have 4 JUC conferences to organize this year! But we need your help in a big way. To ensure the conferences are successful, we need the Community to be very involved and to really make them *Jenkins* conferences, rather than a conference CloudBees is organizing. That is what we’d like to discuss today. 19:23:59 this was an unattributed agenda item, I think it was KK 19:24:19 Yes 19:24:53 what did we do for JUC SF, besides shouting about it a lot on Twitter? 19:25:03 not that I don't enjoy that part 19:25:19 Drumming up presenters was a large effort. 19:25:40 We (CloudBees and KK) blogged, Tweeted, Facebooked, issued press releases. We had the momentum of Java One with us, too. 19:25:52 fwiw, JUC Paris is now looking to have a pretty good lineup of speakers, but I know JUC NYC could still use more. 19:25:56 Some thoughts: We’d like to have several folks from the community step up and be willing to really ramp up the noise in the Community about all 4 JUC conferences. Get people to register to attend (Early Bird pricing in effect right now, too), get organizations to sponsor and have people apply to speak. This could be a mixture of blogging, posting in Jenkins forums, emailing the Jenkins list, Tweeting, Facebooking – and getting o 19:26:10 heidig: are you familiar with our fledgling CIA program? that would be helpful if we had built it up more by now :/ 19:26:32 I have heard some about the CIA program - but not in any detail. I am aware of it - Lisa and Alyssa are, too. 19:26:49 https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CIA+Program 19:27:00 btw LOVE that logo! 19:27:05 heh 19:27:27 I think one key aspect would be to reach out to folks incorporated with local JUGs near the JUC 19:27:38 and offer them a JUG-specific pricing to get a group going 19:27:49 is the CIA program contain larger audience? 19:27:58 Is this something the Community is doing, currently? Or plans to do for the JUCs? 19:28:02 alyssa_: it's really quite young, we're sitll working on it 19:28:14 CIA program will be great for the Fall JUCs (Antwerp & San Francisco) 19:28:18 agreed 19:28:33 we still have to sow the seeds of the program 19:28:38 CIA is basically Jenkins Evangelists, right? 19:28:47 CI Ambassadors my dear lisa! 19:29:01 So what can we do right now, within the Community, to really make some noise about JUC Paris and NY? 19:29:04 yes, just using another term :) 19:29:23 jieryn: are there JUGs in NYC? 19:29:23 Nicolas De Loof has reach out to the local French JUG, etc and we did offer free tix 19:29:31 ah, cool 19:29:52 I have also reached out to some local NYC JUC thanks to Jesse's help 19:30:01 also cool 19:30:06 that's all the ideas I've really had around it 19:30:26 having people more local to the JUC will be mots beneficial from the grassroots perspective 19:30:32 would it help if we wrote some sample tweets and asked the community to spread them / RT? 19:30:48 but it's still not enough to generate registrations and speaker and sponsors 19:31:14 lisawells: have you seen some of the "I'm attending GUADEC" or "I'm attending FOSDEM" logos and badges that those conferences release for people to post on blogs? 19:31:47 no, but I can imagine what they look like 19:31:55 Agreed with Alyssa. What else might make sense for the Community to do? Are there Jenkins users who are particularly well-connected and could really ramp up visibiilty within the Community? 19:32:01 twitter is a little to ephemeral to rely on heavily IMO 19:32:04 too* 19:32:29 heidig: there probably are, but it depends on whether or not that have time or even want to ;) 19:32:34 I have an internal dev community with a couple of hundred devs... 19:32:39 @ryler: for the logos - how many folks in the community blog heavily? 19:33:00 Yeah, I know. Bandwidth is an issue for everyone. How to get more of it... 19:33:03 lisawells: I'm less concerned about jenkins community people, and more concerned with people on the edges 19:33:21 users without community ties to Jenkins (yet) 19:33:46 imod: where are your dev community located? 19:33:56 lisawells: perhaps you guys could create a "CIA package" that we could help publicize, which would contain a couple of hard hitting points for attending JUC 19:34:01 @rtyler: good point! and now we're back to how we reach those folks...? 19:34:06 europe, US, GB 19:34:21 lisawells: combined with some "I'm attending JUC Paris!" badges, and some other short materials (less htan an A4 page) 19:34:44 I would imagine imod could use such a CIA Airdrop 19:34:52 * rtyler is trying out different words for it 19:34:52 CIA package could ge good - would also help launch the program 19:35:09 basically to give guys like imod something really easy to pass around internally 19:35:38 hare_brain: can you take tihs the rest of the way, I need to bounce 19:35:44 I'm also out of ideas 19:35:50 for this anyways ;) 19:35:58 @rtyler: one issue is we (heidig & alyssa_ & me) are already fully loaded doing publicity, sponsorship, planning,etc - do you think the community could help with this? 19:36:06 actually I'm just submitting a talk to Jazoon in switzerland, so I could do some promotion there to 19:36:36 #action rtyler to ponder harder about a CIA Package for JUC, contact lisawells and heidig with outlines/ideas/etc 19:36:45 abayer: how about you, can you close tihs off? 19:36:46 thanks!! 19:36:46 imod: that would help. 19:37:03 imod: when is Jazoon? 19:37:34 rtyler: endo of june 19:38:00 Sorry, distracted. =) 19:38:02 * mika is in the organization team of one of the largest IT events in austria (linuxdays graz, >500 participants), could also do promotion 19:38:10 imod: what's the best way to invovle your community? 19:38:16 Work puling me away at the moment. 19:38:18 s/community/company 19:38:20 xD 19:38:54 lisawells: I'm already running an internal chat channel for jenkins and there are many more like one for java, maven... 19:39:01 rtyler, go ahead and bounce if you need to. Sorry, was looking away. 19:39:07 hare_brain: alright, you're in charge 19:39:41 We want the JUCs to be wildly successful...but we need the Community to register, speak, sponsor, etc. Open to ideas as to how to engage. 19:39:47 +imod: so we just hop on IRC and yak? 19:40:42 What rtyler was concerned about, and I agree with him, is that "the Community" is not equally engaged. 19:40:50 lisawells: thats at least what I can do - but we also have some internal community meetings every other week, so I can place it there too 19:40:53 We have people who hang out here on IRC a lot. 19:41:01 There are the people who interact on the mailing lists 19:41:07 Those are the people that are easy to reach. 19:41:12 +imod: that would be awesome - merci beaucoup! 19:41:25 But the bulk of the community, the "dark matter", if you will, is very disconnected. 19:41:43 @imod: those are the things that really help and make a difference!! 19:41:45 Maybe very is too strong. But more disconnected from these online hangouts. 19:42:04 @hare_brain: you made me laugh. Have you found a good way to reach them? 19:42:18 But if those who are connected can really ramp it up, it makes a huge difference. 19:42:31 I don't have a good way to reach them. 19:42:43 I'm always surprised by how many people are following/etc me, kohsuke, @jenkinsci, etc on Twitter. Pretty much every time I tweet about the JUCs, someone's responding, retweeting, etc. 19:43:39 @bayer - have seen your Tweets. They are great! 19:43:42 I also think that JUC Paris is having a bit of a hard time 'cos of being alongside a new, predominantly French conference, while JUC NYC is in an even tougher spot, given that it's not alongside any conference. 19:43:51 The metaquestion is how are you guys defining community? Yahoo is a company of thousands and we use Jenkins, but I wouldnt' categorize all of them as being part of the community. 19:44:12 Community = Jenkins users. Period. Wherever they are. 19:44:45 I think you want *engaged* Jenkins users. 19:45:23 anyone who cares about Jenkins and wants to engage 19:45:28 We want to reach anyone using Jenkins. To your point, the engaged users are the ones who can really help raise the noise level. 19:46:02 hare_brain: you'r right, some just like to consume - but some just need to be asked 19:48:14 OK, so +imod is going to post to IRC... and hopefully some of you are going to tweet, facebook, linkedin, forum-post, mention in IRC, etc....? I agree with @hare_brain, some folks just need to be asked 19:48:49 Right. We just don't know who they all are - even the engaged ones - to ask them to step up the noise. That's where we need help from the Community - to do the asking. 19:49:36 OK, is that all on this topic? 19:49:47 Anyway - thanks! We appreciate your time today and your thoughts/input. :) 19:50:08 @hare_brain: I think that's it - thanks in advance to all for helping get the word out 19:50:19 #topic Next meeting 19:50:42 If we continue with our recurring schedule, the next meeting will be extra special. 19:50:45 2/29! 19:50:59 :) 19:51:00 Oh, no I'm wrong 19:51:04 Off by a week 19:51:07 It would be 3/7 19:51:13 Darn 19:51:36 shame! 2/29 is almost as cool as 11.11.11 19:51:36 hehehh 19:51:44 Next meeting at 3/7 @ 11 am PST 19:51:46 Objections? 19:51:49 +1 19:52:23 #agreed Next meeting on March 7, 2012 11:00 PST (19:00 UTC) 19:53:10 OK, then that's a wrap. 19:53:19 #endmeeting