Well, vacation does not last indefinitely. (and the out-of-office mails are generally despicable).
And IMO plugin activity is actually generally quite easy to measure (though not always valid): if no commit was done in the last, say 6, months, and you see other older PR rotting for weeks or months then the plugin is clearly abandonned. In the present case, this indeed seems to be clearly the case: last commit is 2 years old. Maybe I'm just overkill here, right. Cheers 2015-05-12 14:34 GMT+02:00 Kari Sivonen <[email protected]>: > But how to know if original author is on vacation or not interesting this > plugin anymore? There is no any out of office here I guess. > > And how to see if someone is active or not? > > Maybe there should be actively and inactively maintained plugins. Author > will told somewhere that actively maintain plugin and that will be valid > e.g six month. For those plugins is not given commit permissions by admins > even no answers in some limit. If author is not said he will maintain > plugin actively admins could give commit access those who likes if no > answers in two weeks. Time limits can be something else also. > > But this is only one idea. > > > lauantai 9. toukokuuta 2015 11.37.45 UTC+3 Baptiste Mathus kirjoitti: >> >> BTW IMO we should consider rephrasing that part: replacing "become a >> committer" by "a maintainer (by asking for commit rights) to convey the >> right message (?). >> >> And 1/2 weeks seems quite short also. >> >> Not sure I would personally like my plugin being taken over just because >> I took a 2 weeks holiday. >> >> WDYT? >> Le 9 mai 2015 10:21 AM, "Richard Bywater" <[email protected]> a écrit : >> >>> I have a feeling he's referring more to the "If you notice that your >>> pull requests aren’t getting attended to within a week or two, please drop >>> us a note at the dev list, and please consider becoming a committer and >>> push the changes directly." part more than taking other as maintainer... >>> although I could be wrong :) >>> >>> Richard. >>> >>> On Sat, 9 May 2015 at 01:24 Baptiste Mathus <[email protected]> wrote: >>> >>>> Did you write to the original maintainer first? >>>> See the governance doc for the process: >>>> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Helpingandtakingoverdormantplugins >>>> >>>> Cheers >>>> Le 8 mai 2015 11:59 AM, "Kari Sivonen" <[email protected]> a >>>> écrit : >>>> >>>>> I made pull request to >>>>> https://github.com/jenkinsci/mongodb-document-upload-plugin >>>>> repository. >>>>> >>>>> After 9 days, no reply from it, so I like to get commit access to it >>>>> to make merge by my self. >>>>> >>>>> My GitHub account: karisivo >>>>> Repo: https://github.com/jenkinsci/mongodb-document-upload-plugin >>>>> >>>>> In my pull request ( >>>>> https://github.com/jenkinsci/mongodb-document-upload-plugin/pull/1) >>>>> plugin is changed so that if "_id" fiels is given in json document, it >>>>> will >>>>> update if document already exist in dataBase. >>>>> >>>>> -Kari >>>>> >>>>> >>>>> -- 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/CANWgJS5bPmGGrkKdhjN28uq%2BtDJ6ayqB3caOF6mQHiPL8G5QRw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
