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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7c3acbea-4efc-4079-a496-8e1116fdd5f9n%40googlegroups.com.
