Re: Reusing Jenkins plugin site for WireMock and other Java projects

[Oleg Nenashev]

FWIW for now I decided to use something dead-simple around MkDocs, its 
multi-repository plugin and import configurator. It is a temporary solution 
that does not include release notes & Co, but it would as MVP until I get 
to a full solution as described 
above. https://github.com/wiremock/components-site. if someone's interested

On Monday, October 9, 2023 at 11:19:23 AM UTC+2 Oleg Nenashev wrote:

> Hello,
>
> TL;DR: What if we generalize some bits of the Jenkins plugin site?
>
> In WireMock we would like to have a plugin listing (GitHub Issue 
> <https://github.com/wiremock/ecosystem/issues/6>), and I would be 
> interested to do that as a part of Hacktoberfest. For that it would be nice 
> to have a "plugin marketplace" engine that...
>
>- Can take the list of the projects from a configuration file
>- Pulls information from GitHub repositories and represents it in a 
>fancy way: READMEs, GitHub Releases, issues, topics, contributors, etc.
>- Has a script for building the website that can be reused in Jenkins 
>or GitHub Actions
>- Supports referencing/embedding Javadoc
>- Showing Maven dependencies, endpoints and usage stats. Nice 2 have: 
>dependencies in open source
>- Customizable so that it could be extended by custom project needs 
>(e.g. plugin dependencies in Jenkins, Jira or Maintainers metadata)
>- Reporting Health Metrics
>- Nice 2 have: List other artifact types in the same interface: 
>developer tools, integration libraries, etc.
>
> I see quite a lot of marketplaces for Java projects like Quarkus 
> extensions, but I have not been able to find a generic engine that would 
> provide a similar experience for Java projects... or a generic marketplace 
> generator that would be extensible enough. And there are quite a lot of 
> smaller Java projects that would be interested in having a generic 
> marketplace generator.
>
> I wonder whether any other Jenkins contributors has a similar use-case and 
> would be interested in maybe having a spin-off project that Reuses the 
> plugin site backend and frontend and introduces a generic static site 
> publication based on that. If you know about generic site generators (e.g. 
> ArtifactHub) that should be rather used for that purpose, it would be great 
> too!
>
> Best regards,
> Oleg
>
> Related: Javadoc site: 
> https://groups.google.com/g/jenkinsci-dev/c/sdvbbm2ggAc/m/EEQv3bMDBAAJ
>

-- 
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/80e1d781-46d3-42db-a230-c779ebeddbf7n%40googlegroups.com.

Re: Proposal: Kris Stern to join the release team

[Oleg Nenashev]

+1

On Wednesday, October 4, 2023 at 1:30:04 PM UTC+2 stephan...@gmail.com 
wrote:

> +1 from me, good work Kris
>
> Le lun. 2 oct. 2023 à 19:57, 'Kevin Martens' via Jenkins Developers <
> jenkin...@googlegroups.com> a écrit :
>
>> +1 from me too!
>>
>> On Mon, Oct 2, 2023 at 1:40 PM Basil Crow  wrote:
>>
>>> +1
>>>
>>> On Mon, Oct 2, 2023 at 5:06 AM Hervé  wrote:
>>>
 FWIW, +1 from me too!

 -- 
 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/CAE1M8%2B9yQf3YzbEPkv%3DnAEQyPFoihRJL5cWGi6myVzwqM9EzZQ%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/CAFwNDjr3h1gnWGTSP0hfwVHd0-VWWA%3DYW_fnvQLr5VAume03Nw%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Kevin Martens
>> Technical Content Developer
>> CloudBees, Inc.
>>
>>
>> E: kmar...@cloudbees.com
>>
>> Pronouns: He/Him/His
>>
>> -- 
>> 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/CAP92yNdo8EE7KMWRrXMiTbZO3QMEHhcMc_v%3DD3%2BdQ_Ss2VU70g%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/8a9b4429-8517-4ddf-befd-e1c94698c73fn%40googlegroups.com.

Reusing Jenkins plugin site for WireMock and other Java projects

[Oleg Nenashev]

Hello,

TL;DR: What if we generalize some bits of the Jenkins plugin site?

In WireMock we would like to have a plugin listing (GitHub Issue 
), and I would be 
interested to do that as a part of Hacktoberfest. For that it would be nice 
to have a "plugin marketplace" engine that...

   - Can take the list of the projects from a configuration file
   - Pulls information from GitHub repositories and represents it in a 
   fancy way: READMEs, GitHub Releases, issues, topics, contributors, etc.
   - Has a script for building the website that can be reused in Jenkins or 
   GitHub Actions
   - Supports referencing/embedding Javadoc
   - Showing Maven dependencies, endpoints and usage stats. Nice 2 have: 
   dependencies in open source
   - Customizable so that it could be extended by custom project needs 
   (e.g. plugin dependencies in Jenkins, Jira or Maintainers metadata)
   - Reporting Health Metrics
   - Nice 2 have: List other artifact types in the same interface: 
   developer tools, integration libraries, etc.

I see quite a lot of marketplaces for Java projects like Quarkus 
extensions, but I have not been able to find a generic engine that would 
provide a similar experience for Java projects... or a generic marketplace 
generator that would be extensible enough. And there are quite a lot of 
smaller Java projects that would be interested in having a generic 
marketplace generator.

I wonder whether any other Jenkins contributors has a similar use-case and 
would be interested in maybe having a spin-off project that Reuses the 
plugin site backend and frontend and introduces a generic static site 
publication based on that. If you know about generic site generators (e.g. 
ArtifactHub) that should be rather used for that purpose, it would be great 
too!

Best regards,
Oleg

Related: Javadoc 
site: https://groups.google.com/g/jenkinsci-dev/c/sdvbbm2ggAc/m/EEQv3bMDBAAJ

-- 
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/4b16558a-fc13-409a-93f8-3969d4924658n%40googlegroups.com.

Re: [Information] 2FA will be enforced in jenkinsci organization

[Oleg Nenashev]

Thanks a lot for driving it! 
+100 for going forward, though there are some GitHub bots to be affected. 
Which is probably a good thing anyway

On Friday, August 4, 2023 at 2:35:05 PM UTC+2 wfoll...@cloudbees.com wrote:

> Hello there,
>
> The jenkinsci administrators have recently received a message from GitHub, 
> that will enforce 2FA setting for more people. It's not related to our 
> settings but a process GitHub is pushing to enforce better security.
>
> The next wave will be for users who have published at least one release in 
> the past. Also note that the scope will increase over time.
>
> For the jenkinsci organization, ~75% of users in scope have already the 
> 2FA in place.
>
> You can read more about this in their blogpost from March 2023 
> 
> .
>
> Best regards,
>
> Wadeck Follonier
> Jenkins Security officer
>

-- 
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/2c15f9a0-abce-4d64-8cb1-c019e6b22442n%40googlegroups.com.

Reusing jenkins-infra/javadoc for WireMock and other projects

[Oleg Nenashev]

Hi all,

I am currently building a Javadoc site generator for WireMock 
repositories. It has a similar structure as Jenkins: 
a number of Java/Kotlin projects in the core, extensions and developer 
tooling.

One could use https://www.javadoc.io/, but the demand from the WireMock 
maintainers is to have a standalone hosting so that additional features 
could be deployed.

It would like to reuse some code 
from https://github.com/jenkins-infra/javadoc and have an updated version 
that...

   1. Takes configuration from a YAML file  (Javadoc components structure)
   2. Supports custom themes, footers and headers for the site, thgat would 
   include the navigation bar by default
   3. Build a static site compatible with GitHub pages
   4. Include a GitHub Actions step for generation
   5. NEXT: Support for including component docs generated by non-Javadoc 
   utilities

I think I could do these bits in a compatible way so that the same 
generator could be used for Jenkins and WireMock, just with a different 
configuration. And the Jenkins one could keep running in Jenkins as now or 
in Jenkinsfile Runner

Would someone else be interested in such a a reusable project?

Best regards,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e44d01ee-142e-4251-a511-279bd25b11ben%40googlegroups.com.

CDF Project Representative nominations

[Oleg Nenashev]

Hi all,

As it was announced in the CDF today, the nominations for CDF project 
representatives are 
open: https://github.com/cdfoundation/foundation/issues/442 . The 
nomination period starts on May 22, 2023 and ends on June 5, 2023. 4 of the 
9 CDF TOC seats are elected from CDF Project representatives per charter. 
Each CDF Project may nominate a maximum of one project representative to 
run for these seats. Nominations must be made under this GitHub issue

I've represented the project since July 2021, and was a TOC chair from 
August 2021 until December 2022. It is a weird situation at the moment, 
because I am taking a long break in the Jenkins community because of the 
war in Ukraine and personal matters. I'm also not very interested in the 
TOC position at the moment, because the foundation cannot back the TOC by 
project management resources to organize sustainable evolution of 
initiatives like CDEvents. I would like to remain the CDF ambassador and 
help the foundation from the advocacy point, but I doubt I could represent 
Jenkins and achieve something positive for the project in the foundation in 
the current state. It would be better if somebody else steps up.

We had a preliminary discussion with Mark Waite, who regularly participates 
in the CDF TOC meetings, and he is interested in taking this role. So I 
would propose to nominate Mark as a single candidate from the Jenkins 
project, unless there are other contributors who want to step up in the 
foundation. Anyone? :) 

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/245fd452-d3e4-48b5-bcfd-8e09d04666can%40googlegroups.com.

Re: Reimbursement for code signing certificate

[Oleg Nenashev]

I am +1 for the request, because obviously code signing is a mission 
critical part of the project, and it took us a lot of effort to get them 
running (e.g. facilitating the CDF legal entity, and so on). As other 
contributors mentioned above, the process was not followed, but in this 
case it should not be a blocker. It worth mentioning that the JEP-15 is 
still in the draft state and not "Active" so one can argue it is not 
obligatory. 

BR, Oleg

On Tuesday, April 18, 2023 at 10:37:18 PM UTC+2 m...@basilcrow.com wrote:

> On Tue, Apr 18, 2023 at 12:29 PM 'Gavin Mogan' via Jenkins Developers
>  wrote:
> > I would argue this discussion should happen before the spending not 
> after.
>
> FTR, from JEP-15 (at revision b8bfe17), § 3.3.4 ("Reimbursement process"), 
> lines
> 193-194:
>
> > Expenses should be pre-approved through the Jenkins developer mailing 
> list and
> > the link Governance meeting **BEFORE** the expense happens.
>

-- 
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/e3ce10fe-b9ca-4fb0-9235-eeaa8a52d2c1n%40googlegroups.com.

Re: Mar 6, 2023 Governance Board Agenda

[Oleg Nenashev]

Hi. Sorry, I will be 30 min late to the meeting

BR, Oleg

On Monday, March 6, 2023 at 6:16:12 PM UTC+1 Mark Waite wrote:

> The Jenkins governance board meets at 6:00 PM UTC today.  Zoom URL is 
> https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 
>
> Agenda:
>
>- 
>
>News
>- 
>   
>   Jenkins is a Google Summer of Code 2023 organization
>   - 
>  
>  Twice a week sessions introducing the project ideas
>  - 
>  
>  Very active conversations in the gitter channels
>  - 
>  
>  Project count will be limited by the number of lead mentors 
>  available
>  - 
>   
>   Jenkins 2.387.1, 2.375.4, and 2.394 release March 8, 2023
>   - 
>  
>  Security release announcement 
>  
>  - 
>   
>   February newsletter being prepared
>   - 
>
>Action items
>- 
>   
>   Rework press contact 
>    page on 
>   jenkins.io - Alexander Brandes
>   - 
>  
>  https://github.com/jenkins-infra/jenkins.io/pull/6115
>  - 
>   
>   Create and distribute election badges for 2022 elections - Mark 
>   Waite 
>   - 
>  
>  No progress, do the research
>  - 
>  
>  Open badge hosted by the Linux Foundation (Oleg can guide Mark)
>  - 
>   
>   EasyCLA to be documented by Oleg
>   - 
>  
>  No progress, no requests pending
>  - 
>   
>   Mark Waite create an empty agenda entry for the next meeting after 
>   each meeting
>   - 
>  
>  Working well, continue doing it
>  - 
>   
>   Mark Waite submit jenkins.io pull request to combine subprojects 
>   and SIGs into a single concept - “working groups”
>   - 
>  
>  No progress, Mark to complete before next meeting
>  - 
>  
>  Roadmap update pull requests, needs to be update
>  - 
>   
>   Retire the Chinese Jenkins site
>   - 
>  
>  Rick recommends  that we redirect the chinese pages to English 
>  equivalents
>  - 
>  
>  Kevin Martens (Docs Officer) tracking help desk ticket 
>   to 
>  replace the Chinese pages with redirects to the English pages
>  - 
>   
>   Mark Waite and Gavin “halkeye” Mogan archive the governance meeting 
>   notes to a GitHub repository, use the Google doc as the working 
> document, 
>   then publish final notes
>   - 
>  
>  Gavin has prepared the archive, need a destination repository
>  - 
>  
>  Alexander Brandes has something in mind how to structure things.
>  - 
>  
>  Infra team raised about the repository location as a question
>  - 
>  
>  Oleg prefers jenkinsci rather than jenkins-infra for a 
>  governance repository (this is not about the archive repository!)
>  - 
> 
> Mark check the infra team preference, discuss if not jenkinsci
> - 
>   
>   Build Monitor View plugin repository transfer to jenkinsci org 
>   @Basil
>   - 
>  
>  Jan Molak published an issue stating he agreed to incorporate 
>  his plugin in the jenkinsci org: 
>  https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/656
>  - 
>  
>  What’s the current status?
>  - 
>
>Reminder of board member role in the Jenkins code of conduct 
>
>- 
>   
>   board members are:
>   “responsible for clarifying and enforcing our standards of 
>   acceptable behavior and will take appropriate and fair corrective 
> action in 
>   response to any behavior that they deem inappropriate, threatening, 
>   offensive, or harmful.”
>   - 
>   
>   Happy to have recommendations for improvements based on recent 
>   gitter chat messages
>   - 
>  
>  User expressing comments with offensive words and harsh 
>  phrasing, responded positively to code of conduct mention
>  - 
>
>Jira license changes affect the Jenkins project on or before Feb 2024
>- 
>   
>   Atlassian has approved our continued use of 
>   https://issues.jenkins.io
>   - 
>   
>   Linux Foundation will continue to host us
>   - 
>   
>   Further discussions in progress to assure all are aligned
>   - 
>
>CDF topics
>- 
>   
>   Jenkins project presentation to the CDF Technical 

Re: Allow up to 2 elected board members from a single company

[Oleg Nenashev]

Hi Mark et all,

There are rumors that the changes to the governance board were voted on 
January 9th, and I can partially see it in the meeting notes 
<https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.86ehtrl3jc4g>
.

I am a bit confused by the current state, because:

   - As far as I can tell, there was no formal voting on the mailing list. 
   Many people are likely to have missed the voting, especially since it was 
   announced only on January 8th as a part of the long agenda 
   message: 
https://groups.google.com/g/jenkinsci-dev/c/URtrswvJDH4/m/SsjfCARZAAAJ 
   . At least, I missed the voting and I would have maintained -1 given the 
   open conversation with Mark in governance board channel and the follow up 
   meeting we were about to have.
   - As far as I can tell, the decision was not announced in the developer 
   mailing list or in other venues after 1 month
   - The governance documentation was not updated, there were no steps 
   identified
  - https://www.jenkins.io/project/governance
  - https://www.jenkins.io/project/board-election-process/
  
Wearing my governance board member hat, I am not sure we can call the 
voting on this matter completed

Best regards,
Oleg Nenashev


On Saturday, December 3, 2022 at 6:49:19 PM UTC+1 Mark Waite wrote:

> On Tuesday, November 29, 2022 at 12:57:14 AM UTC-7 Ullrich Hafner wrote:
>
>> I am currently -1 for this change, but I do not yet have access to the 
>> full governance board discussion yet. 
>>
>> Basically, the reasoning for this change is not clear for me. Looking 
>> back in the history of the governance board, we are 4 active members making 
>> all the decisions. As far as I remember, Kohsuke did not participate in a 
>> decision in the last couple of years. So in practice we have 4 votes in our 
>> meetings, and if 2 of these votes are from one company this company can 
>> block any decision. They have not majority, but we have a stalemate which 
>> is a potential risk. So I would prefer to not change the current situation. 
>> It would even make sense to update the current rule so that no company can 
>> get 50% of the 4 elected seats. Then we do not need discuss if Kohsuke is 
>> affiliated with Cloudbees or not. 
>>
>>
> If the root of your concern is stalemate due to two people elected from a 
> single company, then the current rules already create the potential for 
> that situation today.  If two people from Red Hat, JFrog, AWS, Google, 
> Microsoft, or any other company (with two exceptions) were to be elected to 
> the Jenkins board, that would be allowed by the current rules.  They would 
> not have a majority on the board (2 out of 5) but would be 50% of the 
> active participating members of the board.  There are two companies 
> (CloudBees and Launchable) that are blocked from having two elected members 
> of the board because the current rule disallows a majority of board members 
> to be affiliated with a single company and the current practice has been to 
> declare that Kohsuke is affiliated with CloudBees.
>
> I agree with Basil's observation that we've seen no example of stalemate 
> in the several years that I've been involved with the board.  The most 
> controversial topic brought to the board recently was this proposal to 
> change the rules related to membership of the board.  It had 3 board 
> members in favor, one board member opposed, and Kohsuke stated his support 
> of the proposal separately.
>
> I'm far less concerned with the risk of stalemate than I am with the risk 
> of work not being completed that helps the Jenkins project succeed.
>
> Mark Waite
>

-- 
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/82699ca4-5a10-4ab6-96d6-e8b1a5d4a9d5n%40googlegroups.com.

Re: Disambiguate and document the merge/close process

[Oleg Nenashev]

Thanks for working on it, Basil! I think the pull request documents the 
current process well, and I support merging it in the current form

On Friday, February 10, 2023 at 1:55:18 AM UTC+1 m...@basilcrow.com wrote:

> Over the past few months and especially during Hacktoberfest, I have
> observed several cases where the Jenkins core contribution process did
> not go as smoothly as it could have gone. After thinking deeply about
> several examples, I concluded that the existing process contains
> several ambiguities that, once disambiguated, would make the process
> go more smoothly in the future. I distilled my thoughts into a
> concrete process improvement in
> https://github.com/jenkinsci/jenkins/pull/7516 and submitted my
> proposal for review in December.
>
> Response to this proposal has been mostly positive, with negative
> feedback isolated to specific details of the proposal rather than the
> overall concept. All feedback has been addressed at the present time.
>
> I would like to bring this proposal to a conclusion by March. If any
> active core maintainers have not yet considered the proposal, please
> do so and express (in the pull request) your view — positive,
> negative, or neutral — and the reason for that view. If anyone has
> left feedback already, please confirm that it has been addressed in
> the latest revision by approving the pull request.
>

-- 
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/e8ed0948-f353-4762-a825-b6241e46b0ebn%40googlegroups.com.

Re: Press Contacts

[Oleg Nenashev]

+1 too. We can just drop everything and offer a Jenkins Board and Security 
team contacts instead


On Friday, February 10, 2023 at 1:09:32 AM UTC+1 Alyssa wrote:

> +1 for dropping the contacts. IIRC as long as i've been with the project 
> there hasn't really been press request(s) either. 
> Alternatively there's CDF, perhaps they can be that fitler (contact) for 
> Jenkins.  Just a thought.
>
> alyssa
>
> On Thu, Feb 9, 2023 at 12:30 PM 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> Re 
>>
>> https://github.com/jenkins-infra/jenkins.io/blob/master/content/press.adoc#press-contacts
>>
>> I'm planning on a putting in a PR to remove myself from the contacts. In 
>> the almost two years of me being on the list, i've never had a legitimate 
>> email, its all spam about having sponsored posts.
>>
>> I also think most (maybe 50%) of the people listed are no longer actively 
>> engaged with the project, so probably not the best to a filter for press.
>>
>> My vote is to just drop the contacts section and use the forum or 
>> something. Private communication isn't really great for the projectanyways.
>>
>> Gavin
>>
>> -- 
>> 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/CAG%3D_DuuKa%2Boqh-O-xinqv1K2T%2BietBgtoNe%2B75Au2_mmvgZSkQ%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/3d5d0103-9345-48e2-8f9e-a7b9f226c960n%40googlegroups.com.

Renaming Custom WAR Packager to Custom Jenkins Packager

[Oleg Nenashev]

Hi all,

I would like to rename the Custom War Packager tool to "Custom Jenkins
Packager". https://github.com/jenkinsci/custom-war-packager already
supports Docker images for Jenkins and Jenkinsfile Runner, and I would like
to add a few other outputs over the time:

   1. Jenkins Helm Chart definition
   2. Nix Package definition

Would appreciate your feedback.

P.S: I plan to spend a bit more time with Jenkins while I am on
"fun"employment and looking for a new job. It might take some time because
of the situation in the industry, need to stay in Switzerland and work
80%, and my Russian passport. My focus will likely be about Jenkinsfile
Runner and cleaning up the technical debt accumulated there. If someone is
interested in doing some contract Jenkins, JCasC or jenkinsfile Runner work
in open source, do not hesitate to reach out.

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBFkz%3DJktgCBRtZ1_7VGcnZ-F%3DSYUVY3%2BGq9GGvO13zCg%40mail.gmail.com.

Re: [Event]: FOSDEM'23

[Oleg Nenashev]

Hi all,

Just a quick update, we also want to have a Jenkins dinner on February 4th, 
19:00
If you are interested in joining, please respond 
here: https://forms.gle/v1E6dF6cusWBXjJs9

Best regards,
Oleg Nenashev

On Thursday, January 5, 2023 at 8:43:48 PM UTC+1 alytong13 wrote:

> Hi All,
>
> Happy New Year!
>
> We are a few short weeks away from FOSDEM'23 <https://fosdem.org/2023/>. 
> Jenkins will have a stand at the conference and we are looking for 
> volunteers to join us.
>
> The planning gdoc is HERE 
> <https://docs.google.com/document/d/1ajANRpnhn0akwZV0L1S6qtqDMgK5TRUs5_8wUZYzcZg/edit?usp=sharing>
>  
> so if you're planning on attending FOSDEM and would like to participate in 
> Jenkins activities pls sign up in the doc.
>
> Got suggestions? Pls add to the doc as well.
>
> BR,
> alyssa
>
>
>
>

-- 
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/e805360c-2a3d-4e31-8e06-3781165e5d12n%40googlegroups.com.

Re: Next LTS baseline

[Oleg Nenashev]

Belated +1

On Wednesday, January 25, 2023 at 3:36:25 AM UTC+1 Mark Waite wrote:

> +1 from me for 2.387.
>
> On Tuesday, January 24, 2023 at 2:30:47 AM UTC-7 mc.ca...@gmail.com wrote:
>
>> That would make a viable candidate. The response on the recent weekly 
>> releases has been overall very positive.
>>
>> +1 for 2.387.
>>
>> Best,
>> Alex
>>
>> On Tuesday, 24 January 2023 at 10:03:57 UTC+1 timja...@gmail.com wrote:
>>
>>> Hi all,
>>>
>>> It's time to select the next LTS baseline.
>>> The best candidate right now appears to be 2.387
>>>
>>> See recent changelogs: https://www.jenkins.io/changelog/
>>>
>>> Thanks
>>> Tim
>>>
>>

-- 
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/e418c827-235d-4352-a501-0e6b85c7500en%40googlegroups.com.

Re: Removing inactive Core maintainers to reduce risk

[Oleg Nenashev]

I agree the cleanup is always useful, though it would be definitely nice to 
document explicit criteria in 
https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles 
. Not sure I even count as an active maintainer on my own these days, 
though my "sabbatical" was publicly announced

For transparency reasons, the following maintainers were removed according 
to the audit log:

   - Michael Neale
   - Ryan Campbell
   - Andrew Bayer
   - Stephen Connolly
   - Matt Sicker
   - Steven Christou
   - Keith Zantow
   - Sam van Oort
   - Evaristo Gutiérrez
   - Ramon Leon

All the mentioned contributors are ex CloudBees employees who have already 
moved on, company wise or project wise. Some of them are still active in 
the Jenkins community, but I do not see any activities around Jenkins core 
in the recent 2 years. I would not be too concerned about the removal, 
especially since the permissions can be easily restored upon return to 
Jenkins core contributions.

Best regards,
Oleg


On Sunday, January 29, 2023 at 2:23:21 PM UTC+1 timja...@gmail.com wrote:

> While I’m very much +1 for the change I think it should’ve been discussed 
> on the mailing list publicly
>
> On Sun, 29 Jan 2023 at 13:52, 'wfoll...@cloudbees.com' via Jenkins 
> Developers  wrote:
>
>> Thanks for the positive feedback!
>>
>> >  we decided
>> Decision was made between Damien and me.
>> It was discussed with a few other people and as we got mainly just ultra 
>> positive response, widen the discussion before the act did not seem 
>> necessary. Especially when such a change can be reversed without problems.
>>
>> Concerning the activities, the remaining people did at least a PR review 
>> during the last year. This is not strictly requiring the write permission, 
>> but I don't want to do something that could be seen as a witch hunt. 
>> This kind of risk reduction was rarely done in the past, I don't want to 
>> be too aggressive on that. Starting small and increasing the scope over 
>> time. CERT membership and VPN/infra access will follow soon.
>>
>> Wadeck
>>
>> On Saturday, January 28, 2023 at 9:59:24 AM UTC+1 mc.ca...@gmail.com 
>> wrote:
>>
>>> Thanks for your ongoing efforts to make our repositories secure!
>>>
>>> > Was this decision made in concert with other core maintainers
>>>
>>> I was not aware of such a change, but I heavily endorse the cleanup :)
>>>
>>> Alex
>>>
>>> On Friday, 27 January 2023 at 16:59:41 UTC+1 m...@basilcrow.com wrote:
>>>
 On Fri, Jan 27, 2023 at 1:06 AM 'wfoll...@cloudbees.com' via Jenkins 
 Developers  wrote: 
 > 
 > For that reason we have decided to remove inactive contributors from 
 the ‘core’ team. 

 Thanks! Strongly agree that this is a great move. 

 > we decided 

 Was this decision made in concert with other core maintainers or 
 unilaterally? 

 > one year without any activity in the affected repositories qualifies 
 as inactive 

 Is this one year without any _general_ activity (e.g., opening a PR) 
 or one year without any _maintainer_ activity (e.g., merging or 
 closing a PR)? Write permissions are needed for the latter but not the 
 former. Given the stated goal to reduce the number of people with 
 unnecessary write access, the latter definition makes more sense to 
 me. 

 Basil 

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/007096da-aac2--93ec-44466cb3527an%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/f2790b42-5cf6-4902-86d3-c8a21c9612fbn%40googlegroups.com.

Missing a few governance meetings

[Oleg Nenashev]

Hello,

My apologies, I will have to skip a few upcoming governance meetings due to
personal reasons. I remain available for asynchronous queries,but please
expect delays in my responses. I plan to participate in the governance when
my time and state allow.

As a reminder, I also remain on sabbatical for Jenkins core
maintenance, until the war in Ukraine is over or so.

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCY3JorLD3rr5m%2B4%3D3XQd_B5Dj9JhnhBYT9Z_mGRQoohA%40mail.gmail.com.

Re: Translating some tutorials?

[Oleg Nenashev]

Hi! My recommendation would be to start in a separate resource, e.g. by 
publishing tutorials on Medium or Habr.com
It would give more traffic than just publishing on jenkins.io IMHO, 
especially given the fact it would be difficult to maintain iot for new 
features.

P.S: Happy to promote through https://twitter.com/jenkins_ru and the 
Russian community's Telegram channels

On Tuesday, October 25, 2022 at 3:14:57 PM UTC+2 c_ast...@cloudbees.com 
wrote:

> Hello,
> I think it could be useful translate some tutorial documentation (I'd 
> translate into Russian). I'm looking at 
> https://www.jenkins.io/doc/developer/tutorial/ in particular, it seems 
> like useful entry-level knowledge and I feel like translated guides can 
> ease entry a little.
> I however am not sure of where to put it really? I see a dropdown to 
> switch the whole jenkins.io site to Chinese, but I highly doubt a couple 
> tutorial pages warrant an entire copy of the site. Adding some link to the 
> English tutorial with the translated version, or something like that?
>

-- 
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/c8476f9b-e135-45a6-aa85-3e3f8ed9e216n%40googlegroups.com.

Re: [JENKINS-68652] Migrate from ANTLR2 to ANTLR4

[Oleg Nenashev]

Thanks for the clarification about Strumenta's status!

Just to make sure, does the approval on Oct 31st suit your timeline? We
could theoretically have an out of order meeting on 24th (I can host it),
or make a change in the voting process to allow for async budget decision
on the mailing list. The latter would be beneficial for the community
anyway.

Best regards,
Oleg

On Tue, 18 Oct 2022, 18:41 Basil Crow,  wrote:

> Dear Oleg,
>
> I would like to take this opportunity to publicly reiterate the
> sincere appreciation I expressed to you in DM yesterday for your
> helpful (because you helped me discover a JEP that was previously
> unknown to me) and timely (because you replied to my DMs right away)
> assistance. While you may have interpreted my questions about the
> process and my resulting gesture of appreciation in a negative light,
> I would like to assure you and everyone else reading this thread that
> they were both genuine. My previous message to this list has adhered
> to the process established in JEP-15, chapter and verse, out of my
> sincere and utmost respect for the process itself and for your
> stewardship of it. I stand by what I wrote to you in DM yesterday and
> what I wrote in my previous message to this list, both of which were
> in good faith. It is important to remember that not everyone has been
> involved in the project for as long as you have been, and many
> newcomers like myself are either unaware of these older JEPs or
> unfamiliar with the context behind them. A lot of project
> documentation (e.g., the documentation for CLAs) is incomplete or
> out-of-date, so it can sometimes be difficult to determine which
> documentation is still relevant and which documentation is no longer
> relevant. As people like me learn to navigate these established
> processes, your patience is appreciated. Thanks for understanding.
>
> One additional point of clarification I would like to make is that I
> confirmed with Strumenta that the Linux Foundation meets Strumenta's
> criteria for being a registered business, so VAT does not apply.
> Regarding the price of the engagement, I think that comes with the
> territory of working with legacy technology: there are relatively few
> people with ANTLR2 knowledge/experience who are also willing to work
> on legacy ANTLR2 code, so they can command a higher market rate. (I
> suspect something similar might be the case for COBOL programmers!) I
> can also disclose that I came up with this idea on my own without any
> prompting (either explicit or implicit) from my employer. Like you, I
> think it is in the long-term interest of the project for us to move
> forward with this upgrade and eliminate the liability of one of our
> most ancient dependencies. Proceeding with this engagement will pay
> down technical debt and eliminate an impediment to future Java
> Platform improvements. If there are any additional questions or
> concerns, please let me know!
>
> Thanks,
> Basil
>
> On Tue, Oct 18, 2022 at 6:17 AM Oleg Nenashev 
> wrote:
> >
> > Hi Basil et al,
> >
> > Thanks for the follow-up. As we discussed in the DMs, with all due
> respect to you and to your valuable contributions I do not appreciate the
> passive aggressive tone you chose here or in the original DM conversation
> yesterday. Scoffing about the adopted community process for budget
> approvals does not help either. I do not such an approach helps you to get
> this particular issue resolved faster, as well as it does not help in the
> pull requests and other conversations I see here and there. Everyone in the
> community tries to achieve the best for the project, and please use it as a
> default assumption for communications. It would make the community a more
> pleasant place for everyone. Thanks for understanding.
> >
> > Back to the matter, indeed the budgeting process in JEP-15 follows the
> general Jenkins community decision making process where decisions happen in
> async channels, not during the live meetings. As for governance and
> budgeting matters, this mailing list is used. Nothing has changed in these
> regards since ages, so there is no reason to be surprised a 1,900 EUR
> budget request, which is 20% of the total Jenkins funds available on LFX
> Mentorship, would not be approved without a formal email thread in this
> mailing list. Thanks for understanding again.
> >
> > The request itself
> > Now I would like to share the request Basil, copying the meeting notes
> from the October 03 meeting. So the feedback will be needed:
> >
> > Given the lack of volunteer interest in JENKINS-68652 or alternatives
> (e.g., writing a new parser without ANTLR), Basil Crow has reached out to
> Federico Tomassetti at Strumenta, a co

Re: [JENKINS-68652] Migrate from ANTLR2 to ANTLR4

[Oleg Nenashev]

Hi Basil et al,

Thanks for the follow-up. As we discussed in the DMs, with all due respect 
to you and to your valuable contributions I do not appreciate the passive 
aggressive tone you chose here or in the original DM conversation 
yesterday. Scoffing about the adopted community process for budget 
approvals does not help either. I do not such an approach helps you to get 
this particular issue resolved faster, as well as it does not help in the 
pull requests and other conversations I see here and there. Everyone in the 
community tries to achieve the best for the project, and please use it as a 
default assumption for communications. It would make the community a more 
pleasant place for everyone. Thanks for understanding.

Back to the matter, indeed the budgeting process in JEP-15 follows the 
general Jenkins community decision making process where decisions happen in 
async channels, not during the live meetings. As for governance and 
budgeting matters, this mailing list is used. Nothing has changed in these 
regards since ages, so there is no reason to be surprised a 1,900 EUR 
budget request, which is 20% of the total Jenkins funds available on LFX 
Mentorship, would not be approved without a formal email thread in this 
mailing list. Thanks for understanding again.

*The request itself*
Now I would like to share the request Basil, copying the meeting notes from 
the October 03 meeting. So the feedback will be needed: 

   - *Given the lack of volunteer interest in JENKINS-68652 or alternatives 
   (e.g., writing a new parser without ANTLR), Basil Crow has reached out to 
   Federico Tomassetti at Strumenta, a consulting firm with experience 
   performing migrations from ANTLR2 to ANTLR4*
  - *Strumenta is interested in the project and has scoped the work 
  required to migrate from ANTLR2 to ANTLR4*
  - *Technical consensus has been reached on the developer mailing list 
  <https://groups.google.com/g/jenkinsci-dev/c/bGmc9bc0mp4/m/i1BhSIp-AAAJ> 
(in 
  this thread)*
  - *Proposal from Strumenta* 
  
<https://app.pandadoc.com/document/55d611d49988df16a2c043c5669b679a282d04dc>
   - 
*Basil is requesting funding of 1,900 Euro, possibly with additional 
   Value-Added Tax (VAT), and approval from the governance board to engage 
   Strumenta to begin the project *
  - *If approved, Basil plans to be the primary point of contact with 
  the Strumenta as they prepare the pull request to migrate from ANTLR2 to 
  ANTLR4*
  - *The code is covered by automated testing, and Basil plans to 
  complete additional manual smoke testing beyond that*
  - *Basil also plans to review and approve the pull request*
  - *As thanks for their discount, we will publish a blog post with 
  technical content describing their work and our results of their work. 
  Basil will coordinate the blog post with Strumenta*
   
Some extra context:

   - At the governing board meeting, the following contributors voted in 
   favor of the proposal: Mark Waite, Gavin, me, Basil himself, and Kevin. 
   Note that 3 of these voters are directly involved with the matter and work 
   for the same vendor that might have a commercial interest in the fix. It 
   does not make difference in the consensus building process, especially 
   since this change is definitely beneficial for the project.
   - After the meeting an anonymous contributor has already shared their 
   feedback that the requested sum is too much for the scope of work in this 
   project.

Personally I am rather in favor of the request. We have money from Jenkins 
supporters floating around, and we are not using them. Whether the use of 
the budget is super efficient or not, as Basil said we are not moving 
forward with the ticket. And it may impact vendors and end users requiring 
clear security scans to have Jenkins adopted. So I keep my +1 vote for the 
request.

Please share your feedback!

Best regards,
Oleg Nenashev





On Monday, October 17, 2022 at 8:18:18 PM UTC+2 m...@basilcrow.com wrote:

> On Thu, Sep 22, 2022 at 11:54 AM Basil Crow  wrote:
> >
> > I am starting this thread to reach consensus on the technical side of
> > this proposal; namely, migrating from ANTLR2 to ANTLR4 to decrease
> > technical debt and facilitate compilation on Java 18 or newer.
>
> To summarize our progress in this area, we have reached technical
> consensus on the developer list and budgetary consensus with the
> governance board, which voted in favor of this engagement at its
> meeting on October 3, 2022. Oleg Nenashev has informed me that he is
> unwilling to move forward until the process documented in JEP-15 is
> followed; namely:
>
> > Budget requests should be submitted to the developer mailing list and 
> discussed there[;] the Governance meeting will be doing a formal 
> approval/rejection based on the community feedback.
>
> 

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

[Oleg Nenashev]

+1, thanks for all contributions @NotMyFault!

P.S: On behalf of the exclusive weekly release trainwreck club, please make 
sure to tweet "Not my fault" the first time you break the weekly release :P 


On Saturday, October 15, 2022 at 7:58:15 PM UTC+2 adrien.lec...@gmail.com 
wrote:

> of course +1.
>
>
> Le sam. 15 oct. 2022 à 18:31, Alexander Brandes  a 
> écrit :
>
>> Thanks everyone, I'd be very happy to join the core team :)
>>
>> On Friday, 14 October 2022 at 13:48:48 UTC+2 hle...@cloudbees.com wrote:
>>
>>> +1
>>>
>>> On Fri, Oct 14, 2022 at 1:18 PM James Nord  wrote:
>>>
 +1

 On Thu, 13 Oct 2022 at 20:16, Pedro Amaral  wrote:

> +1
>
> On Thu, Oct 13, 2022 at 10:12 AM 'Kevin Martens' via Jenkins 
> Developers  wrote:
>
>> +1 from me too!
>>
>> On Thu, Oct 13, 2022 at 5:52 AM 'Olblak' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> +1  :) 
>>>
>>> On Thu, Oct 13, 2022, at 11:39 AM, 'Stephane Merle' via Jenkins 
>>> Developers wrote:
>>>
>>> +1 for me too
>>> good luck Alexander
>>>
>>> On Thu, Oct 13, 2022 at 9:44 AM 'Daniel Beck' via Jenkins Developers 
>>>  wrote:
>>>
>>>
>>>
>>> On Thu, Oct 13, 2022 at 9:11 AM Tim Jacomb  
>>> wrote:
>>>
>>> I would like to propose Alexander Brandes (@NotMyFault 
>>> ) to join the Jenkins Core team.
>>>
>>>
>>> +1 
>>>
>>>
>>> -- 
>>> 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/CAMo7PtJFQvvfqtNixCGOk34quz7Fm_bu0as_QNOVxX%2BXY5jvwA%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/CAO%2B-N1qxoBRFwKk4%3DJdVY%2B_gns%2BCaMd8J_DC9xuWnRqzEfYDZA%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/b67d978b-bc39-4cb4-a2a3-3ad69cdf621c%40app.fastmail.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Kevin Martens
>> Technical Content Developer
>> CloudBees, Inc.
>>
>>
>> E: kmar...@cloudbees.com
>>
>> Pronouns: He/Him/His
>>
>> -- 
>> 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/CAP92yNdJ5WrfjJith1bzawZiEsEJw%2BhG4SDv6GxLhVHT6fmjGA%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/CAHnkEpkxT9pBagcAJszwL5Pw5RoSp26myuBC4sntO-GAq5J2sg%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 
 

Re: [Adoption] thin-backup-plugin

[Oleg Nenashev]

+1. Note that there were recent updates by  Thomas Fuerer 16 days 
ago: https://github.com/jenkinsci/thin-backup-plugin/pull/30
It would be nice to have explicit confirmation from him just in case

On Sunday, September 25, 2022 at 1:40:17 PM UTC+2 Mark Waite wrote:

> I see the "Up for adoption" message in the README at 
> https://github.com/jenkinsci/thin-backup-plugin/blob/master/README.md 
>
> +1 from me to have Stefan adopt the plugin.  His contributions to Jenkins 
> core have been consistent and have regularly improved Jenkins core.
>
> Mark Waite
>
> On Sunday, September 25, 2022 at 5:28:23 AM UTC-6 stefan@gmail.com 
> wrote:
>
>> Hi,
>> I would like to adopt a plugin:
>>
>>- *Link*: https://github.com/jenkinsci/thin-backup-plugin
>>- *Pull requests*: 
>>   - https://github.com/jenkinsci/thin-backup-plugin/pull/34 
>>   - https://github.com/jenkinsci/thin-backup-plugin/pull/35 
>>   - https://github.com/jenkinsci/thin-backup-plugin/pull/36
>>- *Status*: for adoption
>>- *GitHub Username*: StefanSpieker 
>>- *Jenkins Infrastructure ID*: stefan_spieker
>>- *Repository Permission Updater PR*: 
>>https://github.com/jenkins-infra/repository-permissions-updater/pull/2818
>>
>> I plan to update and modernize the plugin.
>>
>> Best regards,
>> Stefan Spieker
>>
>

-- 
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/8cb58764-70e3-46f4-89d2-5fea0164289an%40googlegroups.com.

Re: Jenkinsci Cloudevents plugin

[Oleg Nenashev]

Hi, thanks for the interest! AFAICT I am listed as one of co-maintainers 
for this plugin, and I am happy to help with permissions& co.
And maybe Tim is right about forking and renaming the plugin. We have no 
way to safely change artifactIDs after the initial release, so maybe a fork 
is a best approach.





On Tuesday, June 14, 2022 at 5:52:14 PM UTC+2 timja...@gmail.com wrote:

> Or alternatively create a new plugin for CDEvents if the cloud events 
> heritage doesn't make sense any more.
>
> Once you've got it working you could then go through the hosting process 
> <https://www.jenkins.io/doc/developer/publishing/requesting-hosting/>.
>
> Thanks
> Tim 
>
>
>
> On Tue, 14 Jun 2022 at 13:18, Mark Waite  wrote:
>
>>
>>
>> On Tuesday, June 14, 2022 at 6:08:41 AM UTC-6 Ger McMahon wrote:
>>
>>> My name is Ger McMahon and work for Fidelity Investments. As part of 
>>> being an end user member of Continuous Delivery Foundation (CDF), we want 
>>> to get more involved in open source projects and especially ones related to 
>>> the CDF. We have a particular interest in the Jenkinsci Cloudevents 
>>> plugin <https://github.com/jenkinsci/cloudevents-plugin> and understand 
>>> the project has been dormant since it was created as part of the Google 
>>> Summer of Code. Fidelity would have an interest on taking on this project, 
>>> either through mutating the current implementation or forking to align with 
>>> the new CDEvents project <https://cdevents.dev/> from CDF.
>>>
>>>  
>>>
>>> I wanted to connect with the jenkinsci-dev group to determine the next 
>>> steps and appreciate any information or feedback.
>>>
>>>  
>>>
>> Welcome to the developer community!  Great to have your interest in 
>> CloudEvents and happy to have your help.  The "Adopt a plugin" 
>> <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/> 
>> process says:
>>
>> Be sure to provide the following information:
>>
>>- 
>>
>>Link to a plugin you want to adopt - 
>>https://github.com/jenkinsci/cloudevents-plugin
>>- 
>>
>>The status of the plugin ("for adoption" or "abandoned") - abandoned
>>- 
>>
>>Link(s) to pull requests you want to deliver, if applicable - I don't 
>>see any yet, though refer to the "Contributing to Open Source" 
>>
>> <https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.hvd0nm6pz5o4>
>>  
>>document and the "Modernizing a plugin" video series 
>><https://www.youtube.com/watch?v=Fev8KfFsPZE> for suggested starter 
>>pull requests
>>- 
>>
>>Your GitHub username/id (e.g. oleg-nenashev for 
>>https://github.com/oleg-nenashev/) - You'll need to provide this one
>>- 
>>
>>Your Jenkins infrastructure account id. Create your account 
>><https://accounts.jenkins.io/> if you don’t have one. - You'll need 
>>to provide this one
>>- 
>>
>>The link to the "Repository Permission Updater" PR described below - 
>>You'll need to provide this one based on the instructions
>>
>> Be sure that you follow the instructions for the contents of the pull 
>> request and its comments.
>>
>> Thanks again,
>> Mark Waite
>>
>> -- 
>> 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/93cc484d-de7e-497e-9396-3b84d7761a56n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/93cc484d-de7e-497e-9396-3b84d7761a56n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/2fe8bf32-997c-493d-b15e-c239be74ab88n%40googlegroups.com.

Re: [GSoC] Adding a Maintainer to the Jenkins File Runner Github repositories

[Oleg Nenashev]

We still need to understand what the objectives are and what is the actual
scope of the project. What I see in the current design, it likely doesn't
require changes in Jenkinsfile Runner itself, and there is no plan to
modify the existing GitHub actions.

I encourage all interested parties to make the design document public and
to initiate the discussion in the community like it should have happened
during the community bonding phase. I've been around in the project since
the community bonding started, and the meeting on Monday was the first time
when I saw the design document. And the it's not complete according to the
mentee, despite the coding phase beginning on that day.

>From the community standpoint, we must ensure that the design gets
discussed as soon as possible, for example through the cloud native SIG or
another group. Otherwise it may put the whole project at risk. Community
bonding was supposed to get all parties on the same page and to ensure that
the mentee is ready to start coding on day first. Clearly didn't happen and
we have to make up for it during the first coding phase.

Sorry if my feedback is harsh, but I want to help the project to succeed.



On Wed, 15 Jun 2022, 17:06 Jean-Marc Meessen, 
wrote:

> Oleg, please allow me to disagree on your point of view:
>
>- It is a pity and a missed opportunity that you didn't contribute
>when reviewing the proposal earlier in the process.
>- I don't have the same interpretation as you on mentoring (formal and
>informal).
>
> I will closely follow how this unfolds and pull the alarm signal/emergency
> brake should the GSoC project derail and miss its objectives.
>
> /- Jmm
>
> Le mer. 15 juin 2022 à 15:27, Oleg Nenashev  a
> écrit :
>
>> Hello Jean-Marc,
>>
>> Yes, I am not very active in the project at the moment. You and many
>> other community members know the reasons. Also, there have not been any
>> serious contributions that I would be ready to merge as a maintainer.
>> Sadly, I cannot do much more about my capacity at the moment, be sure I
>> would like to return to Jenkins development too.
>>
>> Back to the request. While I understand the desire, at the moment I am
>> against this request. Google Summer of Code is important, but right now
>> there are serious concerns about the project scope and implementation. We
>> discussed it on Slack and during the recent project meeting. The currently
>> planned implementation of the project goes against the common Jenkins
>> extensible architecture and the vision for Jenkinsfile Runner as a
>> manageable tool. As a maintainer of Jenkinsfile Runner I am not ready to
>> accept the hardcoded support for GitHub actions into the core Jenkinsfile
>> Runner components, as the current design intends.
>>
>> And be sure I do not want to be a bottleneck. Quite opposite, I want to
>> have more maintainers in the project. Same time neither Kris nor Yiming
>> have enough experience with Jenkinsfile Runner at the moment, and they do
>> not have enough maintainer experience in Jenkins yet. IMO they are not
>> ready to skip the common maintainer onboarding stages and to become
>> maintainers right away. I am also ready to provide mentorship for them as
>> aspiring maintainers, but it will take a few months before they are ready
>> to become maintainers.
>>
>> During the discussions I committed to provide reviews to all Jenkinsfile
>> Runner contributors, including Kris and Yiming. I am ready to provide
>> technical feedback as an advisor. This is all I can commit to at the
>> moment, and the GSoC org admin team was well aware about it during the
>> project selection. Happy to discuss more at the next GSoC project meetings
>> or in this mailing list.
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
>> On Wednesday, June 15, 2022 at 12:07:13 PM UTC+2 Jean-Marc Meessen wrote:
>>
>>> Hello,
>>>
>>> In my position as Jenkins GSoC Org Admin, I am requesting to add Kris
>>> Stern as maintainer of the Jenkins File Runner Github repositories. Kris is
>>> the lead mentor for the Jenkinsfile Runner Action for GitHub Actions
>>> <https://www.jenkins.io/projects/gsoc/2022/projects/jenkinsfile-runner-action-for-github-actions/>
>>>  2022
>>> GSoC project.
>>> The two Github repositories are
>>> https://github.com/jenkinsci/jenkinsfile-runner and
>>> https://github.com/jenkinsci/jenkinsfile-runner-github-actions
>>>
>>> It is critical for the success of the GSoC projects that at least one
>>> mentor has maintainer rights on the related Github project. A fluid PR flow
>>> is key to achieve the 

Re: [GSoC] Adding a Maintainer to the Jenkins File Runner Github repositories

[Oleg Nenashev]

Hello Jean-Marc,

Yes, I am not very active in the project at the moment. You and many other 
community members know the reasons. Also, there have not been any serious 
contributions that I would be ready to merge as a maintainer. Sadly, I 
cannot do much more about my capacity at the moment, be sure I would like 
to return to Jenkins development too.

Back to the request. While I understand the desire, at the moment I am 
against this request. Google Summer of Code is important, but right now 
there are serious concerns about the project scope and implementation. We 
discussed it on Slack and during the recent project meeting. The currently 
planned implementation of the project goes against the common Jenkins 
extensible architecture and the vision for Jenkinsfile Runner as a 
manageable tool. As a maintainer of Jenkinsfile Runner I am not ready to 
accept the hardcoded support for GitHub actions into the core Jenkinsfile 
Runner components, as the current design intends. 

And be sure I do not want to be a bottleneck. Quite opposite, I want to 
have more maintainers in the project. Same time neither Kris nor Yiming 
have enough experience with Jenkinsfile Runner at the moment, and they do 
not have enough maintainer experience in Jenkins yet. IMO they are not 
ready to skip the common maintainer onboarding stages and to become 
maintainers right away. I am also ready to provide mentorship for them as 
aspiring maintainers, but it will take a few months before they are ready 
to become maintainers.

During the discussions I committed to provide reviews to all Jenkinsfile 
Runner contributors, including Kris and Yiming. I am ready to provide 
technical feedback as an advisor. This is all I can commit to at the 
moment, and the GSoC org admin team was well aware about it during the 
project selection. Happy to discuss more at the next GSoC project meetings 
or in this mailing list.

Best regards,
Oleg Nenashev


On Wednesday, June 15, 2022 at 12:07:13 PM UTC+2 Jean-Marc Meessen wrote:

> Hello,
>
> In my position as Jenkins GSoC Org Admin, I am requesting to add Kris 
> Stern as maintainer of the Jenkins File Runner Github repositories. Kris is 
> the lead mentor for the Jenkinsfile Runner Action for GitHub Actions 
> <https://www.jenkins.io/projects/gsoc/2022/projects/jenkinsfile-runner-action-for-github-actions/>
>  2022 
> GSoC project.
> The two Github repositories are 
> https://github.com/jenkinsci/jenkinsfile-runner and 
> https://github.com/jenkinsci/jenkinsfile-runner-github-actions
>
> It is critical for the success of the GSoC projects that at least one 
> mentor has maintainer rights on the related Github project. A fluid PR flow 
> is key to achieve the objectives within the allocated summer months. This 
> is not the case for the above mentioned project. Oleg Nenashev, who is 
> maintainer, initially volunteered as mentor for that project. But he had to 
> withdraw because of workload and personal issues. Although he still tries 
> to free time to advise the GSoC project team, measures need to be taken to 
> avoid bottlenecks.
> Note that maintainer activity, by Oleg and the two other maintainers (E. 
> Gutierrez and F. Fernandez), has been very low since autumn 2021.
>
> /- Jmm
>
> Jean-Marc Meessen
> Jenkins GSoC Org Admin
>

