I'm personally fine with that plan. For step "4.1", as the plugin is MIT licensed, are we really required to do such non backward compatible change? It's a really good thing to try to reach out, don't get me wrong, totally for it, but it does not work out, then not that a big deal IMO.
I guess 4.2 will indeed be the most logical path (with no answer). 2016-11-22 17:44 GMT+01:00 Oleg Nenashev <o.v.nenas...@gmail.com>: > In addition to this thread, I have tried to reach out Gregory directly > without success. Since he has left his original company as well as his > companion from citools org, it is a low chance we can proceed in the common > way. > > I had an f2f discussion with Jacob at Embedded Conference Scandinavia. We > discussed the current state and agreed on the following: > > 1. Oleg will grant him an access to the klocwork repository within the > jenkinsci organization (an existing repo) > 2. Jacob will push the current changes in citools org and then proceed > with preparing the release in pull requests (he can use > jenkinsci/code-reviewers in order to get help with onboarding) > 3. Oleg will try to reach out Thales directly on behalf of the Jenkins > core team (in order to propose the ownership handover) > 4. If we do not get a response from Thales, we will submit a topic to > the Governance meeting with 2 options: > - Fork of a plugin with renaming/package name changes > - Just a takeover of the plugin by the Jenkins community (with > temporary revokation of upload permissions for original maintainers to > avoid mess if they come back and do not notice this thread) > > WDYT? > > > Best regards, > > Oleg > > > среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev > написал: > >> Any revival of this plugin will be appreciated. >> >> Unfortunately, we cannot just fork the repository and start releasing >> from it. It may be considered as a highjacking of the plugin. Plugin >> maintainers commonly do not sign Jenkins CLA, hence we have no formal >> permission to do so. >> >> I think we should fork the plugin to jenkinsci and start preparing it to >> the release with patches (including stuff like CI, parent POM update, >> etc.). If the maintainer does not respond, likely the only valid option >> will be to rename plugin and to change packages to avoid data conflicts. >> But it will require much work to implement the proper migration code. >> >> I've added Gregory Boissinot to Cc. Maybe he could suggest the proper >> contact. >> >> BR, Oleg >> >> вторник, 15 ноября 2016 г., 14:13:29 UTC+1 пользователь Jacob Larfors >> написал: >>> >>> Ok I tried contacting the other maintainer/user at cittools and his >>> email address for Thales does not work, so I suspect he has left Thales. As >>> there has also been an outstanding pull request since July, and our >>> attempts to contact the people at cittools has failed, I would assume this >>> repository is no longer taken care of... >>> >>> What options do we have? Can we make the jenkinsci repository the "main" >>> one and we will get our commits there? There arent really any valid PRs/FRs >>> in Jira, and the few that are we could look to transfer or fix, as we quite >>> actively work on this plugin and have been shipping hpi files for the past >>> few years to avoid this mess and bottleneck of waiting for cittools. >>> >>> Thanks for the help. >>> >>> Jacob >>> >>> On Tuesday, 15 November 2016 14:59:06 UTC+2, Jacob Larfors wrote: >>>> >>>> Hi Daniel, appreciate the quick feedback and thanks for the info - that >>>> answered another question I had about why the jenkinsci repo even existed. >>>> >>>> I would prefer to use the jenkinsci repo to avoid any future >>>> issues/bottlenecks. I have made one last attempt at contacting cittools >>>> because we tried contacting the owner of the repository for some time now >>>> (gboissinot) with no luck. >>>> >>>> Should this not work, is there some way we can push our commits to the >>>> jenkinsci repository and make this the one linked in Jenkins (i.e. make the >>>> cittools repo redundant)? I assume that can be done without needing >>>> cittools, but I will await a response from them out of courtesy. >>>> >>>> Thanks, >>>> Jacob >>>> >>>> On Tuesday, 15 November 2016 14:46:39 UTC+2, Daniel Beck wrote: >>>>> >>>>> We cannot grant access to repositories outside the jenkinsci GitHub >>>>> organization. Which is one of the reasons why we strongly recommend that >>>>> plugins be maintained in that organization. >>>>> >>>>> We can only grant access to https://github.com/jenkinsci/k >>>>> locwork-plugin and you'd need to sync the existing commits over. This >>>>> however will not transfer existing issues and PRs in the cittools repo. >>>>> IOW, it's a giant clusterfuck thanks to maintainers maintaining elsewhere. >>>>> >>>>> I recommend you contact cittools and coordinate what to do with them. >>>>> I can then transfer the repo as needed, and delete the one in jenkinsci >>>>> that appears to have never been used. >>>>> >>>>> > On 15.11.2016, at 12:58, Jacob Larfors <ja...@larfors.com> wrote: >>>>> > >>>>> > Hi guys, >>>>> > >>>>> > Maybe someone can help me out, but a few weeks back I posted about >>>>> commit access to the Klocwork plugin, following a pull request for a >>>>> colleague, and neither have been answered... We really want to push some >>>>> great features out there but our hands our tied :) >>>>> > >>>>> > If anyone knows how who to contact to get some action or even to >>>>> apply for a transferral of ownership for a plugin that would be great. >>>>> > >>>>> > This is the plugin in question: https://github.com/cittools/kl >>>>> ocwork-plugin >>>>> > >>>>> > My github account: jlarfors >>>>> > >>>>> > Thanks for the help! >>>>> > >>>>> > Jacob >>>>> > >>>>> > -- >>>>> > 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/973c8a41-aac >>>>> 1-4c5f-a76e-5091bb8f3cee%40googlegroups.com. >>>>> > For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> -- > 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/a63d2d26-f248-403a-8ba1-c32d3a02e16d% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a63d2d26-f248-403a-8ba1-c32d3a02e16d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CANWgJS4pRFzajeN-fjuvi16jtKaWvW7FnO75m78WUgn-S55yeg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
