Re: Reduced availability for Mark Waite

[Mark Waite]

On Tue, May 25, 2021 at 11:26 PM Bruce Becker  wrote:

> Dear Mark
>
> Congratulations seems somewhat misplaced, but perhaps the sentiment holds
> true. This is a a fearsome journey for those involved and I wish you
> courage on it.
>
> I will be able to contribute some of my time to maintaining the Docker
> images, since I already do so for $work. If accepted, I might require some
> initial hand-holding from the other maintainers, to understand your process
> and requirements, but I'm happy to contribute back.
>
>
Thanks in advance for your willingness to help with maintaining the Docker
images.  It is deeply appreciated!

I'm looking forward to the journey.  Avoiding kidney dialysis is a great
positive for my nephew.


> Thanks,
> Bruce
>
> On Wednesday, May 26, 2021 at 3:11:12 AM UTC+2 Mark Waite wrote:
>
>> I'm Mark Waite.  I'm a Jenkins contributor.  I’ll be unavailable or have
>> significantly reduced availability to help in the Jenkins project for at
>> least eight weeks beginning Wednesday, June 9, 2021.
>>
>> I have been accepted to donate a kidney to my brother’s son.  He’s the
>> father of three children and has a genetic disorder that is causing his
>> kidneys to fail.  The transplant team tells us that providing him one of my
>> kidneys will allow him to live a longer, more productive life.
>>
>> I need help to fill the roles that I perform for the Jenkins project
>> while I’m unavailable.  This message is my request for help.
>> *Where you can help*
>>
>> We want to spread knowledge around the Jenkins community.  We want others
>> to be able to help the project in ways that are interesting to them and
>> helpful for the community.  This kidney donation is an opportunity for
>> others to learn new things about the Jenkins project and to use those
>> skills to help.
>> Areas that need help are listed below.  These are also areas where we’ve
>> wanted to broaden to allow more people to help.  We hope that volunteers
>> will assist and will continue helping even after I return.
>>
>> *Mentor a Google Summer of Code project*
>>
>> I’m one of the mentors for the Google Summer of Code project, “Git
>> credentials binding for pipeline”
>> .
>> We have two very capable mentors, Justin and Rishabh, but prefer to have
>> three mentors for each project.  This mentor needs to have experience with
>> Jenkins plugin development and with git authentication techniques (both
>> private key and username/password).
>>
>> Send an email message to the Jenkins GSoC mailing list -
>> https://groups.google.com/g/jenkinsci-gsoc-all-public if you’d like to
>> be considered as an additional mentor for the Google Summer of Code
>> project, “Git credentials binding for pipeline”
>> 
>> .
>> *Lead the Platform SIG meeting*
>>
>> The Jenkins Platform Special Interest Group meets every two weeks to
>> discuss topics related to platform support.  Those topics have included
>> hardware support, operating system support, Docker image updates, JDK
>> versions, and more.
>>
>> We need a volunteer to lead the Platform SIG meeting, take the notes of
>> the meeting, and upload the recording of the meeting to the Jenkins YouTube
>> channel.  Contact me if you’re interested in helping with the Platform SIG.
>> *Maintain the Jenkins Docker images*
>>
>> The Jenkins Docker images include images for the controller, the inbound
>> agent, the ssh agent, and other images.  We need more maintainers for the
>> Jenkins Docker images.  The best way to help with maintaining images is to
>> review and comment on the existing pull requests.
>> *Scribe for the UX SIG meeting*
>>
>> The Jenkins User Experience Special Interest Group meets every two weeks
>> to discuss topics related to the Jenkins user interface and the Jenkins
>> user experience.
>>
>> We need one or more volunteers to take the notes of the User Experience
>> SIG meetings and upload the meeting recordings to the Jenkins YouTube
>> channel.  Contact me if you’re willing to act as the scribe of the Jenkins
>> UX SIG.
>>
>> *Review Jenkins bug reports and help users*
>>
>> Many Jenkins users submit bug reports in hopes of finding a solution to a
>> problem they are encountering.  If you are willing to spend time to help
>> other Jenkins users, the issues in the Jenkins core maintainers attention
>> 
>> list would be greatly benefited by additional people willing to offer
>> assistance.
>>
> --
> 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: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Tim Jacomb]

The ircbot has been moved over

On Wed, 26 May 2021 at 19:12, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Project registration has been completed since Saturday I think.
>
> I've removed the channel locks so anyone can create can register channels,
> project owners can claim the channel if it ever becomes an issue.
>
> Cloaks can be requested by any group member.
>
> Jenkins group members:
> Primary (can claim. Can manage group member lists)
> halkeye (me)
> Olblak
>
> Secondary (primary plus requesting cloaks for users)
> Nobody yet
>
>
> Cloaks:
> We have jenkins/* reserved
> I'm thinking jenkins/contributor/$nick for most people, then maybe board
> specific if we care.
>
> On Wed., May 26, 2021, 8:01 a.m. Oleg Nenashev, 
> wrote:
>
>> FYI see the project registration instructions here:
>>> https://libera.chat/chanreg#project-registration
>>>
>> AFAICT from the Governance Board discussion, Gavin and Olivier have
>> already submitted a registration request.
>> It just takes time to process
>>
>>
>>
>> On Wed, May 26, 2021 at 4:57 PM Basil Crow  wrote:
>>
>>> +1. I opened a PR to cover updating the references on jenkins.io:
>>> https://github.com/jenkins-infra/jenkins.io/pull/4384
>>>
>>> FYI see the project registration instructions here:
>>> https://libera.chat/chanreg#project-registration
>>>
>>> --
>>> 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/pEcun5ZSfgo/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/CAFwNDjqK%2BDwkLWdBUDh1iku45C9JjxC5NLXwguXAb3c%3Djx1i7g%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/CAPfivLDg7kSiyUHk6a4VgVHurG-8AcKfZHsSpCv0RG3_bpyFDg%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/CAG%3D_Duu4zWLgXUKN-PC20hdNCD_ct5kPufF9jj9Wh9d9GfbrmQ%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-3Bic-7hmtBNBjm6Q6h3RMETKoMDNib-tQcxi9M%2BLsWaQqAA%40mail.gmail.com.

Weekly Release 2.294 accidentally duplicated to 2.295 + WeeklyWindows Package unavailability: post-mortem

[Damien Duportal]

[Cross-posted on both jenkins-infra and jenkins-dev mailings]


Hello dear maintainers, contributors, and others!

Yesterday, the weekly release process for 2.294 suffered a human error (from I) 
which led to a duplicated release 2.295.

Also, the Windows Weekly Package was unavailable for download (HTTP/404) from 
2021-05-25 11:30 UTC until 2021-05-26 07:51 UT, due to a problem in the release 
process.

I’ve written a post-mortem on this URL: 
https://hackmd.io/@jenkins-infra/SJNjA5jKu 
 to explain the chronology, impact, 
reasons that led to this "outages".

A set of proposal has been made in the document to avoid these errors and 
mistakes again: please feel free to add more in this email thread and/or by 
logging in and commenting the document.

My apologies for the additional work the duplicated release added on your 
shoulders.

Have a nice day all!

Damien DUPORTAL - Jenkins Infra 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/99C8FD52-ADDF-43CD-B115-964D3BDE542E%40gmail.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

['Gavin Mogan' via Jenkins Developers]

Project registration has been completed since Saturday I think.

I've removed the channel locks so anyone can create can register channels,
project owners can claim the channel if it ever becomes an issue.

Cloaks can be requested by any group member.

Jenkins group members:
Primary (can claim. Can manage group member lists)
halkeye (me)
Olblak

Secondary (primary plus requesting cloaks for users)
Nobody yet


Cloaks:
We have jenkins/* reserved
I'm thinking jenkins/contributor/$nick for most people, then maybe board
specific if we care.

On Wed., May 26, 2021, 8:01 a.m. Oleg Nenashev, 
wrote:

> FYI see the project registration instructions here:
>> https://libera.chat/chanreg#project-registration
>>
> AFAICT from the Governance Board discussion, Gavin and Olivier have
> already submitted a registration request.
> It just takes time to process
>
>
>
> On Wed, May 26, 2021 at 4:57 PM Basil Crow  wrote:
>
>> +1. I opened a PR to cover updating the references on jenkins.io:
>> https://github.com/jenkins-infra/jenkins.io/pull/4384
>>
>> FYI see the project registration instructions here:
>> https://libera.chat/chanreg#project-registration
>>
>> --
>> 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/pEcun5ZSfgo/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/CAFwNDjqK%2BDwkLWdBUDh1iku45C9JjxC5NLXwguXAb3c%3Djx1i7g%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/CAPfivLDg7kSiyUHk6a4VgVHurG-8AcKfZHsSpCv0RG3_bpyFDg%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/CAG%3D_Duu4zWLgXUKN-PC20hdNCD_ct5kPufF9jj9Wh9d9GfbrmQ%40mail.gmail.com.

Re: Proposal: Adopting Stapler as official Jenkins project

[Oleg Nenashev]

Thanks to Kohsuke for your approval! And thanks to Kohsuke and Jesse for
feedback!

I do feel, however, that "not encourag[ing] external use" is an
> unnecessarily negative way of framing the mission of the new sub-project.
> Stapler is an unique web framework that enables the extensibility of
> Jenkins, and for that and all the other practical reasons it just makes
> more sense for the project to be adopted to Jenkins. The focus will be on
> serving Jenkins well. I think that's all that need to be said.
>


> I think there is a reason for specifically *discouraging* use outside
> Jenkins: that we have found the need to fix security vulnerabilities by
> defining interfaces in Stapler which are then implemented in Jenkins core.
> An external project is unlikely to keep up with these developments, and
> thus potentially remain vulnerable. It would be irresponsible to advertise
> a library which is unsafe to use on its own.
>

I agree with both statements. Let me think about how to frame it properly.
I will submit a pull request to jenkins.io with the proposal based on the
feedback here and on the private conversation with Kohsuke. Then we can
review it together and approve the wording. Kohsuke is the founder of the
Stapler project, and indeed we should respect and address the feedback.

Best regards,
Oleg




On Wed, May 26, 2021 at 5:27 PM Jesse Glick  wrote:

> On Wed, May 26, 2021 at 11:16 AM Kohsuke Kawaguchi  wrote:
>
>> "not encourag[ing] external use" is an unnecessarily negative way of
>> framing the mission
>>
>
> I think there is a reason for specifically *discouraging* use outside
> Jenkins: that we have found the need to fix security vulnerabilities by
> defining interfaces in Stapler which are then implemented in Jenkins core.
> An external project is unlikely to keep up with these developments, and
> thus potentially remain vulnerable. It would be irresponsible to advertise
> a library which is unsafe to use on its own.
>
> --
> 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/1T3yDHl1nEQ/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/CANfRfr2-T0_Yxc1RG34oV66JJhY6yegH_oMOrAN%2BY1-fPCL2VA%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/CAPfivLDcv93AbnGKdHQCtMaOSDctWiTREpSuqETt58jR--qpFQ%40mail.gmail.com.

Re: Proposal: Adopting Stapler as official Jenkins project

[Jesse Glick]

On Wed, May 26, 2021 at 11:16 AM Kohsuke Kawaguchi  wrote:

> "not encourag[ing] external use" is an unnecessarily negative way of
> framing the mission
>

I think there is a reason for specifically *discouraging* use outside
Jenkins: that we have found the need to fix security vulnerabilities by
defining interfaces in Stapler which are then implemented in Jenkins core.
An external project is unlikely to keep up with these developments, and
thus potentially remain vulnerable. It would be irresponsible to advertise
a library which is unsafe to use on its own.

-- 
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/CANfRfr2-T0_Yxc1RG34oV66JJhY6yegH_oMOrAN%2BY1-fPCL2VA%40mail.gmail.com.

Re: Proposal: Adopting Stapler as official Jenkins project

[Kohsuke Kawaguchi]

Hey, sorry for coming late, I'm happy to move the project closer to where 
the action is. Happy to transfer any/all assets involved.

I do feel, however, that "not encourag[ing] external use" is an 
unnecessarily negative way of framing the mission of the new sub-project. 
Stapler is an unique web framework that enables the extensibility of 
Jenkins, and for that and all the other practical reasons it just makes 
more sense for the project to be adopted to Jenkins. The focus will be on 
serving Jenkins well. I think that's all that need to be said. 

On Thursday, May 20, 2021 at 3:04:28 PM UTC-7 Oleg Nenashev wrote:

> At the governance meeting on May 19 (link 
> ) we agreed to 
> adopt Stapler and its components. We also agreed that a final sign-off from 
> Kohsuke as the project creator is needed before we proceed.
>
> On Wednesday, May 19, 2021 at 6:15:06 AM UTC+2 Oleg Nenashev wrote:
>
>> Thanks to everyone for the feedback!
>> Added the final sign-off to the today's governance meeting agenda
>>
>> On Monday, May 10, 2021 at 9:48:11 PM UTC+2 Jesse Glick wrote:
>>
>>> On Mon, May 10, 2021 at 2:04 PM Oleg Nenashev  
>>> wrote:
>>>
 Other Stapler related personal repositories can be also moved to the 
 jenkinsci org

>>>
>>> Sure; do you know of any?
>>>
>>> https://javadoc.jenkins.io/component/stapler/ includes Javadoc only for 
 https://github.com/stapler/stapler

>>>
>>> https://github.com/stapler/stapler/tree/master/core specifically. The 
>>> other modules do not expose useful Java-level APIs that plugin authors 
>>> should use that I know of.
>>>
>>> Other Stapler repositories like 
 https://github.com/stapler/maven-stapler-plugin are not included

>>>
>>> I do not think there is any need to publish Javadoc for any other 
>>> miscellaneous component. If and when a need arises, it is simple to include.
>>>
>>

-- 
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/b0bb7284-84ee-45f7-8372-7ba3473900a6n%40googlegroups.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Oleg Nenashev]

>
> FYI see the project registration instructions here:
> https://libera.chat/chanreg#project-registration
>
AFAICT from the Governance Board discussion, Gavin and Olivier have already
submitted a registration request.
It just takes time to process



On Wed, May 26, 2021 at 4:57 PM Basil Crow  wrote:

> +1. I opened a PR to cover updating the references on jenkins.io:
> https://github.com/jenkins-infra/jenkins.io/pull/4384
>
> FYI see the project registration instructions here:
> https://libera.chat/chanreg#project-registration
>
> --
> 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/pEcun5ZSfgo/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/CAFwNDjqK%2BDwkLWdBUDh1iku45C9JjxC5NLXwguXAb3c%3Djx1i7g%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/CAPfivLDg7kSiyUHk6a4VgVHurG-8AcKfZHsSpCv0RG3_bpyFDg%40mail.gmail.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Basil Crow]

+1. I opened a PR to cover updating the references on jenkins.io:
https://github.com/jenkins-infra/jenkins.io/pull/4384

FYI see the project registration instructions here:
https://libera.chat/chanreg#project-registration

-- 
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/CAFwNDjqK%2BDwkLWdBUDh1iku45C9JjxC5NLXwguXAb3c%3Djx1i7g%40mail.gmail.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Damien Duportal]

Thanks y'all for stepping so fast on this topic!

Seems a good idea to quickly move on Libera, and delay the "default 
community channel" to later, with a proper community discussion.

If anything is required on the infra's side, I can take over while Olivier 
is not available, and handover back afterwards.

Damien

Le mercredi 26 mai 2021 à 15:58:32 UTC+2, Oleg Nenashev a écrit :

> Thanks to Alex Earl for the IRCBot migration! 
> https://github.com/jenkins-infra/ircbot/pull/100
>
> I think we should not wait until the next Governance meeting if there is a 
> strong consensus in the mailing list. This is a time sensitive topic, and 
> we need to migrate away as soon as possible IMHO
>
>
> On Wednesday, May 26, 2021 at 1:28:26 PM UTC+2 Oleg Nenashev wrote:
>
>> Hi all,
>>
>> I definitely support such a move. For the record we've had a discussion 
>> about the migration among the Jenkins governance board and infra/security 
>> members. I believe we have a consensus that we want to move, effective as 
>> soon as possible. I also support moving all the listed channels. We have 
>> other channels, but all of them are rather dead or redundant.
>>
>> Notes about channels:
>>
>>- I would like to keep #jenkins equivalent, but not as a declared 
>>default channel. We could create #jenkins-users and #jenkins-dev 
>>similar to the mailing lists. Discourse would be indeed preferable for 
>> many 
>>subjects, and the IRC channels might become redundant (see the parallel 
>>thread)
>>- Private CERT chat is not a problem, we can just discontinue it in 
>>favor of mailing lists
>>- #jenkins-release and #jenkins-infra can be moved to Libera chat or 
>>any other chat like Gitter or CDF Slack. I have a preference to keep them 
>>on the same platform with conversation history by default
>>- #jenkins-hosting can be moved anywhere or just replaced by some 
>>form of GitHub/Jira integration bot
>>- #jenkins-meeting and #jenkins-hackhouse can be deleted. For 
>>meetings, if needed, we can create #jenkins-governance later
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
>>
>> On Wed, May 26, 2021 at 12:56 PM Tim Jacomb  wrote:
>>
>>> Hi all,
>>>
>>> I would like to propose moving the following channels that currently 
>>> live on freenode to libera.chat:
>>>
>>>- #jenkins
>>>- #jenkins-hosting
>>>- #jenkins-infra
>>>- #jenkins-release
>>>
>>> There's been some very user / FOSS hostile behaviour from the owner of 
>>> freenode, latest example can be seen in 
>>> https://news.ycombinator.com/item?id=27286628.
>>>
>>> Implementation is:
>>>
>>>- Update jenkins.io
>>>- Let people currently in the channel know
>>>- Update ircbot to connect to new server and create new credentials
>>>
>>> There's been other conversations about moving the community to places 
>>> like discourse and replacing the ircbot with Jira webhooks, but I don't 
>>> believe that this is the right thread for those.
>>>
>>> ircbot does more than just hosting, it manages github permissions and 
>>> Jira components as well.
>>> Any changes to ircbot require or Jira webhook integration requires 
>>> interested contributors to build solutions.
>>>
>>> Thanks
>>> Tim
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Infrastructure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkins-infr...@googlegroups.com.
>>> To view this discussion on the web, visit 
>>> https://groups.google.com/d/msgid/jenkins-infra/CAH-3BidgAHKm6t8iwB91cQ%3DO89XXEbo%2B6SX33AR_ZofsE-Pq%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/5b90f6e9-1122-4864-8a4c-a96ec1f19759n%40googlegroups.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Oleg Nenashev]

Thanks to Alex Earl for the IRCBot migration! 
https://github.com/jenkins-infra/ircbot/pull/100

I think we should not wait until the next Governance meeting if there is a 
strong consensus in the mailing list. This is a time sensitive topic, and 
we need to migrate away as soon as possible IMHO


On Wednesday, May 26, 2021 at 1:28:26 PM UTC+2 Oleg Nenashev wrote:

> Hi all,
>
> I definitely support such a move. For the record we've had a discussion 
> about the migration among the Jenkins governance board and infra/security 
> members. I believe we have a consensus that we want to move, effective as 
> soon as possible. I also support moving all the listed channels. We have 
> other channels, but all of them are rather dead or redundant.
>
> Notes about channels:
>
>- I would like to keep #jenkins equivalent, but not as a declared 
>default channel. We could create #jenkins-users and #jenkins-dev 
>similar to the mailing lists. Discourse would be indeed preferable for 
> many 
>subjects, and the IRC channels might become redundant (see the parallel 
>thread)
>- Private CERT chat is not a problem, we can just discontinue it in 
>favor of mailing lists
>- #jenkins-release and #jenkins-infra can be moved to Libera chat or 
>any other chat like Gitter or CDF Slack. I have a preference to keep them 
>on the same platform with conversation history by default
>- #jenkins-hosting can be moved anywhere or just replaced by some form 
>of GitHub/Jira integration bot
>- #jenkins-meeting and #jenkins-hackhouse can be deleted. For 
>meetings, if needed, we can create #jenkins-governance later
>
> Best regards,
> Oleg Nenashev
>
>
>
> On Wed, May 26, 2021 at 12:56 PM Tim Jacomb  wrote:
>
>> Hi all,
>>
>> I would like to propose moving the following channels that currently live 
>> on freenode to libera.chat:
>>
>>- #jenkins
>>- #jenkins-hosting
>>- #jenkins-infra
>>- #jenkins-release
>>
>> There's been some very user / FOSS hostile behaviour from the owner of 
>> freenode, latest example can be seen in 
>> https://news.ycombinator.com/item?id=27286628.
>>
>> Implementation is:
>>
>>- Update jenkins.io
>>- Let people currently in the channel know
>>- Update ircbot to connect to new server and create new credentials
>>
>> There's been other conversations about moving the community to places 
>> like discourse and replacing the ircbot with Jira webhooks, but I don't 
>> believe that this is the right thread for those.
>>
>> ircbot does more than just hosting, it manages github permissions and 
>> Jira components as well.
>> Any changes to ircbot require or Jira webhook integration requires 
>> interested contributors to build solutions.
>>
>> Thanks
>> Tim
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Infrastructure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins-infr...@googlegroups.com.
>> To view this discussion on the web, visit 
>> https://groups.google.com/d/msgid/jenkins-infra/CAH-3BidgAHKm6t8iwB91cQ%3DO89XXEbo%2B6SX33AR_ZofsE-Pq%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/f4866a28-87b4-42cd-bbd6-a2235c658dfdn%40googlegroups.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Oleg Nenashev]

Hi all,

I definitely support such a move. For the record we've had a discussion
about the migration among the Jenkins governance board and infra/security
members. I believe we have a consensus that we want to move, effective as
soon as possible. I also support moving all the listed channels. We have
other channels, but all of them are rather dead or redundant.

Notes about channels:

   - I would like to keep #jenkins equivalent, but not as a declared
   default channel. We could create #jenkins-users and #jenkins-dev similar
   to the mailing lists. Discourse would be indeed preferable for many
   subjects, and the IRC channels might become redundant (see the parallel
   thread)
   - Private CERT chat is not a problem, we can just discontinue it in
   favor of mailing lists
   - #jenkins-release and #jenkins-infra can be moved to Libera chat or any
   other chat like Gitter or CDF Slack. I have a preference to keep them on
   the same platform with conversation history by default
   - #jenkins-hosting can be moved anywhere or just replaced by some form
   of GitHub/Jira integration bot
   - #jenkins-meeting and #jenkins-hackhouse can be deleted. For meetings,
   if needed, we can create #jenkins-governance later

Best regards,
Oleg Nenashev



On Wed, May 26, 2021 at 12:56 PM Tim Jacomb  wrote:

> Hi all,
>
> I would like to propose moving the following channels that currently live
> on freenode to libera.chat:
>
>- #jenkins
>- #jenkins-hosting
>- #jenkins-infra
>- #jenkins-release
>
> There's been some very user / FOSS hostile behaviour from the owner of
> freenode, latest example can be seen in
> https://news.ycombinator.com/item?id=27286628.
>
> Implementation is:
>
>- Update jenkins.io
>- Let people currently in the channel know
>- Update ircbot to connect to new server and create new credentials
>
> There's been other conversations about moving the community to places like
> discourse and replacing the ircbot with Jira webhooks, but I don't believe
> that this is the right thread for those.
>
> ircbot does more than just hosting, it manages github permissions and Jira
> components as well.
> Any changes to ircbot require or Jira webhook integration requires
> interested contributors to build solutions.
>
> Thanks
> Tim
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Infrastructure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkins-infra+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/jenkins-infra/CAH-3BidgAHKm6t8iwB91cQ%3DO89XXEbo%2B6SX33AR_ZofsE-Pq%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/CAPfivLBnxmgBYUN%2BwngyELWPcVZWZ5Sthv1euhGs5%3DzTqrYJQA%40mail.gmail.com.

Re: Migrate chat channels from freenode to libera.chat

['Olblak' via Jenkins Developers]

Hi Tim,

Thanks for bootstrapping this, I definitely support moving from Freenode to 
Libera.chat.
I have a limited bandwidth capacity at the moment but I'll try to help as soon 
as I can.
I think it's better to first move away from Freenode and then start a 
discussion about the default communication channel we want to use.



On Wed, May 26, 2021, at 12:56 PM, Tim Jacomb wrote:
> Hi all,
> 
> I would like to propose moving the following channels that currently live on 
> freenode to libera.chat:
>  * #jenkins
>  * #jenkins-hosting
>  * #jenkins-infra
>  * #jenkins-release
> There's been some very user / FOSS hostile behaviour from the owner of 
> freenode, latest example can be seen in 
> https://news.ycombinator.com/item?id=27286628.
> 
> Implementation is:
>  * Update jenkins.io
>  * Let people currently in the channel know
>  * Update ircbot to connect to new server and create new credentials
> There's been other conversations about moving the community to places like 
> discourse and replacing the ircbot with Jira webhooks, but I don't believe 
> that this is the right thread for those.
> 
> ircbot does more than just hosting, it manages github permissions and Jira 
> components as well.
> Any changes to ircbot require or Jira webhook integration requires interested 
> contributors to build solutions.
> 
> 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/CAH-3BidgAHKm6t8iwB91cQ%3DO89XXEbo%2B6SX33AR_ZofsE-Pq%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/b82ed260-c747-4f57-945a-d94e8f960faf%40www.fastmail.com.

Migrate chat channels from freenode to libera.chat

[Tim Jacomb]

Hi all,

I would like to propose moving the following channels that currently live
on freenode to libera.chat:

   - #jenkins
   - #jenkins-hosting
   - #jenkins-infra
   - #jenkins-release

There's been some very user / FOSS hostile behaviour from the owner of
freenode, latest example can be seen in
https://news.ycombinator.com/item?id=27286628.

Implementation is:

   - Update jenkins.io
   - Let people currently in the channel know
   - Update ircbot to connect to new server and create new credentials

There's been other conversations about moving the community to places like
discourse and replacing the ircbot with Jira webhooks, but I don't believe
that this is the right thread for those.

ircbot does more than just hosting, it manages github permissions and Jira
components as well.
Any changes to ircbot require or Jira webhook integration requires
interested contributors to build solutions.

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/CAH-3BidgAHKm6t8iwB91cQ%3DO89XXEbo%2B6SX33AR_ZofsE-Pq%3DQ%40mail.gmail.com.

Re: Reduced availability for Mark Waite

['Gavin Mogan' via Jenkins Developers]

> I will be able to contribute some of my time to maintaining the Docker
images,

its not very active but the platform sig hangs out in
https://gitter.im/jenkinsci/platform-sig

On Tue, May 25, 2021 at 10:26 PM Bruce Becker  wrote:

> Dear Mark
>
> Congratulations seems somewhat misplaced, but perhaps the sentiment holds
> true. This is a a fearsome journey for those involved and I wish you
> courage on it.
>
> I will be able to contribute some of my time to maintaining the Docker
> images, since I already do so for $work. If accepted, I might require some
> initial hand-holding from the other maintainers, to understand your process
> and requirements, but I'm happy to contribute back.
>
> Thanks,
> Bruce
>
> On Wednesday, May 26, 2021 at 3:11:12 AM UTC+2 Mark Waite wrote:
>
>> I'm Mark Waite.  I'm a Jenkins contributor.  I’ll be unavailable or have
>> significantly reduced availability to help in the Jenkins project for at
>> least eight weeks beginning Wednesday, June 9, 2021.
>>
>> I have been accepted to donate a kidney to my brother’s son.  He’s the
>> father of three children and has a genetic disorder that is causing his
>> kidneys to fail.  The transplant team tells us that providing him one of my
>> kidneys will allow him to live a longer, more productive life.
>>
>> I need help to fill the roles that I perform for the Jenkins project
>> while I’m unavailable.  This message is my request for help.
>> *Where you can help*
>>
>> We want to spread knowledge around the Jenkins community.  We want others
>> to be able to help the project in ways that are interesting to them and
>> helpful for the community.  This kidney donation is an opportunity for
>> others to learn new things about the Jenkins project and to use those
>> skills to help.
>> Areas that need help are listed below.  These are also areas where we’ve
>> wanted to broaden to allow more people to help.  We hope that volunteers
>> will assist and will continue helping even after I return.
>>
>> *Mentor a Google Summer of Code project*
>>
>> I’m one of the mentors for the Google Summer of Code project, “Git
>> credentials binding for pipeline”
>> .
>> We have two very capable mentors, Justin and Rishabh, but prefer to have
>> three mentors for each project.  This mentor needs to have experience with
>> Jenkins plugin development and with git authentication techniques (both
>> private key and username/password).
>>
>> Send an email message to the Jenkins GSoC mailing list -
>> https://groups.google.com/g/jenkinsci-gsoc-all-public if you’d like to
>> be considered as an additional mentor for the Google Summer of Code
>> project, “Git credentials binding for pipeline”
>> 
>> .
>> *Lead the Platform SIG meeting*
>>
>> The Jenkins Platform Special Interest Group meets every two weeks to
>> discuss topics related to platform support.  Those topics have included
>> hardware support, operating system support, Docker image updates, JDK
>> versions, and more.
>>
>> We need a volunteer to lead the Platform SIG meeting, take the notes of
>> the meeting, and upload the recording of the meeting to the Jenkins YouTube
>> channel.  Contact me if you’re interested in helping with the Platform SIG.
>> *Maintain the Jenkins Docker images*
>>
>> The Jenkins Docker images include images for the controller, the inbound
>> agent, the ssh agent, and other images.  We need more maintainers for the
>> Jenkins Docker images.  The best way to help with maintaining images is to
>> review and comment on the existing pull requests.
>> *Scribe for the UX SIG meeting*
>>
>> The Jenkins User Experience Special Interest Group meets every two weeks
>> to discuss topics related to the Jenkins user interface and the Jenkins
>> user experience.
>>
>> We need one or more volunteers to take the notes of the User Experience
>> SIG meetings and upload the meeting recordings to the Jenkins YouTube
>> channel.  Contact me if you’re willing to act as the scribe of the Jenkins
>> UX SIG.
>>
>> *Review Jenkins bug reports and help users*
>>
>> Many Jenkins users submit bug reports in hopes of finding a solution to a
>> problem they are encountering.  If you are willing to spend time to help
>> other Jenkins users, the issues in the Jenkins core maintainers attention
>> 
>> list would be greatly benefited by additional people willing to offer
>> assistance.
>>
> --
> 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
>