https://github.com/jenkins-infra/jenkins.io/pull/3012 is the pull request that tires to describe labeling.
On Fri, Mar 27, 2020 at 10:55 AM Mark Waite <[email protected]> wrote: > We discussed today in the Jenkins Documentation Special Interest Group and > came to the agreement that I will submit a pull request to the Jenkins > plugin developer documentation that: > > - Encourages developers to apply GitHub topics to plugins they maintain > - Note that topics which match the whitelist will be displayed on > plugins.jenkins.io > - Suggests that topics should be assigned to a plugin when the plugin > relationship to the label is well above average > - Invites pull requests to recommend additions to the label whitelist > - Encourage developers to ask avoid applying labels which are so broad > that they lose value because of overuse. For example, the labels "Jenkins" > and "plugin" are not helpful because they apply almost everywhere > > Pull request should arrive later today > > On Tuesday, March 10, 2020 at 12:40:00 PM UTC-6, Mark Waite wrote: >> >> >> >> On Tuesday, March 10, 2020 at 3:21:34 AM UTC-6, James Nord wrote: >>> >>> > Skip labels provided by parents - When a plugin depends on another >>> plugin, the dependency will be installed automatically. A label is not >>> required on the dependency if the consuming plugin has the label >>> >>> but if the parent can be used without the child (extension) then how >>> does that parent get found in isolation. The only case of not labelling the >>> parent is when it provides no user feature in my opinion (eg it's a pure >>> api plugin) >>> >> >> What I was envisioning was: >> >> Bitbucket Branch Source plugin depends on git plugin. Bitbucket Branch >> Source plugin would be labeled 'bitbucket'. Git plugin would not be >> labeled 'bitbucket' because it will be installed automatically when >> Bitbucket Branch Source is installed. >> >> Git plugin depends on git client plugin. Git plugin would be labeled >> 'git'. Git client plugin would not be labeled 'git' because it will be >> installed automatically when Git plugin is installed. Git client plugin is >> an example of a pure API plugin and would have very few labels. >> >> I think the Bitbucket Branch Source -> Git plugin case is an example of >> your concern for locating a plugin in isolation. In that case, a search >> for the 'bitbucket' label will not show the git plugin. I was assuming >> that a Bitbucket user will prefer to install one of the higher level >> integrations (Bitbucket plugin, Bitbucket Branch Source plugin, Bitbucket >> Pullrequest BUilder, Bitbucket Server Notifier, etc.) and will receive the >> git plugin and the git client plugin as dependencies because they chose one >> or more of the higher level integration plugins. >> >> Did I understand your concern? >> >> -- > 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/a4bee5a1-5fcc-4fbe-a8e6-bf8e27257328%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a4bee5a1-5fcc-4fbe-a8e6-bf8e27257328%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAO49JtFbmSZw_PduNyD0MP1WEvWDE5U%3DwC82a9nnL9fCozCC4w%40mail.gmail.com.
