Request to become maintainer of gitlab-branch-source-plugin

Hello, For the Jenkins Google Summer of Code project, the student I am mentoring is requesting to become the maintainer of the following plugin: Name: gitlab-branch-source-plugin Github link: https://github.com/jenkinsci/gitlab-branch-source-plugin Jenkins JIRA names: jequals5 and baymac

Request to become maintainer of Dependency Graph View Plugin

Hi, I extended the [Dependency Graph View Plugin](https://wiki.jenkins.io/display/JENKINS/Dependency+Graph+View+Plugin) to also support Pipeline Jobs. I already filed a [PR](https://github.com/jenkinsci/depgraph-view-plugin/pull/16) which is ready to merge. Unfortunately, the plugin currently

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi all, Cristoph has been pinged on April 20 in this thread.So yes, we can do the permission transfer. I have granted permissions to Kai-Hsiang and Tony. Kai-Hsiang is also a default assignee in JIRA now. In order to do a release, you will also need to update

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi Daniel, it seems no response from the owner, maybe we can start the process? Alexander Link於 2018年4月27日星期五 UTC+8下午2時55分19秒寫道： > > Hi, > > I collected all open review comments: > https://github.com/sap-production/parameterized-remote-trigger-plugin/issues/20 > We will check the urgency and

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi, I collected all open review comments: https://github.com/sap-production/parameterized-remote-trigger-plugin/issues/20 We will check the urgency and process the urgent ones. But in general we are using the plugin productively and never had severe issues. Minor bugs (recognized in our

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi Alex, If this version has been tested & run for 2 years in your company, I think it's okay to just apply this huge PR and refine the code quality & the comments later. But this is just my opinion, I'm not the maintainer. 2018-04-24 20:22 GMT+08:00 'Alexander Link' via Jenkins Developers <

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi Tony, We incorporated much of the feedback by Oleg (thanks again for the review!), but yes, I think there are still some unprocessed comments (those without +1 marker). We need to decide how urgent they are - currently we are not working on them due to capacity reasons. Nevertheless you

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

I did spend some time looking at that PR, but it appears as though there is still work to be done on it, or at least, changes requested. Is that not the case? I got a little lost trying to figure out what was still to be done. Tony On Tue, Apr 24, 2018 at 12:18 PM, 'Alexander Link' via Jenkins

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi, as Oleg mentioned we did many changes to this plugin in the last 2 years – in our fork unfortunately, since contribution did not work due to missing maintainers. You find *all* changes in our openSource branch:

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

I would like to point out that there is a major work being done on Pipeline compatibility in https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/32 . It would be great to invite Alejandra Ferreiro Vidal and Alexander Link to this discussion. Will do that. BR, Oleg On

Re: Request to become maintainer of the statistics-gatherer-plugin

Hi Luca, Please also take a look at the Daniel's comment. It really makes sense to ping the maintainer via another email before doing the release, just in case. Seems I missed Daniel's comment and expedited the permission transfer a bit. My apologies for that. My proposal would be to... -

Re: Request to become maintainer of the statistics-gatherer-plugin

Oh gosh, this is the messy GitHub PRs :-( I had actually two requests in the pipeline but when you create two PRs in a chain ... GitHub messes them up. Let me fix it manually and re-push. Luca. > On 24 Apr 2018, at 09:15, Oleg Nenashev wrote: > > Hi Luca, > > Thanks

Re: Request to become maintainer of the statistics-gatherer-plugin

Hi Luca, Thanks for the ping! Access to the repo granted. Regarding the release permissions, something is wrong in https://github.com/jenkins-infra/repository-permissions-updater/pull/670 . It refers another plugin you have created recently, but not Statistics gatherer. BR, Oleg On Tuesday,

Re: Request to become maintainer of the statistics-gatherer-plugin

Any updates? The timeout ended yesterday and we got no further feedback from the current maintainer. Thank you. Luca. > On 19 Apr 2018, at 22:48, Oleg Nenashev wrote: > > +1. If there is no response, let's transfer ownership once the response > timeout expires > >

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

@Tony, thx for the cc. github id: cashlalala Jenkins JIRA id: cashlalala Tony Noble於 2018年4月20日星期五 UTC+8下午8時41分52秒寫道： > > I'll happily co-maintain if required. There's a PR needing to be merged > to make it work with CSRF protection (that I've suggested a minor change > to) that really could

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

I'll happily co-maintain if required. There's a PR needing to be merged to make it work with CSRF protection (that I've suggested a minor change to) that really could do with being applied, amongst others. Christoph shows as last person to make any git commits, so I've cc'd him. Tony github

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

> On 20. Apr 2018, at 03:51, Kai-Hsiang Chang wrote: > > this plugin hasn't been updated for at least 2 years, > > I'd like to ask the permission to maintain the plugin. > > please help me with that. > Please follow the instructions from

Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi All, this plugin hasn't been updated for at least 2 years, I'd like to ask the permission to maintain the plugin. please help me with that. Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: Request to become maintainer of the statistics-gatherer-plugin

+1. If there is no response, let's transfer ownership once the response timeout expires On Thursday, April 19, 2018 at 12:54:04 PM UTC+2, lucamilanesio wrote: > > Sounds good, thanks for the feedback. > > Luca > > > On 19 Apr 2018, at 11:53, Daniel Beck > wrote: > > > >

Re: Request to become maintainer of the statistics-gatherer-plugin

Sounds good, thanks for the feedback. Luca > On 19 Apr 2018, at 11:53, Daniel Beck wrote: > > >> On 19. Apr 2018, at 09:55, Luca Milanesio wrote: >> >> am I following the right process to get access to the statistics-gatherer >> plugin? >> It is

Re: Request to become maintainer of the statistics-gatherer-plugin

> On 19. Apr 2018, at 09:55, Luca Milanesio wrote: > > am I following the right process to get access to the statistics-gatherer > plugin? > It is over two weeks that PRs for important bug-fixes are stuck. > > I am really close to fork it, which could create

Re: Request to become maintainer of the statistics-gatherer-plugin

Hi Daniel, Oleg, am I following the right process to get access to the statistics-gatherer plugin? It is over two weeks that PRs for important bug-fixes are stuck. I am really close to fork it, which could create confusion in people discovering it through the Plugin Manager in Jenkins. Thanks

Re: Request to become maintainer of the statistics-gatherer-plugin

Ping @Admins of the JenkinsCI org :-) > On 18 Apr 2018, at 10:05, Luca Milanesio wrote: > > Any news on this request? > > I would wait a couple of days more and if there is no movement, I'll have no > choice but forking it :-( > I agree with Daniel, forking would

Re: Request to become maintainer of the statistics-gatherer-plugin

Any news on this request? I would wait a couple of days more and if there is no movement, I'll have no choice but forking it :-( I agree with Daniel, forking would create confusion. However, having a plugin that extract statistics and is up-to-date with Jenkins 2.0 and Pipelines is definitely

Re: Request to become maintainer of the statistics-gatherer-plugin

I have create the PR https://github.com/jenkins-infra/repository-permissions-updater/pull/670 to request permissions to upload new versions of the artifacts. Is there a form or a similar process to add permissions to the GitHub repository? It has been 14 days (2 weeks) that I tried to get in

Re: Request to become maintainer of the statistics-gatherer-plugin

Hi all, the PR has been waiting for 13 days now (see https://github.com/jenkinsci/statistics-gatherer-plugin/pull/4 ) and still no news from the current maintainer :-( Can we process my request this week? As discussed, I would

Re: Request to become maintainer of the statistics-gatherer-plugin

PIng ... any news from the current Maintainers? Are we set for end of next week to make a decision on this? Luca. > On 10 Apr 2018, at 08:07, Luca Milanesio wrote: > > 2 weeks sound good to me, and yes, I always avoid forks :-) > > Luca. > >> On 10 Apr 2018, at

Re: Request to become maintainer of the statistics-gatherer-plugin

2 weeks sound good to me, and yes, I always avoid forks :-) Luca. > On 10 Apr 2018, at 08:02, Joseph P wrote: > > Usually the wait period is 2 weeks :) I would not recommend creating another > plugin. > > -- > You received this message because you are subscribed to the

Re: Request to become maintainer of the statistics-gatherer-plugin

Usually the wait period is 2 weeks :) I would not recommend creating another plugin. -- 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