-- 
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/aa371b59-1c16-4ddb-b493-1e56c847d9efn%40googlegroups.com.

Re: DevOps World 2022: Looking for Jenkins proposals

[Oleg Nenashev]

Hi,

Sorry for not applying. Sadly it is not possible for me to get a visa on 
time, and I decided to not do any online/prerecorded conferences.

Best regards,
Oleg Nenashev

On Monday, May 23, 2022 at 10:16:57 PM UTC+2 alytong13 wrote:

> Friendly reminder the CFP is closing in 2 days, May 25 - We would love to 
> receive more Jenkins proposals.
>
> BR,
> alyssa
>
> On Mon, Apr 25, 2022 at 1:03 PM Alyssa Tong  wrote:
>
>> I sent this out via community Discourse and thought I'd include it here 
>> as well. 
>>
>> Hello,
>>
>> The Jenkins project will be attending DevOps World 
>> <https://devopsworld.submittable.com/submit?mkt_tok=MzMzLVFQVi03MjUAAAGDx8lX77BtSSAI_To8n6ZsJnrOM_cAS9_bNVFwGo7EmLBHZ3-Dfi_mbzcIxSDEM7Dvr78_YcaOH15kxbWRwwNOhGlrTBzOK5wIwShoRqiN6g>,
>>  
>> live and in person in Orlando, Florida, September 28-29, 2022. We will host 
>> a Jenkins contributor summit. The program will have a track dedicated to 
>> community topics, with many Jenkins sessions.  If you have a Jenkins story 
>> that will inspire others pls submit your talk for consideration, the CFP 
>> is open until May 12 
>> <https://devopsworld.submittable.com/submit?mkt_tok=MzMzLVFQVi03MjUAAAGDx8lX782vHuYoJ5FNSbgRFKX4amLIXQEPDz5GKeEod5iZTIkzA7hd-NSgRRoNNx4qlUWq9g7jvEtwXxNe-D3CPs700Ir6THO4X29UPuAi1w>
>> .
>>
>> If you would like to be on the community review committee pls let me know.
>>
>> Thanks,
>> alyssa
>>
>

-- 
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/5f889a13-82b6-4e6f-b8a2-aa8687f0fc8cn%40googlegroups.com.

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

[Oleg Nenashev]

Jenkins Test Harness is not a core component, it is a separate deliverable
with its own release lifecycle
Same for other developer tools AFAICT


On Wed, Apr 27, 2022 at 11:43 PM Basil Crow  wrote:

> Strong -1 from me. Using GitHub issues for core components but not
> core itself makes it impossible to do project management in a single
> view (Jira epic or GitHub project) that covers both core and core
> components. Additionally, there is no way to define causal
> relationships or dependencies between GitHub issues, which is also
> essential for project management. Please roll back whatever change now
> prevents me from creating new Jira issues for core components.
>
> --
> 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/9sZipk1PHns/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/CAFwNDjpy_QzJ0v4RqUJkDw2migG_RoaX856rJienKLgD%2BxVs%3DQ%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/CAPfivLBm%3DkiYaz%2Bo%3DcHedERt1OGR9fLq14iaBNmzDNaC4LwX-g%40mail.gmail.com.

Jenkins chapter on Bevy instead of Zoom/Meetup.com

[Oleg Nenashev]

Hi all,

Just a heads up, the CDF is gradually deprecating Zoom and meetup.com.
There is no confirmed ETA for full shutdown, but it is expected to happen
by the end of the year. The new Bevy-based community portal has been
deployed on  https://community.cd.foundation. Basically it includes both
Meetup.com replacement and a webinar platform that replaces Zoom and can
also integrate with YouTube live streaming.

Currently we can create new chapters on the CDF Community portal, and I
asked the CDF team to create a test Jenkins chapter. Now we have it on
https://community.cd.foundation/jenkins/ . If you join the platform, I can
make you event organizers upon request.

This year we will need to move all active Jenkins meetups, Governance
Meeting and SIGs to the Bevy platform. It will likely require creation of
multiple chapters there, and also outreach to meetup.com users in order to
ensure they join the new platform. I kindly ask Alyssa to coordinate this
effort as a Jenkins Events Officer. There is a #communitygroups channel on
the CDF Slack where all the conversation happens

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDcMAg8RcneW1dCqcPjOTYSv13g0xz47Xrs4Y%2B_Yw7QiQ%40mail.gmail.com.

Re: File Leak Detector

[Oleg Nenashev]

+1


On Tuesday, March 1, 2022 at 8:36:47 AM UTC+1 timja...@gmail.com wrote:

> +1
>
> On Tue, 1 Mar 2022 at 01:26, Mark Waite  wrote:
>
>>
>>
>> On Monday, February 28, 2022 at 6:13:52 PM UTC-7 Basil Crow wrote:
>>
>>> kohsuke/file-leak-detector has not seen commits since 2018. There are 
>>> a number of open PRs that need to be processed and released, including 
>>> important PRs to add Java 11 support (see JENKINS-52308). 
>>>
>>> We recently moved mock-javamail from Kohsuke's GitHub organization to 
>>> the Jenkins GitHub organization. In the process, I also modernized the 
>>> library and transferred release permissions to the core team. 
>>>
>>> I would like to propose we do the same for kohsuke/file-leak-detector. 
>>> I am willing to do the modernization work, just as I did for 
>>> mock-javamail. 
>>>
>>> Please let me know what you think. If there is consensus in favor of 
>>> this plan, I will open a GitHub issue and ping Kohsuke.
>>
>>
>> +1 from me. 
>>
>> -- 
>> 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/72ca6c90-018e-414c-9f3e-c84eddbdd466n%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/2bc3ddce-97bc-4e56-a958-575530dba938n%40googlegroups.com.

Re: Adopting locale-plugin

[Oleg Nenashev]

+1 from me as former co-maintainer.
Sadly I have no bandwidth for anything Jenkins right now

On Monday, February 28, 2022 at 8:09:59 AM UTC+1 jone...@gmail.com wrote:

> Hi,
>
> I would like to adopt the locale-plugin : 
> https://github.com/jenkinsci/locale-plugin/pull/12
>
> It's currently marked for adoption.
>
> My first goal is to finalize the JCasC support (
> https://github.com/jenkinsci/locale-plugin/pull/12)
>
> My username is 'jonesbusy' (github + jenkins account)
>
> PR for permission is : 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/2413
>
> Thanks!
>

-- 
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/cb61b588-1fe0-4f01-966c-804186ca6cc9n%40googlegroups.com.

Re: winp maintainer

[Oleg Nenashev]

Hi all,

I am [barely] active in the project, but I cannot release it.

Just to share background for the team, Winp is outside Jenkins as it was 
discussed with Kohsuke at some point. Same for the Windows Service Wrapper. 
FTR I brought up the question of WinP and WinSW co-ownership with CloudBees 
engineering teams a few times after I moved outside of the product 
organization in 2019. It was not a priority at that point. I used to 
maintain it when my time allowed (e.g. security fixes or releases requested 
by Jenkins and CloudBees users), but WinP has never been on the top of my 
interest list. It is not trivial to maintain the release environment due to 
specific Windows requirements and Maven Central access. My release 
environment was wiped out when I left CloudBees as I notified the 
engineering teams and my managers,  right now I do not have time to set it 
up.

Regarding moving the components:

   - I do not mind moving WinP, because it is not widely used outside 
   Jenkins. Same for removing the Maven Central dependency, the repository can 
   be easily moved to Jenkins repo or GitHub releases. Theownership can be 
   formally transferred to the Jenkins core team. FTR Ideally we should be 
   looking for deprecating the library and using something popular for Process 
   and Environment management
   - For Windows service Wrapper the situation is different, it will stay 
   in a separate organization. Contributions are 
   welcome: https://github.com/winsw


Best regards,
Oleg Nenashev

On Sunday, February 13, 2022 at 11:40:37 AM UTC+1 Baptiste Mathus wrote:

> Is winp used outside of Jenkins?
>
> Afaik we did move already a few components core to Jenkins to the 
> Jenkinsci GitHub org. Would it make sense to consider moving this one too? 
> Then I assume we'd give permissions to the core team to it?
>
> -- Baptiste
>
> Le ven. 11 févr. 2022 à 22:41, 'James Nord' via Jenkins Developers <
> jenkin...@googlegroups.com> a écrit :
>
>> Hi all,
>>
>> Jenkins has a dependency on https://github.com/kohsuke/winp but it now 
>> seems like there is no one active in the project that can release it.  (
>> https://github.com/kohsuke/winp/pull/69#pullrequestreview-867992611). 
>>
>> Has anyone got the inclination and time and environment to want to step 
>> up as a maintainer for it?
>>
>> Additionally I looked at the new Java9 process API and it allows cross 
>> platform process enumeration but not retrieving environment variables, and 
>> changing to jna appears non trivial as there is no single windows API call. 
>>
>> /James
>>
>>
>> --
>> Sent from my phone, please excuse the brevity, typos and auto-correct 
>> issues.
>>
>> -- 
>> 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/CAPcEHyeDNWeo0dK%2BwYmo%3Diih1EcRUVfs8-PaydspXxGRcP8izg%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPcEHyeDNWeo0dK%2BwYmo%3Diih1EcRUVfs8-PaydspXxGRcP8izg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/b634a9a7-f248-45b0-bf91-c286433748edn%40googlegroups.com.

Re: [GSoC_2022]: Mentors and project ideas are still needed

[Oleg Nenashev]

It is still on my list.
Sorry for being late, personal stuff and now FOSDEM deadlines that I 
already had to stretch (sorry Olivier =) )


On Thursday, January 20, 2022 at 7:31:25 PM UTC+1 alytong13 wrote:

> Hi All,
>
> We are still in need of more mentors and project ideas,
> this page  shows 
> the current list. The goal is to have 2-3 mentors dedicated to a project 
> idea, that said additional mentors are needed for:
>
>- Plugin Installation Manager Tool Improvements  
>
> 
>- Automatic git cache maintenance on the controller  
>
> 
>- and the Ongoing Discussion project proposals
>
> To submit project idea proposal, pls go here 
> 
>
> Thank you,
> alyssa (on behalf of GSoC org admin team)
>

-- 
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/476f5041-5331-48f1-97e1-7f041ac92008n%40googlegroups.com.

Re: Dropping support for IE 11

[Oleg Nenashev]

I would suggest explicitly moving IE 11 to "Tier 3" for now until the 
official end of life, with explicit statement it is deprecated. It would 
have the same effect as removing it, because Tier 3 states that there're 
" No guarantees. We will accept patches, but only if they are low risk. *This 
is the default unless a browser/version is listed below*". Having explicit 
support tier would be useful for those users who look into migration.

I also suggest promoting Microsoft Edge to Tier 1 in the same patch 

IIUC with removal of IE 11 support we will be also able to cleanup all CSS 
style default hacks, right? If so, maybe dropping IE11 right away is 
justified
 

On Sunday, January 16, 2022 at 10:39:27 PM UTC+1 ga...@gavinmogan.com wrote:

> Absolutely on board with this. The fact that some companies decide to
> keep this old legacy broken browser around shouldn't hold anyone else
> back.
>
> > Bootstrap 5 doesn't support it (I assume warnings-ng is already 
> incompatible with IE 11)
>
> Css not working is very different than javascript not working
>
> > Drop IE support completely from the support table on 
> https://www.jenkins.io/doc/administration/requirements/web-browsers/
>
> I know I had to use my open source saucelabs account when I was
> helping out with blueocean, its so hard to test these days.
>
> Gavin
>
> On Sun, Jan 16, 2022 at 12:13 PM Tim Jacomb  wrote:
> >
> > Hello
> >
> > I think it's time that we drop support for IE 11.
> >
> > There's some really good background information for the why's and what's 
> in the angular RFC:
> > https://github.com/angular/angular/issues/41840
> >
> > Some useful reasons why:
> > - IE 11 was released in 2013 and has only received bug and security 
> fixes since
> > - Office365 dropped support in August 2021
> > - Bootstrap 5 doesn't support it (I assume warnings-ng is already 
> incompatible with IE 11)
> > - Official end of life is June 2022
> > - Difficulty of testing changes on it and we have no automated test 
> coverage of it
> >
> > This was last discussed in Nov 2019 (
> https://groups.google.com/g/jenkinsci-dev/c/TV_pLEah9B4)
> >
> > I propose:
> > Drop IE support completely from the support table on 
> https://www.jenkins.io/doc/administration/requirements/web-browsers/
> >
> > When:
> > After the next LTS baseline cutoff, approx 1st February
> >
> > Thoughts?
> >
> > Thanks
> > Tim
> >
> > --
> > 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-3BidYfEY0gTeEH7dRtZ%3DNy%3D%3DC9Tk1KgCSsuqszMi4Jonvvg%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/2c7c3b00-e424-48ac-926a-cbece8dcfbc1n%40googlegroups.com.

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

Dear all,

After some consideration I decided to *NOT* participate as org admin this 
year. I cordially believe Google Summer of Code is super important for the 
community, and I am ready to contribute with advice to the new org admins. 
At the same time, open communication, transparency and follow-ups are 
essential to the success of the GSoC project on the organization level. 
Currently I do not see a level of communication and transparency that would 
make participation comfortable for a non-CloudBees org admin. Hence there 
is no point to participate for me at the moment. Also, my timezone and 
parenting schedule aren't compatible with Alyssa, and it is going to add 
extra complications and make it less enjoyable. 

P.S: I basically stepped down from Advocacy SIG starting from 
September, because they are also not compatible with my schedule. My 
messages about changing the meeting times do not get enough feedback from 
the team. I will keep contributing to other less synchronous activities 
though 

Best regards,
Oleg Neanshev




On Thursday, January 13, 2022 at 8:46:10 PM UTC+1 Oleg Nenashev wrote:

> Hi Alyssa,
>
> Just saw this message. Looks like the timezone was not converted properly 
> by you. I was not available at 4PM UTC, only at 3PM UTC. See my vote in 
> UTC+1 below.
>
> As I communicated to the Advocacy & Outreach SIG numerous times, I cannot 
> join the meetings as scheduled now. It conflicts with my creche run, Keptn 
> community meeting, and the CDF End User Panel. Usually it is creche run for 
> me. I am happy to join on Thursdays if the meetings happen before 4pm UTC 
> or after 9PM UTC
>
> Best regards,
> Oleg
>
>
>
> On Thu, 13 Jan 2022, 01:15 Alyssa Tong,  wrote:
>
>> Hi All,
>>
>> Given Oleg's (limited) availability,  we'll schedule the GSoC Knowledge 
>> Transfer for* tomorrow, Thursday 13 January, 2022 at  4pm UTC | 8am PT* 
>> - and since this time aligns with the Advocacy Outreach Sig meeting we will 
>> use tomorrow's Adv Outreach Sig meeting for this knowledge transfer. We 
>> will record the session for those you can't make it.
>>
>> https://docs.google.com/document/d/1K5dTSqe56chFhDSGNfg_MCy-LmseUs_S3ys_tg60sTs/edit?usp=sharing
>>
>>
>> <https://docs.google.com/document/d/1K5dTSqe56chFhDSGNfg_MCy-LmseUs_S3ys_tg60sTs/edit?usp=sharing>
>> Call in info:  
>> https://zoom.us/j/94535341255?pwd=VHhUNjJVZVNuUk8xRi91SDFub2xhQT09 
>>
>> <https://docs.google.com/document/d/1K5dTSqe56chFhDSGNfg_MCy-LmseUs_S3ys_tg60sTs/edit?usp=sharing>
>>
>> Thank you all!
>>
>> alyssa
>>
>> On Wed, Jan 12, 2022 at 10:09 AM Alyssa Tong  wrote:
>>
>>> thank you Oleg
>>>
>>> On Wed, Jan 12, 2022 at 10:00 AM Oleg Nenashev  
>>> wrote:
>>>
>>>> Sorry, just did it
>>>>
>>>> On Wed, 12 Jan 2022, 18:59 Alyssa Tong,  wrote:
>>>>
>>>>> Hi Oleg,
>>>>>
>>>>> Hope all is well and 2022 is treating you well.
>>>>>
>>>>> Would you mind selecting your time preferences in the doodle 
>>>>> <https://doodle.com/poll/vqrmawt6enkmbs3u?utm_source=poll_medium=link>,
>>>>>  
>>>>> pretty please? I don't want to guess only to get it wrong, which is 
>>>>> mostly 
>>>>> the case :P
>>>>>
>>>>> -- Forwarded message -
>>>>> From: Alyssa Tong 
>>>>> Date: Thu, Jan 6, 2022 at 9:29 PM
>>>>> Subject: Re: Google Summer of Code (GSoC) 2022: Call for organizers, 
>>>>> mentors, and project ideas
>>>>> To: Oleg Nenashev 
>>>>> Cc: Jenkins Dev 
>>>>>
>>>>>
>>>>> Thank you Oleg. Pls select those times in the doodle 
>>>>> <https://doodle.com/poll/vqrmawt6enkmbs3u?utm_source=poll_medium=link>
>>>>> .
>>>>> And i'll look forward to your write up for other project ideas :)
>>>>>
>>>>> On Thu, Jan 6, 2022 at 2:56 PM Oleg Nenashev  
>>>>> wrote:
>>>>>
>>>>>> Hi Alyssa,
>>>>>>
>>>>>> 3 timeslots next week are OK for me. I might also be available 
>>>>>> tomorrow at 4:30PM UTC but not at 4:00PM UTC
>>>>>>
>>>>>> Best regards,
>>>>>> Oleg
>>>>>>
>>>>>> On Thu, Jan 6, 2022 at 6:51 PM Alyssa Tong  wrote:
>>>>>>
>>>>>>> Pls use the below doodle instead. I have updated the poll to include 
>>>>

Re: New Year blogpost for Jenkins

[Oleg Nenashev]

Thanks to everyone who contributed! And sorry that I disappeared 
completely, the court hearing took much more energy than I expected




On Friday, January 14, 2022 at 7:04:27 AM UTC+1 Mark Waite wrote:

> Thanks to all for the suggestions.
>
> Please review the proposed blog post at 
> https://github.com/jenkins-infra/jenkins.io/pull/4821 
>
> I would like to publish before the end of the day in Europe on Friday, 
> January 14, 2022.
>
> Mark Waite
>

-- 
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/305daf8d-b568-4ff2-a73b-f9cbfd21aea7n%40googlegroups.com.

Re: Linux Support Policy

[Oleg Nenashev]

I am in favor of having a support policy in general, as long as it is 
explicit there is no SLA. The original Windows support page and the new 
Linux one says "we intend to fix the reported issues timely." even for Tier 
1. IMHO it is okay.
We could make an explicit disclaimer if not enough @Gavin

Also, should it actually be Unix or Linux?

On Friday, January 14, 2022 at 8:09:54 PM UTC+1 Mark Waite wrote:

> On Friday, January 14, 2022 at 11:58:24 AM UTC-7 Gavin wrote:
>
>> I'm not super comfortable with the word support, as it sets a level of 
>> expectations with users and corporations about what we provide as to 
>> help. We make no guarantees anyone will help you with a linux or linux 
>> + jenkins issue, but we will say we've fully run our automated test 
>> suite on those environments? 
>>
>> I'm just not entirely sure what the point of this policy is, what 
>> problem is it solving? 
>>
>>
> I'm trying to describe current practices in a way that readers can 
> understand current levels of involvement from the contributors to the 
> project.  We build and test on Ubuntu machines and have built and tested on 
> Debian machines previously.  We deliver Linux installers for deb, Red Hat 
> rpm, and SUSE rpm.  We run automated tests of the deb and Red Hat rpm 
> installers.
>
> We do not actively test Jenkins with other Linux distributions like Amazon 
> Linux 2 (uses the Red Hat rpm), Devuan (uses Debian but with System V init 
> rather than systemd), Oracle Linux (uses the Red Hat rpm), and many 
> others.  If issues are detected with a distribution that is not in the 
> "fully supported" list, I want the reader to understand that it will 
> probably receive less attention than an operating system on the "fully 
> supported" list.
>
> I've not seen issues from the Windows support policy page that has used 
> similar phrasing for 18+ months.  I'm open to other phrasing, but I'm not 
> clear what that alternate phrasing might be.
>
> Mark Waite
>

-- 
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/52da2930-e9cd-48e5-b132-934ffb5516bbn%40googlegroups.com.

Re: Governance meeting Jan 12, 2022

[Oleg Nenashev]

Hi all,

I will have to skip today's meeting. I barely slept last night, and I am 
not very productive. 
I do not have major updates from my side.

   -  Still waiting for green light from the Linux Foundation to enable 
   EasyCLA for Jenkins
   - CDF has not yet been accepted to the Inclusive Naming Initiative. Had 
   a chat with two INI directors on Monday w.r.t this topic
   - I will be doing a talk about my vision for Jenkins at FOSDEM. My plan 
   to share it with the community by Friday so that everyone will be able to 
   review/comment. The talk will be still delivered with disclaimer that it is 
   my personal opinion, because it goes against the Jenkins vision of some 
   company members. I do not want to build consensus for my individual talk, 
   and hence the disclaimers. For any roadmap updates and actual changes in 
   Jenkins, of course we will need to build consensus


Best regards,
Oleg Nenashev

On Wednesday, January 12, 2022 at 8:45:57 PM UTC+1 Mark Waite wrote:

> Today's governance meeting will start at 9:00 PM UTC.  Agenda items 
> include:
>
>
>- 
>
>News
>- 
>   
>   Jenkins 2.319.1 LTS 
>   <https://www.jenkins.io/changelog-stable/#v2.319.2> security 
>   released today
>   - 
>   
>   Jenkins 2.330 weekly <https://www.jenkins.io/changelog/#v2.330> 
>   security released today
>   - 
>
>End of year blog post draft
>- 
>   
>   Working copy 
>   <https://github.com/MarkEWaite/jenkins.io/commits/2022-happy-new-year> 
>   under development by Mark Waite
>   - 
>
>Administrative access - Oleg Nenashev
>- 
>   
>   Oleg is still listed as a manager for the CloudBees CLA at Linux 
>   Foundation
>   - 
>  
>  Mark check with Linux Foundation on how to update CLA manager 
>  (not done yet)
>  - 
>
>Google Summer of Code
>- 
>   
>   Alyssa Tong and Jean-Marc Meessen leading the effort
>   - 
>
>She Code Africa Contributhon
>- 
>   
>   Planning has started
>   - 
>  
>  Discussions in Docs Office Hours
>  - 
>  
>  Future discussions on community.jenkins.io 
>  - 
>   
>   Planned for April / May this year rather than March/April
>   - 
>
>Highlights from the mailing lists and community forum
>- 
>   
>   Java 8 end of life JEP needed - Mark Waite plans to write it
>   - 
>   
>   UI modernization continues (thanks Jan Faracik and Tim Jacomb!)
>   
>

-- 
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/2a58aa1d-c4bb-46b7-9d0f-df3ad25dedafn%40googlegroups.com.

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

[Oleg Nenashev]

Hi Jesse,

Enabled it for all remaining projects in the list.

BR, Oleg

On Tuesday, January 11, 2022 at 3:59:28 PM UTC+1 Jesse Glick wrote:

> Anyone with infra-level permissions up for this? I just tried to switch 
> `maven-hpi-plugin` to GH Issues but noticed I lack admin access to the repo 
> (and certainly I would lack permissions to mark a Jira component closed for 
> entry of new issues, which I think is an option).
>

-- 
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/6b6ee004-c348-46d6-9976-142151a447f3n%40googlegroups.com.

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

You've suggested 4 great project ideas. Kris Stern is interested in
> co-mentoring the Jenkinsfile Runner Action for GitHub Actions, I will have
> you both down as mentors for this idea. As for the other 3 project ideas,
> if there's no other volunteers shall we skip them as to respect your time
> w/ family, etc.
>

 I think I will write up project idea drafts anyway. Usually many mentors
join during the application and selection phases, so I would not be
concerned about the number of potential mentors right now

Best regards,
Oleg






On Thu, Jan 6, 2022 at 11:56 PM Oleg Nenashev 
wrote:

> Hi Alyssa,
>
> 3 timeslots next week are OK for me. I might also be available tomorrow at
> 4:30PM UTC but not at 4:00PM UTC
>
> Best regards,
> Oleg
>
> On Thu, Jan 6, 2022 at 6:51 PM Alyssa Tong  wrote:
>
>> Pls use the below doodle instead. I have updated the poll to include
>> later time options in case Oleg (person transferring GSoC knowledge) has
>> family obligations.
>>
>> @Oleg Nenashev  I'm hoping one of these options
>> will work for you. If not, pls suggest a day/time.
>>
>> https://doodle.com/poll/vqrmawt6enkmbs3u?utm_source=poll_medium=link
>>
>> BR,
>> alyssa
>>
>> On Tue, Jan 4, 2022 at 6:53 PM Alyssa Tong  wrote:
>>
>>> Hi,
>>>
>>> I've started this doodle
>>> https://doodle.com/poll/h7acxvmbuxrumpwn?utm_source=poll_medium=link for
>>> the GSoC knowledge transfer.  Pls vote for a date & time.  All are welcome
>>> to join the call.
>>>
>>> Thank you,
>>> alyssa
>>>
>>> On Tue, Jan 4, 2022 at 9:18 AM Alyssa Tong  wrote:
>>>
>>>> Hi Oleg,
>>>>
>>>> You've suggested 4 great project ideas. Kris Stern is interested in
>>>> co-mentoring the Jenkinsfile Runner Action for GitHub Actions, I will have
>>>> you both down as mentors for this idea. As for the other 3 project ideas,
>>>> if there's no other volunteers shall we skip them as to respect your time
>>>> w/ family, etc.
>>>>
>>>> thanks,
>>>> alyssa
>>>>
>>>> On Thu, Dec 16, 2021 at 1:43 AM Oleg Nenashev 
>>>> wrote:
>>>>
>>>>> Hi Alyssa,
>>>>>
>>>>> Thanks a lot for taking care of it! I might be able to participate as
>>>>> org admin in some capacity, but I cannot commit much time next year. My
>>>>> personal situation is still complicated, and I'm not sure how much time I
>>>>> will be able to dedicate to Jenkins in general. I will be also Ieading 
>>>>> GSoC
>>>>> in Keptn so I will definitely be around in the program.
>>>>>
>>>>> Regarding mentorship and potential projects, this year I will be
>>>>> potentially available for the following projects/areas:
>>>>>
>>>>>- Improving Cloud Events plugin and aligning it with the emerging
>>>>>CD Events Standard
>>>>>- Jenkins and OpenTelemetry
>>>>>- Jenkinsfile executor service for Keptn (powered by Jenkinsfile
>>>>>Runner)
>>>>>- Jenkinsfile Runner Action for GitHub Actions
>>>>>
>>>>> Let me know if anyone is interested in those projects :)
>>>>>
>>>>> Best regards,
>>>>> Oleg
>>>>> On Wednesday, December 15, 2021 at 2:23:28 AM UTC+1 alytong13 wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I have started this thread on HERE
>>>>>> <https://community.jenkins.io/t/google-summer-of-code-gsoc-2022-call-for-organizers-mentors-and-project-ideas/1010>
>>>>>>  but thought i'd post it here as well.
>>>>>>
>>>>>> Much like the past 5 years, we are planning to participate in GSoC
>>>>>> 2022 <https://summerofcode.withgoogle.com/>.
>>>>>>
>>>>>> *About GSoC: *
>>>>>>
>>>>>> GSoC is a mentorship program focused on welcoming new contributors
>>>>>> into the community and helping them learn best practices that will help
>>>>>> them be long term OSS contributors.
>>>>>>
>>>>>> GSoC is an annual, global program that has been for college students.
>>>>>> In 2022 GSoC is expanding its program to encourage all newcomers of open
>>>>>> source that are 18 years and older. The program will no longer be sole

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

