Re: CDF Technical Oversight Committee - Jenkins project representative nominations

[Oleg Nenashev]

Dear all,

Thanks to everyone who have provided feedback in this thread and in the 
governance board channels. We have discussed the nomination at the 
governance meeting yesterday. There was only one candidate nominated: Oleg 
Nenashev (yes, me), and we decided no not extend the candidate search 
beyond the announced nominations deadline. Oleg Nenashev is nominated to 
the CDF TOC Representative role from the Jenkins project.

Approvers at the governance meeting: Ulli Hafner, Gavin Mogan, Ewelina 
Wilkosz, Daniel Beck, Baptiste Mathus, Mark Waite

Best regards,
Oleg Nenashev

On Monday, May 3, 2021 at 10:31:13 PM UTC+2 Oleg Nenashev wrote:

> > Having more motivative contributors is crucial for the community. 
> Sharing your routine or stories to us might be a good way to let those who 
> is interested in the community contribution even leading. If there’s any 
> chances I’d like to take some responsibility.
>
> Thanks, it is much appreciated. Just FYI, there is a pending proposal to 
> the board about making our governance activities more open and shareable 
> with others. Likely it will be an additional GitHub Repo with Issues for 
> initiatives/backlog + more frequent roadmap updates. It should help other 
> contributors to pick up tasks including the CDF related ones. We need to 
> reduce the bus factor and let others to be involved.
>
> > Like you said, getting support from the employer is quite important.
>
> Yes, I confirmed with my manager that I will be able to dedicate some 
> working time to the CDF TOC representation. CloudBees is a very active 
> participant in the Jenkins community and the CDF as all of us know, and it 
> is a good opportunity for all parties. 
>
> Best regards,
> Oleg
>
> On Monday, May 3, 2021 at 3:41:09 AM UTC+2 Xiaojie Zhao wrote:
>
>> Having more motivative contributors is crucial for the community. Sharing 
>> your routine or stories to us might be a good way to let those who is 
>> interested in the community contribution even leading. If there’s any 
>> chances I’d like to take some responsibility.
>>
>> Like you said, getting support from the employer is quite important. I’d 
>> like to say a big thanks for all the companies that support open-source.
>>
>> Best regards,
>> Best
>>
>>
>>
>>
>> On 05/3/2021 06:46，Oleg Nenashev wrote： 
>>
>> Dear all,
>>
>> Thanks a lot for the nomination and feedback! I am really humbled and 
>> grateful for that, and I appreciate the trust from the community members. I 
>> am ready to run for the CDF Jenkins representative nomination and for the 
>> TOC seat. I have been participating in the CDF TOC meetings since May 2020, 
>> and I have been handling other project representative responsibilities like 
>> providing project updates and communicating news back to the Jenkins 
>> community. I would be happy to continue doing so in the official capacity, 
>> or to help any other contributor nominated by the Jenkins community.
>>
>> If I get elected, my key priorities will be representing the Jenkins 
>> community interests in the TOC (process, standards and tooling, ecosystem 
>> promotion, etc.) and driving changes towards better interoperability 
>> between Jenkins and other CI/CD projects. I will also work with other 
>> stakeholders in the CDF Governance Board, Outreach Committee and SIGs where 
>> needed, and will do my best to get more contributors and Jenkins SIGs 
>> involved in the higher CDF level activities. I believe that the cooperation 
>> between Jenkins and the CDF could bring us a lot of wins to all sides, and 
>> a TOC project representative is a key role for such initiatives.
>>
>> At the same time, full transparency is needed IMHO. We discussed 
>> the nomination topic with the Jenkins governance board, and 3 of 4 other 
>> board members are ready to support my nomination. I'll let the board 
>> members summarize the positive facts if they want, and focus on the 
>> concerns brought up in that discussion. There were 2 concerns discussed: my 
>> bandwidth due to many other responsibilities (Jenkins core maintenance, 
>> JFR, Jenkins Governance Board, acting Events Officer, etc.), and a very 
>> serious burnout I had this winter. The latter is kinda public on Twitter 
>> , hence it 
>> would be fair to share it here. So, a quick summary for these topics:
>>
>>- I already participate in the CDF TOC meetings and other day to day 
>>activities. If I get elected, not that much will change in principle. I 
>>will also work on having other Jenkins community members participating 
>> from 
>>time to time so that I am not a single point of failure. The details are 
>>TBD.
>>- My burnout was caused by multiple personal and work factors, but 
>>the Jenkins community is not one of them. In fact, it is quite opposite. 
>>The work I am currently doing in the community helps me to recover faster 
>>by focusing on objectives I am 

Re: LTS 2.277.4 RC

[Oleg Nenashev]

Thanks everyone for your efforts! Next stop is the new LTS baseline in June

On Wednesday, May 5, 2021 at 9:16:28 PM UTC+2 Mark Waite wrote:

> Jenkins 2.277.4 has been released today.  
>
>- Changelog - https://www.jenkins.io/changelog-stable/#v2.277.4
>- Upgrade guide - 
>
> https://www.jenkins.io/doc/upgrade-guide/2.277/#upgrading-to-jenkins-lts-2-277-4
>
> Thanks very much to Bea Munoz for acting as the release lead for 2.277.4!
>
> Mark Waite
> On Tuesday, April 27, 2021 at 9:24:12 AM UTC-6 Jesse Glick wrote:
>
>> On Tue, Apr 27, 2021 at 8:52 AM Tim Jacomb  wrote:
>>
>>> The RC is 
>>> http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.277.4-SNAPSHOT/jenkins-war-2.277.4-20210427.105011-1.war
>>>
>>
>>  Would be nice to use incrementals for this purpose but it seems that ATH 
>> is getting in the way?
>>
>> https://ci.jenkins.io/job/Core/job/jenkins/job/stable-2.277/13/testReport/
>>
>

-- 
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/8f58f177-1121-46af-8ea2-356884647369n%40googlegroups.com.

Re: Adoption of plugin Google Container Registry Auth

[Vincent Gerris]

hi, thanks, I did that in the current branch :
https://github.com/jenkinsci/google-container-registry-auth-plugin/compare/master...VGerris:fix-tests-and-clean-pom-wip?expand=1
and also in the one from the PR:
https://github.com/jenkinsci/google-container-registry-auth-plugin/pull/4/
That last one is multiple commits and a bit messy so I will try to make 
everything clean and orderly.
thanks for the help!

On Wednesday, May 5, 2021 at 10:19:11 PM UTC+2 ga...@gavinmogan.com wrote:

> When you do manage to take over, its worth upgrading the parent pom to 
> something modern. It comes with a lot of maven tools to scan for potential 
> issues
>
> https://github.com/jenkinsci/google-container-registry-auth-plugin/blob/master/pom.xml#L21
> It will def require some changes, but its worth doing - 
> https://www.jenkins.io/doc/developer/plugin-development/updating-parent/
>
> On Wed, May 5, 2021 at 1:14 PM Vincent Gerris  wrote:
>
>> Thank you Oleg, let's hope he is not a long vacation and missed it. I 
>> wrote him a few days ago, not being aware of the policy.
>> I would love to hear something anyway, to ask about the way the 
>> end-to-end tests are designed, I wasn't able to compile the old version 
>> easily and I think with all the updates something may have changed.
>> I'm still working on improving that PR, because 5 of now 24 tests are 
>> failing and I got tips from Tim on what to improve, which I did.
>> Great that you guys are all so responsive and cooperative, it feels 
>> really welcoming and professional.
>> Fun to learn and contribute like this, thanks!
>>
>> On Wednesday, May 5, 2021 at 10:52:40 AM UTC+2 Oleg Nenashev wrote:
>>
>>> CCed Wei Z who is currently listed as the plugin maintainer. According 
>>> to the plugin adoption policy 
>>> , 
>>> we will wait for 2 weeks for a response. An earlier response will be 
>>> appreciated!
>>>
>>>
>>> -- 
>> 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/d0c80146-542f-421c-a3a1-bb0ade3488a8n%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/096a77e4-b36b-4a71-8678-28390095824en%40googlegroups.com.

Re: Jenkins SDLC Security: LFX Security/Snyk adoption status updates

[Oleg Nenashev]

UPD: The Jenkins Governance meeting approved official participation in the 
Pilot project.
Approved by: Ulli Hafner, Gavin Mogan, Ewelina Wilkosz, Daniel Beck, 
Baptiste Mathus, Mark Waite (+ Olivier I'd guess)
Thanks everyone for the feedback!


On Wednesday, May 5, 2021 at 7:28:36 PM UTC+2 Oleg Nenashev wrote:

> Hi all,
>
> Just a quick update, we will be setting up a shared Slack channel in the 
> CDF workspace. Once it is ready, we can use it for conversations.
> Pending ticket to the CDF: 
> https://github.com/cdfoundation/foundation/issues/330 
>
> BR, Oleg
>
> On Tuesday, May 4, 2021 at 9:30:06 AM UTC+2 Oleg Nenashev wrote:
>
>> Hi Olivier,
>>
>> For experiments, it might make sense to register Jenkins Infrastructure 
>> as the second organization. I do not anticipate major overlap between 
>> configs taking different technology stacks.
>> Once Snyk adds support for multiple GitHub orgs, we can explore our 
>> options. M> standard GitHub App integration anyway (see my response to Daniel)
>>
>> If you want to start with the Jenkins Infra org, I think you can do it 
>> even now on LFX Security 1.x && standard GitHUb integration. Then it can be 
>> migrated to 2x.
>> Let the LFX Security team know if you want one to be created.
>>
>> Best regards,
>> Oleg
>>
>>
>> On Tue, May 4, 2021 at 8:46 AM 'Olblak' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> Hi Oleg,
>>>
>>> Thanks for driving this.
>>> Once we are allowed to have a second Github Organization, I would be 
>>> very interested to experiment with it for the jenkins-infra organization. 
>>>
>>> On Monday, 3 May 2021 at 22:24:44 UTC+2 Oleg Nenashev wrote:
>>>
 Thanks for the interest Daniel!

 >> Would you like to participate as a contributor?
 > What does this entail?

 That's a good question, to be seen. As a part of the pilot project we 
 will need:

- Try out LFX Security 2.0 and configure it for some of our projects
- Explore options for filtering out false positives, find a 
solution for the Jenkins project taking its scale and needs
- Try out other features like license analysis
- Document the implementation for other maintainers
- Keep evaluation notes and share feedback with Snyk/LFX Security. 
If we experience blockers, multiple iterations might be required

 Note from the discussion: It is unlikely that we will be able to use 
 the standard Snyk's GitHub integration via GitHub App. We will likely need 
 to integrate scanning submissions into our Jenkins pipelines (there is a 
 Snyk plugin FTR) or to use GitHub actions. Reason - GitHub Integration 
 cannot handle custom Bills of Materials which will be supported by the LFX 
 Security 2.0 API (actually, by the Snyk backend).

 > Re licenses -- Is this something we're actively looking at as well, 
 or rather secondary. FWIW I can think of these use cases: That it's 
 actually open source; that it's compatible (no MIT plugin bundling GPL 
 dependencies or similar weirdness); that it's all OSI approved per 
 governance document. Anything else?

 Yes, looks good to me. I would rather prefer to avoid some licenses 
 where compatibility is disputed, e.g. traditional AGPL concerns.


 On Monday, May 3, 2021 at 9:35:17 PM UTC+2 Daniel Beck wrote:

> Thanks again for driving this, Oleg! 
>
>
> > On 3. May 2021, at 19:14, Oleg Nenashev  
> wrote: 
> > 
> > The proposal is to start the pilot from a small list of the 
> repositories controlled by the pilot project participants: Jenkins core, 
> its libraries, and some plugins from maintainers who are interested to 
> participate in the pilot project. 
> > 
> > Call for feedback: 
> > • Would you approve doing an official pilot project together with 
> Snyk and LFX Security? 
>
> Yes, definitely. 
>
> > • Would you like to participate as a contributor? 
>
> What does this entail? 
>
> > • Would you like your plugin to participate in the pilot project? 
>
> Yes (although my plugins tend not to have interesting dependencies so 
> it's probably not that interesting). 
>
>
> Re private PRs and security process (minute 25-28 in the transcripts, 
> again around 0:51) -- I don't really see a need to handle dependency 
> updates in private in most cases, as all information that is based on is 
> usually public anyway (CVEs in dependencies as well as dependency 
> declarations). Additionally, vulnerabilities in plugins don't necessarily 
> mean we're vulnerable (or that the metadata is correct to begin with), 
> and 
> how to exploit it isn't often obvious either. So I don't feel strongly 
> about keeping such content private. What we prepare in jenkinsci-cert in 
> private is almost exclusively fixes for exploitable 

Re: Adoption of plugin Google Container Registry Auth

['Gavin Mogan' via Jenkins Developers]

When you do manage to take over, its worth upgrading the parent pom to
something modern. It comes with a lot of maven tools to scan for potential
issues
https://github.com/jenkinsci/google-container-registry-auth-plugin/blob/master/pom.xml#L21
It will def require some changes, but its worth doing -
https://www.jenkins.io/doc/developer/plugin-development/updating-parent/

On Wed, May 5, 2021 at 1:14 PM Vincent Gerris  wrote:

> Thank you Oleg, let's hope he is not a long vacation and missed it. I
> wrote him a few days ago, not being aware of the policy.
> I would love to hear something anyway, to ask about the way the end-to-end
> tests are designed, I wasn't able to compile the old version easily and I
> think with all the updates something may have changed.
> I'm still working on improving that PR, because 5 of now 24 tests are
> failing and I got tips from Tim on what to improve, which I did.
> Great that you guys are all so responsive and cooperative, it feels really
> welcoming and professional.
> Fun to learn and contribute like this, thanks!
>
> On Wednesday, May 5, 2021 at 10:52:40 AM UTC+2 Oleg Nenashev wrote:
>
>> CCed Wei Z who is currently listed as the plugin maintainer. According to
>> the plugin adoption policy
>> ,
>> we will wait for 2 weeks for a response. An earlier response will be
>> appreciated!
>>
>>
>> --
> 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/d0c80146-542f-421c-a3a1-bb0ade3488a8n%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/CAG%3D_DusThRbJWdv8265pcaGNwEB5JAwwFMwgZa0Hnq-36pS7FQ%40mail.gmail.com.

Re: Adoption of plugin Google Container Registry Auth

[Vincent Gerris]

Thank you Oleg, let's hope he is not a long vacation and missed it. I wrote 
him a few days ago, not being aware of the policy.
I would love to hear something anyway, to ask about the way the end-to-end 
tests are designed, I wasn't able to compile the old version easily and I 
think with all the updates something may have changed.
I'm still working on improving that PR, because 5 of now 24 tests are 
failing and I got tips from Tim on what to improve, which I did.
Great that you guys are all so responsive and cooperative, it feels really 
welcoming and professional.
Fun to learn and contribute like this, thanks!

On Wednesday, May 5, 2021 at 10:52:40 AM UTC+2 Oleg Nenashev wrote:

> CCed Wei Z who is currently listed as the plugin maintainer. According to 
> the plugin adoption policy 
> , 
> we will wait for 2 weeks for a response. An earlier response will be 
> appreciated!
>
>
>

-- 
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/d0c80146-542f-421c-a3a1-bb0ade3488a8n%40googlegroups.com.

Re: LTS 2.277.4 RC

[Mark Waite]

Jenkins 2.277.4 has been released today.  

   - Changelog - https://www.jenkins.io/changelog-stable/#v2.277.4
   - Upgrade guide 
   - 
https://www.jenkins.io/doc/upgrade-guide/2.277/#upgrading-to-jenkins-lts-2-277-4

Thanks very much to Bea Munoz for acting as the release lead for 2.277.4!

Mark Waite
On Tuesday, April 27, 2021 at 9:24:12 AM UTC-6 Jesse Glick wrote:

> On Tue, Apr 27, 2021 at 8:52 AM Tim Jacomb  wrote:
>
>> The RC is 
>> http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.277.4-SNAPSHOT/jenkins-war-2.277.4-20210427.105011-1.war
>>
>
>  Would be nice to use incrementals for this purpose but it seems that ATH 
> is getting in the way?
>
> https://ci.jenkins.io/job/Core/job/jenkins/job/stable-2.277/13/testReport/
>

-- 
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/6267dcb4-2577-4d35-b6d3-e1d681aba5c9n%40googlegroups.com.

Re: JEPs & BDFL ~ KK

[Oleg Nenashev]

I suggest landing the already agreed changes first. I see merits in some
 redesign, but I would not like to block other changes by that

On Wed, May 5, 2021 at 8:53 PM Jesse Glick  wrote:

> On Wed, May 5, 2021 at 2:44 PM Liam Newman  wrote:
>
>> Instead of having proposed JEPs sit as PRs until they meet the bar for
>> "Draft"
>>
>
> It is a pretty low bar I think. You just have to finish writing what you
> plan to do.
>
>
>> This would allow people to more easily collaborate on getting JEPs to
>> Draft state.
>>
>
> If there are truly multiple authors writing content, there are already
> plenty of ways for people to collaboratively draft documents. YAGNI?
>
> --
> 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/hepntz6WZak/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/CANfRfr20tELavC%2BSEb1b2sKSMMHthWWhgZXm3YC%3DuGMtcrCvWQ%40mail.gmail.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/CAPfivLADxXC59Pnvz7MSCczaiUDj6pAQOjANNjNje3dJ4xNSVg%40mail.gmail.com.

Re: JEPs & BDFL ~ KK

[Jesse Glick]

On Wed, May 5, 2021 at 2:44 PM Liam Newman  wrote:

> Instead of having proposed JEPs sit as PRs until they meet the bar for
> "Draft"
>

It is a pretty low bar I think. You just have to finish writing what you
plan to do.


> This would allow people to more easily collaborate on getting JEPs to
> Draft state.
>

If there are truly multiple authors writing content, there are already
plenty of ways for people to collaboratively draft documents. YAGNI?

-- 
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/CANfRfr20tELavC%2BSEb1b2sKSMMHthWWhgZXm3YC%3DuGMtcrCvWQ%40mail.gmail.com.

Re: JEPs & BDFL ~ KK

[Liam Newman]

Oleg,

I just thought of one more possible change.  Instead of having proposed
JEPs sit as PRs until they meet the bar for "Draft", we should add a
"sandbox" folder with named subfolders. So instead of having one pre-draft
folder "" we can have many.  This would allow people to more easily
collaborate on getting JEPs to Draft state.  Alternatively, we could have a
jep-sandbox fork that holds the JEP sandbox (keeping the jep repo cleaner).
That repo would have a wiki-style editing policy with a very low bar for
getting contributor status, letting people make changes without PRs.

-L.



On Wed, May 5, 2021 at 11:30 AM Liam Newman  wrote:

> I can't attend the governance meeting but I'm +1 on the changes we've
> discussed.
>
> On Tue, May 4, 2021 at 1:09 PM Oleg Nenashev 
> wrote:
>
>> Thanks! I will create a pull request for the JEP tomorrow. No laptop at
>> the moment
>>
>> On Tue, May 4, 2021, 21:44 Liam Newman  wrote:
>>
>>> All this sounds good to me.  Thanks for working on this.
>>> -L.
>>>
>>>
>>> On Tue, May 4, 2021 at 10:00 AM Oleg Nenashev 
>>> wrote:
>>>
 Hi Liam,

 "Advisor" looks good to me. Although we would not be using the same
 terminology as in Java JEPs, I agree using this name would help. So I would
 prefer to choose the "Champion/Advisor" pair then.
 For sign-off, I think that the standard Jenkins open governance process
 allows that:

- The Jenkins Developer mailing list provides a trace of those who
sign-off the proposal asynchronously
- The Governance meeting agenda and recording keep trace of votes
at the Governance meeting. We can communicate them back to the developer
mailing list explicitly
- If a decision is delegated to an entity like SIG, it is again
traceable on its level
- If a decision is delegated to a single contributor, this
contributor becomes that "reviewer"

 The main problem with this process is versioning. What if the proposal
 gets changed during the approval process? How do we track that and whether
 the borderline between small change and one requiring re-approvals? I do
 not have exact answer to this. What we could do is the "ready to publish"
 state:

- When a proposal is approved at the "open governance process", a
pull request is submitted to transfer the proposal to the
Active/Accepted/Final state
- There is a timeout similar to "ready-for-merge" in the Jenkins
core PRs. If there is no negative feedback until the timeout, the 
 proposal
gets merged. The timeout time is TBD, but I would not like it to be more
than 1 week
- JEP Champions or an Advisor are expected to explicitly
communicate the merge countdown in the discussion thread

 What do you think?

 Best regards,
 Oleg




 On Tuesday, May 4, 2021 at 5:49:03 PM UTC+2 bitwi...@gmail.com wrote:

> Oleg,
>
> I agree that the names of the roles matter and "Champion/Owner"
> definitely is more descriptive.
> My main concern is confusion around the repurposing of the term
> "Sponsor".  I would agree to this if we can avoid name collision.  What
> about "Advisor" or "Mentor"?
>
> Everyone should review JEPs they are involved in, but there still
> needs to be an explicit list of "Reviewers" that sign off on a JEP.
>
> I look forward to feedback from others on this thread.
>
> -L.
>
>
>
>
>
> On Mon, May 3, 2021 at 2:16 PM Oleg Nenashev 
> wrote:
>
>> In the case changing "Sponsor" -> "Champion/Owner" and adding "(New
>>> role) Sponsor", I'm not convinced there's a huge win there.  We already
>>> define a "Reviewer" role as an alias for "BDFL and BDFL Delegate".   If 
>>> we
>>> replace the "BDFL Delegate" field with "Reivewer" wouldn't that be
>>> sufficient?  It would be significantly less confusing than changing the
>>> meaning of an existing term.
>>
>> Might be. I just wanted to align the "sponsor" term with how it is
>> used in other projects. In our case "sponsors/JEP-1" are de-facto 
>> authors.
>> Maybe a one-time term change would be less confusing for 3rd parties in 
>> the
>> future.
>>
>> For "Reviewer", this is not exactly what I propose. IMO every
>> interested party is expected to review a JEP. The job of the suggested
>> "sponsor" role is to help the authors with the process and with getting 
>> the
>> required community feedback, not necessarily to review the entire JEP and
>> technical merits on their own.
>>
>> Oleg, perhaps you could submit a PR (or more than one) with proposed
>>> changes?
>>>
>> It would be great to reach the consensus first. Then yes, I will
>> submit the JEP update
>>
>>
>> On Mon, May 3, 2021 at 10:52 PM Liam 