Re: Request to become maintainer of the statistics-gatherer-plugin

> On 10. Apr 2018, at 08:45, Luca Milanesio wrote: > > What is the wait time for getting this escalated and giving the possibility > to fix bugs on the plugin? > Alternatively, should I just submit a brand-new plugin proposal? (which could > cause confusion: people

Re: Request to become maintainer of the statistics-gatherer-plugin

PIng ... any feedback from the current maintainer? What is the wait time for getting this escalated and giving the possibility to fix bugs on the plugin? Alternatively, should I just submit a brand-new plugin proposal? (which could cause confusion: people may not know which one is "active")

Re: Request to become maintainer of the statistics-gatherer-plugin

> On 9 Apr 2018, at 11:01, Daniel Beck wrote: > > >> On 9. Apr 2018, at 09:15, Luca Milanesio wrote: >> >> a) His e-mail is not public, not even to the members of the JenkinsCI org >> b) He doesn't respond to mentions in GitHub >> >> Does anybody

Re: Request to become maintainer of the statistics-gatherer-plugin

> On 9. Apr 2018, at 09:15, Luca Milanesio wrote: > > a) His e-mail is not public, not even to the members of the JenkinsCI org > b) He doesn't respond to mentions in GitHub > > Does anybody have a pointer or address to reach him? For future reference, the way I

