18:02:31 #startmeeting 18:02:31 Let the Jenkins meeting commence! 18:02:38 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda 18:02:47 #topic recap of actions 18:03:04 #info https://issues.jenkins-ci.org/browse/MEETING 18:03:25 Hmm, I guess I haven't kept that up to date for a while 18:03:38 Any specific AIs that we want to review? 18:04:00 kohsuke patron program progress? 18:04:04 hey kohsuke :) 18:04:12 Ah 18:04:22 I'm afraid no progress to report 18:04:34 I need to follow up that one 18:04:40 kohsuke: Did you happen to take a look at my ICLA yet? :D 18:04:50 #action kohsuke to write to christina 18:04:52 Kamran Meeting right now, please wait a bit 18:05:02 danielbeck: Okay. 18:05:15 shall we move on to other topics, sinec we have a lot of them? 18:05:36 +1 18:05:42 +3 18:05:45 #topic JUC 2015 - obtain approval for a Mobile Morning mini-track that focus on Jenkins mobile development (Alyssa) 18:06:26 Some sponsors are interested in having a clump of mobile related sessions & panel in JUC 18:06:45 And so alyssa wanted to socialize that idea & see how people feel 18:07:39 (All the usual caveats about no product pitch etc still applies.) 18:07:59 would that be in parallel to other tracks? 18:08:59 I don't think so, it's just putting all the mobile related talks back to back in one of the existing tracks 18:09:21 So it's really just a grouping with a little bit of extra visibility 18:09:49 All right, I take silence as "it's OK" 18:09:51 going once... 18:09:52 mobile developments. Oh my god, I had to fight with xcode and ios build all the day… 18:10:16 Yeah, I'm sure there are a lot of battle scar stories to share 18:10:22 should be fine if attendees have other things to do if not interested. 18:10:27 I’m sure too 18:10:34 Right, it's one of the two tracks 18:10:43 OK, moving on... 18:10:51 #topic Build/publisher steps & AbortException handling 18:11:17 oh but kostyasha is not here 18:11:23 I added the two supplementary links in the wiki but Kostya indicated they we're really what this is about. Sorry about that! 18:11:40 #topic Defining guidelines on expected behavior and/or structure for plugins? If so, should we enforce them? 18:12:20 Let's skip this, I added this as it's somewhat related to Kostya's topic 18:12:29 all right 18:12:37 We already discussed it in October, it's recently come up again 18:12:43 #topic Would changing the meeting time to 10 AM PST/PDT allow overruns? 18:13:00 Basically what it says on the tin. WDYT? 18:13:04 would changing the time allow overrun? 18:13:38 we've had several meeting we had to abort or hurry through, so the question is whether the problem is duration or time 18:13:52 and if it's the latter, would moving the meeting time help? 18:13:58 or frequency. 18:14:16 I think it would also help eastern europe (e.g. Oleg, Kostya) if it was earlier 18:14:31 Personally, if we really need to overrun, I can stay around even in the current time 18:14:46 And likewise, even if we change the time, I'll still be just as likely to want to wrap this up in an hour 18:15:25 alright, so the meeting time is not actually a problem (unless others want it to end earlier due to TZ issues) 18:15:28 If this is to accomodate oleg, kostyasha, etc., I want to hear from them 18:15:45 agreed 18:15:56 I'm open to changing time, but there's certain inertia for things like this 18:16:17 so in the absense of people saying "I can make it if the time moves", I'm inclined to keep it as is 18:16:28 +1 18:16:33 and obviously, my apologies for blowing the previous one 18:16:43 +2 18:16:48 As I wrote, from past meetings I got the impression that end time was a rather hard limit, hence the suggestion. 18:17:08 let's move on 18:17:16 #agreed if oleg, kostyasha or anyone else really want to change the time, we'll reconsider, but for now we keep the time as is. 18:17:25 #topic Who gets voice on IRC? "Committers"... to any plugin? To core? 18:17:36 I couldn't find any info on that. 18:17:48 So the intent of the voice was to (1) give some visibility to active people in the community and 18:17:55 (2) grant access to ircbot 18:18:20 So to me, it is open to any plugin developers 18:18:38 I guess your point is that it should be written down somewhere 18:18:43 AFAIR it was the case. For any developer who asked to have it 18:18:47 we've recently added destructive commands to the bot. 18:18:56 hm 18:19:00 so "any plugin dev" seems to be too permissive 18:19:17 Starting build #4061 for job jenkins_main_trunk (previous build: SUCCESS) 18:19:40 maybe we limit who can run those destructive commands? 18:20:01 we can just hard-code them in the bot, or maybe limit that to ops? 18:20:07 probably. 18:20:08 too few ops 18:20:19 ^ 18:20:48 just seems weird to have someone request a fork of the 1010th plugin and give them control over all the repos and Jira. 18:20:50 there are few ops, thus +1 to allow them to do launch that destructive commands instead of people with only voice 18:21:31 what if we use +v in jenkins-infra for more delicate commands? 18:21:31 then I'll need to finish the jira component refatoring before that goes live :-) 18:21:53 jira component refactoring? 18:21:55 kohsuke would reduced visibility be a problem? 18:22:18 No, it's still the same bot, just that some commands you need to ask from #jenkins-infra 18:22:28 And really, how many times do you need to remove components? 18:22:36 kohsuke Visibility as in the community seems what's going on 18:22:48 kohsuke A few dozen times or so still, but that's still part of https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring so ... rarely 18:23:40 if we log #jenkins-infra I think the visibility concern should be addressed 18:23:58 right 18:24:11 (and perhaps that way we can make the bot even more capable, like restarting jira) 18:24:17 yeah 18:25:04 danielbeck: is that good enough in your opinion? 18:25:23 still a bit too permissive for my taste, but that's the nature of the project I guess. 18:25:36 yes 18:25:40 so yeah, should at least prevent abuse. 18:26:13 #action kohsuke to log #jenkins-infra 18:26:25 can somebody volunteer to update ircbot for this new permission scheme? 18:26:40 I think oleg hacks on ircbot 18:26:51 he's not here, but we can ask 18:26:56 Doesn't jenkins-admin use PircBotX? 18:27:03 Kamran: yeah 18:27:13 Do you want to take this on? 18:27:26 It's a small Java program: https://github.com/jenkins-infra/ircbot 18:27:59 #agreed we'll run jenkins-admin bot also in #jenkins-infra and restrict destructive commands to people with +v on #jenkins-infra 18:28:13 #action danielbeck to ask oleg if he can hack ircbot to do this 18:28:30 if that fails I guess it'll be on me 18:28:40 shall we move on? 18:28:45 yes 18:28:50 #topic JENKINS-27268 18:28:53 JENKINS-27268:"dumb" slave? (Open) https://issues.jenkins-ci.org/browse/JENKINS-27268 18:29:12 A user brought up the terminology issue in Jenkins 18:29:31 similar issue in Django a while back: https://github.com/django/django/pull/2692 18:29:51 OK, I thought for a moment he has a trouble with "dumb" part 18:30:00 but IIUC he's complaining about the "slave" part 18:30:01 So I wanted to raise awareness of this issue and discuss whether it needs to change 18:30:11 It's worse in combination I think 18:30:12 we have enough ambiguity in terminology, imo. I do not feel master/slave to be that problematic personally 18:30:28 the "dump" part worries me more, too 18:31:10 I originally named it "dumb slave" in anticipation of newer smarter slave types, but that never really materialized 18:31:53 So I can definitely change it to "Build slave" or something by just a few changes in the core 18:32:07 I could take that on, since it seems quite easy. 18:32:20 Renaming "slave" to another word that's more politically correct word would be a bit more work 18:32:42 but if some people are offended by it, I suppose we need to do it 18:33:05 Being an immigrant, I don't have the proper American sensibilities to that issue. 18:33:36 I think we should keep slave, but at least change it to build slave like you mentioned. 18:34:05 Is that good enough for the submitter of JENKINS-27268? 18:34:08 JENKINS-27268:"dumb" slave? (Open) https://issues.jenkins-ci.org/browse/JENKINS-27268 18:34:24 I don't know. I can ask. 18:34:33 And looking at that django issue, looks like they have rejected it 18:34:46 or not 18:34:50 kohsuke I think only this particular solution 18:35:00 and implemented another 18:35:12 I suggest "static slave" or "permanent slave" 18:35:12 or please tell me this is the april's joke.. 18:35:30 bookwar Sorry, no. 18:35:33 danielbeck: What about "build node"? 18:35:39 master is also a node 18:35:48 "standalone slave"? "simple slave"? 18:35:55 Wow, that PR quickly turned into a PR circus 18:36:18 kohsuke The reason I wanted to bring this up here, so we don't get caught in the same mess 18:36:40 Yeah, I'm more inclined to fix this now that I see that shit storm 18:36:48 Unwanted attention 18:37:16 kohsuke: What would you guys change "dumb slave" to though? 18:37:16 Kamran: yeah "build node" would work 18:37:22 yay :D 18:37:30 It's close to internal name, too 18:37:41 class Slave extends from Node 18:37:54 Other tools call them agents 18:37:55 Dunno, “slave” term appears throughout documentation and UI. 18:37:56 So that's another option 18:37:57 kohsuke so then there's node-to-master access control? huh? 18:38:11 Changing the basic term now seems ill advised. 18:38:36 jglick: It wouldn't take that much work to change "slave" from "node" on Jenkins' wiki I don't think. 18:38:39 jglick: you have proper American sensibilities! 18:38:51 “Dumb” was never a useful adjective in this context, though. “Static” or “permanent” or “manual” etc. would be more helpful. 18:39:24 jglick: yeah, but i don't think the submitter of that issue likes "slave" either. 18:40:25 I just don't want to see HN/reddit thead like "Jenkins developers insists of using racial terms" 18:40:41 Guaranteed frontpage hitter with charged comments from both sides 18:41:03 yeah, that would really suck to have to deal with that crap. 18:41:28 leader/follower 18:41:41 jglick: you can correct me, but my impression of US of A is that you don't want to be seen defending those things 18:41:53 It's worse with the 'dumb' anthropomorphizing the term, but it seems Django blew up without that anyway 18:41:57 lol, "US of A" :D 18:42:05 I think there is precedent for using “slave” in a purely technical sense. http://en.wikipedia.org/wiki/Master_cylinder for example. 18:42:42 Yeah, I was thinking about master/slave disks in IDE interfaces 18:42:56 "Is it at all ironic that this got merged into master ?" 18:42:58 jglick: I still think we should change "slave" to "node", and change "dumb" to "standalone" or "build" like I mentioned earlier. 18:43:29 however jglick, "static" seems like another good one. 18:43:32 master is also a 'node', so that doesn't help 18:43:38 -0 on using “node” which also encompasses the master. 18:43:54 "static build agent"? 18:43:54 “Slave” is the only term which unambiguously excludes the master node. 18:44:02 kohsuke: yeah, i like that 18:44:20 kohsuke master and agents? 18:44:49 yeah, I'm too lazy to change that. I don't think people would be complaining about master 18:44:54 Does Jenkins support junitparams ? 18:45:06 microm Meeting right now, please ask later. 18:45:26 http://en.wikipedia.org/wiki/Master/slave_%28technology%29 generally 18:45:42 kohsuke: How many files would one need to edit in order to change slave to agent? 18:45:50 jglick "Due to the controversy, the term was selected as the most politically incorrect word in 2004 by Global Language Monitor" 18:45:50 So as long as we do not sell products in LA we are fine! 18:46:12 Oh, Drupal was also changed 18:46:26 I'm trying to see if I can get at least -0 from jglick about "static build agent" 18:46:43 i'll do a search through the Jenkins repo, see how many source files refers to "slave", since GitHub has that ability 18:46:49 I don't want to waste too much on this 18:46:59 Kamran We cannot change classes due to plugin compatibility 18:47:04 oh 18:47:05 dang 18:47:15 Will possibly confuse existing Jenkins users. New users probably would not notice, though the continued use of the term “master” is then just weird. 18:47:17 (which adds an unfortunately layer of terminology confusion for any devs) 18:48:03 jglick: Master could possibly be called "Master build agent", but that would require changing the classes. 18:48:07 as we cannot just get rid of it cleanly 18:48:21 I wonder whether consistent use of "slave node" would be sufficinet 18:48:24 I think existing users will understand what they mean, especially because they see it in the place where they used to see "dumb slave" 18:49:40 kohsuke: yeah. 18:49:42 danielbeck: not if I'm reading JENKINS-27268 right 18:49:44 JENKINS-27268:"dumb" slave? (Open) https://issues.jenkins-ci.org/browse/JENKINS-27268 18:50:41 lets get rid of "dumb" part and see if the requestor is satisfied 18:50:59 kohsuke Given how extensively 'slave' is used it going to be really difficult 18:51:02 "I just don't want to see HN/reddit thead like "Jenkins developers insists of using racial terms" i would be really surprised if the change(if it will be performed) doesn't hit the reddit . Don't do changes because of shitstorm blackmailing please, do it because they are reasonable. if they are. 18:51:27 I mean, agent.jar alone is going to be fun 18:51:36 ogondza: That wouldn't require modifying classes right? Because that would break plugin compatability, like kohsuke just mentioned a few minutes ago. 18:51:49 *changing 18:51:57 -1 on changes to filenames. Much too risky. 18:52:15 I have never considered actually renaming classes, only UI labels 18:52:24 jglick "Want to connect your machine as an agent? Run slave.jar" o_O 18:52:40 I think this is one of the rare moments in which I wave the BDFL flag 18:52:51 BDFL flag? 18:53:00 Benevolent Dictator For Life 18:53:12 Oh, lol. 18:53:18 Basically "let's not argue, please let me have it my way" plea 18:53:21 For "Copy artifacts from another project", do I have to specify project name? Or can it be any upstream project? 18:53:29 sjmikem Meeting right now, please wait a bit 18:53:40 I think we are all on the same page about not upsetting the compatibility requirements 18:53:54 So I feel comfortable getting the changes mostly right 18:54:00 user confusion! 18:54:13 That's mangeable. 18:54:54 kohsuke: We might be able to just change the UI labels, but if we were to get rid of "dumb" what would we rename that to in the UI? 18:55:04 Can we move on? 18:55:15 yes 18:55:17 I feel like we can keep talking about this forever, and there's really more important things 18:55:19 FWIW I'm french and I never had an issue with this. Though I see some ppl in other parts of the world that may see those words carrying strong meaning... 18:55:28 kohsuke: yes, agreed. 18:55:35 #topic Bug bounties/rewards for security issues 18:55:54 A reporter of a security issue brought this up 18:56:12 Basically asking for a reward of some kind 18:56:23 our pockets aren't deep enough to offer anything significant, but I thought perhaps some token gifts would be doable 18:56:44 kohsuke: agreed 18:56:45 we don't have money, but something like a mug or t-shirt maybe? 18:57:05 Ooh, I like the mugs idea Daniel. 18:57:06 Right, maybe a gift card for cafepress.com/jenkinsci 18:57:35 something easy administration wise would be nice, too 18:57:42 something that can be sent over email 18:57:46 yeah 18:58:01 kohsuke Would it be feasible to have exclusive designs? 18:58:24 we need to find someone who can do the artwork 18:59:04 yeah 18:59:04 I can ask to some CB folks, but I've always felt their illustrator creates pictures that feel different 18:59:17 see http://jenkins-ci.org/content/jenkins-100k-celebration-pictures 18:59:20 JENKINS-100:tag this build icon has bad name (Closed) https://issues.jenkins-ci.org/browse/JENKINS-100 19:00:04 shapeway $25 gift card can do for https://www.shapeways.com/model/upload-and-buy/2183445 19:00:04 http://blog.cloudbees.com/2015/01/breakingbuilds-twitter-contest-results.html 19:00:29 (off-topic) odd, i just noticed, jenkins-admin doesn't have the ability to connect to IRC using SSL. 19:00:49 kohsuke non-public link 19:00:55 oh 19:01:20 https://www.shapeways.com/product/NZAN5AGUS/mr-jenkins-v2 19:01:52 Hmm, those look nice, I quite like the 4th one actually 19:02:04 oh wait, you made those 19:02:05 :D 19:02:05 The other part of the program is to limit this to one per person 19:02:11 kohsuke Definitely. 19:02:12 Sorry, danielbeck & jglick you'll only get one 19:02:41 I would just say to disqualify committers. 19:03:01 (Or their families!) 19:03:04 jglick: Why? 19:03:16 Kamran It costs money. 19:03:34 I'm afraid I'm running out of time today 19:03:37 danielbeck: Yeah, true 19:03:39 I want to hear from hare_brain on this one 19:03:43 It is just part of our job. Anyway what if I tried to illicitly build my coffee mug collection by *introducing* vulnerabilities and then reporting them? 19:04:05 kohsuke I think mug/shirt, possibly with exclusive design (if it's just the Jenkins logo + "security team" below, doesn't have to be super elaborate IMO) would be fine. 19:04:07 #chair danielbeck jglick 19:04:07 Current chairs: danielbeck jglick kohsuke 19:04:21 OK, I'll ask CB folks to see if they can do an artwork 19:04:23 I’m sorry. 19:04:29 I’ve been in meetings and not paying attention. 19:04:32 #chair hare_brain 19:04:32 Current chairs: danielbeck hare_brain jglick kohsuke 19:04:46 I need to run now, I'm really sorry 19:04:59 hare_brain: bounty / thank you gift for security vulnerabilities 19:05:05 hare_brain Can we afford t-shirts or mugs for security issue reporters as a token gift? 19:05:31 Seems like we should be able to. 19:05:49 We’re not getting these reports every day are we 19:06:17 kohsuke: Would you please be able to take a look at my ICLA before you run off? 19:06:30 Fairly few, and most are from regular devs, see the recent advisories 19:07:46 So can we agree on (a) token non-cash gifts, (b) not for committers, (c) accepted (or fixed?) issues only? 19:08:08 d) no repeats 19:08:28 +1 19:08:41 Published fixes should be fine 19:08:54 e) must be exploitable, no hardening 19:09:32 agreed 19:09:46 #agreed non-cash gifts to be provided to reporters of SECURITY issues if and when the issue is accepted as a vulnerability (not merely security hardening) and a fix published. Maximum one gift per reporter and Jenkins committers are excluded. 19:10:30 great 19:10:34 Whether we retroactively offer gifts to historical reporters is another question I would leave for now unless anyone feels strongly. 19:11:09 let's move on 19:11:13 agreed 19:11:23 danielbeck do you want to take the other agenda items? Most are from you. 19:11:45 #topic Resurrecting the MEETING Jira project (maybe even have the bot create issues for action items automatically) 19:12:15 Just as kohsuke discovered a few minutes ago, this Jira project is basically dead 19:12:40 I think it would be a great tool for tracking meeting action items, if we can manage to have the bot create issues 19:12:48 or we just shut it down. 19:13:08 any opinions on this? 19:13:16 Never heard of it before. 19:13:21 https://issues.jenkins-ci.org/browse/MEETING 19:13:46 #info https://issues.jenkins-ci.org/browse/MEETING 19:14:12 No opinion from me. 19:14:13 Maybe we could try figuring out how to make the bot create issues? 19:14:48 May be tricky since in general IRC nick != jenkins-ci.org username. 19:15:01 jglick: yeah, true. 19:15:50 danielbeck: What's your opinion on this? 19:15:59 I don't know where the bot source is, unfortunately. 19:16:11 I'd love to get MEETING revived 19:16:15 danielbeck: https://github.com/jenkins-infra/ircbot 19:16:33 I've forgotten probably half the action items assigned to me 19:16:40 Proper tracking would be great 19:16:45 That's the bot source, daniel. 19:16:57 Kamran Isn't that jenkins-admin? This is about robobutler 19:17:01 no 19:17:03 *oh 19:17:15 you guys have two bots in here, totally forgot about that 19:17:24 there's also jenkins-builds 19:17:40 So yeah, not something we can manage without input from kohsuke I'm afraif 19:17:50 Project jenkins_main_trunk build #4061: SUCCESS in 58 min: http://ci.jenkins-ci.org/job/jenkins_main_trunk/4061/ 19:17:50 Jesse Glick: [JENKINS-27700] Noting that JENKINS-27565 changed settings format. 19:17:53 JENKINS-27700:Node configuration missing after downgrading from 1.607 to 1.606 (Resolved) https://issues.jenkins-ci.org/browse/JENKINS-27700 19:17:55 JENKINS-27565:Nodes can be removed as idle before the assigned tasks have started (Resolved) https://issues.jenkins-ci.org/browse/JENKINS-27565 19:18:05 so I think we should just move on 19:18:10 Alright. 19:18:10 and postpone this 19:18:47 uh, danielbeck: https://github.com/jenkins-infra/robobutler 19:19:03 Kamran Nice 19:19:16 :D 19:19:51 still, doesn't look like there's a lot of interest in this topic? 19:20:35 I still think we could at least try and figure out how to make the bot create issues, but not sure how much work that would take, however, I do have an IRC bot coded in python as well, which is what robobutler is coded in 19:20:35 cccccceefndcngbdvrbjrkvgkjjbfdfdherdcjhbfnkg 19:20:47 ops sorry 19:21:01 schristou: were you sleeping on your keyboard? :D 19:21:05 Kamran Could you maybe take a shot to see whether this would be feasible? 19:21:28 Kamran: SHH! ;) 19:22:11 danielbeck: I'll give it a shot. :D 19:23:00 #action Kamran to look into adding MEETING issue creation to robobutler 19:23:06 great! 19:23:09 :) 19:23:29 #topic The important content of the Wiki is difficult to find (between outdated or even empty pages), and there's no real introduction to Jenkins – What can we do about it? 19:23:41 This also includes the web site. 19:24:06 It seems to be unnecessarily difficult to find anything in the wiki 19:24:36 Even the wiki home page is outdated and borderline wrong 19:24:59 https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins 19:25:16 (kinda un-related, but kinda related) Maybe updating the atlassian software (Confluence, JIRA, etc) might make the wiki easier to navigate? Because right now, the Jenkins Wiki is stuck at Confluence version 3.4.7, which is really out of date now. Same applies to JIRA as well. 19:25:30 The second most important function of Jenkins is 'monitor external job' 19:26:21 so I'd really like to clean and/or restructure up the wiki, or anything else that makes the important bits easier to find 19:27:24 maybe having a wiki isn't the best approach to begin with, and something more like a knowledge base site with specific questions/answers might work better for some of the content? 19:27:36 I agree, though have no idea where to start or a vision of the future 19:27:47 danielbeck: I think we should keep the wiki. 19:28:06 Because to be honest, I find wikis to be easier to navigate than knowledge bases. 19:28:57 If you were to restructure the wiki, would you want to move it to GitHub wiki? 19:29:02 Kamran To clarify, 'having _only_ a wiki' 19:29:17 hare_brain That's per repo, right? 19:29:21 danielbeck: yes. 19:29:37 each github wiki is per repository. 19:29:39 that makes as little sense for Jenkins as per-repo issue trackers. 19:29:45 yeah 19:30:02 However, the Jenkins wiki being stuck at Confluence 3.4.7 is kind of a bad thing, especially since that's a really old version. 19:30:45 Kamran I think an update is planned 19:31:00 Really? :D 19:31:16 danielbeck: I am afraid that using knowledgebase would suffer from outdated content as well 19:31:19 But I doubt the wiki version will help a lot with making the content more accessible 19:32:38 danielbeck: It might actually, because Confluence was given a revamp in version 5.x. 19:32:55 and that revamp made Confluence a lot easier to navigate 19:33:02 Maybe we should link more prominently to http://stackoverflow.com/questions/tagged/jenkins ? 19:33:10 in my opinion, anyway 19:33:16 ogondza It would help if we could have a better overview of the content we have, so if something changes, we can actually find the wiki pages to change 19:33:54 jglick Looks more like a mailing list alternative to be honest 19:34:24 danielbeck: the images on the wiki also need to be updated, such as wiki pages with Jenkins screenshots 19:34:25 Well you talked about a “knowledge base” and that is what I think of as the modern version of KBs. 19:34:58 right 19:35:36 As I wrote, for some of the content 19:36:00 that would allow us to focus the wiki more on general documentation 19:36:14 danielbeck: yeah 19:37:24 Should we continue this to the dev list to get more ideas? 19:37:32 *on 19:37:42 +1 19:37:47 danielbeck: yeah 19:37:50 *sure 19:38:33 #action danielbeck to ask for ideas on improving the documentation on the dev list 19:38:49 shall we move on? 19:38:50 :D 19:39:09 #topic Proposal: move Jenkins official image repo to jenkinsci org so enhancement / version updates can be managed by the community 19:39:23 ndeloof isn't here 19:39:25 +1 19:39:37 jglick Can you contact him? 19:39:52 danielbeck: he said he could not make the meeting. 19:40:01 But I think he is not necessary for the topic. 19:40:08 Seems like a reasonable proposal to me. 19:40:18 Yeah, i agree with jglick. 19:40:18 Right now there are several open issues and PRs. 19:40:38 I think it is just for historical reasons that it landed in @cloudbees. 19:40:55 #info https://github.com/cloudbees/jenkins-ci.org-docker 19:41:01 jglick: Doesn't all issues & PRs stay in the repo even when you move it to an organization? 19:41:17 Yes, if you *move* rather than clone. 19:42:07 Should the repo be renamed as well, or is this an established docker naming convention? 19:42:23 From the name it looks more like part of jenkins-infra to me 19:42:23 Not sure if there is any particular convention. 19:42:49 Is that a GH org? 19:42:55 jglick: yes 19:43:04 https://github.com/jenkins-infra 19:43:16 dang it, you beat me to it 19:43:44 Not sure. This is not part of jenkins-ci.org. 19:43:49 That is, the site. 19:43:50 jglick Would be wrong in jenkins-infra, but that's why I wrote that the name confuses. Looks like the docker container driving www.jenkins-ci.org 19:44:15