Adopt view-job-filters-plugin

[Sven Schoenung]

I'd like to adopt the View Job Filters Plugin:

https://github.com/jenkinsci/view-job-filters-plugin

I'm looking into adding a filter for scheduled/unscheduled jobs that would be useful in combination with my own Calendar View Plugin. There's also a number of lingering pull requests that haven't received any attention and about a dozen or so open bugs in JIRA.

The plugin isn't listed on the Adopt a Plugin page in the wiki, but there has clearly been no active development going on for a couple of years now. In fact Jesse Glick removed the maintainer from the POM about three years ago and offered maintenance of the plugin to somebody on GitHub (no takers there):

https://github.com/jenkinsci/view-job-filters-plugin/commit/15ab7fcec369dcacbcbfa0a90f1529306ed57ec9

https://github.com/jenkinsci/view-job-filters-plugin/pull/6#issuecomment-95148268

CCing the previous maintainer in case he's willing to pick up maintenance again or hand off development.

My GitHub ID: svenschoenung

My Jenkins Infra ID: svenschoenung

Should I file a pull request in repository-permissions-updater right away or wait for the two weeks grace period to end?

Thanks,

Sven

[Oleg Nenashev]

Hi Sven,

Thanks for your interest!

I believe that Jesse Glick should be considered as a current maintainer. The last release has been performed by him. Once he confirms the request, I will be happy to transfer the plugin ownership.

Best regards,

Oleg

[Jesse Glick]

On Sun, Aug 19, 2018 at 2:22 PM Oleg Nenashev <o.v.ne...@gmail.com> wrote:
> I believe that Jesse Glick should be considered as a current maintainer.

Huh? No.

> The last release has been performed by him.

It was? If so, it was a one-off thing.

[Sven Schoenung]

> I believe that Jesse Glick should be considered as a current maintainer.

Huh? No.

 

You're listed as the only developer in the permissions YAML file for the plugin, but it looks like that was an done via an automated job.

In any case, Jacob Robertson, the original author, was kind enough to contact me and confirmed that he's no longer interested in maintaining the plugin. His email was addressed to the to mailing list as well, but doesn't seem to have made it through (either because he's not a member of the Google Group or because it's still held up in moderation).

Here's his response:

On Sat, Aug 18, 2018 at 4:49 PM Jacob Robertson wrote:
I am the original author, and have no issue with you adopting this.  Not sure about who is currently maintaining.  I am no longer able to provide support to this plugin.

[Oleg Nenashev]

I believe we can transfer ownership without timeout then. I will do that once I get to the laptop

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/k7YL8MEK5bM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cf161de4-b168-4f6c-895a-ec2fd1acdd25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sven Schoenung]

On Monday, August 20, 2018 at 4:41:01 PM UTC+2, Oleg Nenashev wrote:

I believe we can transfer ownership without timeout then. I will do that once I get to the laptop

Should I be able to commit to the repo? I tried a test commit and it looks like I don't have permission.

No rush if you haven't been able to get to this yet.

[Oleg Nenashev]

As you may guess, I have not done that on Aug 20. IIRC there were issues with the bot, and then I just forgot about it. Now you should have the permissions.

You should have the permissions now.

My apologies for missing the action item, and thanks for the patience!

Best regards,

Oleg

[Sven Schoenung]

Can confirm, I can commit to the repo now. Thank you!