Re: Jenkins Governance meeting on Nov 20

[Oleg Nenashev]

Last time we agreed to do LTS selection in the mailing list. I see no
particular reason to return back to the original process, because there are
only few people who show up at governance meetings at the moment. But we
can add this topic if Oliver votes for it.

I can also run a meeting on Nov 27 if we need it

On Tue, Nov 12, 2019, 23:47 James Nord  wrote:

> is it also too early for LTS.next selection?
>
> --
> 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/jnw3pG892yo/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/ab46071f-29cb-4d90-8640-b9159b05d702%40googlegroups.com
> .
>

-- 
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/CAPfivLAdXf%3DgAi0AcQqMEa8f_SggupR5fP9%2Bop3sSj-L11RBjw%40mail.gmail.com.

Re: [throttle-concurrents] Add basil to throttle-concurrents

[Oleg Nenashev]

+1 from me, thanks Basil!
The plan sounds good to me. I wish I could help more with the knowledge
transfers, but I am not sure how much time I will have for it.

BR, Oleg


On Wed, Nov 13, 2019, 00:53 Basil Crow  wrote:

> The last link should have been:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/1325
>
> On Tue, Nov 12, 2019 at 3:52 PM Basil Crow  wrote:
> >
> > I would like to become a maintainer of throttle-concurrents, at
> > minimum to release jenkinsci/throttle-concurrent-builds-plugin#57 and
> > jenkinsci/throttle-concurrent-builds-plugin#58.
> >
> > I have written the following proposal regarding how to mitigate risk
> > as this plugin transitions to a maintained state:
> >
> https://github.com/jenkins-infra/repository-permissions-updater/pull/1308
> >
> > Thanks,
> > Basil
>

-- 
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/CAPfivLB9fXUR2K777AHaRMeQwmXKd%3DuO_Api9-4m6HVjr1NT%2BQ%40mail.gmail.com.

Re: [throttle-concurrents] Add basil to throttle-concurrents

[Basil Crow]

The last link should have been:
https://github.com/jenkins-infra/repository-permissions-updater/pull/1325

On Tue, Nov 12, 2019 at 3:52 PM Basil Crow  wrote:
>
> I would like to become a maintainer of throttle-concurrents, at
> minimum to release jenkinsci/throttle-concurrent-builds-plugin#57 and
> jenkinsci/throttle-concurrent-builds-plugin#58.
>
> I have written the following proposal regarding how to mitigate risk
> as this plugin transitions to a maintained state:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/1308
>
> Thanks,
> Basil

-- 
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/CAFwNDjokxRDuTf5OX4vhTYkyWKYxDxput7nArZDByjAuRTEUPg%40mail.gmail.com.

[throttle-concurrents] Add basil to throttle-concurrents

[Basil Crow]

I would like to become a maintainer of throttle-concurrents, at
minimum to release jenkinsci/throttle-concurrent-builds-plugin#57 and
jenkinsci/throttle-concurrent-builds-plugin#58.

I have written the following proposal regarding how to mitigate risk
as this plugin transitions to a maintained state:
https://github.com/jenkins-infra/repository-permissions-updater/pull/1308

Thanks,
Basil

-- 
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/CAFwNDjpiL9oA6QvbjWkUucGxJUYMMUYo8kAHkTLWeVcop2-rXw%40mail.gmail.com.

2019 Elections: voting has begun

[Kohsuke Kawaguchi]

The voting has begun! It'll remain open until Nov 24th 5pm PT.

If you have already registered, you should see 3 email in your box for 3
positions that are contended. Please follow the link in those emails to
cast your vote. If you haven't registered, you should have already received
emils to solicit your registration.


-- 
Kohsuke Kawaguchi

-- 
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/CAN4CQ4yxaxnLwXKC7TCDpCRheCc%3DgDEp3ciZJMfF%3De2yrR5tJQ%40mail.gmail.com.

Re: 2019 Elections: voting is delayed

[Kohsuke Kawaguchi]

I've updated the nominee personal statement