Re: JEPs & BDFL ~ KK

[Liam Newman]

I can't attend the governance meeting but I'm +1 on the changes we've
discussed.

On Tue, May 4, 2021 at 1:09 PM Oleg Nenashev  wrote:

> Thanks! I will create a pull request for the JEP tomorrow. No laptop at
> the moment
>
> On Tue, May 4, 2021, 21:44 Liam Newman  wrote:
>
>> All this sounds good to me.  Thanks for working on this.
>> -L.
>>
>>
>> On Tue, May 4, 2021 at 10:00 AM Oleg Nenashev 
>> wrote:
>>
>>> Hi Liam,
>>>
>>> "Advisor" looks good to me. Although we would not be using the same
>>> terminology as in Java JEPs, I agree using this name would help. So I would
>>> prefer to choose the "Champion/Advisor" pair then.
>>> For sign-off, I think that the standard Jenkins open governance process
>>> allows that:
>>>
>>>- The Jenkins Developer mailing list provides a trace of those who
>>>sign-off the proposal asynchronously
>>>- The Governance meeting agenda and recording keep trace of votes at
>>>the Governance meeting. We can communicate them back to the developer
>>>mailing list explicitly
>>>- If a decision is delegated to an entity like SIG, it is again
>>>traceable on its level
>>>- If a decision is delegated to a single contributor, this
>>>contributor becomes that "reviewer"
>>>
>>> The main problem with this process is versioning. What if the proposal
>>> gets changed during the approval process? How do we track that and whether
>>> the borderline between small change and one requiring re-approvals? I do
>>> not have exact answer to this. What we could do is the "ready to publish"
>>> state:
>>>
>>>- When a proposal is approved at the "open governance process", a
>>>pull request is submitted to transfer the proposal to the
>>>Active/Accepted/Final state
>>>- There is a timeout similar to "ready-for-merge" in the Jenkins
>>>core PRs. If there is no negative feedback until the timeout, the 
>>> proposal
>>>gets merged. The timeout time is TBD, but I would not like it to be more
>>>than 1 week
>>>- JEP Champions or an Advisor are expected to explicitly communicate
>>>the merge countdown in the discussion thread
>>>
>>> What do you think?
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>>
>>>
>>> On Tuesday, May 4, 2021 at 5:49:03 PM UTC+2 bitwi...@gmail.com wrote:
>>>
 Oleg,

 I agree that the names of the roles matter and "Champion/Owner"
 definitely is more descriptive.
 My main concern is confusion around the repurposing of the term
 "Sponsor".  I would agree to this if we can avoid name collision.  What
 about "Advisor" or "Mentor"?

 Everyone should review JEPs they are involved in, but there still needs
 to be an explicit list of "Reviewers" that sign off on a JEP.

 I look forward to feedback from others on this thread.

 -L.





 On Mon, May 3, 2021 at 2:16 PM Oleg Nenashev 
 wrote:

> In the case changing "Sponsor" -> "Champion/Owner" and adding "(New
>> role) Sponsor", I'm not convinced there's a huge win there.  We already
>> define a "Reviewer" role as an alias for "BDFL and BDFL Delegate".   If 
>> we
>> replace the "BDFL Delegate" field with "Reivewer" wouldn't that be
>> sufficient?  It would be significantly less confusing than changing the
>> meaning of an existing term.
>
> Might be. I just wanted to align the "sponsor" term with how it is
> used in other projects. In our case "sponsors/JEP-1" are de-facto authors.
> Maybe a one-time term change would be less confusing for 3rd parties in 
> the
> future.
>
> For "Reviewer", this is not exactly what I propose. IMO every
> interested party is expected to review a JEP. The job of the suggested
> "sponsor" role is to help the authors with the process and with getting 
> the
> required community feedback, not necessarily to review the entire JEP and
> technical merits on their own.
>
> Oleg, perhaps you could submit a PR (or more than one) with proposed
>> changes?
>>
> It would be great to reach the consensus first. Then yes, I will
> submit the JEP update
>
>
> On Mon, May 3, 2021 at 10:52 PM Liam Newman 
> wrote:
>
>> As one of the "Sponsors" of JEP-1, I should probably weigh in.
>>
>> I support streamlining the JEP process any way the community sees fit
>> to do.  Removing the BDFL and BDFL Delegate, replacing them with the
>> Governance Board certainly makes sense at this point.  Howver, I don't 
>> like
>> changing the meaning of existing terms unless it makes the process
>> significantly clearer going forward.  In the case changing "Sponsor" ->
>> "Champion/Owner" and adding "(New role) Sponsor", I'm not convinced 
>> there's
>> a huge win there.  We already define a "Reviewer" role as an alias for
>> "BDFL and BDFL Delegate".   If we replace the "BDFL Delegate" field with
>> "Reivewer" wouldn't that 

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Oleg Nenashev]

Hi all. Please do not consider JEP as a huge overhead. As discussed in 
another thread, we will be working on simplifying the process for 
contributors. The process is not meant to be an obstacle, and I plan to 
keep simplifying it where possible.
And, to everyone, please be kind. All of us share the goal to improve 
Jenkins and reduce maintenance overheads

On Wednesday, May 5, 2021 at 7:13:42 PM UTC+2 Baptiste Mathus wrote:

>
> Le mer. 5 mai 2021 à 19:08, Jesse Glick  a écrit :
>
>> On Tue, May 4, 2021 at 10:58 PM Oleg Nenashev  
>> wrote:
>>
>>> What about a quick JEP?
>>>
>>
>> The rule of thumb is that if you are not sure if a JEP might be 
>> needed…file a JEP. It is how we document any decision that might be 
>> controversial or require explanation or context. Certainly any 
>> deliberate compatibility break falls into this category. If your arguments 
>> for why we should do something are coherent, it should not take long to 
>> write up a few paragraphs in AsciiDoc and file it.
>>
>
> Agreed. We'll do one
>
>
>

-- 
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/f8066f0c-9dfe-4209-8fe8-e19bcf30b8e7n%40googlegroups.com.

Re: Hosting Team

[Oleg Nenashev]

Hi all,

We did not have a meeting today, because there were no participants except 
Alex Earl and Daniel Beck. It was a nice chat though. For the original 
topic, we plan to restart the Doodle poll and reconvene after we find more 
interested contributors. 

If you are interested to start contributing, no need to wait:

   - Slides we prepared for the today's meetup: 
   
https://docs.google.com/presentation/d/1bf80nEjbllitdzEM-p00tdr521In5u16GwdTQRI7_ag/edit?usp=sharing
   - 
   
   https://www.jenkins.io/project/teams/hosting/  
   
   - 
   
   https://www.jenkins.io/doc/developer/plugin-governance/ 
   
Any contributions will be appreciated!

Best regards,
Oleg





On Wednesday, May 5, 2021 at 5:54:58 PM UTC+2 cta...@gmail.com wrote:

