Re: [Experiment] Reviewers Team

[Jacob Larfors]

Nice, and thanks for the information.
I was recommended to add jenkinsci code-reviewers but perhaps this is not 
necessary for the low scale plugins I am working on as things have been 
working fine up until now.

PS - I accepted the invitation now to join jenkinsci (email got lost)

On Thursday, 5 January 2017 18:01:36 UTC+2, Daniel Beck wrote:
>
>
> > On 10.08.2016, at 08:42, James Dumay  
> wrote: 
> > 
> > All of the blueocean-plugin PRs mention the reviewers team... so If you 
> are looking to get involved in Blue Ocean reviewing is a great place to 
> start! 
>
> FTR I asked that this practice be stopped a few weeks ago, as it increased 
> the notification traffic a lot, and the BO developers generally seem to 
> have no problem finding reviewers for their changes. 
>
> Now @jenkinsci/code-reviewers should be back to be fairly low traffic and 
> limited to PRs where someone really thinks reviews are needed: 
>
>
> https://github.com/pulls?utf8=%E2%9C%93=is%3Aopen+is%3Apr+team%3Ajenkinsci%2Fcode-reviewers
>  
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/09926995-796e-4a27-a160-0554a2af9665%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Experiment] Reviewers Team

[Jacob Larfors]

Hello,

just checking that the @jenkinsci/code-reviewers 
 group is still 
around? Doesnt seem to exist in GitHub anymore... at least I get a 404 
error not found

https://github.com/orgs/jenkinsci/teams/code-reviewers

I was hoping to get some feedback on a recent pull request 
here: https://github.com/jenkinsci/klocwork-plugin/pull/20

Thanks,
Jacob

On Wednesday, 10 August 2016 09:42:26 UTC+3, James Dumay wrote:
>
> All of the blueocean-plugin PRs mention the reviewers team... so If you 
> are looking to get involved in Blue Ocean reviewing is a great place to 
> start!
>
> On Wednesday, August 10, 2016 at 4:22:56 AM UTC+10, Baptiste Mathus wrote:
>>
>> Small bump: reminder this list 
>>
>> https://github.com/orgs/jenkinsci/teams/code-reviewers
>>
>> is open to *anyone* willing to review Jenkins code in general (core or 
>> plugins). Either you want to grow your skills, or help in general, or both, 
>> this is one good place.
>>
>> Note that being part of that team does *not* require you to review 
>> anything where you get asked to.
>>
>> Le 6 janv. 2016 9:42 PM, "Baptiste Mathus"  a écrit :
>>
>>> Hi everyone,
>>>
>>> If you've already tried to get feedback on a PR you were working on, or 
>>> are interested in helping & learning things by reviewing other's code, read 
>>> on.
>>>
>>> Daniel just helped set up a Jenkinsci GitHub organization new sub-team 
>>> called '*code-reviewers*' to define a group of people willing to try 
>>> and review code at the request of others.
>>>
>>>- If you want to be part of it, click on the right button on that 
>>>page: 
>>>   https://github.com/orgs/jenkinsci/teams/code-reviewers
>>>
>>>- If you want to notify that team (and get reviewed) in a comment, 
>>>use the *@jenkinsci/code-reviewers* form (should autocomplete).
>>>
>>> Here it is. This is something we wanted to try and still very early in 
>>> the process, don't hesitate to tell us what you think of it here or on IRC.
>>>
>>> Hope you find it useful!
>>>
>>> Cheers
>>>
>>> -- Baptiste
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f1a601af-79a9-434b-b3f9-493941e8905f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Thanks for commit access and the information.

Nothing opposed to a fork so lets go with that route to simplify things. The 
people whom I will be sharing work with are colleagues so we can share a fork 
and keep things separate.

Really appreciate all the help.

> On 1 Dec 2016, at 13.19, Daniel Beck <m...@beckweb.net> wrote:
> 
> 
>> On 01.12.2016, at 12:13, Jacob Larfors <ja...@larfors.com> wrote:
>> 
>> Awesome - looks good. Can I also have commit access to this one, or how do 
>> we plan to do this?
>> 
>> My plan was to create an update branch on this repo and then file a pull 
>> request to get this into master and include the Jenkins reviewers as Oleg 
>> suggested.
>> 
>> GitHub user: jlarfors 
> 
> Granted you commit access.
> 
> Plan sounds reasonable if it's supposed to be a branch that multiple people 
> would work on (or if you're opposed to maintaining your own fork), but most 
> probably develop in their own fork first and base PRs on that. It also won't 
> confuse the JIRA bot as it thinks everything in the jenkinsci repos is on 
> master, and even resolves issues based on that :-)
> 
> -- 
> 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/U7SFVsjsHHQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/503C9858-35E9-4770-9913-2BCA949CF01C%40beckweb.net.
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8AA06AD0-4C02-4AD2-8A8F-98454CE177AD%40larfors.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Awesome - looks good. Can I also have commit access to this one, or how do we 
plan to do this?