to reflect the withdrawal of Tracy.

On Mon, Nov 11, 2019 at 11:50 AM Tracy Miranda 
wrote:

> Marky - thanks for the kind words.
>
> Olivier - thanks for the detailed stats - 730 registered, 
> Somehow I also find the 0.01% spam reports strangely comforting - we spend
> a non-zero amount of time worrying how best not to be spammy - good to see
> it is worth worrying about but the numbers put it in the right perspective.
>
> Tracy
>
> On Sat, Nov 9, 2019 at 11:34 AM Olblak  wrote:
>
>> Hey,
>> Some updates with the actual campaign to identify contributors interested
>> by participating to the election
>>
>> Currently they are 730 people who successfully registered for the next
>> stage
>>
>> And here some stats from Sendgrid regarding all the emails sent since
>> yesterday, obviously those numbers should still evolve.
>> So it's too early to take conclusion
>>
>> 90,684: Requests
>> 9,316: Bounces
>> 80,971: Delivered
>> 13,734: Unique Opens
>> 974: Unique Clicks
>> 611: Unsubscribes
>> 6: Spam Reports
>>
>>
>> ---
>> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>> ---
>>
>>
>> On Fri, Nov 8, 2019, at 7:54 PM, Marky Jackson wrote:
>>
>> This is an admirable thing to do Tracy and speaks immensely to your
>> dedication to this project and as a leader, *I HUGELY ADMIRE YOU*
>>
>> On Friday, November 8, 2019 at 6:28:29 AM UTC-8, Tracy Miranda wrote:
>>
>> Hi all,
>>
>> Here's a post on jenkins.io with election update
>> https://jenkins.io/blog/2019/11/08/board-elections/ and what to expect
>> next.
>> Thanks to Mark Waite for helping with this & Oleg for reviews.
>>
>> Also I have withdrawn my candidacy for a board seat as I am doing a bunch
>> behind the scenes with voter registration, etc and would like to stay
>> focussed on overseeing the election process fairly.
>> I expect in my role as CDF board member to work closely with the new
>> board and help out wherever I can to keep things moving forward in Jenkins.
>>
>> Tracy
>>
>> On Mon, Nov 4, 2019 at 2:37 PM Tracy Miranda 
>> wrote:
>>
>> Hi all,
>>
>> We're now in a good position to start sending out voter registration
>> emails. Please look out for an email from electi...@jenkins.io with the
>> title ‘2019 Jenkins Election - Invitation to Participate’.
>> The email will have details on how to register to vote for the elections.
>> Please note we will likely be sending out emails in batches so over the
>> course of the next few days.
>> Once they are all sent I will confirm on the dev list so we can
>> troubleshoot for anyone who has not received an email.
>> Thanks again to Olivier for pulling together a lot of the pieces to make
>> this happen!
>>
>> Thanks,
>> Tracy
>>
>>
>> On Fri, Nov 1, 2019 at 11:47 AM Olblak  wrote:
>>
>> Hi Daniel,
>>
>> As far as I know, there is no jira ticket and it's a good point that we
>> should have that
>> As I said several days ago, I wrote a simple application to collect email
>> and we are testing that approach at the moment with a a small group of
>> people. Basically they received an email inviting them to participate to
>> the election
>>
>> To recall the process
>>
>> Step 1:
>> We send an email to every jenkins account containing a link to '
>> https://polls.jenkins.io/#/participate', mentioning your email account,
>> your unique token, and and poll id
>> Step2:
>> After a period, every members who confirmed there participation, are
>> invited in the Condorcet tool to participate to the election.
>>
>>
>> ---
>> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>> ---
>>
>> On Fri, Nov 1, 2019, at 2:30 PM, Daniel Beck wrote:
>> >
>> >
>> > > On 28. Oct 2019, at 21:44, Tracy Miranda 
>> wrote:
>> > >
>> > > Oct 31, 2019: Voter registration begins
>> > >
>> >
>> > Given that it's Nov 1, where are we with this?
>> >
>> > Are there Jira (or GH) issues tracking progress of this entire process,
>> > that someone interested, but not involved, could follow?
>> >
>> > --
>> > 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 jenkin...@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/jenkinsci-dev/C7E0248E-9F74-4010-87CD-7D1408537AFD%40beckweb.net
>> .
>> >
>>
>> --
>> 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 jenkin...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/546d4625-4965-4da4-b6d5-358fe5284ffd%40www.fastmail.com
>> .
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe 

