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 in advance Jamie On Wednesday, June 22, 2022 at 8:43:44 AM UTC+1 gerard....@fmr.com wrote: > Thanks Vibhav. Jamie Plower from Fidelity will lead this from my team and > is currently working through the approval process for google groups and > slack access. We are also working through our OSPO for the necessary > approvals to take on the plugin and also to contribute to the CDEvents > project as we identify valuable contributions. It might be the middle of > July to get through all the approvals and there is vacation in the middle. > > Thanks > > Ger > > On Monday, June 20, 2022 at 7:31:07 PM UTC+1 vibhav...@gmail.com wrote: > >> Hi Team, Gerard, >> >> Apologies for the late reply. >> I was the mentor on the team for the JenkinsCI Cloudevents plugin. I >> would love to help you get this project restarted for CDEvents for Jenkins. >> I am present on the CDF Slack where you can find me and maybe we can get on >> a call and work out the details. >> >> Regards, >> Vibhav >> >> >> On Fri, Jun 17, 2022 at 2:04 PM 'Gerard McMahon' via Jenkins Developers < >> jenkin...@googlegroups.com> wrote: >> >>> Thanks everyone for the response and I will check with my team. Based on >>> the advise above, i think forking the cloudevents plugin and creating a new >>> cdevents plugin might be the best way to proceed. >>> >>> Ger >>> >>> On Thursday, June 16, 2022 at 2:52:18 PM UTC+1 Oleg Nenashev wrote: >>> >>>> Hi, thanks for the interest! AFAICT I am listed as one of >>>> co-maintainers for this plugin, and I am happy to help with permissions& >>>> co. >>>> And maybe Tim is right about forking and renaming the plugin. We have >>>> no way to safely change artifactIDs after the initial release, so maybe a >>>> fork is a best approach. >>>> >>>> >>>> >>>> >>>> >>>> On Tuesday, June 14, 2022 at 5:52:14 PM UTC+2 timja...@gmail.com wrote: >>>> >>>>> Or alternatively create a new plugin for CDEvents if the cloud events >>>>> heritage doesn't make sense any more. >>>>> >>>>> Once you've got it working you could then go through the hosting >>>>> process >>>>> <https://www.jenkins.io/doc/developer/publishing/requesting-hosting/>. >>>>> >>>>> Thanks >>>>> Tim >>>>> >>>>> >>>>> >>>>> On Tue, 14 Jun 2022 at 13:18, Mark Waite <mark.ea...@gmail.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Tuesday, June 14, 2022 at 6:08:41 AM UTC-6 Ger McMahon wrote: >>>>>> >>>>>>> My name is Ger McMahon and work for Fidelity Investments. As part of >>>>>>> being an end user member of Continuous Delivery Foundation (CDF), we >>>>>>> want >>>>>>> to get more involved in open source projects and especially ones >>>>>>> related to >>>>>>> the CDF. We have a particular interest in the Jenkinsci Cloudevents >>>>>>> plugin <https://github.com/jenkinsci/cloudevents-plugin> and >>>>>>> understand the project has been dormant since it was created as part of >>>>>>> the >>>>>>> Google Summer of Code. Fidelity would have an interest on taking on >>>>>>> this >>>>>>> project, either through mutating the current implementation or forking >>>>>>> to >>>>>>> align with the new CDEvents project <https://cdevents.dev/> from >>>>>>> CDF. >>>>>>> >>>>>>> >>>>>>> >>>>>>> I wanted to connect with the jenkinsci-dev group to determine the >>>>>>> next steps and appreciate any information or feedback. >>>>>>> >>>>>>> >>>>>>> >>>>>> Welcome to the developer community! Great to have your interest in >>>>>> CloudEvents and happy to have your help. The "Adopt a plugin" >>>>>> <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/> >>>>>> process says: >>>>>> >>>>>> Be sure to provide the following information: >>>>>> >>>>>> - >>>>>> >>>>>> Link to a plugin you want to adopt - >>>>>> https://github.com/jenkinsci/cloudevents-plugin >>>>>> - >>>>>> >>>>>> The status of the plugin ("for adoption" or "abandoned") - >>>>>> abandoned >>>>>> - >>>>>> >>>>>> Link(s) to pull requests you want to deliver, if applicable - I >>>>>> don't see any yet, though refer to the "Contributing to Open >>>>>> Source" >>>>>> >>>>>> <https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.hvd0nm6pz5o4> >>>>>> >>>>>> document and the "Modernizing a plugin" video series >>>>>> <https://www.youtube.com/watch?v=Fev8KfFsPZE> for suggested >>>>>> starter pull requests >>>>>> - >>>>>> >>>>>> Your GitHub username/id (e.g. oleg-nenashev for >>>>>> https://github.com/oleg-nenashev/) - You'll need to provide this >>>>>> one >>>>>> - >>>>>> >>>>>> Your Jenkins infrastructure account id. Create your account >>>>>> <https://accounts.jenkins.io/> if you don’t have one. - You'll >>>>>> need to provide this one >>>>>> - >>>>>> >>>>>> The link to the "Repository Permission Updater" PR described >>>>>> below - You'll need to provide this one based on the instructions >>>>>> >>>>>> Be sure that you follow the instructions for the contents of the pull >>>>>> request and its comments. >>>>>> >>>>>> Thanks again, >>>>>> 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 jenkinsci-de...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/93cc484d-de7e-497e-9396-3b84d7761a56n%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/93cc484d-de7e-497e-9396-3b84d7761a56n%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 jenkinsci-de...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/2f00549e-6601-4df1-9930-14bbb16211c3n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/2f00549e-6601-4df1-9930-14bbb16211c3n%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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/80ceacf2-3842-4b37-8a06-64b73d50e19en%40googlegroups.com.