Re: Request to become maintainer for docker-custom-build-environment-plugin

On Fri, Feb 16, 2018 at 8:17 PM, Jon Hermansen wrote: > I'll look into the integration when I can. If you have any > pointers on where to start, that would be helpful and much appreciated. As noted here:

Re: Request to become maintainer for docker-custom-build-environment-plugin

Thanks Jesse. I'll look into the integration when I can. If you have any pointers on where to start, that would be helpful and much appreciated. On Feb 15, 2018 9:29 AM, "Jesse Glick" wrote: Posting here was correct. I was just adding a parenthetical comment about

Re: Request to become maintainer for docker-custom-build-environment-plugin

Posting here was correct. I was just adding a parenthetical comment about extending a bug fix I had developed to work with this plugin as well; you can disregard my message. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: Request to become maintainer for docker-custom-build-environment-plugin

Hey Jesse, I'm not sure exactly what you mean. I'm managing Docker credentials using environment variables already, but I know this plugin does make use of some of docker-commons. I'm trying to get an existing functional bug fixed ( https://issues.jenkins-ci.org/browse/JENKINS-34403 ), not

Re: Request to become maintainer for docker-custom-build-environment-plugin

BTW if I thought the plugin were maintained I might file an integration with https://github.com/jenkinsci/docker-commons-plugin/pull/67 (probably easy). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Request to become maintainer for docker-custom-build-environment-plugin

Hi, I'm a long time user of Jenkins. I've been involved somewhat in the community (was co-organizer of Los Angeles Jenkins Meetup), I've also submitted some minor bug fixes to various plugins on GitHub. Just yesterday, I ran into a bug in this plugin at $work, found that there's a PR open to

Re: Request to become maintainer

Marco, Thank you for volunteering to work on the CppCheck plugin. Do you have any plans to make a new release soon? There is an annoying bug (JENKINS-42727) that recently got fixed in the CppCheck repo, but it has not made it into a release yet. Thanks, Jack On Monday, January 2, 2017 at

Re: Request to become maintainer on docker-plugin

2017-09-06 16:15 GMT+02:00 Jesse Glick : > On Tue, Sep 5, 2017 at 8:28 PM, Oleg Nenashev > wrote: > > […] while it's still compatible with Docker Plugin use-cases > > One of my reservations about both the `docker-plugin` and the >

Re: Request to become maintainer on docker-plugin

On Tue, Sep 5, 2017 at 8:28 PM, Oleg Nenashev wrote: > […] while it's still compatible with Docker Plugin use-cases One of my reservations about both the `docker-plugin` and the `yet-another-docker-plugin` (BTW both incorrectly include `-plugin` in the `artifactId`) is

Re: Request to become maintainer on docker-plugin