> would like to join, but I cannot attend the meeting :(
> On Wednesday, May 5, 2021 at 2:26:57 PM UTC+2 slide wrote:
>
>> The meeting is at 4PM UTC, my mistake.
>>
>> On Tuesday, May 4, 2021 at 1:14:53 PM UTC-7 slide wrote:
>>
>>> Hi Everyone,
>>>
>>> If you have been looking for a way to help out Jenkins, there is an 
>>> opportunity that we are having a kickoff meeting tomorrow. The Hosting team 
>>> needs more people to be involved in helping with onboarding for new 
>>> plugins. We will be going over what goes on during the hosting process and 
>>> how you can be involved tomorrow (May 5) at 3:00PM UTC. The zoom link is 
>>> https://zoom.us/j/92062641880. The hosting process is vital to getting 
>>> new plugins into the update center. It is not a lot of work, but many hands 
>>> make light work and having more eyes will help to improve the plugins that 
>>> get into the Jenkins infrastructure.
>>>
>>> Thanks!
>>>
>>> Alex
>>>
>>

-- 
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/bb2d2bbd-aa36-42fc-a7c1-718e36c95ecbn%40googlegroups.com.

Re: Jenkins SDLC Security: LFX Security/Snyk adoption status updates

[Oleg Nenashev]

Hi all,

Just a quick update, we will be setting up a shared Slack channel in the 
CDF workspace. Once it is ready, we can use it for conversations.
Pending ticket to the CDF: 
https://github.com/cdfoundation/foundation/issues/330 

BR, Oleg

On Tuesday, May 4, 2021 at 9:30:06 AM UTC+2 Oleg Nenashev wrote:

> Hi Olivier,
>
> For experiments, it might make sense to register Jenkins Infrastructure as 
> the second organization. I do not anticipate major overlap between configs 
> taking different technology stacks.
> Once Snyk adds support for multiple GitHub orgs, we can explore our 
> options. M standard GitHub App integration anyway (see my response to Daniel)
>
> If you want to start with the Jenkins Infra org, I think you can do it 
> even now on LFX Security 1.x && standard GitHUb integration. Then it can be 
> migrated to 2x.
> Let the LFX Security team know if you want one to be created.
>
> Best regards,
> Oleg
>
>
> On Tue, May 4, 2021 at 8:46 AM 'Olblak' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> Hi Oleg,
>>
>> Thanks for driving this.
>> Once we are allowed to have a second Github Organization, I would be very 
>> interested to experiment with it for the jenkins-infra organization. 
>>
>> On Monday, 3 May 2021 at 22:24:44 UTC+2 Oleg Nenashev wrote:
>>
>>> Thanks for the interest Daniel!
>>>
>>> >> Would you like to participate as a contributor?
>>> > What does this entail?
>>>
>>> That's a good question, to be seen. As a part of the pilot project we 
>>> will need:
>>>
>>>- Try out LFX Security 2.0 and configure it for some of our projects
>>>- Explore options for filtering out false positives, find a solution 
>>>for the Jenkins project taking its scale and needs
>>>- Try out other features like license analysis
>>>- Document the implementation for other maintainers
>>>- Keep evaluation notes and share feedback with Snyk/LFX Security. 
>>>If we experience blockers, multiple iterations might be required
>>>
>>> Note from the discussion: It is unlikely that we will be able to use the 
>>> standard Snyk's GitHub integration via GitHub App. We will likely need to 
>>> integrate scanning submissions into our Jenkins pipelines (there is a Snyk 
>>> plugin FTR) or to use GitHub actions. Reason - GitHub Integration cannot 
>>> handle custom Bills of Materials which will be supported by the LFX 
>>> Security 2.0 API (actually, by the Snyk backend).
>>>
>>> > Re licenses -- Is this something we're actively looking at as well, or 
>>> rather secondary. FWIW I can think of these use cases: That it's actually 
>>> open source; that it's compatible (no MIT plugin bundling GPL dependencies 
>>> or similar weirdness); that it's all OSI approved per governance document. 
>>> Anything else?
>>>
>>> Yes, looks good to me. I would rather prefer to avoid some licenses 
>>> where compatibility is disputed, e.g. traditional AGPL concerns.
>>>
>>>
>>> On Monday, May 3, 2021 at 9:35:17 PM UTC+2 Daniel Beck wrote:
>>>
 Thanks again for driving this, Oleg! 


 > On 3. May 2021, at 19:14, Oleg Nenashev  wrote: 
 > 
 > The proposal is to start the pilot from a small list of the 
 repositories controlled by the pilot project participants: Jenkins core, 
 its libraries, and some plugins from maintainers who are interested to 
 participate in the pilot project. 
 > 
 > Call for feedback: 
 > • Would you approve doing an official pilot project together with 
 Snyk and LFX Security? 

 Yes, definitely. 

 > • Would you like to participate as a contributor? 

 What does this entail? 

 > • Would you like your plugin to participate in the pilot project? 

 Yes (although my plugins tend not to have interesting dependencies so 
 it's probably not that interesting). 


 Re private PRs and security process (minute 25-28 in the transcripts, 
 again around 0:51) -- I don't really see a need to handle dependency 
 updates in private in most cases, as all information that is based on is 
 usually public anyway (CVEs in dependencies as well as dependency 
 declarations). Additionally, vulnerabilities in plugins don't necessarily 
 mean we're vulnerable (or that the metadata is correct to begin with), and 
 how to exploit it isn't often obvious either. So I don't feel strongly 
 about keeping such content private. What we prepare in jenkinsci-cert in 
 private is almost exclusively fixes for exploitable vulnerabilities 
 originating in Jenkins code. 

 Re CVE ignore list and such -- would like to see a plan (perhaps with 
 the custom graph API that pre-filters plugin dependencies) how to deal 
 with 
 transitive plugin dependencies: Plugin X depends on plugin Y which bundles 
 library Z. The maintainer of X doesn't really care about Z being outdated. 
 (The same applies to "core Y" -- no need for a tool to tell plugin 

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Baptiste Mathus]

Le mer. 5 mai 2021 à 19:08, Jesse Glick  a écrit :

> On Tue, May 4, 2021 at 10:58 PM Oleg Nenashev 
> wrote:
>
>> What about a quick JEP?
>>
>
> The rule of thumb is that if you are not sure if a JEP might be
> needed…file a JEP. It is how we document any decision that might be
> controversial or require explanation or context. Certainly any
> deliberate compatibility break falls into this category. If your arguments
> for why we should do something are coherent, it should not take long to
> write up a few paragraphs in AsciiDoc and file it.
>

Agreed. We'll do one

-- 
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/CANWgJS4gSYUdpZAo%3Dxgp8U8nhj9YzEoMJM85A3b4LAWqaMU%3Dqg%40mail.gmail.com.

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Jesse Glick]

On Tue, May 4, 2021 at 10:58 PM Oleg Nenashev 
wrote:

> What about a quick JEP?
>

The rule of thumb is that if you are not sure if a JEP might be needed…file
a JEP. It is how we document any decision that might be controversial or
require explanation or context. Certainly any deliberate compatibility
break falls into this category. If your arguments for why we should do
something are coherent, it should not take long to write up a few
paragraphs in AsciiDoc and file it.

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

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Baptiste Mathus]

Exactly what Liam said.

I did call out this very page about "compatibility matters" on my first
mail in this thread.

I think we *are* being extremely careful. We even filed PRs on plugins that
the Jenkins Project does not serve anymore and/or plugins abandoned since
close to 10 years.

Le mer. 5 mai 2021 à 17:28, Liam Newman  a écrit :

> Daniel,
>
> From that link:
>
>> This is not to say we don’t ever remove anything, but we do it very
>> carefully.
>>
>
> We are being careful.  I think creating a JEP, even a mostly retrospective
> one, is worth doing.  If nothing else we should do so because of concerns
> like those voiced by Daniel. I will take that task on myself if needed.
>
>   -L.
>
>
> On Wed, May 5, 2021 at 5:14 AM Daniel Beck  wrote:
>
>>
>>
>> > On 5. May 2021, at 09:41, Manuel Ramón León Jiménez <
>> manuelramonleonjime...@gmail.com> wrote:
>> >
>> > I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in
>> for anything to avoid us dealing with the same problems in the future. We
>> need to modernize Jenkins in many aspects and those old / unmaintained
>> plugins are an obstacle and a waste of effort.
>>
>> Time to delete
>> https://www.jenkins.io/project/governance/#compatibility-matters then,
>> because looking at this thread, compatibility clearly doesn't matter
>> anymore?
>>
>> --
>> 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/B214EACA-57A8-4EB4-9FFA-C59B2F0D9D89%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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAA0qCNwD%3DMMh5i%2BjeEte6CxRqQ%3DcCVEZqmNMxtPcgC8JUJ_0vA%40mail.gmail.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/CANWgJS6rpBamE_3%3DVGbFjKepLW%3DrdWbkCazF6Jhm5KGo1f2f5g%40mail.gmail.com.

Re: Hosting Team

[Carlos Tadeu Panato Jr]

would like to join, but I cannot attend the meeting :(
On Wednesday, May 5, 2021 at 2:26:57 PM UTC+2 slide wrote:

> The meeting is at 4PM UTC, my mistake.
>
> On Tuesday, May 4, 2021 at 1:14:53 PM UTC-7 slide wrote:
>
>> Hi Everyone,
>>
>> If you have been looking for a way to help out Jenkins, there is an 
>> opportunity that we are having a kickoff meeting tomorrow. The Hosting team 
>> needs more people to be involved in helping with onboarding for new 
>> plugins. We will be going over what goes on during the hosting process and 
>> how you can be involved tomorrow (May 5) at 3:00PM UTC. The zoom link is 
>> https://zoom.us/j/92062641880. The hosting process is vital to getting 
>> new plugins into the update center. It is not a lot of work, but many hands 
>> make light work and having more eyes will help to improve the plugins that 
>> get into the Jenkins infrastructure.
>>
>> Thanks!
>>
>> Alex
>>
>

-- 
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/cf6491ee-7223-4e79-8f74-41d20e74c14an%40googlegroups.com.

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Liam Newman]

Daniel,

>From that link:

> This is not to say we don’t ever remove anything, but we do it very
> carefully.
>

We are being careful.  I think creating a JEP, even a mostly retrospective
one, is worth doing.  If nothing else we should do so because of concerns
like those voiced by Daniel. I will take that task on myself if needed.

  -L.


On Wed, May 5, 2021 at 5:14 AM Daniel Beck  wrote:

>
>
> > On 5. May 2021, at 09:41, Manuel Ramón León Jiménez <
> manuelramonleonjime...@gmail.com> wrote:
> >
> > I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in
> for anything to avoid us dealing with the same problems in the future. We
> need to modernize Jenkins in many aspects and those old / unmaintained
> plugins are an obstacle and a waste of effort.
>
> Time to delete
> https://www.jenkins.io/project/governance/#compatibility-matters then,
> because looking at this thread, compatibility clearly doesn't matter
> anymore?
>
> --
> 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/B214EACA-57A8-4EB4-9FFA-C59B2F0D9D89%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAA0qCNwD%3DMMh5i%2BjeEte6CxRqQ%3DcCVEZqmNMxtPcgC8JUJ_0vA%40mail.gmail.com.

Re: Online Meetup Submission - From local installation to scalable Jenkins on Kubernetes

[Oleg Nenashev]

// CC Advocacy SIG

On Wed, May 5, 2021 at 2:59 PM Oleg Nenashev  wrote:

> Hi, thanks for the proposal!
> We should definitely do this meetup, Jenkins Operator for Kubernetes is a
> hot topic.
> Created a Doodle Poll for the final timeslot:
> https://doodle.com/poll/a8w4r86q29rgdt42?utm_source=poll_medium=link
>
>
>
> On Wednesday, May 5, 2021 at 2:21:15 PM UTC+2 bant...@virtuslab.com wrote:
>
>> Hi everyone,
>>
>> I'd like to share Online Meetup submission in the area of running Jenkins
>> and Kubernetes.
>>
>> Feel free to share your views and comments - the presentation is still
>> work in progress so we are happy take it into consideration.
>>
>> Abstract:
>> https://docs.google.com/document/d/1jLh15woOiuv3uKmiFnq79t-HMMdTw8eddcsKs0ETCSY/edit?usp=sharing
>>
>> Regards,
>> Bartek
>>
>> --
> 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/L0Gd7PabVrc/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/b1acbaef-7e04-4236-80d6-bec8e7270e36n%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/CAPfivLBqf4PyZLsNLPupE2bk9nhJsCA8T9_hpUa-8Hem3Zza8w%40mail.gmail.com.

Re: Online Meetup Submission - From local installation to scalable Jenkins on Kubernetes

