Let's bring back the infrastructure point of view into the discussion Jira to Jira Cloud INFRA-2010 <https://issues.jenkins-ci.org/browse/INFRA-2010> If someone is willing to do more experimentation with it, be my guest but for what I understand contributors require an Atlassian account to connect on Jira cloud so no GitHub SSO, neither LDAP auth and max 5000 users, which also means regular old accounts and spammers cleanup. For the context, today we have 104626 accounts on Jira -> In the current state, because of the identity management, I am not very optimistic about migrating all projects to Jira cloud,
Remaining on issues.jenkins-ci.orb, [INFRA-2262 <https://issues.jenkins-ci.org/browse/INFRA-2262>], No integration between Jira and Github as it uses Github API and we hit the limit very quickly so we had to disable it The second element, excepted Tyler and me, nobody "maintains" it and unfortunately, we can only accept trusted people to work on issues.jenkins-ci.org as it contains the security work. so I don't see how we can keep maintaining it unless we have someone dedicated to Jira who upgrade Jira every several weeks and also work on performance -> In the current state, because of the maintaining effort, I am seriously not optimistic to stay on issues.jenkins-ci.org Moving to GitHub issues Identity management and maintaining effort is solved, but some extra work is needed to migrate Jira tickets to Github issues. And personally I am a bit concerned about managing the all Jenkins project on GitHub for multiple reasons but they are largely compensated by not having to maintain a ticketing system. I also think that another concern that I have is because I am not as experienced as I am with Jira which is why I am willing to give it a try for a small project like the hosting project. but if we do that, we need to be clear on an end date for the experimentation. Maybe someone has another proposition like neither Github or Jira Cheers --- gpg --keyserver keys.gnupg.net --recv-key 52210D3D --- On Sun, Feb 9, 2020, at 6:24 PM, Daniel Beck wrote: > > > > On 9. Feb 2020, at 00:53, Chris Kilding <chris+jenk...@chriskilding.com> > > wrote: > > > > there seems to be common ground on solving the *access* problem for users > > that report issues. > > > > If we can get a GitHub connector up and running for Jira, so that any user > > who wants to report an issue can simply sign in with the GitHub account > > that they (in all likelihood) have already got, we can solve the access > > problem and lower the barrier to entry for reporters. > > > > I don’t know the split between how many reporters we lose because they > > can’t (or won’t) make a Jira account vs. how many we lose because they > > can’t navigate Jira once they’re in. But it would be a start. > > So far I've never felt like we needed more bugs reported, or features > requested. We collectively suck at responding and fixing anyway. What's > the point of making it easier to have one's issue ignored? > > (To be clear: This is not a good situation. But it seems we should fix > _that_ first.) > > Also, I haven't seen any proof so far for the assumption that everyone > has a GitHub account anyway. That seems like a very OSS developer > centric view of the world. > > -- > 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/1BD227AC-FDF8-4FAC-ACE8-D8F92CF806AF%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/10a48587-a3c0-48f7-a0d5-f76cd5495a9b%40www.fastmail.com.
