Adopting Dependency-Check plugin

[Guido Grazioli]

Hello all,

I would like to adopt the plugin at
https://github.com/jenkinsci/dependency-check-plugin

Github account is: guidograzioli
Infra id is: guido.g...@gmail.com (ggrazioli)

I haven't got PRs open at the moment, but we are heavy users of the
plugin in our CI environment,
and are concerned it could fall out of maintenance.

Kind regards,
Guido

--
Guido Grazioli <guido.g...@gmail.com>
Viale Italia 162
48123 Marina Romea (RA) Italy
Mobile IT: +39 347 1017202 (10-18 GMT+1)
Stackoverflow: http://stackoverflow.com/cv/guidograzioli
Linked in: http://www.linkedin.com/in/guidograzioli
Key FP = 7040 F398 0DED A737 7337 DAE1 12DC A698 5E81 2278

[kudos-dude]

I'd like to retract my offer to adopt and endorse this guy.

[Guido Grazioli]

Oh I am so sorry, I did not check the ML in advance, my bad!
Happy for you to maintain the plugin of course; just wanted to make
sure proposed PRs get
the needed attention

Cheers
Guido

> --
> 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 jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7ee3f843-35fc-49af-9566-3bfd08d9fbcen%40googlegroups.com.

[kudos-dude]

It's no worries!

My thought was that if you had a team working on it, would be better than what I can do in my free time.

Plus, (forgive me for looking), but looks like you have more Java experience than me. I was going to make this a learning opportunity, but to be honest, I don't really have a whole lot of time for that either.

Maybe we could work on it together? No idea how the concept of "maintainers" even works really, but I'd be more than willing to contribute. My former life in software engineering was spent in Front End mostly, so I was going to work on refactoring the Javascript, if you want to be the Java part?

[kudos-dude]

Also, don't know if you saw, but looks like the whole `dependency-check` line is broken at the moment. It was failing our builds due to something internal throwing a critical exception.

I can help look into some better internal error handling as well to clear up that issue. The company I'm working at doesn't want a plugin's internal failures triggering build failures too.

[Gavin Mogan]

Did the two of you decide if both/which one is going to be maintainer?

One of the two of you (or both)  should create a PR for https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-dependency-track.yml as part of the adoption process.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/99f4df0e-51e6-4509-8ce9-45e382953074n%40googlegroups.com.

[kudos-dude]

I would still like to be maintainer. I wouldn't mind being "co-maintainer" if that's a thing either. Either way, I'll continue with the adoption process.