Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1925

Create a java11-support team in the jenkins-infra GitHub org and grant jenkins.io permissions

    Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: github
    • Labels:
      None
    • Similar Issues:

      Description

      Over the next weeks we will be doing a lot of infra and website patches to enable Java 11 support in Jenkins according to https://github.com/jenkinsci/jep/tree/master/jep/211

      In order to simplify the review/delivery process, I propose the following:

      • Create a new java11-support team in jenkins-infra
      • Copy the list of the members from https://github.com/orgs/jenkinsci/teams/java11-support 
      • Grant the java11-support team READ permissions in jenkins.io and update center so that the team reviews can be requested there
      • Grant Mark Waite and Baptiste Mathus write permissions on jenkins.io so that they can merge changes in the Java 11 scope if needed (docs, etc.). Both of them are long-term contributors with signed CLAs, and they can help with landing changes without overloading copy-editors 

       

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          Have you considered using the wiki to deliver frequently updated, quickly outdated information?

          Show
          danielbeck Daniel Beck added a comment - Have you considered using the wiki to deliver frequently updated, quickly outdated information?
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Daniel Beck we will be using Wiki for some content like developer guidelines and Known issues, but we will be also managing Java 11 support policies on Jenkins.io (https://jenkins.io/doc/administration/requirements/java/), writing blogposts and requesting reviews & Co.

           

           

          Show
          oleg_nenashev Oleg Nenashev added a comment - Daniel Beck we will be using Wiki for some content like developer guidelines and Known issues, but we will be also managing Java 11 support policies on Jenkins.io ( https://jenkins.io/doc/administration/requirements/java/ ), writing blogposts and requesting reviews & Co.    
          Hide
          olblak Olivier Vernin added a comment -

          Hi,
          Considering how teams works on Github, I created three 'teams', one parent team with only maintainers in order to allow them to manage child teams.

          .1 java11-support which act as the "parent" team with @batmat @oleg as maintainers and no repository permission. Those maintainers are allow to invite members in 'java11-support' and child teams.

          .2 java11-support-reviewer, which inherit his parent repository permission and has 'read' permission on jenkins-infra/jenkins.io and jenkins-infra/update-center2

          ! Short reminder that read permission is not enough to provide mergeable reviews.

          .3 java11-support-maintainer, which also inherit his parent repository permission and has 'write' permission on jenkins-infra/jenkins.io and jenkins-infra/update-center2

          I had to create 'java11-support-maintainer' because child team inherit their parent permission and child team can only be configured to have more permission than the parent team. In other word, if the parent has write permission, all child have at least write permission.

          The purpose of this is to delegate user management permission for several repository to key contributors without giving access to the all organization.

          Ideally I think that the 'parent' team should be named based on the sig-group where the maintainer is the sig group maintainer but I should introduce this on a JEP.

          Show
          olblak Olivier Vernin added a comment - Hi, Considering how teams works on Github, I created three 'teams', one parent team with only maintainers in order to allow them to manage child teams. .1 java11-support which act as the "parent" team with @batmat @oleg as maintainers and no repository permission. Those maintainers are allow to invite members in 'java11-support' and child teams. .2 java11-support-reviewer, which inherit his parent repository permission and has 'read' permission on jenkins-infra/jenkins.io and jenkins-infra/update-center2 ! Short reminder that read permission is not enough to provide mergeable reviews. .3 java11-support-maintainer, which also inherit his parent repository permission and has 'write' permission on jenkins-infra/jenkins.io and jenkins-infra/update-center2 I had to create 'java11-support-maintainer' because child team inherit their parent permission and child team can only be configured to have more permission than the parent team. In other word, if the parent has write permission, all child have at least write permission. The purpose of this is to delegate user management permission for several repository to key contributors without giving access to the all organization. Ideally I think that the 'parent' team should be named based on the sig-group where the maintainer is the sig group maintainer but I should introduce this on a JEP.

            People

            • Assignee:
              olblak Olivier Vernin
              Reporter:
              oleg_nenashev Oleg Nenashev
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: