On Fri, Feb 14, 2020 at 4:59 PM Jesse Glick <jgl...@cloudbees.com> wrote:
> > Right. It would be great to switch to GitHub SSO, avoiding the > confusion between oleg-nenashev vs. oleg_nenashev and so on, and > ending a bunch of issues such as old email aliases. JIRA and > Artifactory would need to support this connector. (So few people have > special permissions on ci.jenkins.io that this seems like a minor > issue.) “Mapping” would boil down to ensuring that any active > maintainers have gone to https://accounts.jenkins.io/myself/ to set > their GitHub ID prior to the switchover. That is neither complete (as it requires user action), nor a tamper-proof (AFAIR, nothing ensures you're not lying, or even have a typo). We regularly contact maintainers who haven't released anything in more than a year or two about security issues. So this mapping would _at least_ have to be enforced 1-2 years before we switch over to a Jira alternative. -- 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/CAMo7PtK5y_dKmLpwT9Ud3NXFtrm0XcDbKg%3Dfo78wu6qR0vgYYQ%40mail.gmail.com.