Re: repeatableProperty in Jenkins Global Configuration

[Jesse Glick]

On Tue, Nov 12, 2019 at 5:53 PM Ullrich Hafner 
wrote:
> if I remove the last element in the UI then the empty list ist not saved.
More precisely, the data bound setter […]
> Is not called if I remove all elements in the UI (it is called for 1,…,n
elements).

This is a well-known limitation in databinding. The workaround is to
override a `configSubmit` or whatever method to first null out / clear the
list, then call super. Example:

https://github.com/jenkinsci/ui-samples-plugin/blob/7d0fe2b32204a7fe0ec6adb6815e65d48b0dd54e/src/main/java/jenkins/plugins/ui_samples/HeteroList.java#L81

-- 
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/CANfRfr26sng%2BPMm7xULu%2B0SH97CgJhTRf3TdiC4NuPew6NFwSQ%40mail.gmail.com.

repeatableProperty in Jenkins Global Configuration

[Ullrich Hafner]

I have a repeatableProperty in Jenkins Global Configuration page (see 
https://github.com/jenkinsci/warnings-ng-plugin/pull/266 
).

Expanded snippet:

  

  

  

  

  



(And a describable config.jelly)

  

I can successfully add entries and delete entries in the UI. However, if I 
remove the last element in the UI then the empty list ist not saved. More 
precisely, the data bound setter 
/**
 * Sets the list of source directories to the specified elements. Previously 
set directories will be removed.
 *
 * @param sourceDirectories
 * the source directories that contain the affected files
 */
