[Events]: Contributor Summit 2022 Agenda

[Alyssa Tong]

Hello,
We wanted to share the agenda to the Contributor Summit in Orlando, Florida
- as it stands at the moment.
Entry fee:
No cost to attend. Sign up via the sign up sheet

(room capacity: 30). Event is in person only.Location: Orlando World Center
Marriott: 8701 World Center Dr, Orlando,  FL  32821 (Room: Magnolia 19)Key
dates:


* - Sept 27 - Contributor Summit @ 9AM - 5PM - Sept 28 & 29 - Main
conference

(use discount code: DW22JENKINSRTE)*Contact



* - SIG - Advocacy & Outreach
- Contact - Alyssa Tong
and Bruno Verachten- Community via community Discourse:
https://community.jenkins.io *Description

*The Jenkins Contributor Summit brings together current and future
contributors to the Jenkins project. At this event we will talk about the
current state of the project and its future evolution.The summit will
include project updates by the Governance Board, working and special
interest groups. We will also organize breakout sessions to discuss key
initiatives in the project and its roadmap. Topics include but are not
limited to:  architecture changes, Jenkins Security, Cloud Native Jenkins,
interoperability, documentation, and user experience. We will also have
lightning talks and demos of the new and upcoming Jenkins features. We will
also organize a track for newcomer contributors who want to participate in
the project.*Agenda

   -

   Intro, summit overview - 3 min [Bruno Verachten]
   -

   State of Jenkins - one of Jenkins Board members, 7 min [Mark Waite]
   -

  Major news
  -

   Project/SIG Updates,  5-10 min each. SIG leaders, officers, et al. to
   summarize the current state
   -

  Release officer [Tim Jacomb]
  -

  Security [Wadeck Follonier]
  -

  Infra [Damien Duportal]
  -

  Platform [Mark Waite]
  -

  Events  [Alyssa Tong]
  -

  Outreach SIG [Mark Waite & Jean-Marc Meessen]
  -

 Google Summer of Code
 -

 She Code Africa
 -

  Documentation [Mark Waite]
  -

 I18n, L10n
 -

   User Experience [Tim Jacomb & Jan Faracik]
   -

   What’s next for Java [Mark Waite]
   -

  Java 11
  -

 active support ends 30 Sep 2023
 -

 security support ends 30 Sep 2026
 -

  Java 17
  -

 active support ends 30 Sep 2026
 -

 security support ends 30 Sep 2031
 - Plugin health scoring project [Jake Leon]
   - Inspiring plugin health improvements by scoring the current status
  -

  - Ignite Talks / Demos
   -
  - Darin Pope (tbc)
  - Volunteers from audience
   -

   End user presentations/demos [5 min each]
   - Rapidly build and test your iOS Apps with Jenkins on EC2 Mac - Sudhir
  Reddy [10 mim]
  - Migrating Jenkins Unity CI/CD build farms to AWS EC2 Mac instances
  - Sergey Kruson [10 min]
  - Upgrade evaluation process experience- Steve Hill
  - Pipeline experiences - how they use Pipeline
  - Mobile development - Bruno Verachten
  - Administering large Jenkins instances - Damien Duportal
  - Pre-built Jenkins test configurations with Docker - Mark Waite
  - Choosing your tests wisely - Kohsuke Kawaguchi (tbc)
  - Security - Wadeck Follonier
  -

   Hacktoberfest and onboarding new contributors - Jean-Marc & Bruno
   Verachten
   -

   Future of Jenkins
   -

  UI - [Jan Faracik & Tim Jacomb]
  -

  Testing improvements
  -

  Internationalization and localization - Mark Waite and Alex Brandes
  -

 First time contributor tasks (Mark talk with Darin)
 -

  More cloud


  Thank you,

  Alyssa & Bruno

-- 
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/CAC9wNaw2ZtoLw%2Bb4-G7gxi_2m9Zr44jE%2BeJezHg2SKMdmy7Hdw%40mail.gmail.com.

