I am happy that we start this discussion early enough before the current Jira version becomes at the end of life. It's a topic important enough to have as much feedback as possible but also whatever we decide we won't have support from 100% of the contributors otherwise we wouldn't have this long thread.
Whatever we decide, I think we should try to apply the same process for all the tickets. If someone is interested to help to work on a JEP to summarize all the pros/cons here and identify possible solutions, that would be awesome and then I suggest that once done, we organize a vote using the Condorcet <https://civs.cs.cornell.edu/> tool. --- gpg --keyserver keys.gnupg.net --recv-key 52210D3D --- On Tue, Feb 11, 2020, at 8:11 AM, Tim Jacomb wrote: > I feel like we can work something out for the security project, possibly > there’s a better tool for it... > > I don’t think it’ll work easily in the cloud version either > > For transferring you need at least write and possibly admin on both ends to > use the GitHub ui for it, but there’s a GitHub app for it that looks like it > would do what we need: > https://github.com/apps/move > > Not sure how infra having secrets makes it a better fit for jira? > > On Tue, 11 Feb 2020 at 00:57, 'Gavin Mogan' via Jenkins Developers > <jenkinsci-dev@googlegroups.com> wrote: >> I'll freely admit I dislike jira, but I think the mix for plugins of using >> jira and github are very confusing. >> >> I see a major issue, that security issues can't really work in github, since >> they can't be made private for certain people, which means if you'd have >> issues for a plugin in both github and jira its a big mess. And I believe >> only github org admins (or at least someone with write support in both >> repos) can move issues between repos. Which will make issues getting lost >> due to the wrong component even worse. >> >> I'm all in favor of non core and non plugins using github to make things >> more visible, but not for the central project. >> >> And infra has a lot more secrets, so it makes sense to be in jira where >> things can be managed. >> >> I'm totally in favor of moving to cloud jira instead of hosted jira to >> reduce maintenance, but that requires a lot of work too. >> >> >> >> On Mon, Feb 10, 2020 at 5:44 AM Daniel Beck <m...@beckweb.net> wrote: >>> >>> >>> > On 2. Feb 2020, at 12:13, Tim Jacomb <timjaco...@gmail.com> wrote: >>> > >>> > GitHub issues use is growing in the ecosystem, many plugins are now >>> using it, >>> >>> Given the discussion, I now seriously doubt that this would be beneficial >>> over the long-term to the project. >>> >>> Not because the proposal is a bad idea on its own (it's not), but based on >>> the answers so far, it looks to me like some want Jira gone completely, and >>> want to use this proposal as a back door to get rid of issues.j.o without >>> an adequate replacement in the name of "unifying" where issues are tracked. >>> This isn't even perhaps an individual contributor's position, but between >>> "I want GH issues / I don't want Jira" and "Multiple issue trackers are >>> bad", this is where we seem to be heading. >>> >>> If we go with this approach and similar ones (for example the better >>> plugin metadata that allows having an issue tracker link directly in >>> Jenkins plugin manager), we need to be committed to continue having >>> different issue trackers for a while. Making it easier for users who >>> maintainers want to use GH issues shouldn't mean we'll ignore others' >>> preference for Jira. >>> >>> And if Jira presents significant challenges e.g. to the infra team, which >>> it looks like, I'd be happy to have a separate, open discussion about the >>> continued use of Jira. I resist not because I love it so much (I don't), >>> but because I use it a lot and I simply don't see how my use cases >>> translate elsewhere (GH issues and to a degree Jira Cloud) -- some of which >>> are pretty core to my role as security officer (for example the case from >>> my email from yesterday). But that conversation should be based on a >>> properly defined IEP/JEP looking at all aspects of such a transition, >>> rather than a disjointed set of messages across several channels/threads. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to jenkinsci-dev+unsubscr...@googlegroups.com >>> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/9BEC892B-EB0F-430C-BD1B-790DDBA6C1D5%40beckweb.net. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutrL%3D1wKeVhRNATGL_37OSHEfn8aw2hWJoc2dPsW3SQaA%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutrL%3D1wKeVhRNATGL_37OSHEfn8aw2hWJoc2dPsW3SQaA%40mail.gmail.com?utm_medium=email&utm_source=footer>. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicbvO%3DJdC6bOKTMasd--b6X0EkFQt-ss1HSmH9wx1eMsg%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicbvO%3DJdC6bOKTMasd--b6X0EkFQt-ss1HSmH9wx1eMsg%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e8087e4e-2f6f-4997-b650-597cf565b1ce%40www.fastmail.com.