My plan was to create an update branch on this repo and then file a pull 
request to get this into master and include the Jenkins reviewers as Oleg 
suggested.

GitHub user: jlarfors 

Sent from my iPhone

> On 1 Dec 2016, at 13.02, Daniel Beck <m...@beckweb.net> wrote:
> 
> 
>> On 01.12.2016, at 11:34, Jacob Larfors <ja...@larfors.com> wrote:
>> 
>> All good to delete the jenkinsci/klocwork-plugin-fork repo as it was never 
>> used.
> 
> Done, and transferred the one with issues and PRs:
> 
> https://github.com/jenkinsci/klocwork-plugin
> 
> -- 
> 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/U7SFVsjsHHQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/FE1A646F-3671-4635-B1C0-480BB9E91F60%40beckweb.net.
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/EFB2862A-CE2B-49C0-B530-F664ABBB498E%40larfors.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

 

All good to delete the jenkinsci/klocwork-plugin-fork repo as it was never 
used.

On Thursday, 1 December 2016 12:32:59 UTC+2, Daniel Beck wrote:
>
>
> > On 01.12.2016, at 11:17, Jacob Larfors <ja...@larfors.com > 
> wrote: 
> > 
> > Great, I acknowledge and sounds like a good idea - so please go ahead. 
>
> Hmmm that didn't work… 
>
> "jenkinsci already has a repository in the 
> jenkinsci-transfer/klocwork-plugin network" 
>
> It looks like I'll have to delete the repo we already have (now named 
> klocwork-plugin-fork) first. It doesn't look like it contains anything that 
> the original we're transferring doesn't, but can you please confirm? 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/401b8ce3-8b1c-4f76-87c8-f489f46306cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Great, I acknowledge and sounds like a good idea - so please go ahead.

Thanks,
Jacob

On Wednesday, 30 November 2016 21:03:00 UTC+2, Daniel Beck wrote:
>
>
> > On 28.11.2016, at 17:44, Jacob Larfors <ja...@larfors.com > 
> wrote: 
> > 
> > Awesome, and thanks Daniel & Gregory. 
>
> We have control over the klocwork plugin. It currently resides in 
>
> https://github.com/jenkinsci-transfer/klocwork-plugin 
>
> I'll rename the existing repo and move this one into jenkinsci as soon as 
> you acknowledge; as it'll be the same remote URL in Git and could cause 
> confusion when I do this unexpectedly. 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/776b057a-b65f-4631-a959-aa850a948830%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Hi Oleg,

Awesome, and thanks Daniel & Gregory.

See you tomorrow.

Best Regards,
Jacob

