My PR will pull any github labels it has access to, then merge in the wiki
ones (from the
https://github.com/jenkins-infra/update-center2/blob/master/src/main/resources/label-definitions.properties
i believe), then filter them through the whitelist we setup.

So i think merging is taken care of, its just eventually deprecating
wiki/label-definitions.

Next steps could easily be writing a bot that adds all the existing labels
to github

On Mon, Nov 25, 2019 at 1:04 AM Oleg Nenashev <[email protected]>
wrote:

> Update here. After
> https://github.com/jenkins-infra/update-center2/pull/316 by Gavin Mogan I
> think it makes sense to permit using the `adopt-this-plugin` label like in
> Wiki.
> Later we can add some logic to support merging the labels
>
> BR, Oleg
>
>
> On Monday, November 11, 2019 at 4:33:28 PM UTC+1, Oleg Nenashev wrote:
>>
>> First pull request which moves the guidelines without updating them too
>> much
>> https://github.com/jenkins-infra/jenkins.io/pull/2635
>>
>>
>> On Monday, November 11, 2019 at 3:41:55 PM UTC+1, Tim Jacomb wrote:
>>>
>>> +1
>>>
>>> On Mon, 11 Nov 2019 at 14:23, Oleg Nenashev <[email protected]> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Currently the Adoption labels are on Wiki, and hence it is no longer a
>>>> way to mark plugins for adoption or unmark them for common contributors. I
>>>> suggest moving the process to GitHub and to use a more-or-less common
>>>> "adopt-me" GitHub topic.
>>>> Suggested changes:
>>>>
>>>>    - "adopt-me" label is added to plugins which are currently marked
>>>>    for adoption
>>>>       - As a bonus, only people with Write permissions in a repo will
>>>>       be able to mark plugins for adoption
>>>>    - https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin is moved
>>>>    to GitHub. There are pending JEPs to change the process, but we can 
>>>> move it
>>>>    as is for now
>>>>    - "*This plugin is up for adoption.* "  is removed from Jenkins
>>>>    from Jenkins Wiki macros. Later we can add an integration with GitHub
>>>>    topics to the plugin site (
>>>>    https://issues.jenkins-ci.org/browse/INFRA-2240)
>>>>
>>>> Would everyone be fine with such suggestion?
>>>>
>>>> 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/a7ec8008-c0e2-45c3-87e4-932df3af28ba%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/a7ec8008-c0e2-45c3-87e4-932df3af28ba%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/8a5550bd-8006-4ab5-b076-3072da309ccc%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/8a5550bd-8006-4ab5-b076-3072da309ccc%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/CAG%3D_DuuYRCv8VLiJ1nQFZRLggxdXqHNyttGassyQ%2BUWNiWqwSw%40mail.gmail.com.

Reply via email to