Commit access to vstestrunner-plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Commit access to vstestrunner-plugin

Erik Goughnour
Hello All,

Can I get access to vstestrunner-plugin?

I have submitted two issues and opened a pull request to fix them.

I do have an interest in making sure the plugin works.  

I set up Jenkins jobs pretty frequently and it's difficult to run and track .NET tests without it.

Thanks,

Erik

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4b36aae9-7dc2-4a8a-beff-5164c691aa0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Daniel Beck

> On 25. Sep 2017, at 01:39, Erik Goughnour <[hidden email]> wrote:
>
> Can I get access to vstestrunner-plugin?

Please make sure to include the current/previous maintainers in this request to give them a chance to respond, if they're still around.

It doesn't look like there's a lot going on with the plugin, but still.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B5C0B281-A155-4D85-BE08-FC01825F5D7A%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour
That would be @yasu-s.

On Monday, September 25, 2017 at 12:30:28 AM UTC-5, Daniel Beck wrote:

> On 25. Sep 2017, at 01:39, Erik Goughnour <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="LtEQ7IyqBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">e.gou...@...> wrote:
>
> Can I get access to vstestrunner-plugin?

Please make sure to include the current/previous maintainers in this request to give them a chance to respond, if they're still around.

It doesn't look like there's a lot going on with the plugin, but still.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4d62dc0b-e42d-4d08-ba72-2b4febf064b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Baptiste MATHUS
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <[hidden email]>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour
Yasu is CC’d now.   The user email listed in GitHub matches the last git log entry’s email.

On Tuesday, October 3, 2017, Baptiste Mathus <[hidden email]> wrote:
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;e.goughnour@gmail.com&#39;);" target="_blank">e.goughnour@...>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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 <a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;jenkinsci-dev%2Bunsubscribe@googlegroups.com&#39;);" target="_blank">jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to <a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;jenkinsci-dev%2Bunsubscribe@googlegroups.com&#39;);" target="_blank">jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-QPaCoeQ6RCmoiOGmZKTDLgPoB5nfm0ud_UcQtg4AhQkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour

斎藤ヤスユキ様


始めまして。ところでお名前の漢字はどう書きますか?これ突然のメールで申し訳ないです。そしてほんとうに宜しく御願いします。


            御返事を待ちしております。

                             Erik Goughnour


On Tuesday, October 3, 2017, Erik Goughnour <[hidden email]> wrote:
Yasu is CC’d now.   The user email listed in GitHub matches the last git log entry’s email.

On Tuesday, October 3, 2017, Baptiste Mathus <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;ml@batmat.net&#39;);" target="_blank">ml@...> wrote:
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <[hidden email]>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-TzdRsewk%2BoSxDsV_qgkEKPZ2%2BS0DbTf-cLM0im%2B-%3D9PA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour
Requesting commit access again.  

Surely the touchstones are all giving favorable indications by now.

Elapsed time, respect, courtesy, required information, multiple attempts to contact—was there anything else?

Thanks,
Erik

On Wednesday, October 4, 2017, Erik Goughnour <[hidden email]> wrote:

斎藤ヤスユキ様


始めまして。ところでお名前の漢字はどう書きますか?これ突然のメールで申し訳ないです。そしてほんとうに宜しく御願いします。


            御返事を待ちしております。

                             Erik Goughnour


On Tuesday, October 3, 2017, Erik Goughnour <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;e.goughnour@gmail.com&#39;);" target="_blank">e.goughnour@...> wrote:
Yasu is CC’d now.   The user email listed in GitHub matches the last git log entry’s email.

On Tuesday, October 3, 2017, Baptiste Mathus <[hidden email]> wrote:
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <[hidden email]>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-TTBeCEWnf4%2Be30QdBxpgXr%3DMmV%3DXPVRAMX5K%3DY0s8_Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Baptiste MATHUS-3
Well, technically if you read the link I provided, we would usually wait again ~13 days, given IIUC you've CCed Yasu yesterday (?).

2017-10-05 16:17 GMT+02:00 Erik Goughnour <[hidden email]>:
Requesting commit access again.  

Surely the touchstones are all giving favorable indications by now.

Elapsed time, respect, courtesy, required information, multiple attempts to contact—was there anything else?

Thanks,
Erik


On Wednesday, October 4, 2017, Erik Goughnour <[hidden email]> wrote:

斎藤ヤスユキ様