I still plan to work on docker-slaves plugin, but if possible I indeed would like to introduce some bits from it into docker-plugin. Typically ability to create an agent by combining containers. But too early to tell you more until I've spent some more hours in docker-plugin codebase :P

Re: Request to become maintainer on docker-plugin

@Nicolas - Interestingly out of the Docker plugin implementations I've tried so far, https://github.com/jenkinsci/docker-slaves-plugin has come closest to working the way I'd expect. Do you see that you'd roll some of that work into the Docker plugin or do it going down a completely different

Re: Request to become maintainer on docker-plugin

As Nigel gave his +1, I went ahead and made you committer Nicolas. Remember to file the necessary PR on https://github.com/jenkins-infra/repository-permissions-updater if/when you want to release. I tend to agree with Oleg, probably some cleanup already occurred in YAD, but also agreed it's a

Re: Request to become maintainer on docker-plugin

Please - go for it. I don't have the bandwidth these days to support it in anything like a timely manner. On Tue, 5 Sep 2017 at 18:20, nicolas de loof wrote: > Hi folks, > > docker-plugins as 20 pull requests pending for review and no new commits > since Nov 16th. > I

Re: Request to become maintainer on docker-plugin

Hi, >From the quality PoV, I would really suggest deprecating Docker plugin and recommending Yet Another Docker plugin instead. That plugin progressed much more in terms of stability and Cloud API "implementation correctness" while it's still compatible with Docker Plugin use-cases. Working on

Request to become maintainer on docker-plugin

Hi folks, docker-plugins as 20 pull requests pending for review and no new commits since Nov 16th. I volunteer to adopt this plugin. Especially I'd like to have docker-plugin support docker swarm mode, so it can distribute builds on a cluster out of the box. Github-ID: ndeloof Jenkins-ID:

Re: Request to become maintainer for CloudBees Docker Custom Build Environment Plugin

>From the community standpoint the request is perfectly valid. If nobody votes against till June 17, we will be able to transfer the ownership. I have CC Patrick Wolf (CloudBees Product Manager) just to give him a chance to comment if CloudBees wants to maintaining the plugin. Best regards,

Re: Request to become maintainer for CloudBees Docker Custom Build Environment Plugin

I for one would welcome a maintainer for that plugin. I am currently trying to decide between this plugin and the Docker Slaves plugin for what I am working on. Both plugins would need me to put in some work to be usable, and having a maintainer definitely counts on the pro side for this

Request to become maintainer for CloudBees Docker Custom Build Environment Plugin

The CloudBees Docker Custom Build Environment Plugin is currently looking for adoption. I have a Pull Request out that has been approved by past maintainers but was told that no one is currently

Re: Request to become maintainer