@DataBoundSetter
public void setSourceDirectories(final List sourceDirectories) 
{
...


Is not called if I remove all elements in the UI (it is called for 1,…,n 
elements). Has anyone an idea what I am making wrong? 

-- 
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/987D0FAA-15D1-4AD7-9EF8-9918EB79FF62%40gmail.com.

Jenkins Governance meeting on Nov 20

[James Nord]

is it also too early for LTS.next selection?

-- 
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/ab46071f-29cb-4d90-8640-b9159b05d702%40googlegroups.com.

Re: [gitlab-oauth-plugin] Request commit access

['Gavin Mogan' via Jenkins Developers]

Maybe try creating the permission-updater PR, and tagging them incase they
have some sort of email filtering going on.

On Tue, Nov 12, 2019 at 10:41 AM Björn Kasteleiner 
wrote:

> Hello,
>
> thanks to Gavin and Oleg for replying to my mails.
> It was a good idea to try another way to contact the current maintainer.
>
> The situation is kind of weird and I'm not sure if I should continue the
> adoption process.
> Two hours after my email on the 7th the current maintainer merged the
> opened PRs and released the new version, without any comment.
>
> I would like to support, but I don't want to take the maintainer ship away
> from somebody, who is obviously still spending work on the project.
> On the other hand, it seems that there is currently no way of contacting
> him, since he is not responding on his mails.
>
> Cheers
>
> Bjoern
>
> Am 11.11.19 um 12:06 schrieb Oleg Nenashev:
>
> Yes, we usually CC folks in the email to the dev list.
> It is what Bjoern did in the original email, and the email in the profile
> was used.
>
> +1 for a PR to Repository Permission updater and the final CC, but I
> believe that 2-week timeout is over. We can do the transfer this week
>
> On Thursday, November 7, 2019 at 8:01:39 AM UTC+1, Gavin Mogan wrote:
>>
>> I reached out on twitter -
>> https://twitter.com/halkeye/status/1192334639844577280, just in case
>>
>> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin doesn't give
>> explicit steps
>>
>> I think since this has the time elapsed, the best thing is to make an
>> INFRA ticket on jira to get write access to github
>> and creating a PR for
>> https://github.com/jenkins-infra/repository-permissions-updater, pinging
>> yet again the original maintainer
>>
>> Gavin
>>
>>
>> On Wednesday, November 6, 2019 at 10:51:44 PM UTC-8, Bjoern Kasteleiner
>> wrote:
>>>
>>> Hello,
>>>
>>> I would like to adopt the gitlab-oauth plugin, since the current
>>> maintainer isn't responding anymore.
>>> What do I have to do to become maintainer of the plugin?
>>>
>>> Thanks a lot.
>>>
>>> Cheers
>>>
>>> Bjoern
>>>
>>> Am 21.10.19 um 06:47 schrieb Björn Kasteleiner:
>>> > Hello,
>>> >
>>> > I would like to adopt the gitlab-oauth-pugin, to take care of the
>>> > current issues of the plugin.
>>> >
>>> > Gitlab-User-Id: bjkastel
>>> > Jenkins-User-Id: bjkastel
>>> >
>>> > I've already tried to contact the current maintainer at the beginning
>>> > of September, unfortunately he hasn't answered yet. I've added him as
>>> > CC to this mail.
>>> >
>>> > Thanks a lot
>>> >
>>> > Bjoern
>>> >
>>>
>>> --
> 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/027b6163-23e0-4f20-bf3f-39c53154b160%40googlegroups.com
> 
> .
>
>
> --
> 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/70385f03-858b-c92c-0e3e-eaba13731b87%40kasteleiner.net
> 
> .
>

-- 
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/CAG%3D_DuseLwDwwY82_EepSAfCXf7QQaLOffy1jef2PcYCbDm74A%40mail.gmail.com.

Re: [gitlab-oauth-plugin] Request commit access

[Björn Kasteleiner]

Hello,

thanks to Gavin and Oleg for replying to my mails.
It was a good idea to try another way to contact the current maintainer.

The situation is kind of weird and I'm not sure if I should continue the 
adoption process.
Two hours after my email on the 7th the current maintainer merged the 
opened PRs and released the new version, without any comment.


I would like to support, but I don't want to take the maintainer ship 
away from somebody, who is obviously still spending work on the project.
On the other hand, it seems that there is currently no way of contacting 
him, since he is not responding on his mails.


Cheers

Bjoern

Am 11.11.19 um 12:06 schrieb Oleg Nenashev:

Yes, we usually CC folks in the email to the dev list.
It is what Bjoern did in the original email, and the email in the 
profile was used.


+1 for a PR to Repository Permission updater and the final CC, but I 
believe that 2-week timeout is over. We can do the transfer this week


On Thursday, November 7, 2019 at 8:01:39 AM UTC+1, Gavin Mogan wrote:

I reached out on twitter -
https://twitter.com/halkeye/status/1192334639844577280
, just in case

https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin
 doesn't
give explicit steps

I think since this has the time elapsed, the best thing is to make
an INFRA ticket on jira to get write access to github
and creating a PR for
https://github.com/jenkins-infra/repository-permissions-updater
,
pinging yet again the original maintainer

Gavin


On Wednesday, November 6, 2019 at 10:51:44 PM UTC-8, Bjoern
Kasteleiner wrote:

Hello,

I would like to adopt the gitlab-oauth plugin, since the current
maintainer isn't responding anymore.
What do I have to do to become maintainer of the plugin?

Thanks a lot.

Cheers

Bjoern

Am 21.10.19 um 06:47 schrieb Björn Kasteleiner:
> Hello,
>
> I would like to adopt the gitlab-oauth-pugin, to take care
of the
> current issues of the plugin.
>
> Gitlab-User-Id: bjkastel
> Jenkins-User-Id: bjkastel
>
> I've already tried to contact the current maintainer at the
beginning
> of September, unfortunately he hasn't answered yet. I've
added him as
> CC to this mail.
>
> Thanks a lot
>
> Bjoern
>

--
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/027b6163-23e0-4f20-bf3f-39c53154b160%40googlegroups.com 
.


--
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/70385f03-858b-c92c-0e3e-eaba13731b87%40kasteleiner.net.

Jenkins Governance meeting on Nov 20

[Oleg Nenashev]

Hi all,

There is a umber of pending requests w.r.t budgets (GSoC + Hacktberfest to 
be submitted) and trademark approvals from Parker. I suggest we run a 
governance meeting on Nov 20 so that we can review/approve/reject the 
pending requests. I am ready to chair this meeting. If anyone has any 
budget/trademark requests to be approved OR any other topics to be 
discussed, please reply to this thread.

Best regards,
Oleg



-- 
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/cc98635e-e12c-4996-8882-fe3fc9e3abf6%40googlegroups.com.

Re: JCasC Office Hours - JCasC Dev Tools project demo

[Oleg Nenashev]

UPD: The meeting will happen at 9AM UTC

On Tuesday, November 12, 2019 at 1:56:43 PM UTC+1, Oleg Nenashev wrote:
>
> Hi all,
>
> On Nov 13 we will be doing an out-of-order JCasC subproject meeting. At 
> this meeting Sladyn Nunes  will present his 
> community bridge project: JCasC YAML config validation with JSON Schema and 
> a new JCasC plugin for Visual Studio Code.
>
> The meeting will be recorded. We also consider doing a Jenkins Online 
> Meetup later.
>
> Project URL: https://jenkins.io/projects/jcasc/dev-tools/ 
> 
> Meeting URL: https://zoom.us/j/286266977 
> 
>  
> Plugin URL: https://github.com/jenkinsci/jcasc-vscode-extension
>
> Best regards,
> Oleg Nenashev
>
>

-- 
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/207ca9ff-ca28-48d3-996d-3d1bab7bc5d1%40googlegroups.com.

Re: oauth-credentials plugin adoption

[Oleg Nenashev]

Thanks! I have transferred the permissions according to the approvals

On Tue, Nov 12, 2019 at 2:06 PM Eric Johnson  wrote:

> A bit late in a reply - but thanks all!
>
> On Tue, Nov 12, 2019 at 1:03 AM Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com> wrote:
>
>> Thank you both, let me re-add Jenkins Dev List so that @Oleg Nenashev
>>  can see the answers you provided.
>> -- Adrien
>>
>> Le lun. 11 nov. 2019 à 18:46, Craig Barber  a
>> écrit :
>>
>>> Thanks Matt. I approved on the issue, but will also add my LGTM here :)
>>>
>>> On Mon, Nov 11, 2019 at 9:39 AM Matt Moore  wrote:
>>>
 +Craig -list



 I can’t mail the list without being a member, but here’s what I replied
 yesterday.

 -M





 *From: *Matt Moore 
 *Date: *Sunday, November 10, 2019 at 7:25 AM
 *To: *Adrien Lecharpentier , Jenkins
 Developers 
 *Cc: *"erjoh...@google.com" 
 *Subject: *Re: oauth-credentials plugin adoption



 I’m adding Eric Johnson whose team at Google has taken on ownership of
 other plugins my team developed (many) years ago.  It may also be worth
 adding Vic Iglesias, as I believe he was involved in a related thread about
 patching Google’s “source” plugin right before I left (I don’t have his
 email handy).  They might be helpful for the “Google” side.



 From my perspective, I don’t mind.  I would like the owner to not be me
 as I haven’t touched these in like 5-6 years. 

 -M





 *From: *Adrien Lecharpentier 
 *Date: *Sunday, November 10, 2019 at 1:14 AM
 *To: *Jenkins Developers , Matt Moore <
 mattm...@vmware.com>
 *Subject: *Re: oauth-credentials plugin adoption



 I re-add Matt Moor here then.



 Le dim. 10 nov. 2019 à 07:44, Oleg Nenashev  a
 écrit :

 There is no company plugin ownership policy in Jenkins ATM. It is
 something on my radars. Am explicit approval from Matt Moore is needed to
 do the permission transfer. But indeed sign-off from Google is helpful
 here, thanks Jeremy


 Once there is am explicit +1 from Matt in this thread or in the GitHub
 pill request, I will do the transfer

 --
 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/726cdbcf-c45c-4273-83ba-9f6027a63d28%40googlegroups.com
 
 .


