Given the plugins implement different specifications without being too close to the details I would suggest a new plugin even if it’s based on the existing one. There’s no need to confuse users with having a different spec in the artefact id
On Tue, 7 Mar 2023 at 19:47, Mark Waite <[email protected]> wrote: > > > On Monday, March 6, 2023 at 10:54:37 AM UTC-7 Jamie Plower wrote: > > HI all, > > > > I work for Ger McMahon at Fidelity and we working on restarting the above > initiative around building a CDEvents Plugin for Jenkins. Reviewing the > advise above it am keen to commence the process where we can look at > forking and renaming the plugin. Oleg would be possible to follow up with > some help around getting the appropriate permission to kick off the process > and appreciate any assistance in helping me & team navigate through this > process initially in hosting/adopting this CD Events plugin > > > > > Thanks for your willingness to work on CDEvents. That's great news. > > I think that you should adopt the CloudEvents plugin > <https://plugins.jenkins.io/cloudevents/> and use it as the basis for > your efforts. The "Adopt a plugin" > <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/> > instructions guide you through the necessary steps. Vibhav is one of the > maintainers and can approve the adoption request. > > While waiting for approval of the adoption request, you could use the > steps in the "Improve a plugin" > <https://www.jenkins.io/doc/developer/tutorial-improve/> tutorial to > submit preparatory pull requests to that plugin. The plugin needs to be > updated with most of the steps that are included in that tutorial. > > Changing the display name of the plugin is quite easy. See the mailing > list thread > <https://groups.google.com/g/jenkinsci-dev/c/iYSCjRuO61U/m/1MdeHCIfAgAJ> > for details. > > I think that the new plugin you're envisioning will be close enough to the > existing plugin that you'll want to start with the existing plugin rather > than create a new plugin. > > 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/a91e46f2-0217-4024-ba13-5c584d079acfn%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a91e46f2-0217-4024-ba13-5c584d079acfn%40googlegroups.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bidjg70YqnwABUkFrOsbzBWzF5onQvWrds%3D0NnSyQ7v%2BXg%40mail.gmail.com.
