On Thursday, September 1, 2022 at 2:57:57 PM UTC-6 Bart wrote:
> Hi,
>
> >> My intention with adopting this plugin is more for the preparation of
> DevOps world than anything else.
> >> I am not a proper developer in this scenario, but am trying to go
> through the process of adoption as a new Jenkins contributor.
> >> In doing so, I will be assisting with the DevOps world contributor
> summit, and want to ensure I'm providing the best help that I can.
> That's good idea,
>
Thanks for your interest. It is much appreciated. Kevin is acting as a
test case for a workshop and a draft jenkins.io tutorial that we're
creating to help others adopt plugins. He's not a Java developer. He's
not likely to continue as a maintainer of this plugin for the long term.
He's helping us develop the workshop by using his technical skills to
review a tutorial ("Improve a plugin" tutorial
<https://deploy-preview-4806--jenkins-io-site-pr.netlify.app/doc/developer/>
visible
on a preview site) that is being prepared for www.jenkins.io in a draft
pull request <https://github.com/jenkins-infra/jenkins.io/pull/4806>. We
thought that it was better for him to temporarily adopt a lower use and
lower risk plugin as part of the exercise.
We're happy to have others assist as well. However, suggesting that Kevin
should adopt a heavily used plugin and become the permanent maintainer is
not what is expected from this exercise.
> but I can think of some better examples, which are still widely use across
> Jenkins Community and they need some attention.
> Like this one (fairly simple plugin):
> https://plugins.jenkins.io/badge/
>
>
The badge plugin has recently been adopted
<https://github.com/jenkins-infra/repository-permissions-updater/pull/2753>
as part of this preparation for the DevOps World workshop and the
jenkins.io tutorial. Because the adoption is expected to be temporary,
we're not removing the badge plugin or other temporarily adopted plugins
<https://github.com/jenkins-infra/repository-permissions-updater/pulls?q=is%3Apr+is%3Aclosed+author%3AMarkEWaite>
from the "adopt this plugin" list. However, improvements have already
started on the temporarily adopted plugins The badge plugin pull request
queue <https://github.com/jenkinsci/badge-plugin/pulls> has been cleared.
Other plugins that are being temporarily adopted are receiving similar
improvements. We plan to create one or more pull requests to those plugins
to modernize them as preparation for our DevOps World workshop. We hope
that one of the results of the workshop will be that someone will choose to
adopt one or more of those plugins long term. If no one chooses to adopt
the plugins long term, the plugins will still have benefited from our
preparatory work.
> Or:
> https://github.com/jenkinsci/extended-choice-parameter-plugin
> I would be grateful if somebody could take care for this plugin. It looks
> like do to war in Ukraine maintainer is unable to take care of it and any
> work stopped in this sad day :(
>
>
The extended choice parameter plugin
<https://plugins.jenkins.io/extended-choice-parameter/> is not up for
adoption. It would require either approval from the maintainer or a two
week waiting period before it could be adopted.
The extended choice parameter plugin
<https://plugins.jenkins.io/extended-choice-parameter/> has 4 known
security vulnerabilities. Resolving known security vulnerabilities is
outside the scope of the workshop. We've intentionally dropped some
plugins from our temporary adoption because they have open security
vulnerabilities.
> Or some plugins which are serves as common dependencies (but can be hard):
> https://plugins.jenkins.io/jaxb/
> https://plugins.jenkins.io/docker-plugin/
> https://plugins.jenkins.io/docker-java-api/
> https://plugins.jenkins.io/apache-httpcomponents-client-4-api/
>
> I think first option is the best one for start.
>
>
We've intentionally not adopted the library plugins like jaxb,
docker-java-api, and apache-http-components because the workshop and the
tutorial are focused on plugins that contain Java source code. The library
plugins bundle jar files that are provided by other projects. That makes
their adoption and maintenance activities different than the more typical
plugin adoption.
Mark Waite
--
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/8356634a-e734-4fdc-8a12-b0dcc350e888n%40googlegroups.com.