>>>
>>> --
>>> Craig Barber
>>> Software Engineer
>>> Cloud Graphite: Platforms
>>>
>>
>>
>> --
>> Adrien Lecharpentier
>>
>

-- 
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/CAPfivLBH613a9E90nxgtLds7%3Deyc8Z3KGVecnmS%2B-7AxuY1D8Q%40mail.gmail.com.

JCasC Office Hours - JCasC Dev Tools project demo

[Oleg Nenashev]

Hi all,

On Nov 13 we will be doing an out-of-order JCasC subproject meeting. At
this meeting Sladyn Nunes  will present his
community bridge project: JCasC YAML config validation with JSON Schema and
a new JCasC plugin for Visual Studio Code.

The meeting will be recorded. We also consider doing a Jenkins Online
Meetup later.

Project URL: https://jenkins.io/projects/jcasc/dev-tools/

Meeting URL: https://zoom.us/j/286266977

Plugin URL: https://github.com/jenkinsci/jcasc-vscode-extension

Best regards,
Oleg Nenashev

-- 
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/CAPfivLB-jUFf%3Dok%3DmR2MEaiEbvJRs2NeFKreSho%3DHSzkXRTRPg%40mail.gmail.com.

Re: oauth-credentials plugin adoption

[Oleg Nenashev]