Re: Security approval required on UI-related PRs in Jenkins core

[Basil Crow]

On Wed, Jun 22, 2022 at 10:37 AM 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:
> For this reason, as the security officer and effective as of today, I want to 
> block the merge of any UI-related PRs until they have received at least one 
> approval from someone in CERT.

[…]

> Do you have any concerns related to this?

-1 from me. I lack confidence that the CERT team will acknowledge and
respond to all questions asked during the security review process.

-- 
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/CAFwNDjoUGsepzyE4rMnRLcqiU0tpDOGvGmxi4NV5u32d%2BHVecQ%40mail.gmail.com.

Fwd: Plugin Adoption for kryptowire-plugin

[Chris Downey]

Greetings,

My name is Chris Downey and I'm a colleague of Brian Schulte at Kryptowire, 
with whom you worked with about 4 years ago to develop a Jenkins CI/CD 
Plugin for Mobile App Build submissions to the Kryptowire MAST platform.  
We are looking to take full ownership of that Plugin so that we can update 
it with some changes we've made.  Jenkins Devs requested I CC original 
developers who are listed as Admins in the Permissions Updater repo's 
plugin-kryptowire.yml 

 file.  
I've CC'd 2 here in addition to John Frizelle who we engaged in 2018 but is 
not listed as a plugin admin as far as I can tell.  Brian and I would like 
to proceed taking full ownership of the plugin including the Admin list.  

Please reply that you have received this message when you can to approve.  
Thanks for your time.

Plugin in jenkinsci repo:  https://github.com/jenkinsci/kryptowire-plugin
Plugin on Plugins site:  https://plugins.jenkins.io/kryptowire/
My ci.jenkins.io Username:  crdkw
My Github Username:  cdowney-kryptowire
Original Contributor Github Username:  odra 

Regards,

Chris Downey
Senior Product Manager, Kryptowire

-- Forwarded message -
From: Chris Downey 
Date: Wednesday, August 31, 2022 at 9:59:26 AM UTC-5
Subject: Re: Plugin Adoption for kryptowire-plugin
To: Jenkins Developers 


Thank you for the response.  Sorry for my delayed response, I was expecting 
to get emailed any response to my Group post, but never saw an email reply 
so am just now today coming back to the Groups page to check the thread.

My engineering resource is on PTO, but we will get this process started 
when he returns.

Regards,
Chris


On Thursday, August 18, 2022 at 5:51:01 PM UTC-5 ga...@gavinmogan.com wrote:

> So what you've done is a start. You should be CC'ing any of the current 
> maintainers. Also recommend creating a PR or issue that tags them. Thirdly 
> make a PR 
> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-kryptowire.yml
>
> Once that's all done, we wait 2 weeks for a response, if that times out, 
> then we go ahead and give you access.
>
> > We are about to go through a re-branding process at our Company and 
> have iterated on the version of the Plugin the RedHat guys first developed,
>
> Just be careful not to update the artifact id, otherwise it'll prevent 
> existing installs from upgrading.
>
> On Thu, Aug 18, 2022 at 1:58 PM Chris Downey  
> wrote:
>
>> Hello,
>>
>> I am reaching out to this Group email in the hopes of starting the 
>> Adoption process for the kryptowire-plugin in the jenkinsci Project.  
>> Relevant details are as follows.
>>
>> Plugin in jenkinsci repo:  https://github.com/jenkinsci/kryptowire-plugin
>> Plugin on Plugins site:  https://plugins.jenkins.io/kryptowire/
>> My ci.jenkins.io Username:  crdkw
>> My Github Username:  cdowney-kryptowire
>> Original Contributor Github Username:  odra 
>>
>> Other Info:
>>
>> I am a Senior PM at Kryptowire.  We collaborated with some developers 
>> from RedHat for the initial version of the Plugin for which they were 
>> responsible engaging the project for acceptance and maintaining the first 
>> version.  My colleague CC’d here, Brian Schulte may be listed as an Admin 
>> for the Plugin, but I don’t think the process of transferring full 
>> ownership to us was ever completed after the Plugin was first developed in 
>> mid-2018.  We are about to go through a re-branding process at our Company 
>> and have iterated on the version of the Plugin the RedHat guys first 
>> developed, but without full ownership haven’t been able to update the 
>> official Jenkins version.
>>
>> Can you please let me know what the Adoption process should be to take 
>> full ownership of the project in jenkinsci?  If we need to, I can try to 
>> contact the original developers.
>>
>> Regards,
>>
>> Chris Downey
>> Senior Product Manager
>> E: cdo...@kryptowire.com
>> M:+1 512.791.4315 <(512)%20791-4315>
>>
>> -- 
>> 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/55D5672A-1303-4CDC-BEC8-1712C85E4B9B%40kryptowire.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: Plugin Adoption for kryptowire-plugin