始めまして。ところでお名前の漢字はどう書きますか?これ突然のメールで申し訳ないです。そしてほんとうに宜しく御願いします。


            御返事を待ちしております。

                             Erik Goughnour


On Tuesday, October 3, 2017, Erik Goughnour <[hidden email]> wrote:
Yasu is CC’d now.   The user email listed in GitHub matches the last git log entry’s email.

On Tuesday, October 3, 2017, Baptiste Mathus <[hidden email]> wrote:
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <[hidden email]>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-TTBeCEWnf4%2Be30QdBxpgXr%3DMmV%3DXPVRAMX5K%3DY0s8_Lw%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5T-znusKLPdLow83DzxqQTMfLLpV4v3Naa-Obuk7%2BswQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour
 I did read the link.  I had actually read it (along with quite a bit of the rest of the documentation) before I created the PR that I was trying to merge.  There is evidence of this. Notice I tagged the PR per the documentation and that was 11 days ago.

The first message I forwarded to Yasu from the thread was 9 or 10 days ago. The lack of response was what eventually prompted my third post on the 29th.

I had thought the absence of recent activity might have allowed for a shorter timeline.

Of course I can wait for whatever length of time seems best.  If this simply has to be tabled until 17 or 18 October that’s fine.  Let me know what you think.


On Thursday, October 5, 2017, Baptiste Mathus <[hidden email]> wrote:
Well, technically if you read the link I provided, we would usually wait again ~13 days, given IIUC you've CCed Yasu yesterday (?).

2017-10-05 16:17 GMT+02:00 Erik Goughnour <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;e.goughnour@gmail.com&#39;);" target="_blank">e.goughnour@...>:
Requesting commit access again.  

Surely the touchstones are all giving favorable indications by now.

Elapsed time, respect, courtesy, required information, multiple attempts to contact—was there anything else?

Thanks,
Erik


On Wednesday, October 4, 2017, Erik Goughnour <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;e.goughnour@gmail.com&#39;);" target="_blank">e.goughnour@...> wrote:

斎藤ヤスユキ様


始めまして。ところでお名前の漢字はどう書きますか?これ突然のメールで申し訳ないです。そしてほんとうに宜しく御願いします。


            御返事を待ちしております。

                             Erik Goughnour


On Tuesday, October 3, 2017, Erik Goughnour <[hidden email]> wrote:
Yasu is CC’d now.   The user email listed in GitHub matches the last git log entry’s email.

On Tuesday, October 3, 2017, Baptiste Mathus <[hidden email]> wrote:
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <[hidden email]>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.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 <a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;jenkinsci-dev%2Bunsubscribe@googlegroups.com&#39;);" target="_blank">jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-TTBeCEWnf4%2Be30QdBxpgXr%3DMmV%3DXPVRAMX5K%3DY0s8_Lw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to <a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;jenkinsci-dev%2Bunsubscribe@googlegroups.com&#39;);" target="_blank">jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5T-znusKLPdLow83DzxqQTMfLLpV4v3Naa-Obuk7%2BswQ%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-TXHQnbyGUy4SSGKFt4wQPiD4b4QiihjgR8XXExsFBsOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour
Picking this back up again.  Would it still be premature to request commit access?

On Thursday, October 5, 2017, Erik Goughnour <[hidden email]> wrote:
 I did read the link.  I had actually read it (along with quite a bit of the rest of the documentation) before I created the PR that I was trying to merge.  There is evidence of this. Notice I tagged the PR per the documentation and that was 11 days ago.

The first message I forwarded to Yasu from the thread was 9 or 10 days ago. The lack of response was what eventually prompted my third post on the 29th.

I had thought the absence of recent activity might have allowed for a shorter timeline.

Of course I can wait for whatever length of time seems best.  If this simply has to be tabled until 17 or 18 October that’s fine.  Let me know what you think.


On Thursday, October 5, 2017, Baptiste Mathus <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;bmathus@batmat.net&#39;);" target="_blank">bmathus@...> wrote:
Well, technically if you read the link I provided, we would usually wait again ~13 days, given IIUC you've CCed Yasu yesterday (?).

2017-10-05 16:17 GMT+02:00 Erik Goughnour <[hidden email]>:
Requesting commit access again.  

Surely the touchstones are all giving favorable indications by now.

Elapsed time, respect, courtesy, required information, multiple attempts to contact—was there anything else?

Thanks,
Erik


On Wednesday, October 4, 2017, Erik Goughnour <[hidden email]> wrote:

斎藤ヤスユキ様