Thanks to everybody who is involved in this topic.
Matt;s response is enough to do the transfer from my PoV: "From my 
perspective, I don’t mind.  I would like the owner to not be me as I 
haven’t touched these in like 5-6 years.".
As far as I am concerned, Matt is a maintainer of the plugin. There is no 
track of ownership/permission transfer for this plugin.

Unless Eric Johnson or anyone else vote against the transfer in this 
thread, I will do the permission transfer at noon UTC tomorrow


On Tuesday, November 12, 2019 at 10:03:45 AM UTC+1, Adrien Lecharpentier 
wrote:
>
> Thank you both, let me re-add Jenkins Dev List so that ...@Oleg Nenashev 
>  can see the answers you provided.
> -- Adrien
>
> Le lun. 11 nov. 2019 à 18:46, Craig Barber  > a écrit :
>
>> Thanks Matt. I approved on the issue, but will also add my LGTM here :)
>>
>> On Mon, Nov 11, 2019 at 9:39 AM Matt Moore > > wrote:
>>
>>> +Craig -list
>>>
>>>  
>>>
>>> I can’t mail the list without being a member, but here’s what I replied 
>>> yesterday.
>>>
>>> -M
>>>
>>>  
>>>
>>>  
>>>
>>> *From: *Matt Moore >
>>> *Date: *Sunday, November 10, 2019 at 7:25 AM
>>> *To: *Adrien Lecharpentier >, 
>>> Jenkins Developers >
>>> *Cc: *"erjo...@google.com " >> >
>>> *Subject: *Re: oauth-credentials plugin adoption
>>>
>>>  
>>>
>>> I’m adding Eric Johnson whose team at Google has taken on ownership of 
>>> other plugins my team developed (many) years ago.  It may also be worth 
>>> adding Vic Iglesias, as I believe he was involved in a related thread about 
>>> patching Google’s “source” plugin right before I left (I don’t have his 
>>> email handy).  They might be helpful for the “Google” side.
>>>
>>>  
>>>
>>> From my perspective, I don’t mind.  I would like the owner to not be me 
>>> as I haven’t touched these in like 5-6 years. 
>>>
>>> -M
>>>
>>>  
>>>
>>>  
>>>
>>> *From: *Adrien Lecharpentier >
>>> *Date: *Sunday, November 10, 2019 at 1:14 AM
>>> *To: *Jenkins Developers >, 
>>> Matt Moore >
>>> *Subject: *Re: oauth-credentials plugin adoption
>>>
>>>  
>>>
>>> I re-add Matt Moor here then.
>>>
>>>  
>>>
>>> Le dim. 10 nov. 2019 à 07:44, Oleg Nenashev >> > a écrit :
>>>
>>> There is no company plugin ownership policy in Jenkins ATM. It is 
>>> something on my radars. Am explicit approval from Matt Moore is needed to 
>>> do the permission transfer. But indeed sign-off from Google is helpful 
>>> here, thanks Jeremy
>>>
>>>
>>> Once there is am explicit +1 from Matt in this thread or in the GitHub 
>>> pill request, I will do the transfer
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/726cdbcf-c45c-4273-83ba-9f6027a63d28%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>>
>>
>> -- 
>> Craig Barber
>> Software Engineer
>> Cloud Graphite: Platforms
>>
>
>
> -- 
> Adrien Lecharpentier
>