Just out of curiosity: wouldn’t it make more sense to copy the parser (https://github.com/jenkinsci/cppcheck-plugin/blob/master/src/main/java/com/thalesgroup/hudson/plugins/cppcheck/parser/CppcheckParser.java

Re: Request to become maintainer

Hello, As the plugin was already marked orphaned, I've gone ahead and made you committer on the GitHub repo and the lead of the JIRA component. You should have received an invitation and you MUST accept it to be granted the permissions. Please, start slowly, use PR and request reviews. Also

Request to become maintainer

Hi, I would like become a maintainer - especially for the cppcheck plugin since I would like to extend it to support https://issues. jenkins-ci.org/browse/JENKINS-35096. I've already done the implementation and would like to get some review on it... Github-ID: marcosteffan Jenkins-ID:

Request to become maintainer of SCM Sync plugin

Hi, Plugin: https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin https://github.com/jenkinsci/scm-sync-configuration-plugin GitHub ID: rodrigc I'd like to request to become a maintainer of the SCM Sync plugin. There are some pull requests pending which fix many issues

Re: Request to become maintainer of SCM Sync plugin

ns-ci.org/> community member & plugin commiter On Tue, Nov 10, 2015 at 9:49 PM, Craig Rodrigues <rodr...@freebsd.org> wrote: > Hi, > > Plugin: > https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin > https://github.com/jenkinsci/scm-sync-configuratio

Re: Request to become maintainer of plugin-usage-plugin

Hi Victor, Since there was a two-week response timeout, I've granted you a commit access to the plugin. Now you should be able to release changes if you feel strongly about them. Best regards, Oleg понедельник, 26 октября 2015 г., 19:27:39 UTC+3 пользователь Victor Martinez написал: > > Any

[adopt-a-plugin] Request to become maintainer on chucknorris-plugin

Hi, As stated on [1], I'm volunteering to take over maintainance of the critically useful chucknorris-plugin [2] listed there. [1] https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin [2] https://wiki.jenkins-ci.org/display/JENKINS/ChuckNorris+Plugin Thanks Cheers -- Baptiste -- You

Re: [adopt-a-plugin] Request to become maintainer on chucknorris-plugin

Awesome, thanks. Made you committer and Jira lead, and removed the note from the plugin page. On 26.10.2015, at 13:55, Baptiste Mathus wrote: > Hi, > > As stated on [1], I'm volunteering to take over maintainance of the > critically useful chucknorris-plugin [2] listed

Re: Request to become maintainer of plugin-usage-plugin

Any update? Thanks On Friday, 9 October 2015 18:57:44 UTC+2, Victor Martinez wrote: > > Hi there, > > I've been waiting for a new release of this plugin, actually my PR was > merged two weeks ago but it was requested in early July, so I wonder > whether this project is abandoned somehow and

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Hi Stefan, I've transferred the ownership to you. You should get an invitation to jenkinsciorg soon. Welcome aboard! -- 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,

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Thx a lot. I'll go on with merging my branch and make a relase soon... Am Freitag, 9. Oktober 2015 19:02:33 UTC+2 schrieb Oleg Nenashev: > > Hi Stefan, > > I've transferred the ownership to you. You should get an invitation to > jenkinsciorg soon. > > Welcome aboard! > -- You received this

Request to become maintainer of plugin-usage-plugin

Hi there, I've been waiting for a new release of this plugin, actually my PR was merged two weeks ago but it was requested in early July, so I wonder whether this project is abandoned somehow and if I can become a new maintainer of this project. @Christian what do you think? -

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Hi there, I'm back now, we can go further with transfering maintainer role... Cheers, Stefan Oleg Nenashev schrieb am Mo., 28. Sep. 2015 um 13:46 Uhr: > It should be better than releasing a new version and then dissapearing for > a while :) > Regressions may happen with

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Hi, my jira id is slorenz and github id is sisao. I'll be afk for the next 10 days so the merge and a new plugin release have to wait a few more days :-) Greetings, Stefan Oleg Nenashev schrieb am So., 27. Sep. 2015 21:52: > Hi Stefan, > > We commonly grant permissions

Re: Request to become maintainer of SeleniumHtmlReportPublisher

It should be better than releasing a new version and then dissapearing for a while :) Regressions may happen with any plugin, so it's better to monitor the situation after the release. понедельник, 28 сентября 2015 г., 10:06:47 UTC+3 пользователь Stefan Lorenz написал: > > Hi, > my jira id is

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Hi Stefan, We commonly grant permissions if there is no response from the owner within two weeks. If there is no response by Tuesday, the permissions will be granted. Please specify your GitHub ID and Jenkins JIRA ID. They are required to transfer the permissions четверг, 24 сентября 2015 г.,

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Do I have to request something else or do I just have to wait? 2015-09-15 18:55 GMT+02:00 Stefan Lorenz : > > If there is something to improve or if there are issues to solve, I think > can do that... > > Jglick mentioned that I should ask here for the maintainer role..

Request to become maintainer of SeleniumHtmlReportPublisher

Hi, I recently worked on the SeleniumHtmlReportPublisher plugin to extend it for working together with Workflow plugin. It now implements SimpleBuildStep and has some more tests. The pull request is ready to merge but it seems that the current maintainer has abandoned this project, he also

Re: Request to become maintainer of SeleniumHtmlReportPublisher