[Oleg Nenashev]

Hi, thanks for the proposal!
We should definitely do this meetup, Jenkins Operator for Kubernetes is a 
hot topic.
Created a Doodle Poll for the final timeslot:  
https://doodle.com/poll/a8w4r86q29rgdt42?utm_source=poll_medium=link



On Wednesday, May 5, 2021 at 2:21:15 PM UTC+2 bant...@virtuslab.com wrote:

> Hi everyone,
>
> I'd like to share Online Meetup submission in the area of running Jenkins 
> and Kubernetes.
>
> Feel free to share your views and comments - the presentation is still 
> work in progress so we are happy take it into consideration.
>
> Abstract: 
> https://docs.google.com/document/d/1jLh15woOiuv3uKmiFnq79t-HMMdTw8eddcsKs0ETCSY/edit?usp=sharing
>
> Regards,
> Bartek
>
>

-- 
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/b1acbaef-7e04-4236-80d6-bec8e7270e36n%40googlegroups.com.

Re: Hosting Team

[slide]

The meeting is at 4PM UTC, my mistake.

On Tuesday, May 4, 2021 at 1:14:53 PM UTC-7 slide wrote:

> Hi Everyone,
>
> If you have been looking for a way to help out Jenkins, there is an 
> opportunity that we are having a kickoff meeting tomorrow. The Hosting team 
> needs more people to be involved in helping with onboarding for new 
> plugins. We will be going over what goes on during the hosting process and 
> how you can be involved tomorrow (May 5) at 3:00PM UTC. The zoom link is 
> https://zoom.us/j/92062641880. The hosting process is vital to getting 
> new plugins into the update center. It is not a lot of work, but many hands 
> make light work and having more eyes will help to improve the plugins that 
> get into the Jenkins infrastructure.
>
> Thanks!
>
> Alex
>

-- 
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/0ba304d8-0495-42df-84b7-4c76f3959233n%40googlegroups.com.

Online Meetup Submission - From local installation to scalable Jenkins on Kubernetes

['Bartłomiej Antoniak' via Jenkins Developers]

Hi everyone,

I'd like to share Online Meetup submission in the area of running Jenkins 
and Kubernetes.

Feel free to share your views and comments - the presentation is still work 
in progress so we are happy take it into consideration.

Abstract: 
https://docs.google.com/document/d/1jLh15woOiuv3uKmiFnq79t-HMMdTw8eddcsKs0ETCSY/edit?usp=sharing

Regards,
Bartek


-- 
Email correspondence is considered personal data processing. Check out our 
Privacy Policy  for details about the 
controller of your data and your rights according to GDPR/RODO.

-- 
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/f6a526f5-6356-42dc-9a51-c68f40854d19n%40googlegroups.com.

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Daniel Beck]

> On 5. May 2021, at 09:41, Manuel Ramón León Jiménez 
>  wrote:
> 
> I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in for 
> anything to avoid us dealing with the same problems in the future. We need to 
> modernize Jenkins in many aspects and those old / unmaintained plugins are an 
> obstacle and a waste of effort.

Time to delete https://www.jenkins.io/project/governance/#compatibility-matters 
then, because looking at this thread, compatibility clearly doesn't matter 
anymore?

-- 
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/B214EACA-57A8-4EB4-9FFA-C59B2F0D9D89%40beckweb.net.

Re: Jenkins Terminology cleanup continued - sub-terms for controllers

[Daniel Beck]

> On 4. May 2021, at 16:59, Oleg Nenashev  wrote:
> 
>   • Master node => "Built-in Node"

To provide a bit of context for this one for those that don't remember from 
last year :-)

Before, there was no real distinction between "Jenkins master, the process" 
(mostly) and "Jenkins master, the node". When I worked on the PR in which I 
started cleaning up the terms, it became apparent a different term could be 
useful.[1]

A simple example: The built-in node can be offline while the controller is 
otherwise running.

In some code, the relation between master-specific and global node properties 
also wasn't clear in some places because both were occasionally called "master" 
(and only one set is inherited by agents).

There's not a huge list of obvious examples because a lot of the things that 
could matter are shared (process, file system, config file to an extent) or 
irrelevant (node launcher).

I still think it would be useful to distinguish in terms between the controller 
and the built-in node, if only because 'controller' for the node may create 
wrong associations (it controlling things, rather than "just" being part of the 
controller process).


However there are also limitations, which make a different term not an 
obviously correct choice:

- The built-in node is part of the controller process, it shares the 
controller's file system and OS permissions. If the built-in node is doing 
work, the controller has load. A lot of resources are shared, so "the built-in 
node's configuration is stored in the config.xml file with most of the 
controller configuration on the controller file system" etc.
- People seem to confuse executors and nodes/agents fairly regularly, so may 
well consider these to be the same thing because the differences are way less 
relevant than compared to agents, leading to wrong documentation and other 
advice, possibly confusing those aware of the terms. (It might help that 
controller as a term is getting rather well established, and that the node will 
get labels (both UI and environment var) referring to it by its new name, but 
who knows.) 


I encourage you to check out the PR with placeholder term to get a sense for 
the differences and consider whether you think distinguishing the terms is 
useful. As the PR is still a draft and uses an obvious placeholder term, please 
skip doing an actual review for now.

(Note that the behavior-changing code in my PR (related to migration) would be 
needed anyway, regardless of the term we choose. It's more about removing 
"master" than what the replacement term is.)


1: https://github.com/jenkinsci/jenkins/pull/5425

-- 
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/191B4D76-9636-4D27-97C7-E4342186FD12%40beckweb.net.

Re: Plugin end-of-life (EOL) policy

[Oleg Nenashev]

> Thank you Oleg for triggering the discussion. 

Credits go to Basil :) We had the discussion about EOL/adoption policy 
plugins multiple times, and I am totally in favor of getting it over the 
line.
Maintaining the current status quo is a disservice to Jenkins users

On Wednesday, May 5, 2021 at 9:47:27 AM UTC+2 manuel.ramon...@gmail.com 
wrote:

> I'm in for this proposal. We need a way to clean up the ecosystem to be 
> able to progress easily without investing too much on things that are not 
> used.
>
> We can discuss and polish the details, but the aim remains the same. 
>
> Thank you Oleg for triggering the discussion.
>
> On Tue, May 4, 2021 at 7:08 PM Oleg Nenashev  wrote:
>
>> I tentatively put the topic to the tomorrow's governance meeting agenda: 
>> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.1gtco63t6ztr
>> We will discuss it if there are the stakeholders from this thread and 
>> enough time left.
>>
>>
>>
>> On Monday, May 3, 2021 at 3:25:32 PM UTC+2 Jesse Glick wrote:
>>
>>> On Mon, May 3, 2021 at 3:46 AM Daniel Beck  wrote:
>>>
 Something more extensible, with version ranges like we do for security 
 warnings could help here:
 "This plugin is likely to break the UI once you update Jenkins to 
 2.277.x" and "no fix is available" or "update to version X or newer".

>>>
>>> FYI https://issues.jenkins.io/browse/JENKINS-49651 
>>>
>> -- 
>>
> 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/9c82d2f8-4f8a-4cf2-b1a1-ea8247c8e530n%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/f3c21156-5671-423f-928a-e654809a18e8n%40googlegroups.com.

Re: Adoption of plugin Google Container Registry Auth

[Oleg Nenashev]

CCed Wei Z who is currently listed as the plugin maintainer. According to
the plugin adoption policy
,
we will wait for 2 weeks for a response. An earlier response will be
appreciated!

-- 
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/CAPfivLCs4TAzr9d5vVZBvdmxVkUQ3Y3a%3DP3RY4rO6pz%3De5NqZw%40mail.gmail.com.

Re: Adoption of plugin Google Container Registry Auth

[Oleg Nenashev]

Thanks for your interest Vincent! The plugin is not marked for adoption, so 
we will need to ping the maintainers even after 5 years of inactivity (pending 
plugin EOL/adoption policy discussion 
). I will do it.
I have also reviewed the pull request and provided some feedback.


On Wednesday, May 5, 2021 at 10:28:52 AM UTC+2 vge...@gmail.com wrote:

> Hi,
>
> I would like to request push access for ;
> https://plugins.jenkins.io/google-container-registry-auth/
>
> I made a PR that needs some more work, especially on some integration 
> tests, contacted the developer, no response.
> Perhaps it can be marked for adoption first, but I am happy to take it for 
> now.
>
> There is an easy to fix bug in there that causes many other plugins to 
> fail because of  the tables-to-div change.
> Ticket is here:
> https://issues.jenkins.io/browse/JENKINS-64976
> It would be a good start if anyone can remove the mentioned quote, it 
> seems that is the thing that makes it look that a lot of other plugins are 
> broken.
> I upgraded all libraries to recent/latest and I am trying to make the few 
> faiing tests work - it would be great to get some help there because at the 
> moment it is not entirely clear what the author meant to test to me.
>
> Thanks and kind regards,
> Vincent
>

-- 
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/7767d1ec-e47e-4bf6-b742-7eea246aeb5fn%40googlegroups.com.

Adoption of plugin Google Container Registry Auth

[Vincent Gerris]

Hi,

I would like to request push access for ;
https://plugins.jenkins.io/google-container-registry-auth/

I made a PR that needs some more work, especially on some integration 
tests, contacted the developer, no response.
Perhaps it can be marked for adoption first, but I am happy to take it for 
now.

There is an easy to fix bug in there that causes many other plugins to fail 
because of  the tables-to-div change.
Ticket is here:
https://issues.jenkins.io/browse/JENKINS-64976
It would be a good start if anyone can remove the mentioned quote, it seems 
that is the thing that makes it look that a lot of other plugins are broken.
I upgraded all libraries to recent/latest and I am trying to make the few 
faiing tests work - it would be great to get some help there because at the 
moment it is not entirely clear what the author meant to test to me.

Thanks and kind regards,
Vincent

-- 
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/5749afaa-9223-4cd1-b665-9db45fc43fe7n%40googlegroups.com.

Re: Jenkins Governance Meeting on May 05, 2021

[Oleg Nenashev]

Added Commons Digester to the agenda. It looks like we need to agree in the 
thread, e.g. whether JEP is needed

On Tuesday, May 4, 2021 at 11:35:23 PM UTC+2 Baptiste Mathus wrote:

> Yes, socializing the idea at this point I would say. And probably getting 
> some potential feedback on the proposed action plan.
>
> As much as I would obviously love to move forward sooner than later, I 
> think asking for a decision already would be a bit too early and 
> disingenuous from me. 
>
>
> Le mar. 4 mai 2021 à 23:16, Oleg Nenashev  a écrit :
>
>> Hu Baptiste. No objections from me w.r.t. adding it to the agenda. Do you 
>> expect to get a deciaion there? Or is it just a way to socialiye the 
>> proposal? Both options LGTM
>>
>> On Tue, May 4, 2021, 23:05 Baptiste Mathus  wrote:
>>
>>> Hi Oleg, hi everyone, 
>>>
>>> I've just sent an email update in the other thread about 
>>> commons-digester:2.1. 
>>> If you think this would be worth raising this too during the governance 
>>> meeting, I can probably try and join this time (given 20:00 UTC+1 can work 
>>> for me, thanks Summer time :)).
>>>
>>> -- Baptiste
>>>
>>> Le mar. 4 mai 2021 à 19:16, Oleg Nenashev  a 
>>> écrit :
>>>
 Dear all,

 Tomorrow we will have the regular Jenkins Governance meeting. The 
 meeting will start at 7PM UTC, everyone is welcome to participate! 
 Calendar 
 link: here 
 

 Current topics (full agenda and links 
 
 ):

- News: 2.277.4 Release, SheCodeAfrica summary, DevOps World
- Confirming the CDF TOC project representative nomination for 
Jenkins 
- Terminology updates - finalizing the terms
- Update on the Hosting team
- Jenkins SDLC security - confirming the pilot project with LFX 
Security and Snyk
- Roadmap Updates Review
- JEP Process updates (and BDFL?)
- TBD: GitHub Issues for open governance projects/backlog
- TBD: Plugin End-of-Life Policy

 If you want to add a topic, please suggest a topic in the Google Doc. 
 Note that we also have the Roadmap Review topic in the list. Everyone is 
 encouraged to submit their roadmap updates to the jenkins.io repo so 
 that we review them tomorrow: 
 https://github.com/jenkins-infra/jenkins.io/labels/roadmap . 

 #MayThe4BeWithYou,
 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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/3eb70f0b-389a-46c5-ba53-63d5e36357edn%40googlegroups.com
  
 
 .

>>> -- 
>>> 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/YzRC7tvi8tA/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6ZSk%2B-Q6rJOHgee__QqQi2Rree3QGoNfoTtyZcz%2BQXZA%40mail.gmail.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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDRcH41CNniO_UCACfDXMbLf%3Dtw58FpXwCbWwf6GujFzw%40mail.gmail.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/f300b7a5-b85f-4939-8dd7-79060fdda334n%40googlegroups.com.

Proposal: "Friend Of Jenkins" Revamp

[Oleg Nenashev]

Dear all,

We’ve recently had a few discussions with the board and Daniel Beck about 
the “Friend of Jenkins” plugin. This is a plugin referenced from 
https://www.jenkins.io/donate: *“In showing our appreciation, we’ll send 
out a special "friend of Jenkins" plugin to those who have donated at least 
25 USD / 25 EUR. This plugin adds a little icon in the footer section, 
telling that you are a friend of Jenkins. You can install this to your 
Jenkins to show off that you’ve helped us”*. De facto, we have not been 
doing so in the recent years. There are a few problems associated with the 
plugin.

*First of all*, you can become a “Friend of Jenkins” only by donating 
money. IMO it goes against open source values, we should equally appreciate 
all kinds of contributions and avoid promoting money donations 
specifically. *Secondly*, the plugin is private source at the moment. It is 
weird to send a private source plugin to anyone, especially as 
appreciation. *Thirdly*, the plugin is dated. It has not been updated for a 
while, and it does not use modern build/test pipelines. For example the 
code still targets Jenkins 1.396 as the build target. Even if the code is 
tiny, it is not good to send such a questionable build to Jenkins users and 
suggest its installation. *Last but not least*, sending private builds in 
email is flawed on its own due to the risk of various social engineering 
attacks.

I suggest that we completely tear down the “Friend of Jenkins” program:

   - We remove sections about “Friend of Jenkins” from the Donations page
   - Instead of sending the plugin, the Jenkins Governance Board will focus 
   on sending appreciation letters and recognizing donations through Jenkins 
   social media. It should help us to build relationships with donors and 
   hopefully get them involved in the community.
   

Later actions (no specific timeline):

   - We (as community) open source the plugin as the standard Jenkins 
   plugin on https://github.com/jenkinsci, update it to the modern 
   development pipelines.
   - We update the plugin to reference https://www.jenkins.io/participate/ 
   instead of donations.  We might add “Donate” as a type of participation to 
   the list 
   - We release the plugin as 2.0, without changing the artifact ID. Any 
   user of the older private source version, if any, will be able to update 
   via the update center. Any Jenkins user will be also able to install it via 
   the plugin manager, no preconditions.
   - We reference the plugin from the install wizard suggestions (not 
   installed by default), and other places.

There were also some discussions about building signed versions of the 
plugin and somehow allowing to verify the “Friend of Jenkins” status. 
Although I proposed it, now I do not think it is really needed. We can 
discuss it for future iterations.

Would appreciate any feedback, and I suggest discussing that at the next 
Governance meeting.

Best regards,
Oleg Nenashev
Jenkins Governance Board

-- 
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/16fead23-40c3-4908-a1cc-0c1a5d0e25c8n%40googlegroups.com.

Re: Plugin end-of-life (EOL) policy

[Manuel Ramón León Jiménez]

I'm in for this proposal. We need a way to clean up the ecosystem to be
able to progress easily without investing too much on things that are not
used.

We can discuss and polish the details, but the aim remains the same.

Thank you Oleg for triggering the discussion.

On Tue, May 4, 2021 at 7:08 PM Oleg Nenashev  wrote:

> I tentatively put the topic to the tomorrow's governance meeting agenda:
> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.1gtco63t6ztr
> We will discuss it if there are the stakeholders from this thread and
> enough time left.
>
>
>
> On Monday, May 3, 2021 at 3:25:32 PM UTC+2 Jesse Glick wrote:
>
>> On Mon, May 3, 2021 at 3:46 AM Daniel Beck  wrote:
>>
>>> Something more extensible, with version ranges like we do for security
>>> warnings could help here:
>>> "This plugin is likely to break the UI once you update Jenkins to
>>> 2.277.x" and "no fix is available" or "update to version X or newer".
>>>
>>
>> FYI https://issues.jenkins.io/browse/JENKINS-49651
>>
> --
> 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/9c82d2f8-4f8a-4cf2-b1a1-ea8247c8e530n%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/CADN1OJ31%3D_fRNMSxSktSBr%3DzmfYEW6QgSbk63L0MQUmvORbNTw%40mail.gmail.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Oleg Nenashev]

Good question. I added the board, because I do not know which kind of 
traffic we will get.
Changing to Infra is reasonable.


On Wednesday, May 5, 2021 at 9:44:30 AM UTC+2 timja...@gmail.com wrote:

> I see the board is the email contact, 
> https://plugins.jetbrains.com/organizations/jenkins 
>
> Is that an expected contact point? Would it be better to set the dev 
> mailing list or infra?
>
> On Wed, 5 May 2021 at 08:41, Oleg Nenashev  wrote:
>
>> Added Tim and Kohsuke to the org. Everyone is admin for now.
>> We can figure out permissions later if needed
>>
>> On Wednesday, May 5, 2021 at 9:36:32 AM UTC+2 timja...@gmail.com wrote:
>>
>>> > If you want to join the org, please share your JetBrains Marketplace 
>>> account IDs
>>>
>>> my email is my ID as far as I can tell
>>>
>>> On Wed, 5 May 2021 at 07:58, Denys Digtiar  wrote:
>>>
 > Maybe it makes sense to rename the plugin to "Jenkins plugin", 
 Stapler is not really used elsewhere. Having it as Jenkins plugin allows 
 to 
 add more Jenkins-specific features, 
 I actually had the same though. I even put it in writing :) 
 https://github.com/stapler/idea-stapler-plugin/issues/43

 On Wednesday, 5 May 2021 at 16:51:12 UTC+10 Oleg Nenashev wrote:

> I went ahead and created 
> https://plugins.jetbrains.com/organizations/jenkins . If you want to 
> join the org, please share your JetBrains Marketplace account IDs in this 
> thread.
> And thanks to Denys for driving this topic!
>
> On Wednesday, May 5, 2021 at 8:44:19 AM UTC+2 Oleg Nenashev wrote:
>
>> +1000 as well
>>
>> I am not sure we want to just move the existing plugin though. Maybe 
>> it makes sense to rename the plugin to "Jenkins plugin", Stapler is not 
>> really used elsewhere. Having it as Jenkins plugin allows to add more 
>> Jenkins-specific features, e.g. better developer run mode or deeper 
>> integrations with Jenkins Test Harness, or various context help 
>> dedicated 
>> to Jenkins development (e.g. REST API, permission check checks, custom 
>> static analysis rules, etc., etc.). I would also suggest moving it to 
>> the 
>> jenkinsci GitHub organization so that we could manage it more 
>> efficiently 
>> and attract contributors.
>>
>>
>>
>>
>> On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com 
>> wrote:
>>
>>> +1000
>>>
>>> On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:
>>>

 Posting here based on the discussion in 
 @stapler/idea-stapler-plugin#44 
 

 Stapler plugin for IntelliJ IDEA is currently listed under KK's 
 account.
 JetBrains added JetBrains Marketplace Organizations 
  
 which enables plugin listing/management by a group of people.

 Would it be possible to create a Jenkins organization?
 KK then will be able to transfer the plugin to be managed by the 
 wider Jenkins community.

 As a follow-up, the release process can then be fully automated, 
 see https://github.com/stapler/idea-stapler-plugin/issues/14

 -- 
 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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-de...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/a36e20af-d65a-4363-93fe-17384e01c8c5n%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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/db6d87e9-3683-4234-b5f5-3fad171f5958n%40googlegroups.com
>>  
>> 

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Tim Jacomb]

I see the board is the email contact,
https://plugins.jetbrains.com/organizations/jenkins

Is that an expected contact point? Would it be better to set the dev
mailing list or infra?

On Wed, 5 May 2021 at 08:41, Oleg Nenashev  wrote:

