Hello Wes, Thank you for adopting this plugin.
I am working with Mark Waites and a couple of others on various initiatives to improve the contributors and maintainers experience (especially newcomers). It is in that context that I believe that it would be great if we could we discuss your experience by mail of even is a short call (if time zones are favorable). I'd like to know things, among others, like: - was the adoption successful? - what were the friction points? - Did you get (or needed) help? In what form? - what were your motives for adoption? - what is your previous experience as Jenkins/OSS contributor and in java dev? - .... If interested to share your experience, you can contact me at [email protected]. /- Jmm Jean-Marc Meessen Brussels, Belgium Le jeudi 11 novembre 2021 à 21:36:50 UTC+1, kudos-dude a écrit : > I want to apologize for the tone in my original post. Just feeling a bit > overwhelmed at the moment. > > The plugin on Github still contains the `adopt-this-plugin` tag and the > "Seeking a new maintainer" section. > > https://github.com/jenkinsci/dependency-check-plugin > > Please let me know if there is anything else I need to do. > > Wes > On Thursday, November 11, 2021 at 9:10:37 AM UTC-5 [email protected] > wrote: > >> As a side note for this plugin: if someone is willing to refactor the >> existing parser so that it rather writes the output to the object model of >> the analysis-model plugin then we simply can integrate it into the parser >> collections of the warnings plugin. Then the whole OWASP Dependency Check >> plugin will become obsolete and the visualization will be automatically >> improved while the warnings plugin is improving. >> >> Am 10.11.2021 um 22:04 schrieb Mark Waite <[email protected]>: >> >> Thanks for adopting it in April. >> >> The easiest way to list it as "Seeking a new maintainer" is to place a >> topic on the GitHub repository "adopt-this-plugin". Refer to the >> https://github.com/jenkinsci/run-condition-plugin and the >> "adopt-this-plugin" topic that is assigned towards the upper right corner >> of the list of files >> >> >> >> On Wednesday, November 10, 2021 at 1:49:45 PM UTC-7 kudos-dude wrote: >> >>> I adopted this plugin back in April, but my circumstances have changed. >>> >>> I need to formally place this plugin back into a "Seeking a new >>> maintainer" state. I believe that there was interest in the recent past >>> looking to adopt the plugin, which I did at that stage state I was placing >>> the plugin up for adoption again and was willing to transfer ownership. The >>> conversation did not progress and I still own it as a result. >>> >>> I have since received communication about additional work required for >>> the plugin, but as stated above, I simply don't have time. I'd go into the >>> reasons why, but this isn't my personal blog, so I'll spare the details. >>> >>> I don't know what the official requirements are for making this >>> concrete, so I ask any officials within this forum to please take this >>> request across the finish line. >>> >> >> -- >> 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/39e632a3-0462-4b12-b7b2-dd287526f965n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/39e632a3-0462-4b12-b7b2-dd287526f965n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> <screencapture-github-jenkinsci-run-condition-plugin-2021-11-10-14_02_46-edit.png> >> >> >> -- 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/0fdde106-03d2-4b91-b54d-234e8abbd015n%40googlegroups.com.