[Chris Downey]

Thank you for the response.  Sorry for my delayed response, I was expecting 
to get emailed any response to my Group post, but never saw an email reply 
so am just now today coming back to the Groups page to check the thread.

My engineering resource is on PTO, but we will get this process started 
when he returns.

Regards,
Chris


On Thursday, August 18, 2022 at 5:51:01 PM UTC-5 ga...@gavinmogan.com wrote:

> So what you've done is a start. You should be CC'ing any of the current 
> maintainers. Also recommend creating a PR or issue that tags them. Thirdly 
> make a PR 
> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-kryptowire.yml
>
> Once that's all done, we wait 2 weeks for a response, if that times out, 
> then we go ahead and give you access.
>
> > We are about to go through a re-branding process at our Company and 
> have iterated on the version of the Plugin the RedHat guys first developed,
>
> Just be careful not to update the artifact id, otherwise it'll prevent 
> existing installs from upgrading.
>
> On Thu, Aug 18, 2022 at 1:58 PM Chris Downey  
> wrote:
>
>> Hello,
>>
>> I am reaching out to this Group email in the hopes of starting the 
>> Adoption process for the kryptowire-plugin in the jenkinsci Project.  
>> Relevant details are as follows.
>>
>> Plugin in jenkinsci repo:  https://github.com/jenkinsci/kryptowire-plugin
>> Plugin on Plugins site:  https://plugins.jenkins.io/kryptowire/
>> My ci.jenkins.io Username:  crdkw
>> My Github Username:  cdowney-kryptowire
>> Original Contributor Github Username:  odra 
>>
>> Other Info:
>>
>> I am a Senior PM at Kryptowire.  We collaborated with some developers 
>> from RedHat for the initial version of the Plugin for which they were 
>> responsible engaging the project for acceptance and maintaining the first 
>> version.  My colleague CC’d here, Brian Schulte may be listed as an Admin 
>> for the Plugin, but I don’t think the process of transferring full 
>> ownership to us was ever completed after the Plugin was first developed in 
>> mid-2018.  We are about to go through a re-branding process at our Company 
>> and have iterated on the version of the Plugin the RedHat guys first 
>> developed, but without full ownership haven’t been able to update the 
>> official Jenkins version.
>>
>> Can you please let me know what the Adoption process should be to take 
>> full ownership of the project in jenkinsci?  If we need to, I can try to 
>> contact the original developers.
>>
>> Regards,
>>
>> Chris Downey
>> Senior Product Manager
>> E: cdo...@kryptowire.com
>> M:+1 512.791.4315 <(512)%20791-4315>
>>
>> -- 
>> 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/55D5672A-1303-4CDC-BEC8-1712C85E4B9B%40kryptowire.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/7c3acbea-4efc-4079-a496-8e1116fdd5f9n%40googlegroups.com.

Re: Jenkins 2.361.1 LTS RC testing started

[Basil Crow]

On Wed, Aug 31, 2022 at 6:59 AM Vincent Latombe
 wrote:
>
> I mentioned https://issues.jenkins.io/browse/JENKINS-69250 in this thread, 
> because it affects CloudBees in every Jenkins page, since it uses a different 
> header implementation.
> For Jenkins, only the Setup Wizard is affected, but nevertheless I think it 
> should be considered for backport towards 2.361.1.1 LTS.

