Ownership Transfer Request: AWS Device Farm Plugin

66 views
Skip to first unread message

Oleg Nenashev

unread,
Apr 30, 2018, 5:15:18 AM4/30/18
to Jenkins Developers
Hi all,

AWS Device Farm plugin is currently affected by JEP-200 and not compatible with Jenkins 2.102+ (JENKINS-50483, PR #3). There are also pending pull requests like Pipeline support (PR #5 and PR #2).

I have been trying to reach out to the current maintainer (Nikhil Dabhade) for 1 month, without success. There is no activity in the plugin since the last release Aug 27, 2017, and there are also no responses from the maintainer in any PRs or JIRA tickets. On April 23 I have sense an email to Nikhil using his email in Git commit history. I also tried emails mentioned in JIRA. No success. I would consider the plugin as non-maintained from the community PoV.

Taking the current state, I request ownership transfer to Patrick Cadelina (JIRA ID: patcadelina) and me (JIRA ID: oleg_nenashev). Patrick has kindly agreed to be a plugin maintainer, and I will help him with initial release and onboarding.

Taking the "best effort" requirement, I propose to set the response timeout to May 07 (2 weeks since the last direct ping by email in Git). WDYT?

Thanks in advance,
Oleg Nenashev

Mark Waite

unread,
Apr 30, 2018, 7:47:06 AM4/30/18
to jenkin...@googlegroups.com
That sounds very reasonable to me.

--
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/4fdf1a7a-43f9-4c4e-9455-5506e783aca0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Daniel Beck

unread,
Apr 30, 2018, 7:50:11 AM4/30/18
to jenkin...@googlegroups.com

> On 30. Apr 2018, at 11:15, Oleg Nenashev <o.v.ne...@gmail.com> wrote:
>
> Taking the "best effort" requirement, I propose to set the response timeout to May 07 (2 weeks since the last direct ping by email in Git). WDYT?

Seems reasonable.

Patrick Jonathan Cadeliña

unread,
May 2, 2018, 12:27:45 AM5/2/18
to Jenkins Developers
All good.

Oleg Nenashev

unread,
May 7, 2018, 6:51:58 PM5/7/18
to Jenkins Developers
Response timeout.
I will transfer ownership tomorrow and spin the release

Oleg Nenashev

unread,
May 11, 2018, 5:05:50 AM5/11/18
to Jenkins Developers
UPD: Version 1.16 with JEP-200 is out. We will be do the rest of the merges (like Pipeline) support towards 1.17

Thanks to everybody in this thread.

BR, Oleg

Nikhil Dabhade

unread,
Jul 30, 2018, 3:40:04 PM7/30/18
to Jenkins Developers
Hello Everyone,

Firstly, Apologies for the extreme delay here. The email from github made it to a non-inbox folder and did not get catch my eye until now. 
Secondly, Thank for you very much for taking ownership of this plugin due to inactivity on it.

We now have an established process at our end to make sure we can maintain this plugin going forward. 
I would like to continue being one of the maintainers on this plugin. 

Let me know if there are any permissions that I need to refresh/update to do so.
Again thank you for very much for being proactive here.

Regards,
Nikhil

Patrick Jonathan Cadeliña

unread,
Jul 31, 2018, 12:16:38 AM7/31/18
to jenkin...@googlegroups.com
Welcome back Nikhil!

I've just released 1.17 for the plugin to support Pipeline. Moving forward, I'll try to assist you when I can.

Regards,
Pat

--
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/aTuFiNHhTLY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5a9484ff-c322-4a14-97ad-9d1a00682360%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages