18:00:37 #startmeeting 18:00:37 Let the Jenkins meeting commence! 18:00:56 #chair abayer hare_brain kohsuke rtyler 18:00:56 Current chairs: abayer hare_brain kohsuke rtyler 18:01:18 * kohsuke tweets 18:01:46 #topic Recap action items 18:01:57 uh 18:02:00 so I sent in the proposal 18:02:03 #info https://issues.jenkins-ci.org/browse/MEETING 18:02:03 for the FOSDEM dev room 18:02:08 We carried forward a lot of action items from the 8/8 eeting 18:02:26 I guess I'm going to close MEETING-5 then 18:02:33 is the proposal visible somewhere? 18:02:35 we have JIRAs for these O_o 18:02:48 Hello 18:02:57 #info The FOSDEM devroom proposal: https://gist.github.com/6546c827b777c55f1ff7/48124395c9690ff0f95964acf32cce9dd6c1ea2a 18:03:13 Wow I had no idea 18:03:30 I can't tell if kohsuke is messing with us 18:03:39 I think he's messing with us 18:03:54 He did this a month ago. 18:03:59 According to the dates on the issues 18:04:25 I think it was discussed in the meeting and I got an AI to set up JIRA to track actions 18:04:29 Well, huh. 18:04:38 how'bout that 18:04:46 I suck even more than I thought I did. 18:04:58 That was even the action item #1 from the last meeting 18:05:02 kohsuke to set up JIRA for project meeting actions 18:05:02 no ndeloof, so I'm guessing his items are still lingering another couple weeks :) 18:05:12 So we can cross that one off. 18:05:20 KK where is your "I have a bot for that" stock answer 18:05:49 What is the "travel grant" action? 18:06:04 Yeah, in due time, stephenc_ 18:06:26 kohsuke: that was what we discussed to some extent in japan 18:06:40 Yes, I know the context 18:07:05 ah, so this action was "let's discuss FOSDEM travel grant in the next meeting" action 18:07:09 yes 18:07:19 sorry, we were all drunk last time round 18:07:21 I'll add it to the end of the agenda then 18:07:49 mika packaged the ircbot up and I've merged his changes in 18:07:56 oh nice 18:07:58 it's now on me to add the puppet bits 18:08:12 closing https://issues.jenkins-ci.org/browse/MEETING-1 then 18:08:16 I don't think lisa ever got around to a write-up 18:08:16 if you need any further help, just ping me 18:08:26 on meat-space meetups 18:08:55 #action LisaWells to publish the write up on hat we can help to facilitate meet-ups in meat space 18:09:20 s/hat/what/ 18:10:01 I think that's it for actions 18:10:09 let's mooooooooooooooooooooove it 18:10:22 #topic Should the "Sponsor this issue" link be ommited for closed issues 18:10:32 tonylampada: I believe it's yours 18:10:34 all right, my turn 18:10:45 Hi folks 18:11:14 so, I just wanted to ask if should implement https://github.com/freedomsponsors/freedomsponsors-jira-plugin/issues/4 18:11:42 I think it's up to you, but personally, if you ask me, it makes sense to implement it 18:11:45 I also, do a quick check to how do you guys like the new plugin, and if there's anything I can do do improve it 18:12:21 As far as I'm concerned, all I need to hear is "here's the new version, please deploy it" 18:12:26 I've had no interaction with it 18:12:58 * kohsuke now sees that the OpenID fix is somehow not working for him 18:13:24 Do you guys know if ppl check up on http://freedomsponsors.org/ from time to time ? 18:13:53 There's. ummm U$ 270 hanging on open issues already :-) 18:14:22 That's good to know 18:14:26 I mean, the commiters 18:15:02 I don't think there's much else to this topic. 18:15:05 #idea Publicize freedomsponsors.org at JUC? 18:15:08 has anyone seen this bug: 18:15:09 https://gist.github.com/3641693 18:15:15 ok. I will implement it then 18:15:22 :-) 18:15:24 thanks 18:15:26 #idea or a guest post on http://jenkins-ci.org/ ? 18:15:34 is there some feedback to the issue itself as soon as there is some sponsoring on it already? 18:15:43 I like the guest post idea 18:16:05 imod: that's another idea for tonylampada to implement on his service 18:16:16 I like hare_brain's idea! hehe 18:16:42 I'll mention this in my slides then 18:16:42 the guest post idea is a good one too 18:17:16 #action tonylampada to write a guest post on jenkins-ci.org about Freedom Sponsors 18:17:34 If someone could take a picture of Kohsuke with a FS slide in the background, it would make my day :-) 18:17:41 hah 18:17:57 #idea Jenkins newsletter would be another place to talk about this 18:17:57 imod: looks like your comment is already filed as https://github.com/freedomsponsors/freedomsponsors-jira-plugin/issues/5 18:18:10 yep, just seen it too :) 18:18:22 hare_brain: I'll mention that to Lisa 18:18:32 it looks like she's away today 18:18:55 moving on to next topic? 18:19:16 I think implementing issue 5 is easy enough. Will do that too okay? 18:19:28 +1 18:19:37 #topic election process proposal 18:19:48 I need to send this to dev and all 18:19:59 oh snap 18:20:11 and I just wrote it up, so my apologies for being last minute 18:20:13 #info https://wiki.jenkins-ci.org/display/JENKINS/Board+Election+Process+Proposal 18:20:35 I had made this comment to you in email, kohsuke, but your proposal doesn't talk about how people get nominated. 18:20:55 Does the current board nominate new candidates and voters just vote to approve the nomination(s)? 18:21:07 Or do you think it should be more wide open? 18:21:34 I didn't think about that 18:22:03 The risk with wide open is a hijacking by a load of fly by night committers joining 18:22:25 I agree with stephenc__. My preference would be for the first. That's how boards typically work anyway. 18:22:27 yeah there needs to be a stipulation somewhere in there 18:22:40 If you do "semi" I would say any 2 year+ committers can propose 18:23:08 And 10% of that population is required for a nomination 18:23:10 Or write-ins I guess. 18:24:02 Iow if 10%+ of the 2yr+ committers think ted should be on the board then he is nominated and a vote must be held by all to approve 18:24:05 Do I have this right? 2 year+ committers can propose a nominee. 10%+ approval to get that proposal on the ballot in the first place? 18:24:48 I was hoping that we can keep it simple 18:25:01 the more complicated the rules, the harder it is to justify 18:25:04 Ted then needs sufficient votes to get on the board... I am not making a suggestion on the voting process 18:25:16 …all I know is I'm voting for Ted. 18:25:25 Simple is the existing board nominate their replacements 18:25:26 ALL GLORY TO THE HYPNOTED 18:25:42 I tend to agree with kohsuke. stephenc__'s proposal adds a lot more overhead. 18:26:30 As long as we don't fall into cronyism 18:27:28 but I want to be a crony :( 18:27:30 when you say that "voters vote to approve" the candidates selected by the board, are there stipulations on who those voters are 18:27:38 Well if the proposal is rejected by 51% you have to come up with a second proposals 18:27:52 I have never commented here: are you looking to replace all board members at once or will it be rolling upgrade ;-) 18:28:07 dapak, harpreet_: read the propsal. :) 18:28:13 Both of your questions are covered. 18:28:35 words? reading? THIS WOULD NEVER HAPPEN UNDER TED'S RULE 18:28:37 I think if we can find who's interested in serving, while allowing the board to filter out weirdos, that'd be the best of the both worlds 18:28:40 ;) 18:29:02 My only quibble with the proposal is that I feel like I should be stepping down sooner than a year from now - I really haven't been pulling my weight. 18:30:14 hare_brain: thanks 18:30:33 I think I'm OK with letting people nominate themselves 18:30:49 I'm not really worried about weirdos caring enough to nominate themselves and then winning 18:30:53 (total sidenote - looks like there are under a thousand Jenkins *nodes* (slaves and masters) running JDK 1.5) 18:30:54 so as far as voting restriction, i feel like if you can somehow prove you are a jenkins community member you have a right to vote — perhaps contributing in some way traceable to your jenkins account (jira bug, github pull requests, etc) 18:31:25 dapak: If you register or have voted previously, you're eligible. 18:31:28 That simple. 18:31:39 my concern with hare_brain's "board nominates and the community would approve" is that how do the board find out who's willing 18:31:49 There's that. 18:32:14 Ah well, my thinking is that we have an idea of the types of perspectives we want represented on the board. 18:32:22 (ack, that was just masters) 18:32:24 We know people who align with that, and we ask. 18:32:27 I propose we say the existing proposal is a good start, discuss this further on the mailing lists to tweak it as needed 18:32:33 we're getting a little bogged down 18:32:45 elect everyone, problem solved 18:33:01 Occupy Jenkins! 18:33:02 Sorry. 18:33:03 dapak: Now you have two problems 18:33:40 rtyler: OK. 18:33:43 I second rtyler's motion. Clearly we need to work out the nomination process. We can do that over email 18:33:44 rtyler: +1 mroe wide discussion on mailing list 18:33:54 yay i'm contributing 18:34:13 rtyler: It won't last 18:34:18 I'll write up hare_brain's "please trust the boards to nominate good people" model and send it to the dev list 18:34:31 #action I'll write up hare_brain's "please trust the boards to nominate good people" model and send it to the dev list 18:34:40 moving on... 18:34:49 #topic Help wanted: spams are on the rise 18:35:09 #info there has been some on-going spam problem on Wiki 18:35:09 Where is your bot for today 18:35:19 And jira 18:35:32 I've been deleting the posts and banning them manually 18:35:44 Yes, and JIRA, apparently, although I haven't checked it 18:35:59 I think we should have a project in JIRA for spam reports to go into 18:36:04 At least one issue is just spam 18:36:11 1. I wonder if anyone has experience dealing with those stuff 18:36:13 then we'll at least have a queue 18:36:18 Are you really planning on handling spam manually? 18:36:32 and 2. if we can give more power to more people to fight spams 18:36:54 rtyler: Do you mean a project for the spammers to put their spam issues in, or a project for us to report them in 18:36:58 isn't there some kind of wiki plugin to prevent this 18:37:00 Yes, JIRA project could work 18:37:13 if not, perhaps switch to something that's better secure 18:37:28 dapak: switching the system is too much work and not practical 18:37:29 stephenc_: heh, more of a "report the spam" queue 18:37:54 There was me thinking you had a honeypot idea 18:38:11 I did track down 2 spammers sign-up history and they don't look like robots 18:38:18 moreover I;m not sure if it's generated by bot, maybe it's manual spam 18:38:37 (at least they didn't look like a program making HTTP calls right away) 18:39:23 If you're convinced that these are real people signing up just to generate spam, you could try hellbanning them. 18:39:34 what is hellbanning? 18:39:36 hellbanning is where only that user can actually see content that they create 18:39:57 There is no way Kohsuke could write a bot to clean up all the spam over lunch 18:40:19 lets bet on it... 18:40:28 that said, I can't imagine anyone is actually manually performing the spam themself. 18:40:29 It does seem somewhat possible 18:40:40 can you enable a captcha on editing / commenting 18:40:47 #action kohsuke to create a 'report-the-spam' project in JIRA to help track and report spam 18:40:48 https://confluence.atlassian.com/display/DOC/Configuring+Captcha+for+Spam+Prevention 18:41:00 lov: yes, I agree, but then, I find it hard that someone cared enough to write a program against our custom user signup app 18:41:11 dapak: thanks, I'll check that out 18:41:15 No way. I will bet "five minutes of worshiping KK at the next huddle" that it cannot be done 18:41:42 stephenc_ knows how to poke me... 18:42:07 Anyway, I think I'm good on this topic for now 18:42:13 When I was on the Yahoo! Games team, we had all sorts of problem with spam and bots in the game rooms. I used to think like kohsuke did, why would anyone take the time to reverse engineer our protocol just to do this, but they did. 18:42:23 We'll see how effective my incentivising is... 18:42:38 It was an arms race 18:42:41 I wouldn't compare Yahoo! Games and Jenkins at the same level, but ... 18:42:49 mooooooooooooooveee it 18:42:50 Yeah, Jenkins is waaaaaaaay bigger. 18:43:02 #info if anyone is willing to volunteer to be a spam police, please let us know 18:43:03 My point is that some people get their kicks out of the strangest things. 18:43:32 I'm one of those 18:43:34 #topic FOSDEM travel grant 18:43:56 Am I correct that I think there's a reasonable consensus for that? 18:44:01 let's hurry on this topic, I'm hungry :D 18:44:02 I'm strongly in favor. 18:44:12 If so the only real question is how much we should spend 18:44:38 I'm not gona be there this time so -1 :) 18:44:42 heh 18:45:05 I was looking forward to seeing you 18:45:28 you'l have to get to australia ... 18:45:59 holidays are nice too 18:46:02 #info I haven't done the exact count, but I believe we have more than $5000 on our account in SPI 18:46:29 how many people do we want to bring? :P 18:46:30 Project jenkins_main_trunk build #1892: SUCCESS in 47 min: http://ci.jenkins-ci.org/job/jenkins_main_trunk/1892/ 18:46:30 * imod: update to new parent pom and cleanup plugin config to also work with m2e 18:46:31 * imod: update plugins parent to pickup new parent for cleaner m2e support 18:46:44 #info $7348.12 to be exact 18:46:47 #info http://spi-inc.org/meetings/minutes/2012/2012-08-09/ 18:46:49 if we get the devroom, I'll need all the help I can get :) 18:47:07 $1000 each for 2 people? 18:47:10 This grant is to pay for completely, or just subsidize 18:47:13 Where and when is it? 18:47:13 I think we should shoot for at least 2 people 18:47:23 kohsuke: I like 1k for two people 18:47:24 hare_brain: most likely just to subsidize 18:47:44 if we're nominating people, I'd like to bring jieryn over :P 18:47:52 the whole trip will likely cost more than $1K and I think we want to decide how much we spend upfront 18:48:11 $2K is 27% of our funds. 18:48:19 I think starting at $1k will be good, I'll see what I can scrounge up for specific sponsorships 18:48:38 it might be feasible to get a few entities to help sponsor something specific around travel grants to FOSDEM 18:49:22 rtyler: you have some idea about who might pitch in? 18:49:35 * rtyler coughs redhat 18:50:00 let's decide on $2k spend on 2 travel grants for now 18:50:04 hare_brain, abayer? 18:50:09 +! 18:50:16 or +1, y'know, whatever. 18:50:31 0 undecided but willing to go along with the majority 18:50:45 hare_brain: our run rate has been mostly pretty low 18:50:51 redhat just purchased naming rights to an ampitheater here in raleigh for a million+, they could probably squeeze a couple extra dollars for travel :P 18:50:54 it's been just CIA T-shirts and stickers 18:51:29 I'd like to come up with a good program proposal, to structure this so it's not a one time thing 18:51:30 so I think we should be able to spend it 18:51:52 It just feels like a big chunk of what we've built up. Is this what we want to spend a quarter of our reserves on? 18:52:00 I think so. 18:52:09 we'll do another end-of-year fundraiser 18:52:21 I'm hopeful that we can raise a few thousand dollars, at least, every year 18:52:22 No, please let's not do fundraising every year 18:52:27 really? 18:52:32 As I said, I'm willing to go along if everyone else thinks this is a good idea. 18:52:35 no fundraising? 18:52:39 That's so Wikipedia! 18:52:55 You don't want to be a massively successful household name? =) 18:53:00 +1 from me, if I get some support to get to SF next time :) 18:53:09 GIANT PICTURE OF YOU REPLACING THE JENKINS LOGO UNTIL WE GET MONEY 18:53:28 fundraising is an unfortunate fact of life though, we don't have to go full Wikitard, but I think it should be a end-of-year ask 18:53:32 I suggest future funding sources as a topic for the next meeting. 18:53:41 lots of companies have end-of-year budgets that need to spend some money ;) 18:53:43 i second that suggestion 18:53:46 * rtyler nods 18:53:50 I'll add it 18:53:58 #action next agenda item: "I suggest future funding sources as a topic for the next meeting." 18:54:02 heh 18:54:23 that's all the time I have, i'll be back later :) 18:54:26 Let's also see if some people actually want to come to FOSDEM, too 18:54:31 We can also do more targeted fundraising - i.e., raise $2k for the travel grants specifically. 18:55:11 And I gotta run momentarily too. =) 18:55:15 Five minutes left 18:55:27 I had one thing to bring up before rubber stamping the next meeting time 18:55:34 #agreed we are basically OK with spending $1K x 2 people for FOSDEM travel grant, but we want to make sure money is used well 18:55:42 Well if KK is going to fosdem, I may go anyway 18:55:52 stephenc_: I'm going 18:55:58 If we can convince sacha to pay that is ;-) 18:56:02 I had proposed to kohsuke that we should have a project meeting at JUC at the end of the month 18:56:07 but let's give the floor to hare_brain 18:56:28 hare_brain: want to change the topic accordingly? 18:56:44 #topic Hold project meeting at JUC SF on 9/30 18:56:47 hare_brain: and +1 to the project meeting at JUC 18:56:57 I'll +1 it on the condition that I get to resign from the board then. =) 18:56:57 I'm curious what it's going to look like. 18:57:13 We'd have to work out some logistics, since not everyone will be there. 18:57:13 abayer: that won't be sending the right message 18:57:18 bah1 18:57:23 Probably "simulcast" over IRC 18:57:24 =) 18:57:42 But my hope is that we get other people involved that normally not vocal here. 18:58:08 Could we use the panel session time slot at the conference for this? 18:58:24 Or do we need to do this out of band of the conference sessions? 18:58:27 I've got a lightning talk then, but I can finish up quick and run over. 18:58:29 Maybe I could report how we spent money last year 18:58:49 what we should be spending money on could be a great topic, too 18:59:13 I just wanted to get the idea in people's heads, and we can talk more about it at the next meeting, but I wanted to bring it up so we have time to figure it out before JUC 18:59:24 hare_brain: I'll check with Alyssa, but I'm sure it's doable 18:59:26 I don't think there's time right now to get it all sorted it 18:59:52 That's it. I yield the floor. :) 18:59:59 #topic next meeting time 19:00:08 Two weeks from today, same time? 19:00:11 naturally, 9/19, the same time 19:00:16 Rightie-o. 19:00:19 Yup! 19:00:23 #agreed next meeting is the same time in 2 weeks (9/19) 19:00:32 And I think that's it for today 19:00:39 abayer, no sneeking your resignation from the board onto the next meeting's agenda. :p 19:00:42 bah! 19:00:45 Thank you gentlemen 19:00:49 #endmeeting