Hi Alyssa,

3 timeslots next week are OK for me. I might also be available tomorrow at
4:30PM UTC but not at 4:00PM UTC

Best regards,
Oleg

On Thu, Jan 6, 2022 at 6:51 PM Alyssa Tong  wrote:

> Pls use the below doodle instead. I have updated the poll to include later
> time options in case Oleg (person transferring GSoC knowledge) has
> family obligations.
>
> @Oleg Nenashev  I'm hoping one of these options
> will work for you. If not, pls suggest a day/time.
>
> https://doodle.com/poll/vqrmawt6enkmbs3u?utm_source=poll_medium=link
>
> BR,
> alyssa
>
> On Tue, Jan 4, 2022 at 6:53 PM Alyssa Tong  wrote:
>
>> Hi,
>>
>> I've started this doodle
>> https://doodle.com/poll/h7acxvmbuxrumpwn?utm_source=poll_medium=link for
>> the GSoC knowledge transfer.  Pls vote for a date & time.  All are welcome
>> to join the call.
>>
>> Thank you,
>> alyssa
>>
>> On Tue, Jan 4, 2022 at 9:18 AM Alyssa Tong  wrote:
>>
>>> Hi Oleg,
>>>
>>> You've suggested 4 great project ideas. Kris Stern is interested in
>>> co-mentoring the Jenkinsfile Runner Action for GitHub Actions, I will have
>>> you both down as mentors for this idea. As for the other 3 project ideas,
>>> if there's no other volunteers shall we skip them as to respect your time
>>> w/ family, etc.
>>>
>>> thanks,
>>> alyssa
>>>
>>> On Thu, Dec 16, 2021 at 1:43 AM Oleg Nenashev 
>>> wrote:
>>>
>>>> Hi Alyssa,
>>>>
>>>> Thanks a lot for taking care of it! I might be able to participate as
>>>> org admin in some capacity, but I cannot commit much time next year. My
>>>> personal situation is still complicated, and I'm not sure how much time I
>>>> will be able to dedicate to Jenkins in general. I will be also Ieading GSoC
>>>> in Keptn so I will definitely be around in the program.
>>>>
>>>> Regarding mentorship and potential projects, this year I will be
>>>> potentially available for the following projects/areas:
>>>>
>>>>- Improving Cloud Events plugin and aligning it with the emerging
>>>>CD Events Standard
>>>>- Jenkins and OpenTelemetry
>>>>- Jenkinsfile executor service for Keptn (powered by Jenkinsfile
>>>>Runner)
>>>>- Jenkinsfile Runner Action for GitHub Actions
>>>>
>>>> Let me know if anyone is interested in those projects :)
>>>>
>>>> Best regards,
>>>> Oleg
>>>> On Wednesday, December 15, 2021 at 2:23:28 AM UTC+1 alytong13 wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I have started this thread on HERE
>>>>> <https://community.jenkins.io/t/google-summer-of-code-gsoc-2022-call-for-organizers-mentors-and-project-ideas/1010>
>>>>>  but thought i'd post it here as well.
>>>>>
>>>>> Much like the past 5 years, we are planning to participate in GSoC
>>>>> 2022 <https://summerofcode.withgoogle.com/>.
>>>>>
>>>>> *About GSoC: *
>>>>>
>>>>> GSoC is a mentorship program focused on welcoming new contributors
>>>>> into the community and helping them learn best practices that will help
>>>>> them be long term OSS contributors.
>>>>>
>>>>> GSoC is an annual, global program that has been for college students.
>>>>> In 2022 GSoC is expanding its program to encourage all newcomers of open
>>>>> source that are 18 years and older. The program will no longer be solely
>>>>> focused on university students or recent graduates.
>>>>>
>>>>> *Important dates:*
>>>>>
>>>>>- Project application registration opens in February 2022
>>>>>- Registration for GSoC contributors opens in April 2022. See
>>>>>eligibility here 2
>>>>><https://summerofcode.withgoogle.com/get-started>
>>>>>
>>>>> 2022 will be the sixth year the Jenkins project participates in GSoC.
>>>>> As we prepare for this program, we are *looking for volunteers in the
>>>>> following areas:*
>>>>>
>>>>>-
>>>>>
>>>>>Organization administrators (Org admins): This role is to make
>>>>>sure the Project Ideas list is solid. Org admins are the final 
>>>>> authority
>>>>>about matters such 

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

Sure, and welcome back Alyssa!

I agree with Jean-Marc that some async updates to the guidelines would be
awesome. Note that the Jenkins GSoC org admin runbook (referenced from the
Jenkins GSoC project main page) is available here and is waiting for
comments/questions:
https://docs.google.com/document/d/1AeeIBfzst3VeI-hdRNlfPvp8NgcGneqI2uEkQoZ88q4/edit?usp=sharing
. I will not be able to work on it until Jan 13+ as well, but I might be
able to address some comments and questions if any

BR, Oleg




On Tue, Jan 4, 2022 at 4:41 PM Alyssa Tong  wrote:

> Hi Oleg et al,
>
> Happy 2022 
> I was on a much needed Christmas break and am now back.  I'm picking this
> back up, pls standby for additional communications on this today as i'll
> try to move this forward to next steps.
>
> Apologies for the delay.
>
> alyssa
>
> On Tue, Jan 4, 2022 at 6:55 AM Jean-Marc Meessen <
> jean-m...@meessen-web.org> wrote:
>
>> Hello Oleg,
>>
>> Thank you for your interest and dedication on making GSoC 2022 a success
>> for the Jenkins Project. It is good to know that you will be available to
>> contribute from January 13th.
>>
>> Please note that neither Alyssa nor Mark are back from the Christmas/New
>> Year break (circumstances made it a long break).
>>
>> Seen the heavy timezone and personal availability contrains, an
>> asynchronous hand-over seems best suited. Any written hand-over or coaching
>> would thus help.
>>
>> WDYT?
>>
>> /- Jmm
>>
>> On Monday, 3 January 2022 at 18:05:51 UTC+1 Oleg Nenashev wrote:
>>
>>> Hi all,
>>>
>>> So the Christmas break is over, and we should return to this topic as
>>> soon as possible. Currently we are not ready to work with students who
>>> already go to our website. We have not archived the previous year
>>> properly,  we don't have a list of project ideas for the upcoming year.
>>> When I was sent to the garden leave by my previous company, Mark Waite took
>>> an action to coordinate that. I guess there were other more important
>>> topics, but now it is critical if you want to have a good students
>>> contributing to the project. We already lose them, because the most
>>> successful students start looking into Google summer of code before the
>>> Christmas.
>>>
>>> If Alyssa and Jean-Marc are not available to work on that and to
>>> organize knowledge transfers as we agreed one month ago, I will take over
>>> this task after January 13th. I cannot work on that earlier due to the
>>> personal reasons (important court hearings).
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>>
>>>
>>>
>>> On Sat, 25 Dec 2021, 13:09 Oleg Nenashev,  wrote:
>>>
>>>> It is not enough to send an email to get org admins or mentors
>>>> unfortunately.
>>>> A little bit more effort and direct outreach is needed.
>>>>
>>>> On Monday, December 20, 2021 at 5:06:56 PM UTC+1 alytong13 wrote:
>>>>
>>>>> Hi Oleg,
>>>>>
>>>>> The knowledge transfer was mentioned in my original email, I didn't
>>>>> see volunteers for org admins. Nonetheless, let me follow up w/ a doodle
>>>>> for timing, for after the new years, and we'll take it from there.
>>>>>
>>>>> Thank you,
>>>>> alyssa
>>>>>
>>>>> On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev 
>>>>> wrote:
>>>>>
>>>>>> Hello Alyssa and Jean-Marc,
>>>>>>
>>>>>> Did you have a chance to start a poll for the knowledge transfer
>>>>>> meeting, and maybe a first coordination one?
>>>>>>
>>>>>> Taking the timing, it is very unlikely that it's going to happen
>>>>>> before the new year at this stage
>>>>>>
>>>>>> Best regards,
>>>>>> Oleg
>>>>>>
>>>>>> On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:
>>>>>>
>>>>>>> Thank you Kris and Oleg for your responses.  Your inputs are noted
>>>>>>> and I will circle back once we have more on project ideas and mentors.
>>>>>>>
>>>>>>> BR,
>>>>>>> alyssa
>>>>>>>
>>>>>>> On Thu, Dec 16, 2021 at 3:42 AM Kris Stern 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> 

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

Hi all,

So the Christmas break is over, and we should return to this topic as soon
as possible. Currently we are not ready to work with students who already
go to our website. We have not archived the previous year properly,  we
don't have a list of project ideas for the upcoming year. When I was sent
to the garden leave by my previous company, Mark Waite took an action to
coordinate that. I guess there were other more important topics, but now it
is critical if you want to have a good students contributing to the
project. We already lose them, because the most successful students start
looking into Google summer of code before the Christmas.

If Alyssa and Jean-Marc are not available to work on that and to organize
knowledge transfers as we agreed one month ago, I will take over this task
after January 13th. I cannot work on that earlier due to the personal
reasons (important court hearings).

Best regards,
Oleg Nenashev




On Sat, 25 Dec 2021, 13:09 Oleg Nenashev,  wrote:

> It is not enough to send an email to get org admins or mentors
> unfortunately.
> A little bit more effort and direct outreach is needed.
>
> On Monday, December 20, 2021 at 5:06:56 PM UTC+1 alytong13 wrote:
>
>> Hi Oleg,
>>
>> The knowledge transfer was mentioned in my original email, I didn't see
>> volunteers for org admins. Nonetheless, let me follow up w/ a doodle for
>> timing, for after the new years, and we'll take it from there.
>>
>> Thank you,
>> alyssa
>>
>> On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev 
>> wrote:
>>
>>> Hello Alyssa and Jean-Marc,
>>>
>>> Did you have a chance to start a poll for the knowledge transfer
>>> meeting, and maybe a first coordination one?
>>>
>>> Taking the timing, it is very unlikely that it's going to happen before
>>> the new year at this stage
>>>
>>> Best regards,
>>> Oleg
>>>
>>> On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:
>>>
>>>> Thank you Kris and Oleg for your responses.  Your inputs are noted and
>>>> I will circle back once we have more on project ideas and mentors.
>>>>
>>>> BR,
>>>> alyssa
>>>>
>>>> On Thu, Dec 16, 2021 at 3:42 AM Kris Stern  wrote:
>>>>
>>>>> Hi Alyssa and Oleg,
>>>>>
>>>>> I am interested in volunteering and mentoring in GSoC 2022 for
>>>>> Jenkins. In particular, I would like to work on the project idea
>>>>> "Jenkinsfile Runner Action for GitHub Actions" as listed in Oleg's email.
>>>>>
>>>>> Maybe I should introduce myself a bit to begin. I started contributing
>>>>> to open-source in late 2018/early 2019, first working on some astronomy
>>>>> software development, as my PhD project was in astrophysics then. Also, I
>>>>> was previously a GSoC contributor in 2019 and 2020, working under the
>>>>> mentorship of OpenAstronomy, and was able to successfully complete both
>>>>> projects. Professionally currently I work in the IT sector, on software
>>>>> engineering. I am based in Hong Kong, but am comfortable working around
>>>>> different time zones outside of the Asia Pacific (or APAC) area.
>>>>>
>>>>> Please let me know how I may proceed further.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Best,
>>>>> Kris Stern, PhD
>>>>>
>>>>> --
>>>>> *From:* jenkin...@googlegroups.com  on
>>>>> behalf of Oleg Nenashev 
>>>>> *Sent:* 16 December 2021 17:43
>>>>> *To:* Jenkins Developers 
>>>>> *Subject:* Re: Google Summer of Code (GSoC) 2022: Call for
>>>>> organizers, mentors, and project ideas
>>>>>
>>>>> Hi Alyssa,
>>>>>
>>>>> Thanks a lot for taking care of it! I might be able to participate as
>>>>> org admin in some capacity, but I cannot commit much time next year. My
>>>>> personal situation is still complicated, and I'm not sure how much time I
>>>>> will be able to dedicate to Jenkins in general. I will be also Ieading 
>>>>> GSoC
>>>>> in Keptn so I will definitely be around in the program.
>>>>>
>>>>> Regarding mentorship and potential projects, this year I will be
>>>>> potentially available for the following projects/areas:
>>>>>
>>>>>- Improving Cloud Events plugin and aligning it with the 

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Oleg Nenashev]

I see no problem with switching the Weekly release line in February with
the new LTS baseline release. I also agree with Baptiste that a 3-month
notice for deprecation is too short. I suggest announcing the September LTS
as a target for complete Java 8 support removal in the LTS baseline. The
problem is how to switch the weekly early without disrupting the codebase
too much so that LTS becomes sustainable...

 A few options

   - Extend the lifetime of the current LTS baseline until September... or
   later more if needed (read as: "while somebody is dedicating resources to
   maintain it", maybe one of the vendors). We would maintain two LTS lines
   for some time, but the new one will be Java 11 only and hence we will be
   able to integrate all the upgrades shortly into the new LTS line.
   - Keep Java 8 de-facto compatibility until the June LTS cut-off in
   April/May. Add a patch to Extra Executables WAR that disables Java 8 by
   default unless *--use-deprecated-java* is set (inversuion of
   --use-future-java)

I suggest the first option if the Release and Security teams agree. IIUC
the CloudBees part of the security team would have to maintain the old
baseline for quite a while regardless, if I read
https://docs.cloudbees.com/docs/cloudbees-common/latest/maintenance-lifecycle#fixed-release
correctly. So it should not be a huge deal






On Wed, Dec 29, 2021 at 8:20 AM Baptiste Mathus  wrote:

> I like the planning idea, I think updating the minimum in Feb 2021 for
> weeklies and hence June for LTS is a bit too aggressive.
>
> I think we should *at least* target the LTS _after_ June.
>
> And in the meantime keep communicating on this timeline like we had done
> for Java 8.
> Blogs. Tweet encouraging to update to Java 11, etc. Messages on the users
> ML...
>
> Le mar. 21 déc. 2021 à 21:01, Tim Jacomb  a écrit :
>
>> Back to Java 11 :)
>>
>> (I suggest another thread for Java 17 Basil has been doing some great
>> work there)
>>
>> There's been an 'admin monitor' around for quite a while now encouraging
>> users to upgrade to Java 11 if they are on 8.
>>
>> The JavaVersionRecommendationAdminMonitor
>> 
>>  was
>> introduced in (approx):
>>
>>- 2.296 - 1st June 2021
>>- 2.303.1 - 25th August 2021
>>
>> Since that went in Java 11 usage skyrocketed according to
>> https://stats.jenkins.io/plugin-installation-trend/jvms.json
>>
>> Basil has created a PR 
>> for updating the monitor with a specific date (to be filled in) for
>> deprecation.
>>
>> I think we should target the LTS after next for dropping Java 8 support.
>>
>> That would be:
>>
>>- Weekly - 2nd February (week after baseline selection for next LTS)
>>- LTS - approx 7th June (roughly when ths LTS after next will be
>>released)
>>
>> Next LTS would also be possible, we could do:
>>
>>- Weekly - January 19th
>>- LTS - March 9th
>>
>> Thoughts?
>>
>> Thanks
>> Tim
>>
>> On Mon, 20 Dec 2021 at 22:19, Basil Crow  wrote:
>>
>>> On Mon, Dec 20, 2021 at 1:53 PM 'Jesse Glick' via Jenkins Developers
>>>  wrote:
>>> >
>>> > Is this mostly about Servlet API types, or other EE packages?
>>>
>>> Servlet types and JavaMail were the most common cases I saw in the
>>> prototype, along with a new package namespace for FileUpload to go
>>> along with the new servlet types. Seems more straightforward to do one
>>> large Jakarta migration rather than several smaller ones. This is
>>> going to be a major disruption anyway, so might as well just get it
>>> over with. The only migration I didn't tackle in the prototype was the
>>> Jakarta Dependency Injection API, because Guice doesn't support the
>>> new types yet (google/guice#1383). I imagine Guice will support them
>>> at some point in the future; Spring Security and Commons FileUpload
>>> only support the new types in snapshot releases at present. My gut
>>> feeling is that this migration will probably kick into full gear
>>> around late 2022 or early 2023.
>>>
>>> --
>>> 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/CAFwNDjpqkX2mBsBoh7LrwCBJtU%2B3ZGdvR-T9c3A3ij2mew-3ww%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/CAH-3Bie-uApHh6mDCSWOMzR%2BWBNC5ZZmjdVDXGd2cS8iaDtc3Q%40mail.gmail.com
>> 

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

It is not enough to send an email to get org admins or mentors 
unfortunately.
A little bit more effort and direct outreach is needed.

On Monday, December 20, 2021 at 5:06:56 PM UTC+1 alytong13 wrote:

> Hi Oleg,
>
> The knowledge transfer was mentioned in my original email, I didn't see 
> volunteers for org admins. Nonetheless, let me follow up w/ a doodle for 
> timing, for after the new years, and we'll take it from there.
>
> Thank you,
> alyssa
>
> On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev  wrote:
>
>> Hello Alyssa and Jean-Marc,
>>
>> Did you have a chance to start a poll for the knowledge transfer meeting, 
>> and maybe a first coordination one?
>>
>> Taking the timing, it is very unlikely that it's going to happen before 
>> the new year at this stage
>>
>> Best regards,
>> Oleg
>>
>> On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:
>>
>>> Thank you Kris and Oleg for your responses.  Your inputs are noted and I 
>>> will circle back once we have more on project ideas and mentors. 
>>>
>>> BR,
>>> alyssa
>>>
>>> On Thu, Dec 16, 2021 at 3:42 AM Kris Stern  wrote:
>>>
>>>> Hi Alyssa and Oleg,
>>>>
>>>> I am interested in volunteering and mentoring in GSoC 2022 for Jenkins. 
>>>> In particular, I would like to work on the project idea "Jenkinsfile 
>>>> Runner 
>>>> Action for GitHub Actions" as listed in Oleg's email. 
>>>>
>>>> Maybe I should introduce myself a bit to begin. I started contributing 
>>>> to open-source in late 2018/early 2019, first working on some astronomy 
>>>> software development, as my PhD project was in astrophysics then. Also, I 
>>>> was previously a GSoC contributor in 2019 and 2020, working under the 
>>>> mentorship of OpenAstronomy, and was able to successfully complete both 
>>>> projects. Professionally currently I work in the IT sector, on software 
>>>> engineering. I am based in Hong Kong, but am comfortable working around 
>>>> different time zones outside of the Asia Pacific (or APAC) area. 
>>>>
>>>> Please let me know how I may proceed further. 
>>>>
>>>> Thanks!
>>>>
>>>> Best,
>>>> Kris Stern, PhD
>>>>
>>>> --
>>>> *From:* jenkin...@googlegroups.com  on 
>>>> behalf of Oleg Nenashev 
>>>> *Sent:* 16 December 2021 17:43
>>>> *To:* Jenkins Developers 
>>>> *Subject:* Re: Google Summer of Code (GSoC) 2022: Call for organizers, 
>>>> mentors, and project ideas 
>>>>  
>>>> Hi Alyssa,
>>>>
>>>> Thanks a lot for taking care of it! I might be able to participate as 
>>>> org admin in some capacity, but I cannot commit much time next year. My 
>>>> personal situation is still complicated, and I'm not sure how much time I 
>>>> will be able to dedicate to Jenkins in general. I will be also Ieading 
>>>> GSoC 
>>>> in Keptn so I will definitely be around in the program.
>>>>
>>>> Regarding mentorship and potential projects, this year I will be 
>>>> potentially available for the following projects/areas:
>>>>
>>>>- Improving Cloud Events plugin and aligning it with the emerging 
>>>>CD Events Standard
>>>>- Jenkins and OpenTelemetry
>>>>- Jenkinsfile executor service for Keptn (powered by Jenkinsfile 
>>>>Runner)
>>>>- Jenkinsfile Runner Action for GitHub Actions
>>>>
>>>> Let me know if anyone is interested in those projects :)
>>>>
>>>> Best regards,
>>>> Oleg
>>>> On Wednesday, December 15, 2021 at 2:23:28 AM UTC+1 alytong13 wrote:
>>>>
>>>> Hi All,
>>>>
>>>> I have started this thread on HERE 
>>>> <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.jenkins.io%2Ft%2Fgoogle-summer-of-code-gsoc-2022-call-for-organizers-mentors-and-project-ideas%2F1010=04%7C01%7C%7C49022dd5df8341fd5e6d08d9c07876f6%7C84df9e7fe9f640afb435%7C1%7C0%7C637752445889509965%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=aGGzrIGI8r%2BXaiDisYBAEOYoRxJTCAgBS78m8FoiD7s%3D=0>
>>>>  
>>>>  but thought i'd post it here as well.
>>>>
>>>> Much like the past 5 years, we are planning to participate in GSoC 2022

Re: Proposal: Update CloudBees maintained plugins with CloudBees team

[Oleg Nenashev]

FWIW I explicitly -1 adding such undetermined group top any plugin where I 
am listed as co-maintainer.
Happy to discuss on a case by case basis, because I'd step down for some of 
the plugins

On Friday, December 24, 2021 at 7:52:35 PM UTC+1 Oleg Nenashev wrote:

> I requested changes in both pull requests. This approach does not seem to 
> be correct for any plugin having at least one non-CloudBees contributor. I 
> doubt such contributors would expect an arbitrary CloudBees employee to be 
> able to cut the releases. Pretty much the same applies to other plugins. 
> Even if all maintainers are employed by CloudBees, it does not mean that it 
> is maintained during the working time.
>
> I suggest closing these bulk PRs and opening new ones only for those 
> plugins where a consensus with all maintainers is reached
>
>
> On Wednesday, December 22, 2021 at 4:36:28 AM UTC+1 Carroll Chiou wrote:
>
>> Hello all,
>>
>> In an effort to better manage plugins that are being maintained by 
>> CloudBees employees, we would like to add the “cloudbees-developers” team 
>> to the appropriate repository permission files and update the corresponding 
>> GitHub repos. You can review the proposed plugins here: 
>>
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/2265
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/2266
>>
>> Thanks,
>> Carroll Chiou
>
>

-- 
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/3867c881-5569-4d7c-b757-6f37f8404b8cn%40googlegroups.com.

Re: Proposal: Update CloudBees maintained plugins with CloudBees team

[Oleg Nenashev]

I requested changes in both pull requests. This approach does not seem to 
be correct for any plugin having at least one non-CloudBees contributor. I 
doubt such contributors would expect an arbitrary CloudBees employee to be 
able to cut the releases. Pretty much the same applies to other plugins. 
Even if all maintainers are employed by CloudBees, it does not mean that it 
is maintained during the working time.

I suggest closing these bulk PRs and opening new ones only for those 
plugins where a consensus with all maintainers is reached


On Wednesday, December 22, 2021 at 4:36:28 AM UTC+1 Carroll Chiou wrote:

> Hello all,
>
> In an effort to better manage plugins that are being maintained by 
> CloudBees employees, we would like to add the “cloudbees-developers” team 
> to the appropriate repository permission files and update the corresponding 
> GitHub repos. You can review the proposed plugins here: 
>
> https://github.com/jenkins-infra/repository-permissions-updater/pull/2265
> https://github.com/jenkins-infra/repository-permissions-updater/pull/2266
>
> Thanks,
> Carroll Chiou

-- 
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/1d0e5f63-8607-4cc6-b312-afc9d3a4a747n%40googlegroups.com.

New Year blogpost for Jenkins

[Oleg Nenashev]

Hi all,

So the New Year's coming soon. So now we will need a yearly a report for
the Continuous Delivery Foundation. I guess we would like to have a
standard Jenkins blog post this year, right?

Would anyone be interested to contribute to this blog post? I might be able
to coordinate the effort though I'm not sure this is very appropriate. I
haven't been as active for in the community this year as used to be before.

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBTyBdzX0Jj4EaHtkrqWZ2s09WW3L3Q24Lqh1KW%2BZ_JaA%40mail.gmail.com.

Re: Add timja to jep editors

[Oleg Nenashev]

+1

On Tuesday, December 21, 2021 at 3:47:25 PM UTC+1 m...@basilcrow.com wrote:

> +1
>

-- 
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/fddeceec-2156-4c50-a07c-db204e0013bcn%40googlegroups.com.

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Oleg Nenashev]

Thanks to Basil for starting a pull request for it. Probably this is a case
when we should probably work on the JEP together with all platform SIG
members.

As a first step, I would recommend putting a warning for upcoming Java 8
depreciation as a Jenkins administrative monitor and to the startup log in
https://github.com/jenkinsci/extras-executable-war

On Sun, Dec 19, 2021 at 7:06 AM Olivier Lamy  wrote:

> Jetty 11 is too far away and by the way mean moving to Jakarta namespace
> which means having our all frameworks (and plugins) using this namespace…
>
> We should first migrate to jetty 10 which only have java11 minimum. I have
> started a branch in winstone for this but need to finish it.
>
> On Sat, 18 Dec 2021 at 10:48 pm, Basil Crow  wrote:
>
>> On Tue, Nov 16, 2021 at 2:30 AM Olivier Lamy 
>> wrote:
>>
>>> But as it turns EOL, we will have to upgrade to Jetty 10 (or 11 but not
>>> sure at this stage Jenkins will have been migrated to use
>>> jakarta.servlet/jakarta.* namespaces).
>>>
>>
>> I put together a prototype
>>  of the Jetty 11
>> upgrade and found that the Jakarta EE 9 package name transition required a
>> corresponding upgrade to Spring Security 6, which has a Java 17 and Jakarta
>> EE 9 baseline. So an upgrade to Jetty 11 requires an upgrade to Java 17.
>>
>> --
>> 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/CAFwNDjpDtk%2B2Y8OoXxtkQ_N1Z0%3DQJZRFQ6VEd6AodT6bHjuRDA%40mail.gmail.com
>> 
>> .
>>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> --
> 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/YghQ0YP4m78/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/CAPoyBqSEM9HwJR6yc1DTE_b7AO5Mzcz%3DBdoqHBt-RYhDYrNgsg%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/CAPfivLBQY4qQrSXdjztQfRyd9oXHcvm3%2BUh5LdrLLFVLxu37iA%40mail.gmail.com.

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

Hello Alyssa and Jean-Marc,

Did you have a chance to start a poll for the knowledge transfer meeting,
and maybe a first coordination one?

Taking the timing, it is very unlikely that it's going to happen before the
new year at this stage

Best regards,
Oleg

On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:

> Thank you Kris and Oleg for your responses.  Your inputs are noted and I
> will circle back once we have more on project ideas and mentors.
>
> BR,
> alyssa
>
> On Thu, Dec 16, 2021 at 3:42 AM Kris Stern  wrote:
>
>> Hi Alyssa and Oleg,
>>
>> I am interested in volunteering and mentoring in GSoC 2022 for Jenkins.
>> In particular, I would like to work on the project idea "Jenkinsfile Runner
>> Action for GitHub Actions" as listed in Oleg's email.
>>
>> Maybe I should introduce myself a bit to begin. I started contributing to
>> open-source in late 2018/early 2019, first working on some astronomy
>> software development, as my PhD project was in astrophysics then. Also, I
>> was previously a GSoC contributor in 2019 and 2020, working under the
>> mentorship of OpenAstronomy, and was able to successfully complete both
>> projects. Professionally currently I work in the IT sector, on software
>> engineering. I am based in Hong Kong, but am comfortable working around
>> different time zones outside of the Asia Pacific (or APAC) area.
>>
>> Please let me know how I may proceed further.
>>
>> Thanks!
>>
>> Best,
>> Kris Stern, PhD
>>
>> --
>> *From:* jenkinsci-dev@googlegroups.com 
>> on behalf of Oleg Nenashev 
>> *Sent:* 16 December 2021 17:43
>> *To:* Jenkins Developers 
>> *Subject:* Re: Google Summer of Code (GSoC) 2022: Call for organizers,
>> mentors, and project ideas
>>
>> Hi Alyssa,
>>
>> Thanks a lot for taking care of it! I might be able to participate as org
>> admin in some capacity, but I cannot commit much time next year. My
>> personal situation is still complicated, and I'm not sure how much time I
>> will be able to dedicate to Jenkins in general. I will be also Ieading GSoC
>> in Keptn so I will definitely be around in the program.
>>
>> Regarding mentorship and potential projects, this year I will be
>> potentially available for the following projects/areas:
>>
>>- Improving Cloud Events plugin and aligning it with the emerging CD
>>Events Standard
>>- Jenkins and OpenTelemetry
>>- Jenkinsfile executor service for Keptn (powered by Jenkinsfile
>>Runner)
>>- Jenkinsfile Runner Action for GitHub Actions
>>
>> Let me know if anyone is interested in those projects :)
>>
>> Best regards,
>> Oleg
>> On Wednesday, December 15, 2021 at 2:23:28 AM UTC+1 alytong13 wrote:
>>
>> Hi All,
>>
>> I have started this thread on HERE
>> <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.jenkins.io%2Ft%2Fgoogle-summer-of-code-gsoc-2022-call-for-organizers-mentors-and-project-ideas%2F1010=04%7C01%7C%7C49022dd5df8341fd5e6d08d9c07876f6%7C84df9e7fe9f640afb435%7C1%7C0%7C637752445889509965%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=aGGzrIGI8r%2BXaiDisYBAEOYoRxJTCAgBS78m8FoiD7s%3D=0>
>>  but thought i'd post it here as well.
>>
>> Much like the past 5 years, we are planning to participate in GSoC 2022
>> <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsummerofcode.withgoogle.com%2F=04%7C01%7C%7C49022dd5df8341fd5e6d08d9c07876f6%7C84df9e7fe9f640afb435%7C1%7C0%7C637752445889509965%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=mGnqe3ZaS317zEert5hXbuNSac7%2Bx11WcopIrvxOBys%3D=0>
>> .
>>
>> *About GSoC: *
>>
>> GSoC is a mentorship program focused on welcoming new contributors into
>> the community and helping them learn best practices that will help them be
>> long term OSS contributors.
>>
>> GSoC is an annual, global program that has been for college students. In
>> 2022 GSoC is expanding its program to encourage all newcomers of open
>> source that are 18 years and older. The program will no longer be solely
>> focused on university students or recent graduates.
>>
>> *Important dates:*
>>
>>- Project application registration opens in February 2022
>>- Registration for GSoC contributors opens in April 2022. See
>>eligibility here 2
>>
>> <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsummerofcode.withgoogle.com%2Fget-star

Re: Proposal: Changing the Contributor License Agreement Process

[Oleg Nenashev]

Hi all,

Quick update here from the yesterday's governance meeting:

   - The LFX EasyCLA support ticket is still open for jenkinsci and 
   jenkins-infra organizations. Stapler maintainers can already adopt it if 
   they are ready & want to try
   - I pinged the LFX support team to get the request over the line. I do 
   not have permissions to manage the CDF EasyCLA GitHub organizations with my 
   level of the permissions, but then I can manage the repositories
   
Best regards,
Oleg
On Tuesday, November 9, 2021 at 2:42:34 AM UTC+1 boa...@gmail.com wrote:

> I think simplifying the ICLA process is a fantastic idea. It’s something 
> I’d like to implement at Apache at some point, too. Reducing contributor 
> friction is usually a great idea.
>
> Matt Sicker
>
> On Nov 8, 2021, at 05:20, Mark Waite  wrote:
>
> 
>
> +1 from me.  Thanks very much for doing it.
>
> On Mon, Nov 8, 2021 at 2:38 AM Oleg Nenashev wrote:
>
>> Hi all,
>>
>> I would like to proceed with  https://github.com/jenkinsci/infra-cla and 
>> to build a new process around this repository for now (TL;DR: ditching PDFs 
>> for new CLAs and gradually migrating old ones). Any objections?
>>
>> Best rgeards,
>> Oleg
>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-de...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE_xBY3S__MB%2BkRdXML2-WRbDDz-3LkyUh11OApSCfm7w%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE_xBY3S__MB%2BkRdXML2-WRbDDz-3LkyUh11OApSCfm7w%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/04e312d2-0cde-4f91-a5b0-8ca653ff7523n%40googlegroups.com.

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

Hi Alyssa,

Thanks a lot for taking care of it! I might be able to participate as org 
admin in some capacity, but I cannot commit much time next year. My 
personal situation is still complicated, and I'm not sure how much time I 
will be able to dedicate to Jenkins in general. I will be also Ieading GSoC 
in Keptn so I will definitely be around in the program.

Regarding mentorship and potential projects, this year I will be 
potentially available for the following projects/areas:

   - Improving Cloud Events plugin and aligning it with the emerging CD 
   Events Standard
   - Jenkins and OpenTelemetry
   - Jenkinsfile executor service for Keptn (powered by Jenkinsfile Runner)
   - Jenkinsfile Runner Action for GitHub Actions

Let me know if anyone is interested in those projects :)

Best regards,
Oleg
On Wednesday, December 15, 2021 at 2:23:28 AM UTC+1 alytong13 wrote:

> Hi All,
>
> I have started this thread on HERE 
> <https://community.jenkins.io/t/google-summer-of-code-gsoc-2022-call-for-organizers-mentors-and-project-ideas/1010>
>  
>  but thought i'd post it here as well.
>
> Much like the past 5 years, we are planning to participate in GSoC 2022 
> <https://summerofcode.withgoogle.com/>.
>
> *About GSoC: *
>
> GSoC is a mentorship program focused on welcoming new contributors into 
> the community and helping them learn best practices that will help them be 
> long term OSS contributors.
>
> GSoC is an annual, global program that has been for college students. In 
> 2022 GSoC is expanding its program to encourage all newcomers of open 
> source that are 18 years and older. The program will no longer be solely 
> focused on university students or recent graduates.
>
> *Important dates:*
>
>- Project application registration opens in February 2022
>- Registration for GSoC contributors opens in April 2022. See 
>eligibility here 2 <https://summerofcode.withgoogle.com/get-started>
>
> 2022 will be the sixth year the Jenkins project participates in GSoC. As 
> we prepare for this program, we are *looking for volunteers in the 
> following areas:*
>
>- 
>
>Organization administrators (Org admins): This role is to make sure 
>the Project Ideas list is solid. Org admins are the final authority about 
>matters such as which GSoC contributor projects will be accepted, who will 
>mentor whom, and what the end date will be for a coding project.
>- 
>
>Topics & Mentors: Here’s how to submit project ideas  
><https://www.jenkins.io/projects/gsoc/proposing-project-ideas/>
>
> If you have any questions, or want to get involved, there is a Gitter 
> channel <https://gitter.im/jenkinsci/gsoc-sig> and a dedicated mailing 
> list <https://groups.google.com/g/jenkinsci-gsoc-all-public>. Please join 
> the Jenkins GSoC mailing list 
> <https://groups.google.com/g/jenkinsci-gsoc-all-public> if you would like 
> to be kept up to date on GSoC information.
>
> Lastly, Oleg Nenashev, the driver of Jenkins GSoC for the past years, will 
> be hosting a walk thru of GSoC best practices. This would be great if 
> you’re thinking about joining me as an org admin. More to come on this soon.
>
> BR,
> alyssa
>

-- 
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/458549a6-b88e-406c-874c-b203659b0d77n%40googlegroups.com.

Re: Help maintaining role-strategy-plugin

[Oleg Nenashev]

Hi Thomas,

Thanks a lot for stepping up! Indeed it would be great to have a maintainer 
for the plugin, and I'm happy to support you in this role. I have very 
limited bandwidth but I will do my best to help with some code reviews and 
onboarding if needed.

I will add you to GitHUb. Before releasing the plugin, let's have a chat in 
the email. To get release permissions, yu will need to submit a pull 
request 
to 
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-role-strategy.yml

Best regards
Oleg Nenashev


On Monday, November 29, 2021 at 8:17:18 PM UTC+1 Thomas Nemer wrote:

> Hello Mark,
>
> Thanks for this nice documentation.
> I'll read it entirely soon (and have a look at the videos too), but at 
> first glance, it seems I'm already familiar with all the tools and practice 
> described.
>
> I already have made this 
> <https://github.com/jenkinsci/role-strategy-plugin/pull/154> pull 
> request, which motivated the idea of becoming a maintainer for the plugin.
>
> Thomas Nemer
> On 29/11/2021 17:52, Mark Waite wrote:
>
>
>
> On Monday, November 29, 2021 at 9:42:35 AM UTC-7 Thomas Nemer wrote:
>
>> Hello Jenkins Developers, 
>>
>> It seems the role-strategy-plugin could need some help for maintenance, 
>> and I'm willing to offer my help on that subject. 
>> Oleg Nenashev proposed to discuss that here. 
>>
>> I am globally not familiar with this process, but as I understand, there 
>> is a permission manager tool that needs to be updated so that it is 
>> possible to push on the binary repository and permissions needed on the 
>> git repo, but that's about all I know ^^ 
>>
>> As I said to Oleg, I'm far from being an experienced plugin developer, 
>> I've only created a couple of PRs on nested-view plugin and I have one 
>> PR waiting on role-strategy-plugin which will probably need some rework 
>> before being acceptable, but I'm using the plugin on a daily basis, and 
>> would be happy to help making it properly maintained. 
>>
>>
> Thanks very much for your willingness to contribute to the plugin and to 
> become a maintainer.
>
> If one of the maintainers of the plugin is willing to approve you as a 
> maintainer, you can be made a maintainer immediately.  If they're not ready 
> to do that yet, you can start contributing to the plugin through a series 
> of pull requests. The "Contributing to Open Source" workshop 
> <https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.hvd0nm6pz5o4>
>  
> from DevOps World 2021 suggests a series of small steps that help the 
> plugin and help a new contributor become familiar with the plugin.  That 
> document includes links to a five part video series 
> <https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.oz0bxvhyvna5>
>  
> that illustrates many of the steps.
>
> Mark Waite
>  
>
>>
>> Thomas Nemer 
>>
>> -- 
> 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/dfb11be7-e55e-4b25-9af2-e5c702ccfe40n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/dfb11be7-e55e-4b25-9af2-e5c702ccfe40n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/6a547253-2750-4642-a34f-fa3558d76fb2n%40googlegroups.com.

Re: New members of jenkins.io triage team

[Oleg Nenashev]

Sorry, I dropped the ball on it. TooManyEmergenciesException
On Thursday, November 25, 2021 at 5:43:30 AM UTC+1 Mark Waite wrote:

> Kristin is now a member of the triage team.
>
> Invitations have been sent to Meg and Dheeraj.  Thanks to all.
>
> On Wed, Nov 17, 2021 at 9:34 AM Tim Jacomb  wrote:
>
>> +1 no need for triage, it doesn't give much permission at all
>>
>> On Wed, 17 Nov 2021 at 16:16, Mark Waite  wrote:
>>
>>> We met in Docs Office Hours this week and decided that we should proceed 
>>> to add the new members to the triage team even without the new CLA process.
>>>
>>> On Thu, Nov 4, 2021 at 10:41 AM Mark Waite  wrote:
>>>
>>>> +1 from me to enable EasyCLA for the  
>>>> https://github.com/jenkinsci/infra-cla repository .
>>>>
>>>> No problem if we want to make the CLA a pre-req for triage team 
>>>> membership, especially if they can use EasyCLA to do it.
>>>>
>>>> Mark Waite
>>>>
>>>> On Thursday, November 4, 2021 at 12:47:06 AM UTC-6 Oleg Nenashev wrote:
>>>>
>>>>> +1 for all candidates. FTR I would recommend making ICLA a 
>>>>> prerequisite for Triage team as well.
>>>>> If everyone is fine, I will proceed with enabling EasyCLA for the 
>>>>> https://github.com/jenkinsci/infra-cla repository so that we switch 
>>>>> to a new flow instead of the PDF requirements
>>>>>
>>>>> -- 
>>>> 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/pLpIi7e9pMU/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/07d34361-d5ca-4802-9356-c1be79f6625dn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/07d34361-d5ca-4802-9356-c1be79f6625dn%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>>> 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/CAO49JtENMjscBHORt5OspqNtOES-sXOwGFb89jP2bLypGjTg%2BQ%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtENMjscBHORt5OspqNtOES-sXOwGFb89jP2bLypGjTg%2BQ%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> -- 
>> 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-3BicVARVA-TEf0XznNVPYMbkWuOmFLJu6-yh-xab1jUswSg%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicVARVA-TEf0XznNVPYMbkWuOmFLJu6-yh-xab1jUswSg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/0ca4955f-7597-4d8b-b63c-d4b44e3b8ae3n%40googlegroups.com.

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Oleg Nenashev]

Yes, something is definitely wrong. We have a sync-up with Andrew Bayer
today, let's see what whether we could triage that quickly

On Wed, Nov 17, 2021 at 10:17 AM 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
>
> On Wed, Nov 17, 2021 at 10:03 AM Daniel Beck  wrote:
>
>>
>> In fact, looking at the difference between
>> https://stats.jenkins.io/jenkins-stats/svg/total-jenkins.svg and the JVM
>> stats, we can see they were almost equal (99+%) up to early 2019. And then
>> around the time https://www.jenkins.io/changelog-stable/#v2.164.1
>> happened, the difference started to grow, and we're now having 25% fewer
>> installs with JVM information than total known installs.
>>
>
>
> FTR
> https://docs.google.com/spreadsheets/d/1_7jf9Nx6uaZA9ydFgdN5bgFpqceCEwGuVmcY76MvBiw/edit#gid=0
>
>
> JVM stats from
>
> $ jq --raw-output '.jvmStatsPerMonth | to_entries[] | "\( .key | tonumber
> / 1000 | todateiso8601[0:7] )\t\( .value | add )"' jvms.json
>
>
> --
> 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/YghQ0YP4m78/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/CAMo7PtJtRs8V5b3PYJxfk%3Do_WjPa8GTuHu1dz_O6KPobuA1JWQ%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/CAPfivLCaj%2BibnSvDUiXHKyufpE7ybbGmJhfMomraCf20Av73QA%40mail.gmail.com.

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Oleg Nenashev]

I think we should eventually drop Java 8 support but only when we have 
enough Java 11 adoption
What we could do in short term is to deprecate Java 8 and to put explicit 
recommendation to switch to Java 11 or 17 preview
IMHO we are already in the state when we can announce our intent to drop 
support for Java 8, maybe with minimum timeframe of 6/9 months in the 
announcement. The actual timeline could be even longer, e.g. 1 year for LTS 
best case

BR, Oleg

On Tuesday, November 16, 2021 at 2:05:27 PM UTC+1 Mark Waite wrote:

> There is no plan to make Java 11 a Jenkins minimum requirement yet.
>
> When the Docker images were changed to Java 11 
>  
> in August, 2021, the discussions in the governing board meeting noted that 
> we don't have a plan to make Java 11 a minimum requirement for Jenkins.  
> Java 11 discussions were also held in the Java 11 workshop at the June 
> 28, 2021 contributor summit .
>
> The "Reasoning" 
>  
> section of JEP-232 that describes the change to Java 11 as the default in 
> the Docker images notes that there are still too many users running Jenkins 
> on Java 8 to consider dropping support for Java 8.
>
> The JGit development team is discussing their move to Java 11 as minimum 
> required Java version.  JGit 6 (no release date stated yet, but under 
> discussion, possibly as soon as early 2022) will drop support for Java 8.  
> The discussion thread is available on their mailing list archive 
> .  We're relying on 
> JGit's continued support of older versions for security fixes since they've 
> done that in the past.
>
> Mark Waite
>
> On Tuesday, November 16, 2021 at 3:30:16 AM UTC-7 olive...@gmail.com 
> wrote:
>
>> Hi,
>> There have been some announcements on Jetty user mailing list regarding 
>> EOL of Jetty 9.4.x (the current version used by Winstone) see thread here 
>> [1].
>> Please note EOL of Jetty 9.4.x is not soon (probably 2 maye more 3 years).
>> But as it turns EOL, we will have to upgrade to Jetty 10 (or 11 but not 
>> sure at this stage Jenkins will have been migrated to use 
>> jakarta.servlet/jakarta.* namespaces).
>> Is there any plan to make Jenkins Java 11 as a minimum requirement? soon?
>>
>> regards
>> -- 
>> Olivier 
>> [1] https://www.eclipse.org/lists/jetty-users/msg10029.html
>>
>

-- 
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/024f7f7e-2db4-48b3-acf1-af91eb21140dn%40googlegroups.com.

Re: Proposal: Changing the Contributor License Agreement Process

[Oleg Nenashev]

Hi all,

I would like to proceed with  https://github.com/jenkinsci/infra-cla and to 
build a new process around this repository for now (TL;DR: ditching PDFs 
for new CLAs and gradually migrating old ones). Any objections?

Best rgeards,
Oleg

On Tuesday, June 22, 2021 at 11:25:44 PM UTC+2 Oleg Nenashev wrote:

> Hi Tim. I would not like to enforce it for the Jenkins core and components 
> until we have all active core maintainers and company contributors to sign 
> ICLA/CCLA. It may take months. What I want to do is to enable EasyCLA 
> without enforcement. So I need a few repositories where we could enable 
> EasyCLA so that everyone can prepare.
>
> I suggest the following repositories:
>
>- https://github.com/jenkinsci/infra-cla - good repo for testing CLA. 
>Everyone can submit PR with removing dated CLAs while verifying their 
>signatures in the process :)
>- platformlabeler-plugin and the elastic-axis-plugin as suggested by 
>Mark
>- https://github.com/jenkinsci/custom-war-packager - not actively 
>developed at the moment
>- https://github.com/jenkinsci/label-verifier-plugin - not actively 
>developed at the moment
>
> Is everyone fine with the ICLA/CCLA text? There are some minor differences 
> from the current ICLA/CCLAs we use
>
> BR, Oleg
>
>
>
>
> On Tuesday, June 22, 2021 at 11:00:31 PM UTC+2 timja...@gmail.com wrote:
>
>> Is this close enough for a vote? Do we actually want to do this?
>>
>> Moving the CLA process away from the current process sure, but enabling 
>> it on Jenkins core?
>>
>> On Tue, 22 Jun 2021 at 21:12, Mark Waite  wrote:
>>
>>> Those all sound great to me.
>>>
>>> I volunteer the platformlabeler-plugin and the elastic-axis-plugin as 
>>> two that could be used for testing if needed.
>>>
>>> Mark Waite
>>>
>>> On Tue, Jun 22, 2021 at 12:44 PM Oleg Nenashev  
>>> wrote:
>>>
>>>> Thanks to Justin Harringa, Mark Waite and Coleen Waite for testing the 
>>>> EasyCLA process on the 
>>>> https://github.com/jenkinsci-infra-ircbot-test/test-easycla  
>>>> repository.
>>>> We have reported a few minor issues discovered during testing, but 
>>>> overall the process works pretty well.
>>>>
>>>> I suggest going ahead and enabling individual CLAs for a number of 
>>>> repositories within jenkinsci. I suggest taking peripheral repos, because 
>>>> we need to figure out company CLAs and have all key maintainer permissions 
>>>> before enabling EasyCLA for the Jenkins core. 
>>>>
>>>> I suggest voting for enabling Easy CLA in the Jenkins core next week
>>>>
>>>> Best regards,
>>>> Oleg
>>>>
>>>>
>>>> On Tuesday, June 8, 2021 at 9:13:36 AM UTC+2 Oleg Nenashev wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Just a quick update on the pending project:
>>>>>
>>>>>- At the Governance meeting in April we agreed to proceed with 
>>>>>exploring EasyCLA
>>>>>- We submitted a request to the Linux Foundation. After several 
>>>>>iterations, we agreed to keep EasyCLA management as a part of the CDF 
>>>>>account for now. It technically allows all individuals and contributor 
>>>>>companies to sign a single CLA for all projects, and then moderate 
>>>>> where 
>>>>>they contribute by company CLA and internal guidelines
>>>>>- I have got an access yesterday so that I am able to configure 
>>>>>EasyCLA for Jenkins
>>>>>- I set up a test repository in 
>>>>>https://github.com/jenkinsci-infra-ircbot-test/test-easycla and 
>>>>>enabled EasyCLA for it. I also enabled branch protection there, and it 
>>>>>works well. Anyone welcome to try out the new process by submitting 
>>>>> pull 
>>>>>requests to the repository.
>>>>>
>>>>> I will proceed with a process JEP to document the current state. Any 
>>>>> feedback is welcome!
>>>>>
>>>>> Best regards,
>>>>> Oleg
>>>>>
>>>>>
>>>>> On Thursday, April 8, 2021 at 8:00:14 PM UTC+2 Oleg Nenashev wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Just in case, you can find some notes from the EasyCLA webinar and 
>>>>>> 

Re: Jenkins Elections 2021

[Oleg Nenashev]

Hi all,

Was yesterday the deadline for registrations? Or are they still open?

Best regards,
Oleg

On Tuesday, September 21, 2021 at 9:44:17 AM UTC+2 Olblak wrote:

> Hi Everybody, 
>
> The Jenkins project will elect two board members and five officers during 
> upcoming elections.
>
> If you've contributed to Jenkins prior to September 1, 2021, you're 
> eligible to vote. All contributions count for eligibility! If you've helped 
> others with Jenkins, tested Jenkins, documented Jenkins, reviewed the 
> changes of others, or made changes yourself, you're eligible to vote.
>
> Register to vote in the election by joining the Jenkins election voter 
> group at https://community.jenkins.io/g/election-voter
>
> Nominations are open for Jenkins board members and for Jenkins officers. 
> Submit nominations by sending a message to the Jenkins elections committee 
> through https://community.jenkins.io/g/election-committee
>
> https://www.jenkins.io/blog/2021/09/20/election-period-opened/
>
> Cheers,
>
>

-- 
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/017369d5-28a4-48c7-a7a5-9acc91dbf1dfn%40googlegroups.com.

Re: New members of jenkins.io triage team

[Oleg Nenashev]

+1 for all candidates. FTR I would recommend making ICLA a prerequisite for 
Triage team as well.
If everyone is fine, I will proceed with enabling EasyCLA for 
the https://github.com/jenkinsci/infra-cla repository so that we switch to 
a new flow instead of the PDF requirements

On Wednesday, November 3, 2021 at 8:01:17 AM UTC+1 timja...@gmail.com wrote:

> +1
>
> On Wed, 3 Nov 2021 at 06:48, 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> Sounds good to me.
>>
>> On Tue, Nov 2, 2021 at 4:04 PM Mark Waite  wrote:
>>
>>> During Docs Office Hours yesterday we discussed adding more people to 
>>> the copy editors team on Jenkins.io.  The process that has been outlined 
>>> previously 
>>> 
>>>  
>>> is that we first assign people to the triage team, then mentor them for a 
>>> time.  Once there is a pattern of contributed reviews, then the docs 
>>> officer or the contributor proposes that they be added to the copy editors 
>>> team.
>>>
>>> I propose that the following regular attendees at Docs office hours be 
>>> added to the jenkins.io triage team:
>>>
>>>- Kristin Whetstone  - Google Summer 
>>>of Code mentor, Google Season of Docs mentor, pipeline steps doc 
>>> generator 
>>>author, regular participant in Docs office hours
>>>- Dheeraj Singh Jodha  - Jenkins 
>>>weekly changelog reviewer, regular contributor to Jenkins documentation, 
>>>regular participant in Docs office hours
>>>- Meg McRoberts  - Jenkins training 
>>>author, contributor to Jenkins documentation, regular participant in 
>>> Docs 
>>>office hours
>>>
>>> During the mentoring period, they will also need to submit their 
>>> individual contributor license agreements.  Once the mentoring period is 
>>> complete and the ICLA's have been submitted, we'll propose that they be 
>>> made copy editors.
>>>
>>> Mark Waite 
>>>
>>> -- 
>>> 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/c886e34a-513a-4366-b50b-76809e88afdan%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/CAG%3D_Dut8bka4iE6SoFfVHLjmP%2B6_gK0ipzJ-bLq2ump7L-Ku1Q%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/e1476679-4c47-4d1e-88ee-cd9b62b4b745n%40googlegroups.com.

Re: Wiki restoration

[Oleg Nenashev]

Thanks Herve for building this service! It is really nice to have it taking 
the vast number of external links to Wiki.
It would be nice to update the layout so that for each page there is notice 
that Wiki is deprecated + link it to the migration guidelines.
Hopefully it will help to facilitate contributions to the Docs migration 
story


On Wednesday, November 3, 2021 at 5:01:07 PM UTC+1 hle...@cloudbees.com 
wrote:

> My bad, yes the migration is already done. Restoring "wiki-test" domains 
> right now: https://github.com/jenkins-infra/charts/pull/1627
>
> On Wednesday, November 3, 2021 at 4:51:39 PM UTC+1 ga...@gavinmogan.com 
> wrote:
>
>> Did you migrate already? Every one of the test links gives me 404 right 
>> now
>>
>> On Wed., Nov. 3, 2021, 6:50 a.m. 'Herve Le Meur' via Jenkins Developers, <
>> jenkin...@googlegroups.com> wrote:
>>
>>> Hello! Working on https://issues.jenkins.io/browse/INFRA-3092, I’ve 
>>> made an nginx image (
>>> https://github.com/jenkins-infra/docker-confluence-data) to put the 
>>> wiki content exported from Confluence back online.
>>>
>>> It serves the existing content (almost) as it was exported, and also 
>>> redirects to jenkins.io or plugins.jenkins.io
>>>
>>>- if there is existing content corresponding to the URL (ex: 
>>>https://wiki-test.jenkins-ci.org/display/infra/Adding+a+new+mirror)
>>>- if there was an existing manual redirection (ex: 
>>>
>>> https://wiki-test.jenkins-ci.org/display/JENKINS/Anchore+Container+Image+Scanner+Plugin
>>>)
>>>- if there is no content and the URL contains “plugin” > search in 
>>>plugins.jenkins.io (ex: 
>>>https://wiki-test.jenkins-ci.org/display/infra/Adding+a+new+mirror+plugin
>>>)
>>>- if there is no content and the URL doesn’t contains “plugin” > 
>>>search in jenkins.io on google (for now) (ex: 
>>>https://wiki-test.jenkins-ci.org/display/infra/Adding+a+new+mirror+stuff
>>>)
>>>
>>> It’s currently hosted at https://wiki-test.jenkins.io and 
>>> https://wiki-test.jenkins-ci.org, you’ll find a list of test links here:
>>>  
>>> https://github.com/jenkins-infra/docker-confluence-data/blob/main/test-links.txt
>>>
>>> The next step will be to serve it from its original domains 
>>> wiki.jenkins.io and wiki.jenkins-ci.org, planned for this afternoon 
>>> around 15h00 UTC.
>>>
>>> Let us know if you have an issue with this or if you have a critical use 
>>> case relying on this content.
>>>
>>> -- 
>>> 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/80ead862-a004-496d-ad69-fc04d2269dbcn%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/8d568a30-a2d8-4630-b64f-b8c2b0bde268n%40googlegroups.com.

1Password tram for Jenkins passwords?

[Oleg Nenashev]

Hi all,

1Password launched a free offering open source teams:
https://github.com/1Password/1password-teams-open-source. From what I see
we are compliant with sponsorship conditions.

We have quite a lot of passwords we use, especially in Advocacy & Outreach
(Zoom, Twitter accounts, etc.). It would be generally useful if we could
transfer these passwords to a shared storage so that we could share them
with people, track access and credential leaks.

The same might be useful for infrastructure accounts if it don't have SSO,
and for various test accounts we have.

WDYT? I thin

Best regards,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCk0iSK2yHE6GujCj361Cexwo3QhXcO6y7f6o2Okp08ww%40mail.gmail.com.

Re: Creating a testcontainer for Jenkins Update Center

[Oleg Nenashev]

W.r.t Docker Fixtures, a while ago I tried hacking a wrapper so that it 
uses testcontainers under the hood. Hit the timebox but I can look for this 
PR.
Anyway, just replacing integrations in plugins would be nice.

> Why would you need that when you can already add such a test dep yourself?

In the current form there are a few upper-bounds warning which may make 
experience for developers not that great.
Anyway, we indeed need clear benefits for including test-containers, e.g. a 
number of Jenkins implementations (e.g. SSH Agent or Update Center or maybe 
even Jenkins core for realistic tests)


On Thursday, October 21, 2021 at 6:43:04 PM UTC+2 Jesse Glick wrote:

> On Wed, Oct 20, 2021 at 10:05 AM Oleg Nenashev  
> wrote:
>
>>
>>- What would everyone say about introducing dependency on 
>>testcontainers into Jenkins Test Harness directly?
>>
>> Why would you need that when you can already add such a test dep yourself?
>
>>
>>- Should we go ahead and deprecate Docker Fixtures in favor of 
>>Testcontainers?
>>
>> It already basically is, if not formally: 
> https://github.com/jenkinsci/docker-fixtures#overview If you feel like 
> actually filing PRs to replace existing usages, go ahead. 
>

-- 
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/9e9922c6-f263-4f57-b11a-e1b448f7cf5an%40googlegroups.com.

Re: New LTS baseline selection

[Oleg Nenashev]

2.317 looks good to me. No objections w.r.t 2.318 too, but we do not know a 
full scope yet.
Personally I would be happy to get Winstone BOM into it 
(https://github.com/jenkinsci/winstone/pull/172), but I do not think it is 
a justification on its own.
This patch is just a quality of life improvement for Jenkinsfile Runner

Best regards,
Oleg

On Wednesday, October 20, 2021 at 9:24:46 PM UTC+2 Mark Waite wrote:

> The changelist in 2.317 makes it very attractive to me, including:
>
>- JENKINS-66753 - Ongoing build disappears from build history
>- JENKINS-61212 - Agent handshake fix for websockets on Java 11
>
> Anything older than 2.317 and later than 2.313 would require a backport of 
> JENKINS-66753.
>
> Mark Waite
>
> On Wed, Oct 20, 2021 at 12:31 PM Tim Jacomb  wrote:
>
>> Hi all,
>>
>> It's time to select the next LTS baseline.
>> The best candidate right now appears to be 2.317 or the upcoming 2.318
>>
>> 2.317 fixed JENKINS-66753 
>>  which was reported as a 
>> major issue across a few versions.
>>
>> Thanks
>> Tim
>>
>> -- 
>> 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-3Bifbmg5g8FXeW_ArLDHqj0BRZkLJuwcUOVBeE9%3DgHCnsYA%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/f44dba88-0682-401e-b9f8-7275de079ba2n%40googlegroups.com.

Creating a testcontainer for Jenkins Update Center

[Oleg Nenashev]

Hi all,

I am currently working on improving plugin management flows in Plugin 
Installation Manager, Custom WAR Packager and Jenkinsfile Runner. All 
repositories depend on Jenkins update centers and download sites in some 
configurations. Currently we run some integration tests against production 
update centers, and some use Mocked versions. Both these options are not 
ideal, because they either rely on external environment or use a simplified 
model.

I would like to introduce new integration tests that provision the Jenkins 
Update Center in a container for a test, with necessary caching between 
tests to improve performance. https://www.testcontainers.org/ provides such 
feature, and I would like to use this library instead of our in-house Docker 
Fixtures <https://github.com/jenkinsci/docker-fixtures>.

A few questions:

   - Would anyone else be interesting in creating such a TestContainer? It 
   might be useful for some integration tests in the Jenkins core and plugins, 
   e.g. multi-site-update-center plugin
   - Would we be fine w.r.t building a Dockerized version of the Update 
   Center as a part of the https://github.com/jenkins-infra/update-center2 
   deployment flow? It would allow to ship update center images for each 
   release/deployment, and it could help users who want to deploy local update 
   centers but do not want to maintain everything on their own
  - If not, I would like to ask for a permission to create a new 
  repository within jenkinsci
   
And a few more strategic questions:

   - What would everyone say about introducing dependency on testcontainers 
   into Jenkins Test Harness directly? It is already used in multiple plugins, 
   and it seems to be a better way for new development than our Docker Fixtures
   - Should we go ahead and deprecate Docker Fixtures in favor of 
   Testcontainers?

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/983f6761-4f3b-4ff0-b665-361e654fdb14n%40googlegroups.com.

GitHub Org profiles for better contributor onboarding and repo navigation

[Oleg Nenashev]

Hi all,

GitHub now supports adding profile pages to organizations, similarly to 
what was done for users a while ago (e.g. my profile: 
http://github.com/oleg-nenashev)

I have started a discussion about adding profile pages to GitHub org 
roots: 
https://community.jenkins.io/t/proposal-adding-profile-pages-to-github-orgs/578/4
 
. Would appreciate feedback from the community

*Why?* Currently https://github.com/jenkinsci looks pretty bad. We cannot 
even pin the key repositories (e.g. Jenkins core) due to whatever bug in 
GitHub that prevents us from doing so. It was raised to GitHub almost 1 
year ago, no progress so far. The page does not provide much assistance for 
those who want to contribute and land on the org page.

How? See the community.jenkins.io thread

Best regards,
Oleg

Best regards,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/308d5438-2596-438d-9520-3aeb5bfd7969n%40googlegroups.com.

Jenkinsfile Runner - project roadmap for review

[Oleg Nenashev]

Hi all,

As a follow-up to the Oct 09 Jenkins Contributor Summit, I have created a 
draft roadmap for Jenkinsfile Runner. It includes various key initiatives 
in terms of features, infrastructure, community, etc. It is implemented as 
GitHub project for now.


   - Roadmap: https://github.com/jenkinsci/jenkinsfile-runner/projects/1
   - Discussion on Discourse: 
   https://community.jenkins.io/t/jenkinsfile-runner-roadmap-discussion/583

I would appreciate feedback about the format and contents.
Best regards,
Oleg Nenashev




-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6408609e-537c-41b4-b0fc-d200010bbb86n%40googlegroups.com.

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

[Oleg Nenashev]

I am +1 too. I switched Jenkins Test Harness taking the feedback.
Will give it a bit more time for the rest of the repositories

On Monday, October 18, 2021 at 4:12:11 PM UTC+2 timja...@gmail.com wrote:

> +1 to Jesse’s list
>
> On Mon, 18 Oct 2021 at 14:33, 'Jesse Glick' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> On Sun, Oct 17, 2021 at 4:50 AM Oleg Nenashev  
>> wrote:
>>
>>> Currently we have only a few issues in Jira
>>>
>>
>> BTW if switching canonical issue tracker I recommend also closing any 
>> remaining open issues in Jira and refiling them in GitHub (with links in 
>> either direction for reference). 
>>
>> -- 
>>
> 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/CANfRfr3YMJjyc7RfC4cWV-zUX13yKQhZ0O75h8mK_qDSerTTQw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3YMJjyc7RfC4cWV-zUX13yKQhZ0O75h8mK_qDSerTTQw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/2f2a02d8-2b3b-4b0e-9379-55413aa8da39n%40googlegroups.com.

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

[Oleg Nenashev]

I would actually expand that to all developer tools we have in the project
They are isolated from distributions, and hence it does not make much sense 
to keep them in the integrated Jira

On Sunday, October 17, 2021 at 12:05:17 PM UTC+2 timja...@gmail.com wrote:

> +1
>
> On Sun, 17 Oct 2021 at 09:50, Oleg Nenashev  wrote:
>
>> Hi all,
>>
>> I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. 
>> This is a test framework, and it is not exposed to the user ecosystem. 
>> Using GitHub issues would be ore convenient for use-cases, and particularly 
>> for onboarding new contributors. What do you think?
>>
>> Currently we have only a few issues in Jira: 
>> https://issues.jenkins.io/browse/JENKINS-66236?jql=component%20%3D%20jenkins-test-harness%20and%20status%20not%20in%20(Closed%2C%20Resolved)
>>
>> Best regards,
>> Oleg
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/2c71f107-a566-40ab-bd7d-88e6d7207472n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/2c71f107-a566-40ab-bd7d-88e6d7207472n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/04557b5a-ccec-4410-9324-97b0d27058bbn%40googlegroups.com.

Re: 2.303.3 release lead

[Oleg Nenashev]

It would be nice to have https://issues.jenkins.io/browse/JENKINS-61212 
integrated since we package Java 11 by default in Docker
https://issues.jenkins.io/browse/JENKINS-66613 is IMHO reasonable too.

I have no access to Jira but I will try to scrub the recent reports

FWIW, it seems we are missing a few weekly release steps with the current 
process - resolving Jira issues and marking defects for backporting if 
seems reasonable

BR, Oleg


On Sunday, October 17, 2021 at 3:41:38 PM UTC+2 timja...@gmail.com wrote:

> Shall we cancel the release then if there's nothing to add?
>
> On Thu, 14 Oct 2021 at 11:37, Raihaan Shouhell  
> wrote:
>
>> Our lts-candidate filter seems to be without issues.
>>
>> https://issues.jenkins-ci.org/issues/?filter=12146
>>
>> Our regression fix PRs is also dry of new issues 
>> https://github.com/jenkinsci/jenkins/pulls?q=is%3Apr+label%3Aregression-fix+is%3Aclosed
>>
>> Does anyone have any candidates for backport?
>>
>> Cheers,
>> Raihaan
>>
>> On Thu, Oct 14, 2021 at 4:07 PM Oleg Nenashev  
>> wrote:
>>
>>> Thank you!
>>>
>>> On Wednesday, October 13, 2021 at 2:41:44 PM UTC+2 timja...@gmail.com 
>>> wrote:
>>>
>>>> Thanks!
>>>>
>>>> (libera IRC, not freenode, copied from an old email -.-)
>>>>
>>>> On Wed, 13 Oct 2021 at 13:32, Raihaan Shouhell  
>>>> wrote:
>>>>
>>>>> Sure I'll take it
>>>>>
>>>>> Cheers,
>>>>> Raihaan
>>>>>
>>>>> On Wed, Oct 13, 2021, 8:22 PM Tim Jacomb  wrote:
>>>>>
>>>>>> Hello
>>>>>>
>>>>>> Is anyone interested in being the release lead for 2.303.3?
>>>>>>
>>>>>> Planned dates can be seen on the event calendar: 
>>>>>> https://www.jenkins.io/events/#event-calendar
>>>>>> Release candidate by 20th October
>>>>>> Release on 3rd November
>>>>>>
>>>>>> The documentation is at:
>>>>>> https://github.com/jenkins-infra/release
>>>>>> /blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
>>>>>>
>>>>>> I'll be available to answer any questions and provide guidance (along 
>>>>>> with hopefully other past release leads)
>>>>>>
>>>>>> We chat in #jenkins-release on freenode IRC, 
>>>>>> https://www.jenkins.io/chat/#jenkins-release
>>>>>>
>>>>>> Anyone interested?
>>>>>>
>>>>>> Thanks
>>>>>> Tim
>>>>>>
>>>>>> -- 
>>>>>> 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-3BidLkUsXcz%3DnE%2BK1useR3r63imzJ0gLtdTX%2BS%2BTRYa64mA%40mail.gmail.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidLkUsXcz%3DnE%2BK1useR3r63imzJ0gLtdTX%2BS%2BTRYa64mA%40mail.gmail.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>>
>>>>> -- 
>>>>> 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/CAFoxvgwJE8rR2VvWPqvFFrRiM_AUOhEpX-Nq3233LagzBSovuw%40mail.gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgwJE8rR2VvWPqvFFrRiM_AUOhEpX-Nq3233LagzBSovuw%40mail.gmail.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> -- 
>>> 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/aedaa5af-d3ac-4e4b-8fa4-18a74f2b0279n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/aedaa5af-d3ac-4e4b-8fa4-18a74f2b0279n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> -- 
>> 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/CAFoxvgwyrDJ4aR1m%3Dh%2BXbMrFK1fwjVrRm0qj26GS1ZxDpN%3DOjw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgwyrDJ4aR1m%3Dh%2BXbMrFK1fwjVrRm0qj26GS1ZxDpN%3DOjw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/43b11f02-d98b-46b6-a09f-15e85d3d979an%40googlegroups.com.

Re: Request to adopt schedule-build-plugin

[Oleg Nenashev]

The request has been merged by now

On Saturday, October 9, 2021 at 5:26:13 PM UTC+2 Mark Waite wrote:

> I hosted a workshop at DevOps World on contributing to open source.  That 
> workshop focused on a series of small steps to improve a plugin while 
> preparing to adopt the plugin.  The schedule build plugin was the example 
> we used.
>
> I'd like to adopt the schedule-build-plugin so that I can use it in 
> further demonstrations of the techniques to adopt a plugin.
>
> I hope to also create a series of pages for www.jenkins.io that highlight 
> the small steps described in the workshop outline 
> 
> .
>
> I've submitted pull request 2125 
>  
> requesting permissions.
>
> Mark Waite
>

-- 
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/83ca909e-f3bc-4ad1-b7ec-2f57aaa293a2n%40googlegroups.com.

Re: Plugin Maintainer alumni metadata

[Oleg Nenashev]

GitHub contributor metadata does not list former maintainers specifically, 
unless you want to query audit log
Listing all contributors is possible through that and it would be cool 
indeed, but it is not a specific use-case for maintainer alumni

On Sunday, October 17, 2021 at 10:46:48 AM UTC+2 Daniel Beck wrote:

>
>
> > On 17. Oct 2021, at 10:15, Oleg Nenashev  wrote:
> > 
> > Just to follow-up on 
> https://groups.google.com/g/jenkinsci-dev/c/e3T6QG24YVg , I propose 
> adding a new "Alumni" category to 
> https://github.com/jenkins-infra/repository-permissions-updater to 
> reference ex maintainers of the plugins.
> > 
> > Such a category could serve two purposes:
> > • Giving credit on plugins.jenkins.io while not keeping permissions for 
> older maintainers
> > • Simplifying the return process if an old maintainer re-applies for 
> plugin ownership
> > What do you think?
> > 
>
> Seems like unnecessary clutter.
>
> The former can be accomplished much more nicely by integrating with 
> GitHub's contributor information.
>
> The latter is just noise, if you've been a maintainer before and actually 
> did something, it'll be easy enough to show that.
>
> This only makes sense if the idea is that there are two classes of former 
> maintainers, those that are eligible to be credited and return, and those 
> that are not?
>
>

-- 
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/775d379a-bc88-4cbc-997c-e5bfd5ab526fn%40googlegroups.com.

Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

[Oleg Nenashev]

Hi all,

I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. 
This is a test framework, and it is not exposed to the user ecosystem. 
Using GitHub issues would be ore convenient for use-cases, and particularly 
for onboarding new contributors. What do you think?

Currently we have only a few issues in 
Jira: 
https://issues.jenkins.io/browse/JENKINS-66236?jql=component%20%3D%20jenkins-test-harness%20and%20status%20not%20in%20(Closed%2C%20Resolved)

Best regards,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2c71f107-a566-40ab-bd7d-88e6d7207472n%40googlegroups.com.

Plugin Maintainer alumni metadata

[Oleg Nenashev]

Hi all,

Just to follow-up 
on https://groups.google.com/g/jenkinsci-dev/c/e3T6QG24YVg , I propose 
adding a new "Alumni" category 
to https://github.com/jenkins-infra/repository-permissions-updater to 
reference ex maintainers of the plugins.

Such a category could serve two purposes:

   - Giving credit on plugins.jenkins.io while not keeping permissions for 
   older maintainers
   - Simplifying the return process if an old maintainer re-applies for 
   plugin ownership

What do you think?

Best regards,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f153ff98-45ec-4e4e-9d71-5aaba453896bn%40googlegroups.com.

Re: Release team members

[Oleg Nenashev]

Hi,

Better late than never, I would like to join the group indeed. I have not 
been contributing a lot in the past few months, but I plan to start 
spending more time once my personal and work stuff settle. My main priority 
will remain contributing to the weekly release line and triaging 
regressions there.

Best regards,
Oleg

On Thursday, October 7, 2021 at 10:31:14 AM UTC+2 bmu...@cloudbees.com 
wrote:

> Thank you!
>
> Yes please add me!
>
> On Monday, September 27, 2021 at 12:14:01 PM UTC+2 raihaan...@gmail.com 
> wrote:
>
>> +1 I'd be happy to help where I can
>>
>> On Monday, 27 September 2021 at 17:16:55 UTC+8 timja...@gmail.com wrote:
>>
>>> Thanks all.
>>>
>>> I've added it to the people who have replied so far:
>>>
>>> [image: image.png]
>>>
>>> Cheers
>>> Tim
>>>
>>> On Mon, 27 Sept 2021 at 07:52, 'wfoll...@cloudbees.com' via Jenkins 
>>> Developers  wrote:
>>>
 Good initiative Tim, thank you :) 

 (yes you can add me ^^)

 Wadeck

 On Friday, September 24, 2021 at 9:52:30 AM UTC+2 Ildefonso Montero 
 wrote:

> No issues from my side :-) Thanks for driving this Tim!
>
> On Thu, Sep 23, 2021 at 9:29 PM Mark Waite  
> wrote:
>
>> I would like to be a member of that group.
>>
>> On Wed, Sep 22, 2021 at 11:49 PM Tim Jacomb  
>> wrote:
>>
>>> Hello
>>>
>>> Continuing from 
>>> https://groups.google.com/g/jenkinsci-dev/c/YhXRKybGgMg/m/IRjH_VykCwAJ
>>>  
>>>
>>> I would like to invite the previous release leads to join the 
>>> release team officially in jenkinsci/jenkins-infra GitHub organisations:
>>>
>>>
>>>- 
>>>
>>>Beatriz Muñoz (@bmunozm)
>>>- 
>>>
>>>Ildefonso Montero (@imonteroperez)
>>>- 
>>>
>>>Mark Waite (@MarkEWaite)
>>>- 
>>>
>>>Raihaan Shouhell (@res0nance)
>>>- 
>>>
>>>Basil Crow (@basil)
>>>
>>>
>>> Daniel, Olivier (olblak), Wadeck, Oleg you are all in the team in 
>>> jenkins-infra, would you like to join the team in jenkinsci as well?
>>>
>>> If you would like to join then please reply to this email.
>>>
>>> For others if you would like to get involved in a release then 
>>> consider stepping up for a release lead role for an LTS release or 
>>> joining 
>>> the #jenkins-release room on Libera IRC
>>>
>>> Thanks
>>> Tim
>>>
>>> -- 
>>> 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-3BieVaZAEP3wJBVzpKe1g5YvjEBcRag49vSJ-Fy8Q2%3DDQCw%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/CAO49JtFtg4-tYwuqB%3DqnA0tvR4MDiL2j%3D_QhaFHtnC8%3DrCmHPQ%40mail.gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
>
> Ildefonso Montero Pérez
> Senior Software Engineer
>
> CloudBees, Inc
>
>
>
> E: imon...@cloudbees.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/2bda6d62-3252-4bb7-97fc-29980ed32465n%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/5d4ad569-b4ec-4413-b29e-7ca0467e6864n%40googlegroups.com.

Re: 2.303.3 release lead

[Oleg Nenashev]

Thank you!

On Wednesday, October 13, 2021 at 2:41:44 PM UTC+2 timja...@gmail.com wrote:

> Thanks!
>
> (libera IRC, not freenode, copied from an old email -.-)
>
> On Wed, 13 Oct 2021 at 13:32, Raihaan Shouhell  
> wrote:
>
>> Sure I'll take it
>>
>> Cheers,
>> Raihaan
>>
>> On Wed, Oct 13, 2021, 8:22 PM Tim Jacomb  wrote:
>>
>>> Hello
>>>
>>> Is anyone interested in being the release lead for 2.303.3?
>>>
>>> Planned dates can be seen on the event calendar: 
>>> https://www.jenkins.io/events/#event-calendar
>>> Release candidate by 20th October
>>> Release on 3rd November
>>>
>>> The documentation is at:
>>> https://github.com/jenkins-infra/release
>>> /blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
>>>
>>> I'll be available to answer any questions and provide guidance (along 
>>> with hopefully other past release leads)
>>>
>>> We chat in #jenkins-release on freenode IRC, 
>>> https://www.jenkins.io/chat/#jenkins-release
>>>
>>> Anyone interested?
>>>
>>> Thanks
>>> Tim
>>>
>>> -- 
>>> 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-3BidLkUsXcz%3DnE%2BK1useR3r63imzJ0gLtdTX%2BS%2BTRYa64mA%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/CAFoxvgwJE8rR2VvWPqvFFrRiM_AUOhEpX-Nq3233LagzBSovuw%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/aedaa5af-d3ac-4e4b-8fa4-18a74f2b0279n%40googlegroups.com.

