Re: Request to adopt label-linked-jobs-plugin

In general you don't need community involvement unless the original author has abandoned it and isn't available. If they want you to co maintain or fully take over they can do so via GitHub and approve a pr in the permissions repo. Gavin On Wed., Dec. 9, 2020, 11:11 p.m. Rick, wrote: > Hi

Request to adopt label-linked-jobs-plugin

Hi team, I'd like to adopt label-linked-jobs-plugin . I'm a maintainer of serval Jenkins plugins. According to the current maintainer of label-linked-jobs-plugin. He has not worked on this plugin for a few years. And he wishes this plugin

Re: Jenkins ebook #1

my apologies for not being clear. My ask - on page 2, at the end of the letter where we currently have "The Jenkins Project" we would like the names of the governance board members below this line. As though this letter is from the governance board. Hope that helps. On Tue, Dec 8, 2020 at 3:18

Re: Jenkins Operator managed service name (sublicensing)

Hi Pawel, We had a conversation at the Jenkins Governance meeting last week, and the consensus was that we are not ready to vote. Our consensus was that "VirtusLab Operator Service for Jenkins" or similar names represent a pretty much automatic approval while VirtusLab Jenkins Operator