-- 
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/e9b3c8ce-9d18-47be-82bc-9ce13890a758%40googlegroups.com.

Re: oauth-credentials plugin adoption

[Adrien Lecharpentier]

Thank you both, let me re-add Jenkins Dev List so that @Oleg Nenashev
 can see the answers you provided.
-- Adrien

Le lun. 11 nov. 2019 à 18:46, Craig Barber  a
écrit :

> Thanks Matt. I approved on the issue, but will also add my LGTM here :)
>
> On Mon, Nov 11, 2019 at 9:39 AM Matt Moore  wrote:
>
>> +Craig -list
>>
>>
>>
>> I can’t mail the list without being a member, but here’s what I replied
>> yesterday.
>>
>> -M
>>
>>
>>
>>
>>
>> *From: *Matt Moore 
>> *Date: *Sunday, November 10, 2019 at 7:25 AM
>> *To: *Adrien Lecharpentier , Jenkins
>> Developers 
>> *Cc: *"erjoh...@google.com" 
>> *Subject: *Re: oauth-credentials plugin adoption
>>
>>
>>
>> I’m adding Eric Johnson whose team at Google has taken on ownership of
>> other plugins my team developed (many) years ago.  It may also be worth
>> adding Vic Iglesias, as I believe he was involved in a related thread about
>> patching Google’s “source” plugin right before I left (I don’t have his
>> email handy).  They might be helpful for the “Google” side.
>>
>>
>>
>> From my perspective, I don’t mind.  I would like the owner to not be me
>> as I haven’t touched these in like 5-6 years. 
>>
>> -M
>>
>>
>>
>>
>>
>> *From: *Adrien Lecharpentier 
>> *Date: *Sunday, November 10, 2019 at 1:14 AM
>> *To: *Jenkins Developers , Matt Moore <
>> mattm...@vmware.com>
>> *Subject: *Re: oauth-credentials plugin adoption
>>
>>
>>
>> I re-add Matt Moor here then.
>>
>>
>>
>> Le dim. 10 nov. 2019 à 07:44, Oleg Nenashev  a
>> écrit :
>>
>> There is no company plugin ownership policy in Jenkins ATM. It is
>> something on my radars. Am explicit approval from Matt Moore is needed to
>> do the permission transfer. But indeed sign-off from Google is helpful
>> here, thanks Jeremy
>>
>>
>> Once there is am explicit +1 from Matt in this thread or in the GitHub
>> pill request, I will do the transfer
>>
>> --
>> 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/726cdbcf-c45c-4273-83ba-9f6027a63d28%40googlegroups.com
>> 
>> .
>>
>>
>
> --
> Craig Barber
> Software Engineer
> Cloud Graphite: Platforms
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvxwdpsJbXZgyAR4KzOzsTn4h5BzgJz0gYBaQHBXeR3eLw%40mail.gmail.com.