Re: Regressions in IntelliJ and Stapler Framework Support plugins.

[Oleg Nenashev]

Thanks for the warning Denys! 

On Thursday, October 14, 2021 at 3:20:20 AM UTC+2 Denys Digtiar wrote:

> If you have upgraded to IntelliJ 2021.2 you might have noticed that Jelly 
> files are no longer recognized as XML. This is due to regression in the 
> platform "Since 2021.2 plugin can't register extensions for existing file 
> types via FileTypeFactory : IDEA-277310"[1]. It should be fixed in 2021.3
>
> Thinking it was a new way platform works, I tried to work above regression 
> around and caused regression in the IntelliJ Maven plugin. Stapler 
> Framework Support 2.0.1 and 2.0.2 are causing the issue. I reverted my 
> "fix" in version 2.0.3. 
>
> So, please update Stapler Framework Support to 2.0.3 if you currently run 
> 2.0.1 or 2.0.2.
> If you are on IntelliJ 2021.2 and Jelly is not recognized as XML, please 
> add file type association manually as a workaround.
> Sorry for the inconvenience.
>
> 1: https://youtrack.jetbrains.com/issue/IDEA-277310
> https://github.com/jenkinsci/idea-stapler-plugin/issues/58
> https://github.com/jenkinsci/idea-stapler-plugin/issues/67
> https://github.com/jenkinsci/idea-stapler-plugin/issues/70
>

-- 
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/242f00f8-f938-4007-9a6f-2dc507417fc6n%40googlegroups.com.

Re: Add Mark Waite to Jep editors

[Oleg Nenashev]

I am +1. Actually I propose to go even further and to grant all board 
members and officers JEP editor rights. JEP editing is a relatively simple 
administrative process, decision making happens by the BDFL delegate or, 
once my suggestion is accepted, by the community. Even in the case of a 
process mistake, a pull request can be easily reverted.

Catching up on the JEP backlog at the moment



On Wednesday, October 6, 2021 at 5:39:47 PM UTC+2 Jesse Glick wrote:

> Oh yes please +1
>

-- 
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/7d827132-37af-4720-baf2-d14289053b20n%40googlegroups.com.

Jenkins Contributor Summit - Call for unconference topics on Oct 09

[Oleg Nenashev]

Dear all,

I am happy to confirm that we will have the second part of the Jenkins 
contributor summit on Oct 09, starting from UTC. The summit will include 
short project updates and breakout unconference sessions where we will 
discuss key initiatives in the project and its roadmap. Then we will have 
lightning talks and demos of the new and upcoming Jenkins features, and 
afterparty. RSVP 
here: https://www.meetup.com/Jenkins-online-meetup/events/281089570/

For the unconference part, everyone is invited to submit their topic 
proposals! The main goal is to work together on the Jenkins roadmap and 
discuss ideas of how we could make Jenkins better. Google Doc for 
suggestions: 
https://docs.google.com/document/d/1QLWXNG23ui-LvQXth3UREzOvLYgTMSZcv-El0H141a4/edit#heading=h.ekkv6qocz7b1

Best regards,
Oleg



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a28d2341-6843-4fde-8b2c-d9e6873a58f5n%40googlegroups.com.

Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team

[Oleg Nenashev]

We've got +1s from most of the active Jenkins core maintainers. I went
ahead and added Basil to the Jenkins core team.
Thanks to everyone for the votes!

On Thu, Sep 23, 2021 at 11:08 AM Raihaan Shouhell 
wrote:

> +1 he has been leading the charge on a variety of improvements
>
> On Thu, Sep 23, 2021, 4:25 PM Baptiste Mathus  wrote:
>
>> +1. IMO Basil is wa past the minimum criteria to get this status.
>>
>> Le mer. 22 sept. 2021 à 11:14, Oleg Nenashev  a
>> écrit :
>>
>>> Dear all,
>>>
>>> Basil has been a very active contributor to the Jenkins core since 2020,
>>> and he has contributed a lot to Jenkins over the past several years. He is
>>> an active community member, and he helps a lot with the technical debt
>>> cleanup and code reviews in Jenkins.
>>>
>>> It would be great to have Basil joining the Jenkins core maintainers
>>> team. I propose to officially add Basil to the Jenkins core team. IMHO the
>>> code reviewer stage can be skipped, because he has been already
>>> contributing a lot to the reviews. Opinions/votes?
>>>
>>> References:
>>>
>>>- https://github.com/basil
>>>- Jenkins core maintainers team and ladder:
>>>
>>> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#team
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/0c920f79-f7b7-4299-92d7-15a814821632n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/0c920f79-f7b7-4299-92d7-15a814821632n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> 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/CANWgJS55rBhwXNumbJL2rLRa1cc4h%2BpjLgiM00n%2BByBLsxf9fw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS55rBhwXNumbJL2rLRa1cc4h%2BpjLgiM00n%2BByBLsxf9fw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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/FpxsrxAgycA/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/CAFoxvgy%3D%3Dx0C6nibxugptU_Mm3p2zaKHNdn%3Dv6%3D7yBpwPDsSOw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgy%3D%3Dx0C6nibxugptU_Mm3p2zaKHNdn%3Dv6%3D7yBpwPDsSOw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPfivLC4f%2BFvK7N2sTzL0qkPPSNQO%3DPNPPcjBDEsms--8K0SSw%40mail.gmail.com.

Re: Jenkins Governance Meeting, Sep 8, 2021

[Oleg Nenashev]

Hello. Sorry for the just in time message. I have sent credentials to
Gavin, Ulli and Ewelina

On Wed, 22 Sep 2021, 20:55 Ullrich Hafner,  wrote:

> I also do not have the credentials.
>
> Do we have some topics to discuss? The agenda is empty. And I do not have
> topics (still holiday time for me).
>
>
> Am 22.09.2021 um 18:59 schrieb Ewelina Wilkosz :
>
> I don't have either
>
> On Wednesday, September 22, 2021 at 6:27:27 PM UTC+2 ga...@gavinmogan.com
> wrote:
>
>> I don't have zoom access no
>>
>> On Wed, Sep 22, 2021 at 9:26 AM Oleg Nenashev 
>> wrote:
>>
>>> Let's keep it as is th then to avoid chaos due to the late change. I
>>> will join as soon as possible.
>>>
>>> @Ewelina @Gavin. You have Zoom credentials, right?
>>>
>>> On Wed, 22 Sep 2021, 18:24 'Gavin Mogan' via Jenkins Developers, <
>>> jenkin...@googlegroups.com> wrote:
>>>
>>>> Normally I can do later, but today I have work meetings on either side
>>>> of it.
>>>>
>>>> On Wed, Sep 22, 2021 at 8:19 AM Ewelina Wilkosz 
>>>> wrote:
>>>>
>>>>> I can have this meeting few hours earlier or an hour later
>>>>> we're changing time in a few weeks? I can't remember which
>>>>> direction... we should consider that too though
>>>>> but the bottom line is that I can make it work any time Wednesday
>>>>> afternoon till late evening
>>>>>
>>>>> On Wednesday, September 22, 2021 at 3:30:17 PM UTC+2 Mark Waite wrote:
>>>>>
>>>>>> I am not able to attend the governance meeting this week due to
>>>>>> travel. Will be playing with my grandchildren in Alaska
>>>>>>
>>>>>> On Wed, Sep 22, 2021, 4:13 AM Oleg Nenashev 
>>>>>> wrote:
>>>>>>
>>>>>>> Yes, making it when I'll leave to would be helpful for me for the
>>>>>>> time being. Not sure about the today's meeting but it would be my 
>>>>>>> personal
>>>>>>> preference too
>>>>>>>
>>>>>>> On Wed, 22 Sep 2021, 12:05 Ullrich Hafner, 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> For me it will work if we change in from 7 UTC to 8 UTC. (Using 7
>>>>>>>> UTC or 8 UTC will work on the other days as well for me).
>>>>>>>> Earlier is not so easy for me (only possible on Thursdays).
>>>>>>>>
>>>>>>>> Am 22.09.2021 um 11:09 schrieb Oleg Nenashev :
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> Any opinions regarding changing the meeting time?
>>>>>>>> The current time is still unlikely to work for me, depends on my
>>>>>>>> son.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Oleg
>>>>>>>>
>>>>>>>> On Wednesday, September 8, 2021 at 8:36:05 PM UTC+2 Oleg Nenashev
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I will try to join if my son goes to bed timely. Sorry for
>>>>>>>>> skipping so many meetings, my schedule was a mess due to some family
>>>>>>>>> emergencies.
>>>>>>>>>
>>>>>>>>> Finally I was able to get my calendar more or less fixed. Until
>>>>>>>>> Nov 01 at least, I should be available full day on Monday and Tuesday 
>>>>>>>>> and
>>>>>>>>> until 3/4PM UTC on other days. I can also make it if the meetings 
>>>>>>>>> happen
>>>>>>>>> one hour later than now. Otherwise I may be late, because I need to 
>>>>>>>>> put my
>>>>>>>>> son to the bed.
>>>>>>>>>
>>>>>>>>> Would others be interested to reconsider the schedule and move the
>>>>>>>>> meeting? No problem if not, will proceed asynchronously for now
>>>>>>>>>
>>>>>>>>> Best regards,
>>>>>>>>> Oleg
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>

Re: Jenkins Governance Meeting, Sep 8, 2021

[Oleg Nenashev]

Let's keep it as is th then to avoid chaos due to the late change. I will
join as soon as possible.

@Ewelina @Gavin. You have Zoom credentials, right?

On Wed, 22 Sep 2021, 18:24 'Gavin Mogan' via Jenkins Developers, <
jenkinsci-dev@googlegroups.com> wrote:

> Normally I can do later, but today I have work meetings on either side of
> it.
>
> On Wed, Sep 22, 2021 at 8:19 AM Ewelina Wilkosz 
> wrote:
>
>> I can have this meeting few hours earlier or an hour later
>> we're changing time in a few weeks? I can't remember which direction...
>> we should consider that too though
>> but the bottom line is that I can make it work any time Wednesday
>> afternoon till late evening
>>
>> On Wednesday, September 22, 2021 at 3:30:17 PM UTC+2 Mark Waite wrote:
>>
>>> I am not able to attend the governance meeting this week due to travel.
>>> Will be playing with my grandchildren in Alaska
>>>
>>> On Wed, Sep 22, 2021, 4:13 AM Oleg Nenashev  wrote:
>>>
>>>> Yes, making it when I'll leave to would be helpful for me for the time
>>>> being. Not sure about the today's meeting but it would be my personal
>>>> preference too
>>>>
>>>> On Wed, 22 Sep 2021, 12:05 Ullrich Hafner, 
>>>> wrote:
>>>>
>>>>> For me it will work if we change in from 7 UTC to 8 UTC. (Using 7 UTC
>>>>> or 8 UTC will work on the other days as well for me).
>>>>> Earlier is not so easy for me (only possible on Thursdays).
>>>>>
>>>>> Am 22.09.2021 um 11:09 schrieb Oleg Nenashev :
>>>>>
>>>>> Hello,
>>>>>
>>>>> Any opinions regarding changing the meeting time?
>>>>> The current time is still unlikely to work for me, depends on my son.
>>>>>
>>>>> Best regards,
>>>>> Oleg
>>>>>
>>>>> On Wednesday, September 8, 2021 at 8:36:05 PM UTC+2 Oleg Nenashev
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I will try to join if my son goes to bed timely. Sorry for skipping
>>>>>> so many meetings, my schedule was a mess due to some family emergencies.
>>>>>>
>>>>>> Finally I was able to get my calendar more or less fixed. Until Nov
>>>>>> 01 at least, I should be available full day on Monday and Tuesday and 
>>>>>> until
>>>>>> 3/4PM UTC on other days. I can also make it if the meetings happen one 
>>>>>> hour
>>>>>> later than now. Otherwise I may be late, because I need to put my son to
>>>>>> the bed.
>>>>>>
>>>>>> Would others be interested to reconsider the schedule and move the
>>>>>> meeting? No problem if not, will proceed asynchronously for now
>>>>>>
>>>>>> Best regards,
>>>>>> Oleg
>>>>>>
>>>>>>
>>>>>> On Wednesday, September 8, 2021 at 6:40:55 PM UTC+2 Mark Waite wrote:
>>>>>>
>>>>>>> Today we will have the regular Jenkins Governance meeting.  The
>>>>>>> meeting will start at 7PM UTC, everyone is welcome to participate.
>>>>>>>
>>>>>>> See the agenda draft
>>>>>>> <https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.2psx4azbf3p1>
>>>>>>>  for
>>>>>>> details.
>>>>>>>
>>>>>>>- News - Jenkins project Confluence instance attacked, Jenkins
>>>>>>>2.310, Jenkins 2.303.2
>>>>>>>- Hosting status
>>>>>>>- Elections process proposal approval
>>>>>>>
>>>>>>> If you'd like to add a topic, please suggest it in the Google Doc
>>>>>>> <https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.apj7jmvnm2f3>
>>>>>>> .
>>>>>>>
>>>>>>> Mark Waite
>>>>>>>
>>>>>>
>>>>> --
>>>>> 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.
>>>>

Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team

[Oleg Nenashev]

To Jesse's point, I'm plus one for the cleanup. In the maintenance guide we
set an expectation people could be demoted if they didn't contribute in the
last 6 months. Currently it's not written in the documentation explicitly
but I would be happy to support such a policy

Let's discuss it in a separate thread

BR, Oleg

On Wed, 22 Sep 2021, 14:10 wfoll...@cloudbees.com, 
wrote:

> +1 as well, really involved in the community so it's just natural :-)
>
> On Wednesday, September 22, 2021 at 2:05:32 PM UTC+2 Jesse Glick wrote:
>
>> If he is interested, absolutely +1!
>>
>> By the way there are a number of people in
>> https://github.com/orgs/jenkinsci/teams/core/members who are no longer
>> active in the Jenkins community and who should likely be removed.
>>
> --
> 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/FpxsrxAgycA/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/2735a776-6bdf-485c-bdb0-96d45175ab67n%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/CAPfivLAw1vBsXVy1bsqLhRQcMyGrJ02-p7B0B3OiuoRmst6sPA%40mail.gmail.com.

Re: Jenkins Governance Meeting, Sep 8, 2021

[Oleg Nenashev]

Yes, making it when I'll leave to would be helpful for me for the time
being. Not sure about the today's meeting but it would be my personal
preference too

On Wed, 22 Sep 2021, 12:05 Ullrich Hafner,  wrote:

> For me it will work if we change in from 7 UTC to 8 UTC. (Using 7 UTC or 8
> UTC will work on the other days as well for me).
> Earlier is not so easy for me (only possible on Thursdays).
>
> Am 22.09.2021 um 11:09 schrieb Oleg Nenashev :
>
> Hello,
>
> Any opinions regarding changing the meeting time?
> The current time is still unlikely to work for me, depends on my son.
>
> Best regards,
> Oleg
>
> On Wednesday, September 8, 2021 at 8:36:05 PM UTC+2 Oleg Nenashev wrote:
>
>> Hello,
>>
>> I will try to join if my son goes to bed timely. Sorry for skipping so
>> many meetings, my schedule was a mess due to some family emergencies.
>>
>> Finally I was able to get my calendar more or less fixed. Until Nov 01 at
>> least, I should be available full day on Monday and Tuesday and until 3/4PM
>> UTC on other days. I can also make it if the meetings happen one hour later
>> than now. Otherwise I may be late, because I need to put my son to the bed.
>>
>> Would others be interested to reconsider the schedule and move the
>> meeting? No problem if not, will proceed asynchronously for now
>>
>> Best regards,
>> Oleg
>>
>>
>> On Wednesday, September 8, 2021 at 6:40:55 PM UTC+2 Mark Waite wrote:
>>
>>> Today we will have the regular Jenkins Governance meeting.  The meeting
>>> will start at 7PM UTC, everyone is welcome to participate.
>>>
>>> See the agenda draft
>>> <https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.2psx4azbf3p1>
>>>  for
>>> details.
>>>
>>>- News - Jenkins project Confluence instance attacked, Jenkins
>>>2.310, Jenkins 2.303.2
>>>- Hosting status
>>>- Elections process proposal approval
>>>
>>> If you'd like to add a topic, please suggest it in the Google Doc
>>> <https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.apj7jmvnm2f3>
>>> .
>>>
>>> Mark Waite
>>>
>>
> --
> 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/87863ab9-b8dc-4805-a5ca-1b38720543d5n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/87863ab9-b8dc-4805-a5ca-1b38720543d5n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
> --
> 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/def0hzTa-z4/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/F1586E2B-A1F9-4E87-9F6A-51E0D3925B94%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/F1586E2B-A1F9-4E87-9F6A-51E0D3925B94%40gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPfivLA2JYTmtYqjXkfDsbLjMazRcb%2BRATgfntdaSwLh%3DWv17g%40mail.gmail.com.

Proposal: Adding Basil Crow to the Jenkins Core maintainers team

[Oleg Nenashev]

Dear all,

Basil has been a very active contributor to the Jenkins core since 2020, 
and he has contributed a lot to Jenkins over the past several years. He is 
an active community member, and he helps a lot with the technical debt 
cleanup and code reviews in Jenkins.

It would be great to have Basil joining the Jenkins core maintainers team. 
I propose to officially add Basil to the Jenkins core team. IMHO the code 
reviewer stage can be skipped, because he has been already contributing a 
lot to the reviews. Opinions/votes?

References:

   - https://github.com/basil
   - Jenkins core maintainers team and 
   ladder: 
https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#team

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0c920f79-f7b7-4299-92d7-15a814821632n%40googlegroups.com.

Re: Jenkins Governance Meeting, Sep 8, 2021

[Oleg Nenashev]

Hello,

Any opinions regarding changing the meeting time?
The current time is still unlikely to work for me, depends on my son.

Best regards,
Oleg

On Wednesday, September 8, 2021 at 8:36:05 PM UTC+2 Oleg Nenashev wrote:

> Hello,
>
> I will try to join if my son goes to bed timely. Sorry for skipping so 
> many meetings, my schedule was a mess due to some family emergencies. 
>
> Finally I was able to get my calendar more or less fixed. Until Nov 01 at 
> least, I should be available full day on Monday and Tuesday and until 3/4PM 
> UTC on other days. I can also make it if the meetings happen one hour later 
> than now. Otherwise I may be late, because I need to put my son to the bed.
>
> Would others be interested to reconsider the schedule and move the 
> meeting? No problem if not, will proceed asynchronously for now
>
> Best regards,
> Oleg
>
>
> On Wednesday, September 8, 2021 at 6:40:55 PM UTC+2 Mark Waite wrote:
>
>> Today we will have the regular Jenkins Governance meeting.  The meeting 
>> will start at 7PM UTC, everyone is welcome to participate.
>>
>> See the agenda draft 
>> <https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.2psx4azbf3p1>
>>  for 
>> details.
>>
>>- News - Jenkins project Confluence instance attacked, Jenkins 2.310, 
>>Jenkins 2.303.2
>>- Hosting status
>>- Elections process proposal approval
>>
>> If you'd like to add a topic, please suggest it in the Google Doc 
>> <https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.apj7jmvnm2f3>
>> .
>>
>> Mark Waite
>>
>

-- 
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/87863ab9-b8dc-4805-a5ca-1b38720543d5n%40googlegroups.com.

Re: Release team

[Oleg Nenashev]

+1 from me. I will implement the Jenkinsci GitHub repo part it tomorrow if 
no negative feedback

On Tuesday, September 21, 2021 at 8:43:51 PM UTC+2 ullrich...@gmail.com 
wrote:

> +1
>
> Am 21.09.2021 um 11:32 schrieb Tim Jacomb :
>
> Hello
>
> I would like to propose a release team in the Jenkins GitHub org.
> The role and permissions are documented in 
> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles 
> but they don’t actually exist in the jenkinsci GitHub org.
>
> In jenkins-infra we have a release team which current has:
>
>- Mark Waite
>- Daniel Beck
>- Olivier Vernin
>- Wadeck Follonier
>- Oleg Nenashev
>- Myself
>
>
> I would like to have a release team in JenkinsCI that has write 
> permissions on jenkinsci/jenkins and jenkinsci/packaging created, with 
> myself (release officer) as the maintainer of the team.
>
> I’ll post a list proposing people separately if people are happy with this 
> idea.
>
> People gaining core access here should be using their permissions for 
> release activities, e.g. backporting, build fixes. 
>
> Ideally the jenkinsci/jenkins-infra teams should be synced as well, this 
> would grant write access to the ‘jenkins-infra/release’ repository, which 
> will be helpful for:
>
>- Any release team member will be able to update the release checklist
>- Merging of PRs updating next release version / stable line
>
>
> The people joining the team should also be either (thoughts?):
>
>1. Added to the LDAP group ‘release-core’
>2. Join the LDAP group when acting as a release lead and be removed 
>after
>
>
> Any feedback?
>
> Thanks
> Tim
>
> -- 
> 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-3Bic1AHThGLJoR%2Bb3bP1pKZHDZTDePOE1p3CAx%2B7aa_qCew%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic1AHThGLJoR%2Bb3bP1pKZHDZTDePOE1p3CAx%2B7aa_qCew%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/54eda6f0-43d7-4962-9685-32b3c01392a4n%40googlegroups.com.

Re: Jenkins Election 2021 Proposal

[Oleg Nenashev]

Hello. Sorry for the delay, I finally got some time to work on my community 
backlog.
Thanks to Olivier for stepping up and leading the election process this 
year!

On Thursday, September 2, 2021 at 10:38:13 AM UTC+2 Olblak wrote:

> Hi Everybody,
>
> As you may guess with the title, I am looking for feedback regarding the 
> upcoming election.
> I would like to validate this process by next week's Governance meeting
>
> Feel free to add your suggestion or feedback on community.jenkins.io 
> 
>
> Cheers
>

-- 
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/dd6f36c1-6c98-4d82-81eb-35d44b2556adn%40googlegroups.com.

Re: Hacktoberfest CI Load

[Oleg Nenashev]

It is a good question to discuss with the Infra Team. I have added it to 
the contributor summit logistics Google Doc, because this is the weekend 
when the load is expected to spike the 
most. 
https://docs.google.com/document/d/1QLWXNG23ui-LvQXth3UREzOvLYgTMSZcv-El0H141a4/edit#heading=h.jhodwcaw6jcl

FTR last year we did not have serious issues with CI, because we did not 
promote the event too much. In 2019 we had a massive CI outage in the 
beginning of the event, so James definitely has a point. We are interested 
to keep our CI stable to provide good contributor experience, whether they 
participate in Hacktoberfest or not



On Friday, September 10, 2021 at 7:06:55 PM UTC+2 ga...@gavinmogan.com 
wrote:

> ooh maybe use some of our digital ocean credits to expand build capacity
>
> On Fri, Sep 10, 2021 at 10:00 AM Jesse Glick  wrote:
>
>> On Fri, Sep 10, 2021 at 11:32 AM jn...@cloudbees.com  
>> wrote:
>>
>>> I at least hope to find some time to get the ATH to zero failures at 
>>> some point.
>>>
>>
>> That would be great!
>>
>> Is there a plan to increase the capacity (temporarily or not)
>>>
>>
>> or INFRA-1633  
>>
>> -- 
>> 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/CANfRfr1ZvaDVX-MyDgF2CtDD5eNSAcxeMVSr4uk_5RPgCEyt1A%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/65a1b306-0777-4ffd-8418-f1cb60edcf39n%40googlegroups.com.

Re: Is an explicit dependency on jenkins-test-harness now needed?

[Oleg Nenashev]

I'd guess it is a temporary issue caused by JCasC test dependency being 
higher than your current version of Plugin POM. JCasC test harness depends 
on JTH explicitly.

IMHO it is time to make one step forward and to include JCasC test harness 
and into Jenkins Test Harness or to Plugin POM by default. There is wide 
adoption of JCasC test automation thanks to so many contributors, and IMHO 
there is no particular point in making users to explicitly define it these 
days. Opinions?

On Tuesday, September 14, 2021 at 11:44:57 AM UTC+2 Chris Kilding wrote:

> Hi,
>
> I've seen the following dependency error in 2 plugins regarding 
> jenkins-test-harness:
>
> Require upper bound dependencies error for 
> org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 paths to 
> dependency are:
> 22:20:04 
> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33
> 22:20:04 and
> 22:20:04 
> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
> 22:20:04 +-io.jenkins.configuration-as-code:test-harness:1.52
> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 
> (managed) <-- org.jenkins-ci.main:jenkins-test-harness:1589.vc23fca066d5c
>
> Both projects use CasC, so they have been inheriting the actual 
> jenkins-test-harness dependency transitively through config-as-code test 
> harness. This was fine until BOM 937.v51fde92016ed, when the error started.
>
> Is it now necessary to include an explicit jenkins-test-harness dependency 
> in a project's POM (to fix this), and if so is this stated anywhere?
>
> Regards,
>
> Chris
>