If there is something to improve or if there are issues to solve, I think can do that... Jglick mentioned that I should ask here for the maintainer role.. Am Dienstag, 15. September 2015 13:48:25 UTC+2 schrieb Daniel Beck: > > Hi Stefan, > > it looks like the plugin has been abandoned with

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Hi Stefan, it looks like the plugin has been abandoned with the last activity years ago, so that should definitely be possible. Still, CCing the previous maintainer. Just to clarify, you'd like to become maintainer, i.e. work further on improving the plugin rather than just merging your PR

Jenkins admin added you to team Everyone Was: Request to become maintainer

Am Montag, 8. Juni 2015, 11:07:54 schrieb Kohsuke Kawaguchi: Added you as a committer. As a rule of thumb, I'd like to reduce us blocking people who are interested in contributing, so we should grant the commit access in parallel to suggesting to talk to the current maintainer. Just

Re: Jenkins admin added you to team Everyone Was: Request to become maintainer

Am Dienstag, 9. Juni 2015, 21:00:43 schrieb Daniel Beck: What happens when you go to https://github.com/orgs/jenkinsci/teams/everyone and click 'leave'? You’ve successfully left the team. Thanks! I wasn´t aware of that trick. Martin -- Cd wrttn wtht vwls s mch trsr. -- You received this

Re: Jenkins admin added you to team Everyone Was: Request to become maintainer

I made you a committer of just cmakebuilder-plugin now. On 09.06.2015, at 21:09, Martin Weber fifteenknots...@gmail.com wrote: Am Dienstag, 9. Juni 2015, 21:00:43 schrieb Daniel Beck: What happens when you go to https://github.com/orgs/jenkinsci/teams/everyone and click 'leave'? You’ve

Re: Request to become maintainer

@Kohsuke. I disagree with your statement as well. On-request direct push/release permissions will lead to the violation of common plugin development practices (compatibility, core dependencies, etc.). If a person wants to contribute and get the new version ASAP, it's better to provide a review

Re: Request to become maintainer

, 07 Jun 2015 07:49:50 +0200 Subject: Re: Request to become maintainer (2nd try) Hi Martin, since I don't seem to be able to carve out any significant time out of my schedule to do some work on cmakebuilder, it's alright for me if you become maintainer of the plugin. I hereby officially hand

Re: Request to become maintainer

+1 with Daniel Oleg. For a concrete example, I recently processed a PR [1] after it lingered for 12 days (it already happened to stay a bit longer), answered and asked for some rework because I disagreed with the implementation. After some times, I just closed politely the PR. With this policy,

Re: Request to become maintainer

Am Montag, 8. Juni 2015, 12:47:08 schrieb Oleg Nenashev: @Kohsuke. I disagree with your statement as well. On-request direct push/release permissions will lead to the violation of common plugin development practices (compatibility, core dependencies, etc.). If a person wants to contribute

Re: Request to become maintainer

Am Montag, 8. Juni 2015, 11:07:54 schrieb Kohsuke Kawaguchi: Added you as a committer. Thank you, Kohsuke. As a rule of thumb, I'd like to reduce us blocking people who are interested in contributing, so we should grant the commit access in parallel to suggesting to talk to the current

Re: Request to become maintainer

On Jun 8, 2015, at 23:57, Martin Weber fifteenknots...@gmail.com wrote: Am Montag, 8. Juni 2015, 12:47:08 schrieb Oleg Nenashev: @Kohsuke. I disagree with your statement as well. On-request direct push/release permissions will lead to the violation of common plugin development practices

Re: Request to become maintainer

Am Sonntag, 31. Mai 2015, 20:37:05 schrieb Daniel Beck: ... Could you ask the current maintainer again? If he doesn't really have the time to work on it, a confirmation that he's fine with adding you as (co-)maintainer would be good. I did. Volker want to hand over mainainership to me. See

Re: Request to become maintainer

There has been some activity on the Github side of things (wiki still links to SVN, probably because there has not been a release) since my comments in JENKINS-25807. https://github.com/jenkinsci/cmakebuilder-plugin/commits/master Could you ask the current maintainer again? If he doesn't

Re: Request to become maintainer of Exclusive Execution Plugin

I can not see Merge pull request option on my own pull request. Is that option not available and should I directly commit to main branch? [image: Merge pull request button] This is what I see: Add more commits by pushing to the master https://github.com/fmiguelez/exclusive-execution-plugin

