> On 28. Aug 2018, at 11:00, Robert Sandell <[email protected]> wrote: > > I don't think jenkins-infra/repository-permissions-updater should be the > starting point. It's hard to find and harder to remember,
It will necessarily be linked from anywhere documenting the adoption process. If your experience is that remembering the name to get there directly via browser history is difficult -- that won't be what potential new contributors will be doing. They will click a link in docs. > And once found it's hard to find stuff in it. Web based? Go to the repo root page, press 't', then enter the artifactId of whatever you want to see. > And the couple of times that I've done changes in there it takes me a while > to figure out if I have messed something up or not before filing the PR. Perhaps we can make the upload permissions definition more approachable, but this repo is inherently part of the maintainership transfer already today. It's not like this part of the process would be skipped by going through Jira. In fact, as I write, it's basically the only thing that's actually required (for example when former and future maintainer already discussed things already in private email -- it has happened before). -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/A2472755-A268-4385-8841-D6D9236BDCAB%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