-- 
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/033ceeaf-187a-4012-9f7a-c576d172fdfcn%40googlegroups.com.

Re: 2.303.2 release lead

[Oleg Nenashev]

+1 for Bea if she is interested and there are no other nominations.
Thanks for stepping up!

On Monday, September 6, 2021 at 10:56:42 AM UTC+2 bmu...@cloudbees.com 
wrote:

> I would like to be! :-D
>
> El 6 sept 2021, a las 9:25, Tim Jacomb  escribió:
>
> Hello
>
> Is anyone interested in being the release lead for 2.303.2?
>
> Planned dates can be seen on the event calendar: 
> https://www.jenkins.io/events/#event-calendar
> Release candidate by 8th September (apologies for short notice)
> Release on 22nd September
>
> The documentation is at:
> https://github.com/jenkins-infra/release
> /blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
>
> I'll be available to answer any questions and provide guidance (along with 
> hopefully other past release leads)
>
> We chat in #jenkins-release on freenode IRC, 
> https://www.jenkins.io/chat/#jenkins-release
>
> Anyone interested?
>
> Thanks
> Tim
>
> -- 
> 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-3Bidwce0ZN%3DmFdbOMpnismvsYYUAex0LpRSba_CU9xXs9KA%40mail.gmail.com
>  
> 
> .
>
>
> Beatriz Muñoz Manso
> Sr Software Engineer 
> CloudBees, Inc.
>
>
>

-- 
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/bfe87277-7b4e-458e-a630-5a2411548451n%40googlegroups.com.

Re: Jenkins Governance Meeting, Sep 8, 2021

[Oleg Nenashev]

Hello,

I will try to join if my son goes to bed timely. Sorry for skipping so many 
meetings, my schedule was a mess due to some family emergencies. 

Finally I was able to get my calendar more or less fixed. Until Nov 01 at 
least, I should be available full day on Monday and Tuesday and until 3/4PM 
UTC on other days. I can also make it if the meetings happen one hour later 
than now. Otherwise I may be late, because I need to put my son to the bed.

Would others be interested to reconsider the schedule and move the meeting? 
No problem if not, will proceed asynchronously for now

Best regards,
Oleg


On Wednesday, September 8, 2021 at 6:40:55 PM UTC+2 Mark Waite wrote:

> Today we will have the regular Jenkins Governance meeting.  The meeting 
> will start at 7PM UTC, everyone is welcome to participate.
>
> See the agenda draft 
> 
>  for 
> details.
>
>- News - Jenkins project Confluence instance attacked, Jenkins 2.310, 
>Jenkins 2.303.2
>- Hosting status
>- Elections process proposal approval
>
> If you'd like to add a topic, please suggest it in the Google Doc 
> 
> .
>
> Mark Waite
>

-- 
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/acc63c53-4eea-45f0-9e98-9e9f19b677f1n%40googlegroups.com.

Re: LTS backporting policy

[Oleg Nenashev]

I am +0.5, but being eligible does not immediately mean the change would be 
backported. Dependency updates may also introduce regressions. As any other 
backport, risks need to be evaluated. IMHO it should be up for backporting 
requesters to prove the safety of changes and to ensure there is enough 
soak testing and test coverage. Same for any other non-critical backport

On Tuesday, August 31, 2021 at 8:16:08 PM UTC+2 boa...@gmail.com wrote:

> Are there specific libraries we can list for safe upgrades? Like XStream, 
> Jackson, Commons, etc, for common upgrades. I wouldn’t be super comfortable 
> with a blanket policy, but for all our more stable ones, I think it’s a 
> good idea.
>
> Matt Sicker
>
> On Aug 31, 2021, at 09:01, wfoll...@cloudbees.com  
> wrote:
>
> Totally agree. Especially when the update is not a major bump of 3 
> versions. Most of the time it's just a minor/bug version bump.
>
> That will greatly help on the security scanners area, where the "fear" 
> dominates the market :-)
>
> Thanks James for the suggestion, great idea.
>
> Wadeck
>
> On Tuesday, August 31, 2021 at 3:58:38 PM UTC+2 jn...@cloudbees.com wrote:
>
>> Hi all,
>>
>> I would like to propose that we add to the list of eligible criteria for 
>> backporting the following
>>
>> * is a dependency update with a known security issue
>>
>> The reason for this if we have a dependency with a security issue that is 
>> exploitable from Jenkins we already do include that as a LTS issue via the 
>> current SECURITY process, however if the issue is *not* exploitable then 
>> we do not. (for example the recent XStream issues have not impacts Jenkins 
>> as we already use an allow list).
>>
>> However as supply chain issues are becoming more prominent to our users, 
>> they are scanning software with automated tools that look at the 
>> dependencies, and these scanners do not understand how a library is used 
>> or  configured, and has the potential to:
>>
>> * make the software look insecure (thus be a barrier to adoption) 
>> or 
>> * cause extra nose asking about CVE-2021-123456
>>
>> WDYT?
>>
>> /James
>>
> -- 
> 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/6d65b90e-1e31-475c-b3f6-9920bb4ee33en%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/9f2fceb7-68eb-470a-8cdd-93367d65680en%40googlegroups.com.

Hacktoberfest 2021

[Oleg Nenashev]

Dear all,

In one month we will have the new edition of Hacktoberfest. As usual, it 
would be great if we could participate and attract contributions to the 
Jenkins community. I am starting this thread so that we could collaborate 
and prepare the content. More about Hacktoberfest in Jenkins: 
https://www.jenkins.io/events/hacktoberfest/

What are we looking for:

   - Maintainers who would like to highlight their SIGs/plugins/projectsin 
   Hacktoberfest
  - You can create newcomer friendly issues for your components and 
  also mark them with the 'hacktoberfest' label/topic
  - You can add your project or component to the Featured Projects 
  <https://www.jenkins.io/events/hacktoberfest/#featured-projects> list 
  via a pull request
  - You can present at outr online meetup or write a blogpost. Any 
  "Contributing to [ANYTHING about Jenkins]" is welcome!
  - Organizers for online and, where safe enough, local events. 
   - Speakers for the Jenkins online meetup who want to talk about 
   developer tools and/or developing with Jenkins

Any additional ideas and suggestions are welcome!

Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/845df23e-81eb-4446-8003-958d03171526n%40googlegroups.com.

Re: Community.jenkins.io

[Oleg Nenashev]

Thanks for the reminder, Gavin! 
Indeed we should promote this channel as much as possible so that it 
becomes adopted by Jenkins developers and users.

May I suggest a few possible promotion options we could implement?

   - A jumbotron on jenkins.io
   - Announcement blogpost
   - Referencing community.jenkins.io in default GitHub issue templates as 
   the source for Q We could also add an entry for "new issue" screens
   - Updating the default SUPPORT.md for Jenkins components. 
   https://github.com/jenkinsci/.github/blob/master/SUPPORT.md
   - A short introductory video on Jenkins YouTube we could promote in 
   social media
   
As always, more contributors are welcome!

Best regards,
Oleg
On Friday, August 27, 2021 at 6:30:53 AM UTC+2 ga...@gavinmogan.com wrote:

> Hey Everyone, It's Gavin again, and I'm here to let you know about 
> https://community.jenkins.io again.
>
> First off, if you don't feel comfortable using it for any reason, please 
> reach out to me any way you can (halkeye on most platforms). Any 
> information on how we can improve is appreciated. 
>
> I'm still a huge fan of discourse. I find it works great in other 
> projects, and have all the communication in one place. Honestly I think it 
> could even replace a lot of the real time, but that's a discussion for 
> another time.
>
> How can you help out?
> * Sign up for a new account
> * Post an introduction on the intro topic - 
> https://community.jenkins.io/t/introductions-topic/158
> * Post questions you have in the "Ask a question" Category - 
> https://community.jenkins.io/c/using-jenkins/support/8
> * Got a cool script? ui? dashboard? book? blog post? Post it to the 
> showing off category - 
> https://community.jenkins.io/c/using-jenkins/showing-off/9
> * Show some love to the amazing work timja has done on implementing a non 
> blueocean view of the pipeline tool - 
> https://community.jenkins.io/t/blue-ocean-but-in-classic-ui/96/18
> * Champions. Would love your help to promote the new community site. I 
> know how to market and social media, but I'm not very good at it.
>
> There's plenty more. If you're unsure, just post to the top level category 
> (or DM me) and one of us will help sort it, or even if need be, make some 
> new categories.
>
> If you missed the last blast where I described a bunch of the features I'm 
> excited about checkout out - 
> https://community.jenkins.io/t/draft-discourse-annoucement-to-mailing-lists/74
>
> Gavin 

-- 
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/c31ee05b-89d5-4c9f-b989-efa5b5497f54n%40googlegroups.com.

Re: Docker LTS image: issue with locale, should we rebuild?

[Oleg Nenashev]

I would rather recommend 2.303.2. Docker images are so popular at the 
moment, I see no reason in separating their versioning from the Jenkins LTS 
releases.
On Monday, August 30, 2021 at 2:26:38 PM UTC+2 ma...@torstenwalter.de wrote:

> Would be great if you could announce once it's done. So that people who 
> build images based on it have the chance of triggering a re-build.
> People who use it in Kubernetes might have a problem with the updated 
> images in case they use image pull policy IfNotPresent.
>
>
> Am Mo., 30. Aug. 2021 um 14:09 Uhr schrieb Mark Waite <
> mark.ea...@gmail.com>:
>
>> No issue or objection from me to have the 2.303.1 Debian images updated.
>>
>> On Mon, Aug 30, 2021 at 2:34 AM Damien Duportal  
>> wrote:
>>
>>>
>>> Hello dear developers and maintainers,
>>>
>>> We (the Jenkins Infra team) were recently bitten by a change in the 
>>> latest Docker image for Jenkins controller, in its LTS 2.303.1 (released 
>>> last week).
>>>
>>> The issue is related to a change of locale from "C.UTF-8" to "POSIX" 
>>> when using Debian image (as an upstream change from Debian bullseye).
>>>
>>> A fix has already been made by a user in 
>>> https://github.com/jenkinsci/docker/pull/1194 and is already merge in 
>>> GitHub.
>>>
>>> We (the Jenkins Infra team) would like to rebuild the Docker image for 
>>> the LTS 2.303.1 to avoid our users to be annoyed by this issue.
>>> - It should not imply any tagging version change (as the Docker image 
>>> tags are only about the Core version of Jenkins used, not about the other 
>>> dependencies on the image)
>>> - It should only impact the Debian images (amd64 and arm64)
>>> - It should not impact the weekly (next weekly will have the fix of 
>>> course)
>>> - It should make the image being advertised as updated a few days after 
>>> the official LTS release
>>>
>>> - Is there any issue or counter voice to this change?
>>> - Is there any question or element unclear?
>>>
>>> For the Jenkins infra team
>>>
>>> Damien DUPORTAL
>>>
>>>
>>> -- 
>>> 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/0e3ad65e-9bd7-4074-9fc6-e35328f837dcn%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/CAO49JtFUzjbbxT5jbcFxGW3D52ViNJ3LOwNzeNKFhQOGbEEQnQ%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/e46c0a8e-e075-4db9-9974-1c5cf5e07b4en%40googlegroups.com.

Re: https://plugins.jenkins.io/custom-tools-plugin/ adoption

[Oleg Nenashev]

Hi Roberto,

Thanks again for stepping up as a maintainer. It is much appreciated. This 
plugin is essential for many large scale instances, and it has its uses 
even in the container CI/CD environments. Unfortunately I did not have 
enough time to properly maintain and evolve this plugin :(

I am currently taking a break from the Jenkins community due to personal 
community unrelated reasons, but I plan to be back in August or so. If you 
have some time and interest, I would be happy to share my vision for this 
plugin and to help with onboarding. I could do it in this thread, or we 
could start a community.jenkins.io discussion. Later we could also have a 
dedicated Jenkins developer meeting. What do you think?

Just key items from my mental backlog:

   - Removing dependency on Extended Choice plugin, restoring the tool 
   versioning engine
   - Better Pipeline compatibility 
   (https://issues.jenkins.io/browse/JENKINS-30680)
   - Better JCasC integrations, including support for templating and 
   advanced configuration export
   - Introducing a "Container Image Selector" capability for tools packaged 
   as Docker images. It would allow using the plugin in Docker and K8s 
   environments more easily, and the engine would be more or less similar
   - Introducing traceability of tool usages using Jenkins fingerprints 
   engine and UI
   - Unraveling the tool/environment management logic and making it more 
   simple. Or at least documenting the behavior
   - Moving issues to GitHub issues and doing issue scrub in Jira

Best regards,
Oleg Nenashev


On Sunday, July 11, 2021 at 3:34:36 AM UTC+2 roberto...@gmail.com wrote:

> Thank you Ulrich, 
>
> I've already filed a pull request: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/2018. 
> The two validations for de PR passed, but the PR hasn't been merged, so I 
> was wondering who should do with that? 
>
> Also I was wondering how or who would give me access to the github repo 
> for the plug-in? 
>
> Thanks for al the help!
>
>
>
> On Thursday, July 8, 2021 at 12:27:38 PM UTC-6 ullrich...@gmail.com wrote:
>
>> Hi Roberto,
>>
>> Thanks for helping to keep the custom-tools-plugin alive! 
>>
>> Since this plugin is already up for adoption we can directly proceed with 
>> the next steps:
>> Please read 
>> https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ and 
>> then file a pull request 
>> for https://github.com/jenkins-infra/repository-permissions-updater.
>>
>> Ulli
>>
>> Am 07.07.2021 um 06:30 schrieb Roberto Hernandez :
>>
>>  
>> Hi, 
>>  
>> I would like to become a maintainer of the following plugin: 
>>  
>> URL: https://plugins.jenkins.io/custom-tools-plugin/
>> Github username: https://github.com/robertohern83 
>> Jenkins infrastructure account id: rhernandezm
>>  
>> I have some ideas to improve it, but I don’t have yet a PR, I wanted to 
>> understand a little bit more about the process to send changes first.
>>
>>  
>> _
>> Mag. Roberto Hernández Montoya
>>  
>>
>> 
>>
>> -- 
>> 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/CH0PR03MB6116D2E66EAD06EA6DAC3DB6A21A9%40CH0PR03MB6116.namprd03.prod.outlook.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CH0PR03MB6116D2E66EAD06EA6DAC3DB6A21A9%40CH0PR03MB6116.namprd03.prod.outlook.com?utm_medium=email_source=footer>
>> .
>>
>>
>>

-- 
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/2a3bfb84-f2ca-4dd1-8aca-1ff779979847n%40googlegroups.com.

Re: Join docker packaging team

[Oleg Nenashev]

+1

On Friday, July 2, 2021 at 2:50:20 PM UTC+2 Mark Waite wrote:

> +1 from me to make Tim one of the maintainers of the Docker images.
>
> On Fri, Jul 2, 2021 at 6:46 AM Tim Jacomb  wrote:
>
>> Hello
>>
>> I'm doing some work on multi arch builds for the controller docker image.
>> (see https://github.com/jenkinsci/docker/pull/1137)
>>
>> Also working on speeding up the build to go with this.
>>
>> In order to make some of these changes I'll need to make changes to the 
>> Jenkinsfile.
>>
>> I would like to request commit access to help with this.
>>
>> I don't want to commit to any long term maintenance but I _may_ help out 
>> where I can.
>>
>> Thanks
>> Tim
>>
>> -- 
>> 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-3Bie36o%3D1-dT5p2Livz5Wmr6CeWQh0-oDNOK9JAb4emckUQ%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/cf765322-5dcd-45f3-89d6-a2d832c9b09fn%40googlegroups.com.

Re: Jenkins Governance

[Oleg Nenashev]

Hello,

I tried to join 10 minutes after the meeting was supposed to start, and 
there was the "waiting for the host" message.

BR, Oleg

On Wednesday, June 30, 2021 at 8:54:15 PM UTC+2 Mark Waite wrote:

> Sorry for the poor subject line.
>
> It should have been
>
> *Jenkins Governance Meeting June 30, 2021*
>
> On Wed, Jun 30, 2021 at 12:06 PM Mark Waite  wrote:
>
>> Today we will have the regular Jenkins Governance meeting. The meeting 
>> will start at 7PM UTC, everyone is welcome to participate! 
>>
>> Current topics include:
>>
>>- News - Jenkins 2.289.2 security release, Contributor Summit
>>- Jenkins funding - status report
>>- Plugin End-of-Life Policy
>>- Discourse evaluation status report
>>
>> If you'd like to add a topic, please suggest it in the Google Doc 
>> 
>> .
>>
>> Mark Waite
>>
>> -- 
>> 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/fb7e2be0-a5d1-49ab-9003-58b89755122en%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/3a6e6cf5-d1ec-4865-b5b1-a726ac0e8166n%40googlegroups.com.

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

[Oleg Nenashev]

Hi all,

Looking forward to see the discussion from the contributor summit 
summarized here. Sadly I missed it due to having another session, but I've 
heard it was a great discussion that resulted in a proposal. Thanks to Mike 
Cirioli and Mark Waite for driving this topic at the summit, and thanks to 
all contributors. Just posting the links shared by Mike and Runxia in the 
Google Doc:


   - Slides: 
   
https://docs.google.com/presentation/d/1i1gkUQ0Ha-CRgFvRRpRWUDjbpPr383D0DSywLGAFN-Y/edit?usp=sharing
   - Meeting notes: 
   
https://docs.google.com/document/d/1BwllcgX3rmsvwRKIFkmE24g7zHGo8kufcimL0BnWaWE/edit?usp=sharing

I might be unavailable when the decision making happens, so I would like to 
cast my votes in advance. Note that I have not fully went through the 
notes, and might be misaligned. I am happy to support whatever decision 
made by the community. My votes are:

   - +1 for making Java 11 a default in all Jenkins distributions starting 
   from September LTS. It applies to Jenkins controller and agent Docker 
   images. It also applies to Helm chart, Jenkins Operator and whatever other 
   packaging that happens to include Java. Jenkinsfile Runner already ships 
   Java 11 by default FTR.
   - +1 for allowing Java 11 only plugins starting from the September LTS. 
   We have tooling embedded into the Jenkins core and Jenkins update centers 
   starting from LTS releases in 2018 (2.164.x IIRC), so all modern Jenkins 
   versions will be able to properly notify users in the UI Plugin 
   manager. https://github.com/jenkinsci/plugin-pom/pull/133 should be 
   finalized to make it possible in the tooling
   - Dropping Java 8 support
  - -1 for dropping Java 8 support in the September LTS
  - +0.5 for officially announcing it as deprecated. Needs more 
  planning and definition what deprecation actually means
  - +1 for declaring an intent to drop support for Java 8 in the coming 
  years
   - Java 17 support:
  - +1 for any coordinated efforts on this front, and thanks to all 
  contributors. I will be exploring Java 17 in the coming months, but I 
might 
  be unable to contribute.
  - +1 for library updates and non-severe breaking changes if they are 
  needed to support Java 17
   
Best regards,
Oleg




On Friday, June 25, 2021 at 12:36:16 AM UTC+2 m...@basilcrow.com wrote:

> Allow me to append myself to the list of developers who would like access 
> to Java 11 APIs. If we had access to Java 11 APIs, then this 
> 
>  
> (and similar code in a CloudBees-proprietary plugin) could be switched to 
> the Java Platform's ProcessHandle#pid() (to say nothing of ProcessTree in 
> Jenkins core), which would mean that we could get rid of JNR from Jenkins 
> core, which would mean that we could get rid of ASM from Jenkins core, 
> which would eliminate a long-standing pain point in the dependency tree.
>

-- 
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/92ae7850-fc4c-4426-8206-9a829bd697bcn%40googlegroups.com.

Re: Sign-up for 'beta projects' in GitHub issues

[Oleg Nenashev]

+1 from me and thanks to Tim for starting this thread! I did a little 
Twitter intervention to highlight the fact that some of the Jenkins 
contributors have difficulties with accessing beta features on GitHub. I 
hope that it will help to gain access and to evaluate the features. With 
GitHub Issues becoming more and more popular in Jenkins, I think it is 
important to try the new stuff there early so that we can see how to make 
lives of maintainers, user and contributors easier.

On Thursday, June 24, 2021 at 12:24:41 AM UTC+2 Mark Waite wrote:

> Thanks!  Yes, I would like to try it on 
> https://github.com/jenkins-infra/jenkins.io .
>
> On Wed, Jun 23, 2021 at 2:26 PM 'Olblak' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> I added jenkins-infra to the waiting list 
>>
>> On Wed, Jun 23, 2021, at 10:03 PM, Tim Jacomb wrote:
>>
>> Mark mentioned on Twitter he’s like to try it on Jenkins.io too 
>> https://twitter.com/markewaite/status/1407780053769850882?s=21
>>
>> On Wed, 23 Jun 2021 at 20:04, Tim Jacomb  wrote:
>>
>> Hello,
>>
>> Should we sign-up for the new beta projects in jenkinsci?
>>
>> https://github.com/features/issues
>>
>> Would be useful to be able to set-up more featureful boards across 
>> plugins, probably other use-cases too.
>>
>> Thanks
>> Tim
>>
>>
>> -- 
>> 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-3Bid10mD4XwChU-Yf-iL%3DMsTVkCCY_cYMga4-yi2szCykuQ%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/7fb8aa14-9b28-4b49-97a5-0fdb71a4c573%40www.fastmail.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/2b789129-4721-4a5a-8377-18cb44f9fb1dn%40googlegroups.com.

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

[Oleg Nenashev]

Thanks to Angelique for the summary and for creating a JEP based on the 
previous discussions and Google Docs. JEP-16 - Inclusive terminology 
guidelines and continuous updates 
<https://github.com/jenkinsci/jep/tree/master/jep/16> has been accepted as 
a draft, and we can keep evolving it. Any feedback will be welcome!

The Inclusive naming initiative is now also listed on the Advocacy 
page: https://www.jenkins.io/sigs/advocacy-and-outreach/#inclusive-naming

Best regards,
Oleg 

On Wednesday, June 23, 2021 at 8:40:48 AM UTC+2 aj...@cloudbees.com wrote:

> Hello all :)
>
> As a developer at CloudBees I am part of a team that is trying to 
> participate in the terminology change effort and we had the same concern 
> about the limits of changes (UI, logs, console, local variable, package 
> name ??). So I can share our way of working so far =>
>
> What we do first, is change only UI text and log/console text because it's 
> fast with an immediate very visible change for end users and with very few 
> backward compatibility issues (mainly test assertions to update).
>
> We also changed the text in the comments, since the more terms are 
> changed, the easier it is to see if there are some places with remaining 
> deprecated words (so github search is faster). 
>
> I personally think that the ultimate goal would be to have the deprecated 
> words removed everywhere including in code BUT this is complex to not break 
> any backward compatibility.
>
> I believe that anyone is free to go further, by being careful on backward 
> compatibility because any piece of code can be user visible at some point, 
> it can be a package name used on System property, a local field 
> automatically exposed by Jenkins configuration as Code and or some future 
> feature.
>
> For code change we are looking one by one and see if it’s possible to have 
> a backward compatible way, mainly by keeping along the old terminology and 
> the new one. For example for Jenkins cli or Configuration as Code it’s 
> quite easy to keep the deprecated terminology working as previously and 
> just mark it as deprecated and in the same time adding the same code 
> execution with the new naming convention. And remove the deprecated 
> terminology, later, one day…. If I come up with ways that works fine (for 
> cli or config as code or) I will share them to the JEP I think.
>
> I also believe in small steps  so I think it's better to split UI text 
> changes and code change it make it more easy to review and test.
> On Wednesday, June 23, 2021 at 8:03:47 AM UTC+2 Oleg Nenashev wrote:
>
>> +1 to what Gavin said. I cannot comment on a particular EPIC, but 
>> renaming classes is generally in the scope for the terminology cleanup 
>> initiative: 
>> https://community.jenkins.io/t/jenkins-terminology-cleanup-initiative-coordination/180#full-scope-5
>>
>> "Being in scope" does not mean it will happen soon. All Jenkins 
>> initiatives depend on contributions, and the time many individual and 
>> company contributors are willing to invest. I totally agree with Gavin that 
>> user-facing items should be a priority. Then it should be developer facing 
>> things, where possible and feasible. If any contributor or end user has 
>> strong opinions about fixing a particular occurrence, they are welcome and 
>> encouraged to go ahead and submit pull requests. Lower priority does not 
>> mean the things should not be fixed now, everyone can work as they prefer.
>>
>>
>>
>> On Wed, Jun 23, 2021 at 7:27 AM 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> If a class name is serialized or used external to the plugin, its super 
>>> hard to change without breaking compatibility. Generally the initial push 
>>> is for using facing changes. Text strings, Help files. Docs. Etc
>>>
>>> On Tue, Jun 22, 2021 at 6:35 AM 'Fritz Elfert' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
>>>> On 22.06.21 12:01, Oleg Nenashev wrote:
>>>> > Hi all,
>>>> > 
>>>> > I am currently updating roadmap and the Jenkins website to reference 
>>>> the initiative and contributing.
>>>> > To group everything and to coordinate contributions, I have created a 
>>>> Discourse topic here: 
>>>> https://community.jenkins.io/t/jenkins-terminology-cleanup-initiative-coordination/180
>>>>  
>>>> <
>>>> https://community.jenkins.io/t/jenkins-terminology-cleanup-initiative-coordination/180>
>>>>  . 
>>>> I will be using it as a main source of contributing gui