Hello. We are just now following up on this request from 2022 to take ownership of the Kryptowire Jenkins Plugin. My colleague Brian Schulte has opened an issue in the project and tagged the original maintainers of the plugin.
https://github.com/aerogear/aerogear-kryptowire-jenkins-plugin/issues/14 He also created a PR in the repo requested by a previous responder. https://github.com/jenkins-infra/repository-permissions-updater/pull/4555 Please let us know the next steps Chris Downey Senior Product Manager, Kryptowire dba Quokka On Wednesday, August 31, 2022 at 9:18:29 AM UTC-6 Chris Downey wrote: > Greetings, > > My name is Chris Downey and I'm a colleague of Brian Schulte at > Kryptowire, with whom you worked with about 4 years ago to develop a > Jenkins CI/CD Plugin for Mobile App Build submissions to the Kryptowire > MAST platform. We are looking to take full ownership of that Plugin so > that we can update it with some changes we've made. Jenkins Devs requested > I CC original developers who are listed as Admins in the Permissions > Updater repo's plugin-kryptowire.yml > <https://github.com/jenkins-infra/repository-permissions-updater/blob/daaa3d5d1cd632f26494162a0d72202677e129b7/permissions/plugin-kryptowire.yml> > file. > I've CC'd 2 here in addition to John Frizelle who we engaged in 2018 but is > not listed as a plugin admin as far as I can tell. Brian and I would like > to proceed taking full ownership of the plugin including the Admin list. > > Please reply that you have received this message when you can to approve. > Thanks for your time. > > Plugin in jenkinsci repo: https://github.com/jenkinsci/kryptowire-plugin > Plugin on Plugins site: https://plugins.jenkins.io/kryptowire/ > My ci.jenkins.io Username: crdkw > My Github Username: cdowney-kryptowire > Original Contributor Github Username: odra > > Regards, > > Chris Downey > Senior Product Manager, Kryptowire > > ---------- Forwarded message --------- > From: Chris Downey <Unknown> > Date: Wednesday, August 31, 2022 at 9:59:26 AM UTC-5 > Subject: Re: Plugin Adoption for kryptowire-plugin > To: Jenkins Developers <Unknown> > > > Thank you for the response. Sorry for my delayed response, I was > expecting to get emailed any response to my Group post, but never saw an > email reply so am just now today coming back to the Groups page to check > the thread. > > My engineering resource is on PTO, but we will get this process started > when he returns. > > Regards, > Chris > > > On Thursday, August 18, 2022 at 5:51:01 PM UTC-5 ga...@gavinmogan.com > wrote: > >> So what you've done is a start. You should be CC'ing any of the current >> maintainers. Also recommend creating a PR or issue that tags them. Thirdly >> make a PR >> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-kryptowire.yml >> >> Once that's all done, we wait 2 weeks for a response, if that times out, >> then we go ahead and give you access. >> >> > We are about to go through a re-branding process at our Company and >> have iterated on the version of the Plugin the RedHat guys first developed, >> >> Just be careful not to update the artifact id, otherwise it'll prevent >> existing installs from upgrading. >> >> On Thu, Aug 18, 2022 at 1:58 PM Chris Downey <cdo...@kryptowire.com> >> wrote: >> >>> Hello, >>> >>> I am reaching out to this Group email in the hopes of starting the >>> Adoption process for the kryptowire-plugin in the jenkinsci Project. >>> Relevant details are as follows. >>> >>> Plugin in jenkinsci repo: >>> https://github.com/jenkinsci/kryptowire-plugin >>> Plugin on Plugins site: https://plugins.jenkins.io/kryptowire/ >>> My ci.jenkins.io Username: crdkw >>> My Github Username: cdowney-kryptowire >>> Original Contributor Github Username: odra >>> >>> Other Info: >>> >>> I am a Senior PM at Kryptowire. We collaborated with some developers >>> from RedHat for the initial version of the Plugin for which they were >>> responsible engaging the project for acceptance and maintaining the first >>> version. My colleague CC’d here, Brian Schulte may be listed as an Admin >>> for the Plugin, but I don’t think the process of transferring full >>> ownership to us was ever completed after the Plugin was first developed in >>> mid-2018. We are about to go through a re-branding process at our Company >>> and have iterated on the version of the Plugin the RedHat guys first >>> developed, but without full ownership haven’t been able to update the >>> official Jenkins version. >>> >>> Can you please let me know what the Adoption process should be to take >>> full ownership of the project in jenkinsci? If we need to, I can try to >>> contact the original developers. >>> >>> Regards, >>> >>> Chris Downey >>> Senior Product Manager >>> E: cdo...@kryptowire.com >>> M:+1 512.791.4315 <(512)%20791-4315> >>> >>> -- >>> 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/55D5672A-1303-4CDC-BEC8-1712C85E4B9B%40kryptowire.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/55D5672A-1303-4CDC-BEC8-1712C85E4B9B%40kryptowire.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/cd8ead78-eeec-4124-9c14-f6867dbe4922n%40googlegroups.com.