Re: Request to become maintainer of Exclusive Execution Plugin

Seems that you did not yet accept the invitation from GitHub to be part of that repo committers… Please check your emails. Am 03.02.2015 um 16:33 schrieb Fernando Miguélez fernando.migue...@gmail.com: I can not see Merge pull request option on my own pull request. Is that option not

Re: Request to become maintainer of Exclusive Execution Plugin

Well I approved pull request and already documented changes in wiki. What should I do so version 0.8 is released? Should I use maven release plugin or is there any automatic mechanism (such as the pull request verification through own Jenkins) that automatically performs plugin release?

Re: Request to become maintainer of Exclusive Execution Plugin

You were right ;-) Pull request merged now. Let's update wiki page. Thank you very much. El martes, 3 de febrero de 2015, 17:06:31 (UTC+1), Ullrich Hafner escribió: Seems that you did not yet accept the invitation from GitHub to be part of that repo committers… Please check your emails.

Re: Request to become maintainer of Exclusive Execution Plugin

Please use mvn release... Am 03.02.2015 um 18:04 schrieb Fernando Miguélez fernando.migue...@gmail.com: Well I approved pull request and already documented changes in wiki. What should I do so version 0.8 is released? Should I use maven release plugin or is there any automatic

Re: Request to become maintainer of Exclusive Execution Plugin

If you would write us your GitHub user name (and the repository name) then we could give you access rights… Am 02.02.2015 um 18:35 schrieb Fernando Miguélez fernando.migue...@gmail.com: Hi admins, After waiting for more than 2 weeks original maintainer of Exclusive Execution Plugin

Re: Request to become maintainer of Exclusive Execution Plugin

Hi Ulli, My github user is fmiguelez and repository is: https://github.com/jenkinsci/exclusive-execution-plugin Regards, Fernando On Mon, Feb 2, 2015 at 9:55 PM, Ulli Hafner ullrich.haf...@gmail.com wrote: If you would write us your GitHub user name (and the repository name) then we could

Re: Request to become maintainer of Exclusive Execution Plugin

Done. Welcome aboard! Ulli Am 02.02.2015 um 23:57 schrieb Fernando Miguélez fernando.migue...@gmail.com: Hi Ulli, My github user is fmiguelez and repository is: https://github.com/jenkinsci/exclusive-execution-plugin https://github.com/jenkinsci/exclusive-execution-plugin Regards,

Request to become maintainer of Exclusive Execution Plugin

Hi admins, After waiting for more than 2 weeks original maintainer of Exclusive Execution Plugin (Marco Ambu) has not responded. The other maintainer (Sam Tavakoli) advised me to ask for commit rights to main branch after submitting and reviewing my pull request. Since there seems to be no

Re: Request to become maintainer

Done. Welcome aboard! Ulli Am 04.01.2015 um 20:07 schrieb Larry Bordowitz lbordow...@yahoo-inc.com: It looks like this project doesn't have any maintainer, it's probably abandoned: https://wiki.jenkins-ci.org/display/JENKINS/LabeledTestGroupsPublisher+Plugin I have a feature that I'd

Request to become maintainer

It looks like this project doesn't have any maintainer, it's probably abandoned: https://wiki.jenkins-ci.org/display/JENKINS/LabeledTestGroupsPublisher+Plugin I have a feature that I'd like to make available, and although the pull request fails, it's probably because the plugin is so old.

Re: Request to become maintainer of the Reverse Proxy Auth. Plugin

Done. Am 02.12.2013 um 09:42 schrieb Wilder Rodrigues wilder.rodrig...@gmail.com: Hi again Dominik, I forgot to mention my GitHub ID - in order to get commit rights -: wilderrodrigues Cheers, Wilder On Saturday, 30 November 2013 17:05:14 UTC+1, Wilder Rodrigues wrote: Hi guys,

Updating the Priority Sorter (request to become maintainer)

Hi, a while back I requested hosting for a new plugin. After some discussion I agreed to try to merge my efforts into the Priority Sorter rather can creating a new, competing, plugin. The changes from my part will include more advanced types of sorting such as Fair Queuing. I'm currently working