18:02:50 #startmeeting 18:02:50 Let the Jenkins meeting commence! 18:03:02 #topic JUC 18:03:11 Alyssa take it away 18:03:13 JUC SF is Oct 23. Registration page is up http://www.eventbrite.com/e/jenkins-user-conference-us-west-san-francisco-oct-23-2014-tickets-10558684309 18:03:24 Woohoo 18:03:29 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Jul23thMeeting 18:03:49 We have early bird price so pls help spread the word 18:04:39 #info early bird price in effect 18:04:58 In the last meeting. we talked about opt-in/out option. Lisa wanted to know if it was ok to share title of attendees w platinum/gold sponsors 18:06:22 To me, that’s a reasonable ask. 18:06:28 Originally, we were to share name, company name, city/state/country and email address 18:06:50 Would that be a required field for registration then? 18:07:09 right. we'll ask for title but is it ok to share that w/ platinum & gold sponsors? 18:07:43 “hare_brain: To me, that’s a reasonable ask. [11:06am]" 18:08:20 Anyone else have an opinion? 18:08:30 if not, 18:08:40 #agreed can share title w/ Pt/Au sponsors 18:08:49 thanks! 18:09:14 Anything else about JUC? Meetup? 18:09:26 yes for meet up pls 18:09:43 do we want to do a meet up along w/ JUC ? 18:09:53 #topic JUC meetup 18:09:56 rather..after or before juc? 18:10:23 Along the lines of the Jenkins Scalability Summit last year? 18:10:49 similar I think. I haven't talk to KK about details 18:11:01 Starting build #3544 for job jenkins_main_trunk (previous build: SUCCESS) 18:11:15 just wanted to see what folks think about doing similar along that line 18:11:27 Is there a topic? Seems like there was a big thread on Jenkins UI. 18:11:53 Seems like a decent idea. 18:12:04 I think it may be on Workflow 18:12:15 (a subject near and dear to me) 18:12:16 :-) 18:12:23 Confirmation bias. :) 18:12:30 jglick: :o) 18:12:46 Maybe send out a call for requests for meetup themes? 18:12:51 +1 18:12:55 With some initial suggestions? 18:12:57 good idea 18:13:06 Would it be at the hotel, or at CloudBees office again? 18:13:08 Or somewhere else. 18:13:17 #action Alyssa to call for meetup theme suggestions/votes 18:13:20 If it’s too far from the hotel, people may have transportation issues 18:13:32 CloudBees was reasonably close to JCC last year. 18:14:13 @hare_brain: JUC is in Burlingame this year..we've out grown JCC. We're not sure re: location yet 18:15:00 Yes. That’s what I meant. I was asking if the meetup would be near JUC location. 18:15:30 @hare_brain: dunno yet :( 18:15:42 Ah. 18:16:06 I think that should be factored in. If it’s not near JUC, people traveling for the conference may have a hard time getting to it. 18:16:34 thanks. will keep in mind as we work this out. 18:16:36 Alyssa, as an aside, is there a reason JUC is not close to J1? Other than making people spend 2× the airfare if they want to get to both? 18:16:43 (close in time I meant) 18:17:39 Jglick: it a resource issue for us. short on man power ..i'm afraid 18:18:00 Alright, OT anyway I guess. 18:18:01 doing back to back events is hard on the team 18:18:10 Anything else on JUC? 18:18:19 that's it thnx 18:18:38 moving on then… 18:18:39 #topic JIRA components 18:18:56 danielbeck: I do not see oleg_nenashev (correct nick?) here 18:19:19 oleg-nenashev I think, but he's not here 18:19:33 https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring 18:19:41 Proposals look fairly reasonable 18:20:05 And I've written a script to add the '-plugin' suffix to all components that are a plugin as I suggested a few weeks ago 18:20:28 Excellent. 18:20:37 Requires admin + API though. Tested on my Jira instance. 18:20:58 So who would be driving this? Oleg? In that case we should defer discussion till a time when he can join, or ask on the list to proceed. 18:21:29 As Oleg isn't here we should probably postpone further discussion. Maybe suggest on the list we do this in two weeks. 18:21:57 Until then everyone interested can review the suggestions and suggest changes. 18:22:00 Sensible. His last message: “If everyone agrees, it would be great if somebody with JIRA administration rights takes the action point.” 18:22:13 Probably that would be kohsuke. 18:22:31 #action oleg-nenashev to report on status of JIRA component change 18:22:39 #action kohsuke to implement JIRA component change 18:23:10 I would also like to see a final list of components for concreteness. 18:23:32 Anything else on this? 18:23:38 If not, any other topics? 18:23:50 I’d like to request rules/conventions for when new components are created. 18:24:14 How do I install jenkins on Ubuntu 14.04.1 LTS? 18:24:20 There’s some that are already implicit: which is -plugin for components related to a plugin. Component maps to repo 18:24:31 john_doe_jr: later please, meeting in progress 18:24:40 Are there others that should be codified? 18:24:42 k sorry 18:24:54 hare_brain: I think that is the only real rule, that when you make a plugin you add a matching component. 18:25:39 Looks like a lot of existing components are going to get merged into core. Will that make it harder to manage looking through core issues? 18:25:56 Easier actually IMO 18:25:56 Or is the solution to that, just break more core into plugins? 18:25:59 Most things physically in core are already filed in it. 18:26:09 Right now you have no idea where something in core would be filed. 18:26:15 And yes, breaking out functionality into plugins is great when it is possible! 18:26:31 (I am working on hudson.tasks.test/junit, FYI.) 18:26:45 Agreed with danielbeck, predictability is crucial. 18:27:02 Can always use labels to indicate what aspect of the code you are dealing with. 18:27:03 As a matter of personal preference, I think that “unsorted” is rather non-descript. 18:27:19 re: labels. Great. 18:27:21 The goal should be to keep unsorted empty. 18:27:23 IMO 18:27:32 I agree with that. 18:27:33 Well yes. 18:27:51 #agreed want unsorted component empty, but maybe need a more descriptive name 18:28:32 Anything else before I close? 18:28:37 A few more questions 18:28:37 we are ready for 1.565.1 18:28:50 #topic 1.565.1 18:28:52 Is the intent of the unsorted component to be a holding place for “I don’t know where to file this” or 18:29:02 sorry 18:29:07 #topic JIRA components 18:29:12 Is it things that haven’t been triaged. If the latter, then that seems to be duplicative for the untriaged stage. 18:29:43 I think the intent was as a temporary holding place for historical issues in anomalous components, or newly filed things where the reporter is just clueless. 18:29:46 But I am not really sure. 18:30:10 i.e., if we have an unsorted component, does moving it out of that component mean that a ticket has been triaged? 18:30:13 typically users are filing in the component they believe responsible anyway. Not sure what to do with issues that don't have the component (plugin) in Jira 18:30:48 Right, typically you would know the right component when you are filing. (If not, probably you should not be filing issues to begin with.) 18:31:13 #action oleg-nenashev to document intended usage of unsorted 18:31:21 OK, I’m done. Thanks. 18:31:26 OK. 18:31:30 #topic 1.565.1 18:31:40 ogondza you say we are ready for a release? 18:31:46 yes 18:31:50 then 18:31:55 #action kohsuke cut 1.565.1 18:32:33 Haha 18:32:37 JENKINS-18065 is on my short list for 1.565.2 backporting. 18:32:39 JENKINS-18065:AbstractLazyLoadRunMap.iterator() calls .all() (Resolved) https://issues.jenkins-ci.org/browse/JENKINS-18065 18:33:08 I think kohsuke is traveling and busy today and perhaps for a few days, but can probably get to it Monday or thereabouts. 18:33:29 Anything else? 18:33:50 #info jglick runs meetings really well 18:34:01 #info next meeting Aug 06 18:34:18 (thanks! though I know little about the JUC planning) 18:34:29 #endmeeting