> Added Tim and Kohsuke to the org. Everyone is admin for now.
> We can figure out permissions later if needed
>
> On Wednesday, May 5, 2021 at 9:36:32 AM UTC+2 timja...@gmail.com wrote:
>
>> > If you want to join the org, please share your JetBrains Marketplace
>> account IDs
>>
>> my email is my ID as far as I can tell
>>
>> On Wed, 5 May 2021 at 07:58, Denys Digtiar  wrote:
>>
>>> > Maybe it makes sense to rename the plugin to "Jenkins plugin", Stapler
>>> is not really used elsewhere. Having it as Jenkins plugin allows to add
>>> more Jenkins-specific features,
>>> I actually had the same though. I even put it in writing :)
>>> https://github.com/stapler/idea-stapler-plugin/issues/43
>>>
>>> On Wednesday, 5 May 2021 at 16:51:12 UTC+10 Oleg Nenashev wrote:
>>>
 I went ahead and created
 https://plugins.jetbrains.com/organizations/jenkins . If you want to
 join the org, please share your JetBrains Marketplace account IDs in this
 thread.
 And thanks to Denys for driving this topic!

 On Wednesday, May 5, 2021 at 8:44:19 AM UTC+2 Oleg Nenashev wrote:

> +1000 as well
>
> I am not sure we want to just move the existing plugin though. Maybe
> it makes sense to rename the plugin to "Jenkins plugin", Stapler is not
> really used elsewhere. Having it as Jenkins plugin allows to add more
> Jenkins-specific features, e.g. better developer run mode or deeper
> integrations with Jenkins Test Harness, or various context help dedicated
> to Jenkins development (e.g. REST API, permission check checks, custom
> static analysis rules, etc., etc.). I would also suggest moving it to the
> jenkinsci GitHub organization so that we could manage it more efficiently
> and attract contributors.
>
>
>
>
> On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com
> wrote:
>
>> +1000
>>
>> On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:
>>
>>>
>>> Posting here based on the discussion in
>>> @stapler/idea-stapler-plugin#44
>>> 
>>>
>>> Stapler plugin for IntelliJ IDEA is currently listed under KK's
>>> account.
>>> JetBrains added JetBrains Marketplace Organizations
>>> 
>>> which enables plugin listing/management by a group of people.
>>>
>>> Would it be possible to create a Jenkins organization?
>>> KK then will be able to transfer the plugin to be managed by the
>>> wider Jenkins community.
>>>
>>> As a follow-up, the release process can then be fully automated, see
>>> https://github.com/stapler/idea-stapler-plugin/issues/14
>>>
>>> --
>>> 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/a36e20af-d65a-4363-93fe-17384e01c8c5n%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/db6d87e9-3683-4234-b5f5-3fad171f5958n%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 

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Manuel Ramón León Jiménez]

I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in for
anything to avoid us dealing with the same problems in the future. We need
to modernize Jenkins in many aspects and those old / unmaintained plugins
are an obstacle and a waste of effort. Something like put for adoption
every plugin without a release for a year or use another label and state
clearly that the effort from the community won't take into account the
plugins with this label. Or something like that.

Basically what Oleg wrote on the email *Plugin end-of-life (EOL) policy.*

Thanks!

On Wed, May 5, 2021 at 4:58 AM Oleg Nenashev  wrote:

> What about a quick JEP? We are working on removing obstacles in the
> process, an a test for the new process would be great
>
> On Wed, May 5, 2021, 01:16 Basil Crow  wrote:
>
>> On Tue, May 4, 2021 at 2:02 PM Baptiste Mathus  wrote:
>> > So the big question is: what do we do?
>> >
>> > I personally think we should NOT make these PRs land if no maintainer
>> steps up.
>> > In other words, once we merge and release the Core PR, these plugins
>> will likely just fail loading on newer Jenkins releases.
>>
>> I concur with Baptiste. For plugins that have not seen any activity,
>> yet alone a release, in more than five years (and on which no other
>> plugins depend), I do not believe the benefit to be gained is worth
>> the cost.
>>
>> --
>> 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/m2fEX5ALvbg/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/CAFwNDjp9q5sdO%2BuYUH2voGYqufHs%2BE3gULdvdnwCHwgWGByLEg%40mail.gmail.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/CAPfivLDz5m2Z8W441jCPQAxsj%3DvfG2uK5TdRJZpLXSH8uanKfA%40mail.gmail.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/CADN1OJ1%3DpCdSQrQiqM%2BxVgOczh0n9MoyiV3HcPGQkc3r%3D0k8gg%40mail.gmail.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Oleg Nenashev]

Added Tim and Kohsuke to the org. Everyone is admin for now.
We can figure out permissions later if needed

On Wednesday, May 5, 2021 at 9:36:32 AM UTC+2 timja...@gmail.com wrote:

> > If you want to join the org, please share your JetBrains Marketplace 
> account IDs
>
> my email is my ID as far as I can tell
>
> On Wed, 5 May 2021 at 07:58, Denys Digtiar  wrote:
>
>> > Maybe it makes sense to rename the plugin to "Jenkins plugin", Stapler 
>> is not really used elsewhere. Having it as Jenkins plugin allows to add 
>> more Jenkins-specific features, 
>> I actually had the same though. I even put it in writing :) 
>> https://github.com/stapler/idea-stapler-plugin/issues/43
>>
>> On Wednesday, 5 May 2021 at 16:51:12 UTC+10 Oleg Nenashev wrote:
>>
>>> I went ahead and created 
>>> https://plugins.jetbrains.com/organizations/jenkins . If you want to 
>>> join the org, please share your JetBrains Marketplace account IDs in this 
>>> thread.
>>> And thanks to Denys for driving this topic!
>>>
>>> On Wednesday, May 5, 2021 at 8:44:19 AM UTC+2 Oleg Nenashev wrote:
>>>
 +1000 as well

 I am not sure we want to just move the existing plugin though. Maybe it 
 makes sense to rename the plugin to "Jenkins plugin", Stapler is not 
 really 
 used elsewhere. Having it as Jenkins plugin allows to add more 
 Jenkins-specific features, e.g. better developer run mode or deeper 
 integrations with Jenkins Test Harness, or various context help dedicated 
 to Jenkins development (e.g. REST API, permission check checks, custom 
 static analysis rules, etc., etc.). I would also suggest moving it to the 
 jenkinsci GitHub organization so that we could manage it more efficiently 
 and attract contributors.




 On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com wrote:

> +1000
>
> On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:
>
>>
>> Posting here based on the discussion in 
>> @stapler/idea-stapler-plugin#44 
>> 
>>
>> Stapler plugin for IntelliJ IDEA is currently listed under KK's 
>> account.
>> JetBrains added JetBrains Marketplace Organizations 
>>  
>> which enables plugin listing/management by a group of people.
>>
>> Would it be possible to create a Jenkins organization?
>> KK then will be able to transfer the plugin to be managed by the 
>> wider Jenkins community.
>>
>> As a follow-up, the release process can then be fully automated, see 
>> https://github.com/stapler/idea-stapler-plugin/issues/14
>>
>> -- 
>> 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/a36e20af-d65a-4363-93fe-17384e01c8c5n%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/db6d87e9-3683-4234-b5f5-3fad171f5958n%40googlegroups.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Tim Jacomb]

> If you want to join the org, please share your JetBrains Marketplace
account IDs

my email is my ID as far as I can tell

On Wed, 5 May 2021 at 07:58, Denys Digtiar  wrote:

> > Maybe it makes sense to rename the plugin to "Jenkins plugin", Stapler
> is not really used elsewhere. Having it as Jenkins plugin allows to add
> more Jenkins-specific features,
> I actually had the same though. I even put it in writing :)
> https://github.com/stapler/idea-stapler-plugin/issues/43
>
> On Wednesday, 5 May 2021 at 16:51:12 UTC+10 Oleg Nenashev wrote:
>
>> I went ahead and created
>> https://plugins.jetbrains.com/organizations/jenkins . If you want to
>> join the org, please share your JetBrains Marketplace account IDs in this
>> thread.
>> And thanks to Denys for driving this topic!
>>
>> On Wednesday, May 5, 2021 at 8:44:19 AM UTC+2 Oleg Nenashev wrote:
>>
>>> +1000 as well
>>>
>>> I am not sure we want to just move the existing plugin though. Maybe it
>>> makes sense to rename the plugin to "Jenkins plugin", Stapler is not really
>>> used elsewhere. Having it as Jenkins plugin allows to add more
>>> Jenkins-specific features, e.g. better developer run mode or deeper
>>> integrations with Jenkins Test Harness, or various context help dedicated
>>> to Jenkins development (e.g. REST API, permission check checks, custom
>>> static analysis rules, etc., etc.). I would also suggest moving it to the
>>> jenkinsci GitHub organization so that we could manage it more efficiently
>>> and attract contributors.
>>>
>>>
>>>
>>>
>>> On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com wrote:
>>>
 +1000

 On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:

>
> Posting here based on the discussion in
> @stapler/idea-stapler-plugin#44
> 
>
> Stapler plugin for IntelliJ IDEA is currently listed under KK's
> account.
> JetBrains added JetBrains Marketplace Organizations
> 
> which enables plugin listing/management by a group of people.
>
> Would it be possible to create a Jenkins organization?
> KK then will be able to transfer the plugin to be managed by the wider
> Jenkins community.
>
> As a follow-up, the release process can then be fully automated, see
> https://github.com/stapler/idea-stapler-plugin/issues/14
>
> --
> 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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/a36e20af-d65a-4363-93fe-17384e01c8c5n%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/CAH-3Bic_Znt-2hM6hLgNDjFXMCSaGAsexq%3DFnfYw5qWmc6jgOQ%40mail.gmail.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Denys Digtiar]

Thank you, Oleg! 
The next steps according to the docs are
1. Add KK to the Org
2. Change the Vendor in the plugin metadata and release
3. Transfer the plugin
I will find time to follow-up

On Wednesday, 5 May 2021 at 16:58:52 UTC+10 Denys Digtiar wrote:

> > Maybe it makes sense to rename the plugin to "Jenkins plugin", Stapler 
> is not really used elsewhere. Having it as Jenkins plugin allows to add 
> more Jenkins-specific features, 
> I actually had the same though. I even put it in writing :) 
> https://github.com/stapler/idea-stapler-plugin/issues/43
>
> On Wednesday, 5 May 2021 at 16:51:12 UTC+10 Oleg Nenashev wrote:
>
>> I went ahead and created 
>> https://plugins.jetbrains.com/organizations/jenkins . If you want to 
>> join the org, please share your JetBrains Marketplace account IDs in this 
>> thread.
>> And thanks to Denys for driving this topic!
>>
>> On Wednesday, May 5, 2021 at 8:44:19 AM UTC+2 Oleg Nenashev wrote:
>>
>>> +1000 as well
>>>
>>> I am not sure we want to just move the existing plugin though. Maybe it 
>>> makes sense to rename the plugin to "Jenkins plugin", Stapler is not really 
>>> used elsewhere. Having it as Jenkins plugin allows to add more 
>>> Jenkins-specific features, e.g. better developer run mode or deeper 
>>> integrations with Jenkins Test Harness, or various context help dedicated 
>>> to Jenkins development (e.g. REST API, permission check checks, custom 
>>> static analysis rules, etc., etc.). I would also suggest moving it to the 
>>> jenkinsci GitHub organization so that we could manage it more efficiently 
>>> and attract contributors.
>>>
>>>
>>>
>>>
>>> On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com wrote:
>>>
 +1000

 On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:

>
> Posting here based on the discussion in 
> @stapler/idea-stapler-plugin#44 
> 
>
> Stapler plugin for IntelliJ IDEA is currently listed under KK's 
> account.
> JetBrains added JetBrains Marketplace Organizations 
>  
> which enables plugin listing/management by a group of people.
>
> Would it be possible to create a Jenkins organization?
> KK then will be able to transfer the plugin to be managed by the wider 
> Jenkins community.
>
> As a follow-up, the release process can then be fully automated, see 
> https://github.com/stapler/idea-stapler-plugin/issues/14
>
> -- 
> 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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/d816e445-f3a5-47ff-afbb-7066cb22604cn%40googlegroups.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

[Oleg Nenashev]

FTR here is the query for known Java 11 compatibility issues 
in
 
Jira. Some issues are not a blocker, for example Illegal Reflective Access 
which will become a big deal in Java 17.

The biggest remaining issue is Removal of JAXB dependencies and replacing 
them by the JAXB API plugin where required (JENKINS-55944 
). It impacts a number of 
plugins including CppCheck, codesonar, Job Import, etc. Baptiste Mathus has 
created a number of pull requests when we were working on the Java 11 
support, but not all of them were merged/released AFAICT. Ideally we should 
do an issue scrub and review the state before deciding on this topic.

Time to write up a JEP by the way?


On Thursday, April 29, 2021 at 9:21:48 AM UTC+2 Olblak wrote:

> Hi,
>
> I am definitely in favor of switching to jdk11 by default, it's really 
> time to move forward. We have been using it on the Jenkins infrastructure 
> project for almost a year now without major issues but we also had to 
> fine-tune the java configuration for java 11.
>
> That remains a major change with potential breaking changes, so I would 
> announce it enough in advance so people can already switch to jdk11, and 
> keep the java8 for several stable releases with a deprecation warning.
>
>
>
> On Wed, Apr 28, 2021, at 6:20 PM, Tim Jacomb wrote:
>
> Defaults and (people not seeing a need to change)
>
> Shipping an ‘admin monitor’ encouraging people to update would probably 
> make a difference 
>
> On Wed, 28 Apr 2021 at 17:18, Tim Jacomb  wrote:
>
> It’s just down to defaults I think.
>
> We’ve seen the numbers rise as we changed the website and helm chart to 
> use Java 11 by default
>
> On Wed, 28 Apr 2021 at 17:08, Daniel Beck  wrote:
>
>
>
> On Wed, Apr 28, 2021 at 1:42 AM Oleg Nenashev  wrote:
>
> I am in favor of making JDK11 the default in all our distributions, 
> including controller and agent Docker images.
> At the same time I am afraid that removal of Java 1.8 support is 
> premature. The vast majority of Jenkins users still uses this version, and 
> the migration to Java 11 won't be seamless in al l cases. For example, 
> Maven Plugin will effectively switch project builds to Java 11 once the 
> agent images are updated. It will cause unexpected issues in user builds 
> here and there. Nothing should be critical, but we should not force users 
> to migrate immediately.
>
> IMHO there should be a grace period between Java 8 support deprecation and 
> the actual removal. Maybe 6 months or so.
>
>
> Agree; I'd even be more conservative than just six months. We can and 
> should update the default Docker images to run on JDK 11. But we shouldn't 
> ignore that just ~0.3% of instances use Java 11, let's do something about 
> that first. I wouldn't be surprised that there are still some problems to 
> work out but we just have no users yet who would be affected.
>
>
> -- 
> 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/CAMo7PtLW05CwT6JyDHHpq52V%2BZwcRy3hQxPW7O9U-D%3DR1adL7Q%40mail.gmail.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-de...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicOSJ%2B%3DMhXxO2HRz4QL7O8tm5P56MJhJPsU13z3tTe0og%40mail.gmail.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/cbc3bad1-f32d-47fd-a7cc-ba025b8219f1n%40googlegroups.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Denys Digtiar]

> Maybe it makes sense to rename the plugin to "Jenkins plugin", Stapler is 
not really used elsewhere. Having it as Jenkins plugin allows to add more 
Jenkins-specific features, 
I actually had the same though. I even put it in writing :) 
https://github.com/stapler/idea-stapler-plugin/issues/43

On Wednesday, 5 May 2021 at 16:51:12 UTC+10 Oleg Nenashev wrote:

> I went ahead and created 
> https://plugins.jetbrains.com/organizations/jenkins . If you want to join 
> the org, please share your JetBrains Marketplace account IDs in this thread.
> And thanks to Denys for driving this topic!
>
> On Wednesday, May 5, 2021 at 8:44:19 AM UTC+2 Oleg Nenashev wrote:
>
>> +1000 as well
>>
>> I am not sure we want to just move the existing plugin though. Maybe it 
>> makes sense to rename the plugin to "Jenkins plugin", Stapler is not really 
>> used elsewhere. Having it as Jenkins plugin allows to add more 
>> Jenkins-specific features, e.g. better developer run mode or deeper 
>> integrations with Jenkins Test Harness, or various context help dedicated 
>> to Jenkins development (e.g. REST API, permission check checks, custom 
>> static analysis rules, etc., etc.). I would also suggest moving it to the 
>> jenkinsci GitHub organization so that we could manage it more efficiently 
>> and attract contributors.
>>
>>
>>
>>
>> On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com wrote:
>>
>>> +1000
>>>
>>> On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:
>>>

 Posting here based on the discussion in @stapler/idea-stapler-plugin#44 
 

 Stapler plugin for IntelliJ IDEA is currently listed under KK's account.
 JetBrains added JetBrains Marketplace Organizations 
  
 which enables plugin listing/management by a group of people.

 Would it be possible to create a Jenkins organization?
 KK then will be able to transfer the plugin to be managed by the wider 
 Jenkins community.

 As a follow-up, the release process can then be fully automated, see 
 https://github.com/stapler/idea-stapler-plugin/issues/14

 -- 
 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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/a36e20af-d65a-4363-93fe-17384e01c8c5n%40googlegroups.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Oleg Nenashev]

I went ahead and created 
https://plugins.jetbrains.com/organizations/jenkins . If you want to join 
the org, please share your JetBrains Marketplace account IDs in this thread.
And thanks to Denys for driving this topic!

On Wednesday, May 5, 2021 at 8:44:19 AM UTC+2 Oleg Nenashev wrote:

> +1000 as well
>
> I am not sure we want to just move the existing plugin though. Maybe it 
> makes sense to rename the plugin to "Jenkins plugin", Stapler is not really 
> used elsewhere. Having it as Jenkins plugin allows to add more 
> Jenkins-specific features, e.g. better developer run mode or deeper 
> integrations with Jenkins Test Harness, or various context help dedicated 
> to Jenkins development (e.g. REST API, permission check checks, custom 
> static analysis rules, etc., etc.). I would also suggest moving it to the 
> jenkinsci GitHub organization so that we could manage it more efficiently 
> and attract contributors.
>
>
>
>
> On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com wrote:
>
>> +1000
>>
>> On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:
>>
>>>
>>> Posting here based on the discussion in @stapler/idea-stapler-plugin#44 
>>> 
>>>
>>> Stapler plugin for IntelliJ IDEA is currently listed under KK's account.
>>> JetBrains added JetBrains Marketplace Organizations 
>>>  
>>> which enables plugin listing/management by a group of people.
>>>
>>> Would it be possible to create a Jenkins organization?
>>> KK then will be able to transfer the plugin to be managed by the wider 
>>> Jenkins community.
>>>
>>> As a follow-up, the release process can then be fully automated, see 
>>> https://github.com/stapler/idea-stapler-plugin/issues/14
>>>
>>> -- 
>>> 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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/2a5073de-5cf9-46dc-b78b-69d7df03b3cen%40googlegroups.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Oleg Nenashev]

+1000 as well

I am not sure we want to just move the existing plugin though. Maybe it 
makes sense to rename the plugin to "Jenkins plugin", Stapler is not really 
used elsewhere. Having it as Jenkins plugin allows to add more 
Jenkins-specific features, e.g. better developer run mode or deeper 
integrations with Jenkins Test Harness, or various context help dedicated 
to Jenkins development (e.g. REST API, permission check checks, custom 
static analysis rules, etc., etc.). I would also suggest moving it to the 
jenkinsci GitHub organization so that we could manage it more efficiently 
and attract contributors.




On Wednesday, May 5, 2021 at 8:21:17 AM UTC+2 timja...@gmail.com wrote:

> +1000
>
> On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:
>
>>
>> Posting here based on the discussion in @stapler/idea-stapler-plugin#44 
>> 
>>
>> Stapler plugin for IntelliJ IDEA is currently listed under KK's account.
>> JetBrains added JetBrains Marketplace Organizations 
>>  
>> which enables plugin listing/management by a group of people.
>>
>> Would it be possible to create a Jenkins organization?
>> KK then will be able to transfer the plugin to be managed by the wider 
>> Jenkins community.
>>
>> As a follow-up, the release process can then be fully automated, see 
>> https://github.com/stapler/idea-stapler-plugin/issues/14
>>
>> -- 
>> 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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/d3fbfec7-75d7-4a3f-b6ae-e7c5f3df9fd4n%40googlegroups.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Tim Jacomb]

+1000

On Wed, 5 May 2021 at 02:48, Denys Digtiar  wrote:

>
> Posting here based on the discussion in @stapler/idea-stapler-plugin#44
> 
>
> Stapler plugin for IntelliJ IDEA is currently listed under KK's account.
> JetBrains added JetBrains Marketplace Organizations
>  which
> enables plugin listing/management by a group of people.
>
> Would it be possible to create a Jenkins organization?
> KK then will be able to transfer the plugin to be managed by the wider
> Jenkins community.
>
> As a follow-up, the release process can then be fully automated, see
> https://github.com/stapler/idea-stapler-plugin/issues/14
>
> --
> 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/e1aaf8ea-f767-4aa5-aac6-4695718ad596n%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/CAH-3BifkvinTMQT5DbOm537j6viCr1Y2rj8H7HkxP8RZnC7Vxg%40mail.gmail.com.