始めまして。ところでお名前の漢字はどう書きますか?これ突然のメールで申し訳ないです。そしてほんとうに宜しく御願いします。


            御返事を待ちしております。

                             Erik Goughnour


On Tuesday, October 3, 2017, Erik Goughnour <[hidden email]> wrote:
Yasu is CC’d now.   The user email listed in GitHub matches the last git log entry’s email.

On Tuesday, October 3, 2017, Baptiste Mathus <[hidden email]> wrote:
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <[hidden email]>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-TTBeCEWnf4%2Be30QdBxpgXr%3DMmV%3DXPVRAMX5K%3DY0s8_Lw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS5T-znusKLPdLow83DzxqQTMfLLpV4v3Naa-Obuk7%2BswQ%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-QESnEu3rB6ZFn7R5w0MXiuJTqgFFQQNi3xc9MwLrR3Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Commit access to vstestrunner-plugin

Erik Goughnour
Requesting commit access.  By anyone’s count this has now been a sufficient wait.

On Tuesday, October 17, 2017, Erik Goughnour <[hidden email]> wrote:
Picking this back up again.  Would it still be premature to request commit access?

On Thursday, October 5, 2017, Erik Goughnour <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;e.goughnour@gmail.com&#39;);" target="_blank">e.goughnour@...> wrote:
 I did read the link.  I had actually read it (along with quite a bit of the rest of the documentation) before I created the PR that I was trying to merge.  There is evidence of this. Notice I tagged the PR per the documentation and that was 11 days ago.

The first message I forwarded to Yasu from the thread was 9 or 10 days ago. The lack of response was what eventually prompted my third post on the 29th.

I had thought the absence of recent activity might have allowed for a shorter timeline.

Of course I can wait for whatever length of time seems best.  If this simply has to be tabled until 17 or 18 October that’s fine.  Let me know what you think.


On Thursday, October 5, 2017, Baptiste Mathus <[hidden email]> wrote:
Well, technically if you read the link I provided, we would usually wait again ~13 days, given IIUC you've CCed Yasu yesterday (?).

2017-10-05 16:17 GMT+02:00 Erik Goughnour <[hidden email]>:
Requesting commit access again.  

Surely the touchstones are all giving favorable indications by now.

Elapsed time, respect, courtesy, required information, multiple attempts to contact—was there anything else?

Thanks,
Erik


On Wednesday, October 4, 2017, Erik Goughnour <[hidden email]> wrote:

斎藤ヤスユキ様


始めまして。ところでお名前の漢字はどう書きますか?これ突然のメールで申し訳ないです。そしてほんとうに宜しく御願いします。


            御返事を待ちしております。

                             Erik Goughnour


On Tuesday, October 3, 2017, Erik Goughnour <[hidden email]> wrote:
Yasu is CC’d now.   The user email listed in GitHub matches the last git log entry’s email.

On Tuesday, October 3, 2017, Baptiste Mathus <[hidden email]> wrote:
Hello, 

Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit with Git, so just use your local clone and use git log). 
If you're able to show some discussions on GitHub with current maintainer(s) that can also work.
Just try to provide the necessary data and put yourself in our shoes: for now, you only said you would like to get commit rights, and tried to contact the maintainer, but no actual track of this was given anywhere.

For obvious reasons, we don't want to hand over maintenance of a given plugin to someone without making best effort to get feedback from the current maintainer(s), paying basic respect for the time spent.

That does not mean we don't welcome your help, we're grateful you want to take the baton :). Let's just do that in a clean way so that everybody is happy.

Thanks

-- Baptiste

2017-09-29 14:56 GMT+02:00 Erik Goughnour <[hidden email]>:
I forwarded this thread to Yasu as of a few days ago.

 [I have to pause here and admit I am not incredibly familiar with Google Groups.]

Is there a better way to solicit a response?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a3a9ccb-493f-4118-a54b-01c497ab80d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS4wCnOnMWx8d-MvBY66Y6ArQ_AuFj6Ksp9iPTg%3DtK7qdA%40mail.gmail.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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-TTBeCEWnf4%2Be30QdBxpgXr%3DMmV%3DXPVRAMX5K%3DY0s8_Lw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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/NtnBVgM_O-w/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/CANWgJS5T-znusKLPdLow83DzxqQTMfLLpV4v3Naa-Obuk7%2BswQ%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACAiU-Qy-haGeWV%2BSwR3PK29S4tFzJ%3Dm8aZHb9Qz1NU4pD6qiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.