+1 to this idea and initial maintainers. This would go a long way toward unblocking changes in this area! :)
On Tue, Dec 10, 2019 at 7:42 AM Marky Jackson <[email protected]> wrote: > > I have not been as active as I would like but I would also like to be a > maintainer based on our previous conversation > > On Dec 10, 2019, at 3:34 AM, Oleg Nenashev <[email protected]> wrote: > > > BTW, I suggest the following list of maintainers based on the recent activity: > > Mark Waite > Alex Earl > Carlos Sanchez > Oleg Nenashev > Baptiste Mathus > Olivier Vernin > > Alternative is to just keep all members of > https://github.com/orgs/jenkinsci/teams/docker/members though some > contributors are not active at the moment > > BR, Oleg > > On Tuesday, December 10, 2019 at 11:42:49 AM UTC+1, Mark Waite wrote: >> >> I would like that very much >> >> On Tue, Dec 10, 2019, 11:19 AM Oleg Nenashev <[email protected]> wrote: >>> >>> Hi all, >>> >>> Right now we have a number of official packages for Docker: >>> >>> https://github.com/jenkinsci/docker >>> https://github.com/jenkinsci/docker-slave >>> https://github.com/jenkinsci/docker-ssh-slave >>> https://github.com/jenkinsci/docker-jnlp-slave >>> https://github.com/jenkinsci/jnlp-agents >>> >>> All these repositories have different teams which define permissions/. In >>> addition to that we have jenkinsci/docker and >>> jenkinsci/docker-packaging-team team which also grant permissions. It is >>> quite difficult to manage the repositories in the current state, and it is >>> difficult to request reviews. >>> >>> I suggest to keep things simple and just proceed with a single team for the >>> official packaging: >>> >>> Introduce an official "docker-packaging-team" under umbrella of Platform >>> Special Interest group which currently manages Docker packaging >>> Cleanup existing teams, leave just one for all official Jenkins master and >>> agent mages. Plugin Docker packaging (e.g. Remoting over Apache Kafka, >>> Swarm plugin) will not be affected >>> Update GitHub and DockerHub teams to reflect the changes (mostly >>> jenkins4eval which grants write permissions) >>> Add new team to CODEOWNERS in all repos >>> >>> WDYT? >>> >>> Thanks in advance, >>> Oleg >>> >>> -- >>> 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/CAPfivLCPBvAvsqC4nqpr2e%2BqBOo2BdMqa%3DY5%3Dx%2BhVO735YzX_w%40mail.gmail.com. > > -- > 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/d333d077-28bb-431f-9f5a-950440970429%40googlegroups.com. > > -- > 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/11566D48-9955-40F5-B5EA-75CAEB228589%40gmail.com. -- Matt Sicker Senior Software Engineer, CloudBees -- 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/CAEot4oxKYCkyCgnqxkxR0A%2BaDk%3Dbj0krcd-xAteAE-r1z-QK%3Dg%40mail.gmail.com.