+1 from me. I verified the fix manually by running through the setup
wizard and observing no JavaScript errors, and it has been delivered
in the 2.366 weekly release.

-- 
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/CAFwNDjpxD22kMxoEZfB0uHwf7cYyG-EqkGGP5UQrLtT%2BZSAG%2BA%40mail.gmail.com.

Adopt Dynamic Search View plugin

['Kevin Martens' via Jenkins Developers]

 Hi there,

I was hoping that I could adopt the Dynamic Search View plugin. I've gone
and submitted the PR for permissions update, and mentioned Oleg in the PR,
as he is currently listed as a maintainer. The plugin does show the "up for
adoption" status, so please let me know if there is anything else I need to
do.

- https://plugins.jenkins.io/dynamic-search-view/
- Plugin is up for adoption (Oleg is listed as a current maintainer)
- kmartens27 / https://github.com/kmartens27\
- https://github.com/jenkins-infra/repository-permissions-updater/pull/2786
-- 
Kevin Martens
Technical Content Developer
CloudBees, Inc.


E: kmart...@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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAP92yNcpUcGowjvib3NMc%2BAzwkO5APgJoj1bq%3DCiVdhet7eLtA%40mail.gmail.com.

Re: Jenkins 2.361.1 LTS RC testing started

[Vincent Latombe]

I mentioned https://issues.jenkins.io/browse/JENKINS-69250 in this thread,
because it affects CloudBees in every Jenkins page, since it uses a
different header implementation.
For Jenkins, only the Setup Wizard is affected, but nevertheless I think it
should be considered for backport towards 2.361.1.1 LTS.

Vincent


Le mer. 31 août 2022 à 15:29, Basil Crow  a écrit :

> Hello Vincent,
>
> On Mon, Aug 29, 2022 at 1:50 AM Vincent Latombe
>  wrote:
> > https://issues.jenkins.io/browse/JENKINS-69250 is affecting both Setup
> Wizard and custom Headers implementations. I've submitted a pull request.
>
> Thank you for submitting this pull request! Is there a reason why you
> have mentioned your submission in this email thread?
>
> Thanks,
> Basil
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqeWWx0Sgh7U6gkrqDN%3DLVWcxEDX%2By6iZ1VF_v3%3DxydWQ%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-zGCjRQN7uuyEd4xjWDy%2BpOKfJLMLRW5ovuHBUy2ro9vV9Fg%40mail.gmail.com.

Re: Jenkins 2.361.1 LTS RC testing started

[Basil Crow]

Hello Vincent,

On Mon, Aug 29, 2022 at 1:50 AM Vincent Latombe
 wrote:
> https://issues.jenkins.io/browse/JENKINS-69250 is affecting both Setup Wizard 
> and custom Headers implementations. I've submitted a pull request.

Thank you for submitting this pull request! Is there a reason why you
have mentioned your submission in this email thread?

Thanks,
Basil

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

Re: Jenkins 2.361.1 LTS RC testing started

[Kris Stern]

Hi Basil,

Thanks for the correction!

Best,
Kris

On Tuesday, August 30, 2022 at 10:51:34 PM UTC+8 m...@basilcrow.com wrote:

> On Tue, Aug 30, 2022 at 5:00 AM Kris Stern  wrote:
> >
> > Regarding the issue mentioned previously (
> https://issues.jenkins.io/browse/JENKINS-69250), the PR for addressing it 
> has been opened and merged and can be accessed at 
> https://github.com/jenkinsci/jenkins/pull/7034.
>
> No. jenkinsci/jenkins#7034 
>  was a backport of 
> jenkinsci/jenkins#7033 . 
> The PR for addressing JENKINS-69250 
>  on the main branch was 
> jenkinsci/jenkins#7043 .
>

-- 
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/b94f287a-dcc0-4135-bb27-b025ca0b3973n%40googlegroups.com.