> On 28 Nov 2016, at 17.35, Oleg Nenashev <o.v.nenas...@gmail.com> wrote:
> 
> Hi,
> 
> Just FYI, we have got a reply from Gregory in the separate thread. Now you 
> have an authorization from the original maintainer, hence you can proceed 
> with the release once you are ready.
> 
> See you tomorrow!
> 
> Best regards,
> Oleg
> 
> 2016-11-28 16:20 GMT+01:00 Jacob Larfors <ja...@larfors.com 
> <mailto:ja...@larfors.com>>:
> Hi Oleg,
> 
> That's great - I saw the meeting summary so thanks for bringing this to 
> light. I spoke with our plugin developer on Friday and we will get the plugin 
> updated and ready for release whilst we wait for a reply from gboissinot and 
> prepare a branch on the jenkinsci project ready for a pull request.
> 
> Hopefully see you at the CoDe Conf tomorrow so we can talk about this a bit 
> more.
> 
> Safe travels with Lufthansa.
> 
> Best Regards,
> Jacob
> 
> 
> On Saturday, 26 November 2016 07:58:30 UTC+1, Oleg Nenashev wrote:
> Hi Jacob,
> 
> On Wednesday we agreed with the proposed plan. Here is the meeting summary: 
> http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-11-23-18.00.html
>  
> <http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-11-23-18.00.html>
> 
> We agreed that I and Daniel will make the last attempt to reach out the 
> original plugin maintainers with a final 2-week timeout. If we do not get a 
> response, we will grant you the release permissions, no need in plugin 
> renaming, etc.
> 
> I have granted you push permissions to 
> https://github.com/jenkinsci/klocwork-plugin 
> <https://github.com/jenkinsci/klocwork-plugin>, hence you can start 
> integrating changes there. I kindly recommend to consider using Pull requests 
> and CCing jenkinsci/code-reviewers at the first steps (just to get some 
> knowledge transfer). It is also recommended to update Jenkins core dependency 
> to something newer and to use the new parent POM.
> 
> Best regards,
> Oleg Nenashev 
> 
> 
> 
> среда, 23 ноября 2016 г., 11:19:27 UTC+3 пользователь Jacob Larfors написал:
> Many thanks for helping so much with this. The plan sounds good to me.
> 
> My Jenkinsci account is: jlarfors
> 
> Thanks again,
> Jacob
> 
> On Tuesday, 22 November 2016 18:05:20 UTC+1, Oleg Nenashev wrote:
> I have added the the topic to the agenda of the tomorrow's governance 
> meeting: 
> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Nov23meeting
>  
> <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Nov23meeting>
> 
> Jacob, could you please provide your Jenkinsci account?
> 
> Thanks in advance,
> Oleg
> 
> вторник, 22 ноября 2016 г., 17:44:02 UTC+1 пользователь Oleg Nenashev написал:
> In addition to this thread, I have tried to reach out Gregory directly 
> without success. Since he has left his original company as well as his 
> companion from citools org, it is a low chance we can proceed in the common 
> way.
> 
> I had an f2f discussion with Jacob at Embedded Conference Scandinavia. We 
> discussed the current state and agreed on the following:
> Oleg will grant him an access to the klocwork repository within the jenkinsci 
> organization (an existing repo)
> Jacob will push the current changes in citools org and then proceed with 
> preparing the release in pull requests (he can use jenkinsci/code-reviewers 
> in order to get help with onboarding)
> Oleg will try to reach out Thales directly on behalf of the Jenkins core team 
> (in order to propose the ownership handover)
> If we do not get a response from Thales, we will submit a topic to the 
> Governance meeting with 2 options:
> Fork of a plugin with renaming/package name changes
> Just a takeover of the plugin by the Jenkins community (with temporary 
> revokation of upload permissions for original maintainers to avoid mess if 
> they come back and do not notice this thread)
> WDYT?
> 
> 
> 
> Best regards,
> 
> Oleg
> 
> 
> 
> среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev написал:
> Any revival of this plugin will be appreciated.
> 
> Unfortunately, we cannot just fork the repository and start releasing from 
> it. It may be considered as a highjacking of the plugin. Plugin maintainers 
> commonly do not sign Jenkins CLA, hence we have no formal permission to do so.
> 
> I think we should fork the plugin to jenkinsci and start preparing it to the 
> release with patches (including stuff like CI, 

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Hi Oleg,

That's great - I saw the meeting summary so thanks for bringing this to 
light. I spoke with our plugin developer on Friday and we will get the 
plugin updated and ready for release whilst we wait for a reply from 
gboissinot and prepare a branch on the jenkinsci project ready for a pull 
request.

Hopefully see you at the CoDe Conf tomorrow so we can talk about this a bit 
more.

Safe travels with Lufthansa.

Best Regards,
Jacob

On Saturday, 26 November 2016 07:58:30 UTC+1, Oleg Nenashev wrote:
>
> Hi Jacob,
>
> On Wednesday we agreed with the proposed plan. Here is the meeting 
> summary: 
> http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-11-23-18.00.html
>
> We agreed that I and Daniel will make the last attempt to reach out the 
> original plugin maintainers with a final 2-week timeout. If we do not get a 
> response, we will grant you the release permissions, no need in plugin 
> renaming, etc.
>
> I have granted you push permissions to 
> https://github.com/jenkinsci/klocwork-plugin, hence you can start 
> integrating changes there. I kindly recommend to consider using Pull 
> requests and CCing jenkinsci/code-reviewers at the first steps (just to get 
> some knowledge transfer). It is also recommended to update Jenkins core 
> dependency to something newer and to use the new parent POM.
>
> Best regards,
> Oleg Nenashev 
>
>
>
> среда, 23 ноября 2016 г., 11:19:27 UTC+3 пользователь Jacob Larfors 
> написал:
>>
>> Many thanks for helping so much with this. The plan sounds good to me.
>>
>> My Jenkinsci account is: jlarfors
>>
>> Thanks again,
>> Jacob
>>
>> On Tuesday, 22 November 2016 18:05:20 UTC+1, Oleg Nenashev wrote:
>>>
>>> I have added the the topic to the agenda of the tomorrow's governance 
>>> meeting: 
>>> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Nov23meeting
>>>
>>> Jacob, could you please provide your Jenkinsci account?
>>>
>>> Thanks in advance,
>>> Oleg
>>>
>>> вторник, 22 ноября 2016 г., 17:44:02 UTC+1 пользователь Oleg Nenashev 
>>> написал:
>>>>
>>>> In addition to this thread, I have tried to reach out Gregory directly 
>>>> without success. Since he has left his original company as well as his 
>>>> companion from citools org, it is a low chance we can proceed in the 
>>>> common 
>>>> way.
>>>>
>>>> I had an f2f discussion with Jacob at Embedded Conference Scandinavia. 
>>>> We discussed the current state and agreed on the following:
>>>>
>>>>1. Oleg will grant him an access to the klocwork repository within 
>>>>the jenkinsci organization (an existing repo)
>>>>2. Jacob will push the current changes in citools org and then 
>>>>proceed with preparing the release in pull requests (he can use 
>>>>jenkinsci/code-reviewers in order to get help with onboarding)
>>>>3. Oleg will try to reach out Thales directly on behalf of the 
>>>>Jenkins core team (in order to propose the ownership handover)
>>>>4. If we do not get a response from Thales, we will submit a topic 
>>>>to the Governance meeting with 2 options:
>>>>   - Fork of a plugin with renaming/package name changes
>>>>   - Just a takeover of the plugin by the Jenkins community (with 
>>>>   temporary revokation of upload permissions for original maintainers 
>>>> to 
>>>>   avoid mess if they come back and do not notice this thread)
>>>>   
>>>> WDYT?
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Oleg
>>>>
>>>>
>>>> среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev 
>>>> написал:
>>>>>
>>>>> Any revival of this plugin will be appreciated.
>>>>>
>>>>> Unfortunately, we cannot just fork the repository and start releasing 
>>>>> from it. It may be considered as a highjacking of the plugin. Plugin 
>>>>> maintainers commonly do not sign Jenkins CLA, hence we have no formal 
>>>>> permission to do so.
>>>>>
>>>>> I think we should fork the plugin to jenkinsci and start preparing it 
>>>>> to the release with patches (including stuff like CI, parent POM update, 
>>>>> etc.). If the maintainer does not respond, likely the only valid option 
>>>>> will be to

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Many thanks for helping so much with this. The plan sounds good to me.

My Jenkinsci account is: jlarfors

Thanks again,
Jacob

On Tuesday, 22 November 2016 18:05:20 UTC+1, Oleg Nenashev wrote:
>
> I have added the the topic to the agenda of the tomorrow's governance 
> meeting: 
> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Nov23meeting
>
> Jacob, could you please provide your Jenkinsci account?
>
> Thanks in advance,
> Oleg
>
> вторник, 22 ноября 2016 г., 17:44:02 UTC+1 пользователь Oleg Nenashev 
> написал:
>>
>> In addition to this thread, I have tried to reach out Gregory directly 
>> without success. Since he has left his original company as well as his 
>> companion from citools org, it is a low chance we can proceed in the common 
>> way.
>>
>> I had an f2f discussion with Jacob at Embedded Conference Scandinavia. We 
>> discussed the current state and agreed on the following:
>>
>>1. Oleg will grant him an access to the klocwork repository within 
>>the jenkinsci organization (an existing repo)
>>2. Jacob will push the current changes in citools org and then 
>>proceed with preparing the release in pull requests (he can use 
>>jenkinsci/code-reviewers in order to get help with onboarding)
>>3. Oleg will try to reach out Thales directly on behalf of the 
>>Jenkins core team (in order to propose the ownership handover)
>>4. If we do not get a response from Thales, we will submit a topic to 
>>the Governance meeting with 2 options:
>>   - Fork of a plugin with renaming/package name changes
>>   - Just a takeover of the plugin by the Jenkins community (with 
>>   temporary revokation of upload permissions for original maintainers to 
>>   avoid mess if they come back and do not notice this thread)
>>   
>> WDYT?
>>
>>
>> Best regards,
>>
>> Oleg
>>
>>
>> среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev 
>> написал:
>>>
>>> Any revival of this plugin will be appreciated.
>>>
>>> Unfortunately, we cannot just fork the repository and start releasing 
>>> from it. It may be considered as a highjacking of the plugin. Plugin 
>>> maintainers commonly do not sign Jenkins CLA, hence we have no formal 
>>> permission to do so.
>>>
>>> I think we should fork the plugin to jenkinsci and start preparing it to 
>>> the release with patches (including stuff like CI, parent POM update, 
>>> etc.). If the maintainer does not respond, likely the only valid option 
>>> will be to rename plugin and to change packages to avoid data conflicts. 
>>> But it will require much work to implement the proper migration code.
>>>
>>> I've added Gregory Boissinot to Cc. Maybe he could suggest the proper 
>>> contact.
>>>
>>> BR, Oleg
>>>
>>> вторник, 15 ноября 2016 г., 14:13:29 UTC+1 пользователь Jacob Larfors 
>>> написал:
>>>>
>>>> Ok I tried contacting the other maintainer/user at cittools and his 
>>>> email address for Thales does not work, so I suspect he has left Thales. 
>>>> As 
>>>> there has also been an outstanding pull request since July, and our 
>>>> attempts to contact the people at cittools has failed, I would assume this 
>>>> repository is no longer taken care of...
>>>>
>>>> What options do we have? Can we make the jenkinsci repository the 
>>>> "main" one and we will get our commits there? There arent really any valid 
>>>> PRs/FRs in Jira, and the few that are we could look to transfer or fix, as 
>>>> we quite actively work on this plugin and have been shipping hpi files for 
>>>> the past few years to avoid this mess and bottleneck of waiting for 
>>>> cittools.
>>>>
>>>> Thanks for the help.
>>>>
>>>> Jacob
>>>>
>>>> On Tuesday, 15 November 2016 14:59:06 UTC+2, Jacob Larfors wrote:
>>>>>
>>>>> Hi Daniel, appreciate the quick feedback and thanks for the info - 
>>>>> that answered another question I had about why the jenkinsci repo even 
>>>>> existed.
>>>>>
>>>>> I would prefer to use the jenkinsci repo to avoid any future 
>>>>> issues/bottlenecks. I have made one last attempt at contacting cittools 
>>>>> because we tried contacting the owner of the repository for some time now 
>>>>> (

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Ok I tried contacting the other maintainer/user at cittools and his email 
address for Thales does not work, so I suspect he has left Thales. As there 
has also been an outstanding pull request since July, and our attempts to 
contact the people at cittools has failed, I would assume this repository 
is no longer taken care of...

What options do we have? Can we make the jenkinsci repository the "main" 
one and we will get our commits there? There arent really any valid PRs/FRs 
in Jira, and the few that are we could look to transfer or fix, as we quite 
actively work on this plugin and have been shipping hpi files for the past 
few years to avoid this mess and bottleneck of waiting for cittools.

Thanks for the help.

Jacob

On Tuesday, 15 November 2016 14:59:06 UTC+2, Jacob Larfors wrote:
>
> Hi Daniel, appreciate the quick feedback and thanks for the info - that 
> answered another question I had about why the jenkinsci repo even existed.
>
> I would prefer to use the jenkinsci repo to avoid any future 
> issues/bottlenecks. I have made one last attempt at contacting cittools 
> because we tried contacting the owner of the repository for some time now 
> (gboissinot) with no luck.
>
> Should this not work, is there some way we can push our commits to the 
> jenkinsci repository and make this the one linked in Jenkins (i.e. make the 
> cittools repo redundant)? I assume that can be done without needing 
> cittools, but I will await a response from them out of courtesy.
>
> Thanks,
> Jacob
>
> On Tuesday, 15 November 2016 14:46:39 UTC+2, Daniel Beck wrote:
>>
>> We cannot grant access to repositories outside the jenkinsci GitHub 
>> organization. Which is one of the reasons why we strongly recommend that 
>> plugins be maintained in that organization. 
>>
>> We can only grant access to https://github.com/jenkinsci/klocwork-plugin 
>> and you'd need to sync the existing commits over. This however will not 
>> transfer existing issues and PRs in the cittools repo. IOW, it's a giant 
>> clusterfuck thanks to maintainers maintaining elsewhere. 
>>
>> I recommend you contact cittools and coordinate what to do with them. I 
>> can then transfer the repo as needed, and delete the one in jenkinsci that 
>> appears to have never been used. 
>>
>> > On 15.11.2016, at 12:58, Jacob Larfors <ja...@larfors.com> wrote: 
>> > 
>> > Hi guys, 
>> > 
>> > Maybe someone can help me out, but a few weeks back I posted about 
>> commit access to the Klocwork plugin, following a pull request for a 
>> colleague, and neither have been answered... We really want to push some 
>> great features out there but our hands our tied :) 
>> > 
>> > If anyone knows how who to contact to get some action or even to apply 
>> for a transferral of ownership for a plugin that would be great. 
>> > 
>> > This is the plugin in question: 
>> https://github.com/cittools/klocwork-plugin 
>> > 
>> > My github account: jlarfors 
>> > 
>> > Thanks for the help! 
>> > 
>> > Jacob 
>> > 
>> > -- 
>> > 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/973c8a41-aac1-4c5f-a76e-5091bb8f3cee%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/afe264e9-b0d9-463e-b964-9b892aa3b70f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Hi Daniel, appreciate the quick feedback and thanks for the info - that 
answered another question I had about why the jenkinsci repo even existed.

I would prefer to use the jenkinsci repo to avoid any future 
issues/bottlenecks. I have made one last attempt at contacting cittools 
because we tried contacting the owner of the repository for some time now 
(gboissinot) with no luck.

Should this not work, is there some way we can push our commits to the 
jenkinsci repository and make this the one linked in Jenkins (i.e. make the 
cittools repo redundant)? I assume that can be done without needing 
cittools, but I will await a response from them out of courtesy.

Thanks,
Jacob

On Tuesday, 15 November 2016 14:46:39 UTC+2, Daniel Beck wrote:
>
> We cannot grant access to repositories outside the jenkinsci GitHub 
> organization. Which is one of the reasons why we strongly recommend that 
> plugins be maintained in that organization. 
>
> We can only grant access to https://github.com/jenkinsci/klocwork-plugin 
> and you'd need to sync the existing commits over. This however will not 
> transfer existing issues and PRs in the cittools repo. IOW, it's a giant 
> clusterfuck thanks to maintainers maintaining elsewhere. 
>
> I recommend you contact cittools and coordinate what to do with them. I 
> can then transfer the repo as needed, and delete the one in jenkinsci that 
> appears to have never been used. 
>
> > On 15.11.2016, at 12:58, Jacob Larfors <ja...@larfors.com > 
> wrote: 
> > 
> > Hi guys, 
> > 
> > Maybe someone can help me out, but a few weeks back I posted about 
> commit access to the Klocwork plugin, following a pull request for a 
> colleague, and neither have been answered... We really want to push some 
> great features out there but our hands our tied :) 
> > 
> > If anyone knows how who to contact to get some action or even to apply 
> for a transferral of ownership for a plugin that would be great. 
> > 
> > This is the plugin in question: 
> https://github.com/cittools/klocwork-plugin 
> > 
> > My github account: jlarfors 
> > 
> > Thanks for the help! 
> > 
> > Jacob 
> > 
> > -- 
> > 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/973c8a41-aac1-4c5f-a76e-5091bb8f3cee%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5ba62706-bc9a-44c5-bdd3-c821a10b4c7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Hi guys,

Maybe someone can help me out, but a few weeks back I posted about commit 
access to the Klocwork plugin, following a pull request for a colleague, 
and neither have been answered... We really want to push some great 
features out there but our hands our tied :)

If anyone knows how who to contact to get some action or even to apply for 
a transferral of ownership for a plugin that would be great.

This is the plugin in question: https://github.com/cittools/klocwork-plugin

My github account: jlarfors

Thanks for the help!

Jacob

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/973c8a41-aac1-4c5f-a76e-5091bb8f3cee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Klocwork Plugin commit access

[Jacob Larfors]

Hello,

myself and a colleague have a pull request for the Klocwork Jenkins plugin 
that has not been responded to. We have tried contacting the owner but 
cannot get hold of him.
Repository: https://github.com/jenkinsci/klocwork-plugin

Requesting commit access to this repository as we actively maintain this 
plugin in a separate repository and currently provide .hpi files for new 
versions with fixes / new features that we would gladly like to merge & 
share with the wider world.

Github account: jlarfors

Thanks for the help!

Jacob

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/aa3debf4-685f-4554-b8c5-f7cdebccdf08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.