19:00:02 #startmeeting 19:00:03 Let the Jenkins meeting commence! 19:00:18 #topic Recap of last meeting's action items 19:00:19 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Jan11thMeeting 19:00:23 #chairs abayer kohsuke 19:00:31 #chair abayer kohsuke 19:00:31 Current chairs: abayer kohsuke rtyler 19:00:47 no dean, bummer 19:00:55 I'll go ahead and run down the list of my AIs 19:01:00 he sent us a regret. Food poisoning 19:01:05 oh yikes 19:01:17 #info aheritier now in the users-core module 19:01:41 #info backups at Contegix are actually blocked on me setting up a role account on the machine 19:02:06 #info The 'contingency' plans on the infra wiki are still not really fleshed out, shame on me 19:02:15 kohsuke: you're up :) 19:02:17 #info fund-raising is concluded successfully, and the post added. rtyler still needs to submit the reimbursement request. 19:02:32 #info SCALE10x CI dinner --- oops 19:03:02 I think rtyler and I need to sync up a bit more 19:03:13 ... on the date 19:03:17 indeed 19:03:49 #info The great seal of the Jenkins CIA program is ready for action, but not the slides 19:04:13 #action rtyler to post a template of Jenkins CIA intro slides 19:04:43 and imod and I should probably start putting contents in parallel and apply the template when it's ready 19:04:59 yep 19:05:12 #info LTS 1.424.2 is RC-ed, tested, and released. 19:05:30 ... mad props to vjuranek and others as alwaysy 19:05:49 abayer: are you there? 19:05:57 Mostly. =) 19:06:12 there's one action of yours to ping GitHub about a private repo 19:06:56 Ah, yeah - I think we opted to go with one on one of our personal accounts for now, yes? 19:07:10 that's what I said I'd do for the infra secrets 19:07:57 abayer: if you feel this won't happen, then that's OK. We just need to figure out another plan. 19:08:09 But if you think we just need to ask, then I think we should ask. 19:08:19 Ah. I'll deal with it,t hen. Sorry. 19:08:38 next? 19:08:40 #action abayer to ping github again for a private repo for CLA (and infra secrets) 19:08:59 I think that's it for actions 19:09:00 brb 19:09:06 #topic Autopopulating Affected Version/s and Fix Version/s in JIRA 19:09:10 fredg02: you're up 19:09:36 thx, I just wanted to get the discussion started again. 19:10:04 it's been a long pending plan, so I thought it would be a good idea to bring it up again 19:10:20 I'm now generating LTS changelogs from git-log and ticket IDs in the commit messages 19:10:35 (That's http://jenkins-ci.org/changelog-stable) 19:10:53 I think it would be a good idea to popuplate the mentioned fields in JIRA (automatically if possible) 19:11:05 So if we can define the appropriate field in JIRA, then I think expanding this script to fill that in would be easy enough. 19:11:27 but thats for core only - right? 19:11:41 Yes. 19:11:53 I think we need a bit more work to make it work to plugins 19:12:12 separate components in JIRA? 19:12:31 so before the fields get populated core and plugins need to be split right? 19:12:54 fredg02: There are actually many ways to do it 19:13:10 It's less useful but it can be done without moving plugins to separate JIRA projects 19:13:17 didn't someone start some investigation on this? 19:13:18 ok. 19:13:28 ... by making them all share the same pool of version numbers 19:14:08 imod: yes, aheritier, but to be fair, I think the arrangement was that we first give them the second instance to play with those new scheme 19:14:15 ... which we haven't delivered. 19:14:22 I think it would be nice to give plugin developers some more freedom by making plugins separate JIRA projects 19:14:32 ok, understandable :) 19:15:14 fredg02: IIRC, the downside is that multiple projects require higher admin overheads on our side 19:15:35 ... and updating some existing automations, like jenkins-admin 19:15:37 where would the list of versions come from? 19:15:57 often, you might not know what next release's version number is going to be 19:16:06 rpetti: If there's an API to create a new version, then the automated filler program would be the right one to create it, I think 19:16:27 rpetti: exactly, that's why I'm advocating for retroactively parsing it from git-log 19:16:34 i agree 19:16:38 ... after a release is made 19:16:44 +1 19:17:04 And e-mail generated by that update would serve as a nice reminder to encourage people to use it 19:17:38 I can't judge how big the admin overhead is. but it would be worth a try in a sandbox environment, I guess 19:17:42 love it already! 19:18:09 fredg02: maybe we can do this in parallel. 19:18:38 Hmm, not sure what I mean by that 19:19:09 if you need any help with this, feel free to contact me :) 19:19:13 Evidently the main obstacle was that we failed to prepare the secondary JIRA instance necessary to play with this. 19:19:35 action item? 19:19:54 I think JIRA not wanting to be puppet-ed discouraged us enough not to tackle it 19:20:14 (or was it something else? am I fabricating the history?) 19:20:40 rtyler: do you have any thoughts on the best way to start a secondary instance? 19:21:00 if only we had this monstrosity puppeted... 19:21:12 yeah, i'm not really sure 19:21:17 I vaguely recall we were also waiting for another server to come online to house this. 19:21:20 Was it cabbage? 19:21:25 you'll run into licensing problems with a second jira too :/ 19:21:27 cabbage or lettuce 19:21:46 could we give fredg02 a backup and let him figure it out? :D 19:21:46 evilchili: I'm sure we can get a FLOSS license for it too 19:21:57 indeed 19:21:59 rtyler: fredg02: works for me 19:22:13 but he also needs to have access to the infra, right? 19:22:27 for him to do the experiment on this local system won't do any good 19:23:11 can we AI this to figure out, it's wider in scope than is suitable for this meeting IMHO 19:23:21 #info Possibly related is that eggplant, the current server of JIRA, has a number of problems 19:23:36 ranging from smaller disk space to the database option being not friendly to JIRA... 19:24:01 rtyler: would you want to phrase the AI? 19:24:32 fredg02: how much does puppet scare you? :P 19:25:07 dunno yet. I'm definitely interested. wanted to talk to you about puppet at FOSDEM anyways ;) 19:25:14 if we could kill two birds with one stone: https://github.com/jenkinsci/infra-puppet/issues/1 19:25:37 #action fredg02 and rtyler to work together on figuring out bringing up a issues-beta.jenkins-ci.org on our infrastructure 19:25:45 rtyler: fredg02: we might as well get paid by Atlassian to do it! 19:25:53 paid o_O 19:26:05 sounds good B) 19:26:06 if we can figure out a way to use puppet for this great, if not, so be it 19:26:16 I mean, they don't even have a debian package 19:26:45 I think I'm going to improve my changelog generator script slowly & steadily. 19:26:45 I've been in contact with the guy who coauthored Pro Puppet (also helped with puppet-jenkins) 19:26:50 I wonder if he'd be willing to help 19:27:11 I have debian packaging experience 19:27:19 pretty extensive really 19:27:20 heh 19:27:41 though time is something which has been hard for me to find lately. =/ 19:28:21 as a side note, because it was asked yesterday: JIRA can handle multiple affects versions and multiple fix versions 19:28:27 I think making JIRA a debian package is a nice separation of work. 19:29:48 we should close out the meeting if there are no more topics 19:29:57 rtyler: I've added two 19:30:03 ah 19:30:03 heh 19:30:09 then let's move on xD 19:30:13 And I was going to ask Majost if he's volunteering 19:30:18 for jira.deb 19:30:21 he's always volunteering 19:30:25 hah 19:30:25 :-) 19:31:07 Let's ask i386 if we can get some help from Atlassian 19:31:28 #action kohsuke to ping i386 about JIRA debian package 19:31:34 Right now, I can code review... 19:31:49 OK, I think we are done with this topic 19:31:55 np 19:32:21 #topic funding give-away items 19:32:33 is abayer awake still? :D 19:32:44 Sorry, distracted by work. =) 19:33:05 So, we got SCALE10x, FOSDEM, and Jenkins CIA program, and as well as various local meet ups 19:33:10 Not to mention 4 Jenkins User Conferences 19:33:27 And we got a bit of money thanks to the fund-raising drive. 19:33:58 So I wanted to see if people think it's a goo use of our money to buy some give-away materials for those events and efforts 19:34:24 More concretely, stickers as a general give away 19:34:32 ... and T-shirts for CIA agents 19:34:58 Are stickers expensive ? 19:35:10 I don't have the exact price, but a few hundreds for 1000 19:35:28 based on Alyssa, who has done one for JUC 19:35:29 http://www.stickermule.com/products/custom-die-cut-stickers 19:35:46 I'd pay for a t-shirt! :) (even more than retail if it's a donation) 19:35:54 T-shirts are more expensive, so they aren't give aways for everyone. 19:36:12 I did 1000 of them for my JUG and distribute to speakers & attendees, that was a nice advertising to find more audience 19:36:13 But rtyler and I thought it'd be a great incentive for recruiting CIA agents 19:36:19 * rtyler nods 19:36:32 I thing this makes sense to have such (low cost) goodies on conferences 19:36:36 #info https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CIA+Program 19:36:38 I'm all in for this 19:37:07 To try to be fair, the arguments on the other side is that we need to live cheaply 19:37:19 I don't think we want to do fund-raising every year like Wikipedia does. 19:37:57 true, but I think now its the time to get more people into the Jenkins world and that will pay out again... 19:38:18 agree 19:38:18 hehe. I like kohsuke staring at me from a banner more than those wikipedia guys 19:38:52 abayer: your thoughts? 19:38:57 we'll have to get some more fun images next time around ;) 19:39:11 I think we've got some cash to burn. =) 19:39:14 I'll have to see if kohsuke can do a buddy christ impression: http://upload.wikimedia.org/wikipedia/en/thumb/9/93/Buddy_christ.jpg/300px-Buddy_christ.jpg 19:39:35 kohsuke: I think setting a quarterly or annual budget for this makes sense 19:40:01 if we were to say we have a $1500 evangelism budget this year or something like that, that would guide our decisions much better IMHO 19:40:31 We have about $6K in our bank right now (excluding what's already committed) 19:40:38 CIA Agents should make a note about donation at every presentation... 19:41:21 kohsuke: I'm inclined to be more conservative with the funds honestly, I don't like begging :P 19:41:31 rtyler: Me too 19:42:13 how about putting a small donation fee on every merchandise item? 19:43:03 How about we allocate $500 for stickers and $500 for T-shirts (when CIA is ready to launch), and see how long it lasts? 19:43:12 I like that 19:43:15 * rtyler pokes abayer 19:43:25 +1 19:43:27 I got some CloudBees-funded stickers on my way, so it should last. 19:43:56 Any other +1/-1s? 19:44:02 +1 19:44:07 +1 19:44:15 #info How about we allocate $500 for stickers and $500 for T-shirts (when CIA is ready to launch), and see how long it lasts? 19:44:32 +1 19:44:34 #action kohsuke to get +1 from hare_brain for it 19:44:44 rtyler: your right about the conservative fund raising! 19:44:47 you might be able to setup some pre-orders too 19:44:57 could offset the cost a little 19:45:08 fredg02: the tricky part is to make the markup go to SPI without going through any individuals 19:45:24 ok. 19:45:36 I suspect the said individual has to deal with taxes and other stuff, too 19:45:56 but if you figure it out, let us know 19:46:07 ok :P 19:46:09 agree : thinks aren't simple if we introduce local payments 19:46:32 OK, I think that's it for this 19:46:42 #topic CLA collection 19:47:10 This last one is just to say that we will start collecting CLAs for the core, even while we figure out the final destinations of those PDFs 19:47:28 More of a note to myself to get this ball rolling 19:47:49 #action kohsuke to start whipping us to sign CLAs 19:47:52 link to template for the doc ? 19:48:04 It's in the governance document somewhere 19:48:07 ok 19:48:30 #topic next meeting 19:48:35 #info https://raw.github.com/jenkinsci/infra-cla/approved/icla.txt 19:48:41 #info https://raw.github.com/jenkinsci/infra-cla/approved/ccla.txt 19:49:03 1/25, same time? 19:49:18 works for me, that'll be right after SCALE so we'll have much to talk about 19:49:20 and right before FOSDEM! 19:50:02 #agreed next meeting is two weeks from now, same time 19:50:19 Anyone wants to talk about anything else? 19:50:46 I have this rash on my side.. 19:50:53 Guess not. Thanks! 19:50:55 #endmeeting