Re: Beta releases of new UI modules available

[Ullrich Hafner]

I already thought about this as well. The JUnit plugin is not in the core 
anymore, or am I missing something? Or can’t the JUnit plugin depend on other 
plugins? Or are you referring to the large backlog of open PRs in this plugin 
that indicates that changes to that plugin should be done very carefully?

(Another much simpler option is to add such a chart in the warnings plugin that 
hides the orginal JUnit chart but that would be kind of hack...)


> Am 16.01.2020 um 22:36 schrieb James Nord :
> 
> I was looking at how old and outdated the junit test result charts looked 
> next to you new charts.
> ild love to try and update junit charts but that you is in the core so I feel 
> this would be a step to far for my lack of frontend skills.
> 
> but amazing results!
> 
> -- 
> 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/29e96d2f-b228-439e-8e5b-51141c679652%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/E81F4FF8-4AE4-4416-84DE-0E149D5E88C4%40gmail.com.

Re: Jenkins comic project: Call for brainstorming volunteers

[Alyssa Tong]

Thanks Arnaud for sharing ..too funny. I love the idea of members as "proud
to be a butler"

On Tue, Jan 14, 2020 at 10:50 PM Arnaud Héritier 
wrote:

> Hi
>
>   I won’t be able to attend but related to this topic I wanted to share
> this experiment done by Oleg with my head already Created by commit strip:
>
> https://twitter.com/oleg_nenashev/status/1214694618811514881?s=21
>
>   Couldn’t we take the opportunity to have something similar for visible
> members of the community and create a communication around “proud to be
> butler” or something like this ?
>
> Cheers
>
> Le mer. 15 janv. 2020 à 02:23, Alyssa Tong  a écrit :
>
>> Hello,
>>
>> We are looking to do a fun project with Jenkins.  We are looking to do
>> Jenkins comic with the help and talent of CommitStrip. Thank you to
>> CloudBees for sponsoring this project. On Thursday, 23 Jan we will be
>> holding a brainstorming session with CommitStrip to discuss the tone of
>> voice for the butler, and what ever else CommitStrip may need to give life
>> to the butler.  If you'd like to be involved in this process, pls add your
>> name and email address to this gdoc
>> 
>> so I may send you call-in info once we are close to 23 Jan.
>>
>> thank you,
>> 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/CAC9wNaybYttkcTYo%2BjWhi-4cUpjnCEgXWU4cW6ZvnWjW3A-%2B1w%40mail.gmail.com
>> 
>> .
>>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
> --
> 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/CAFNCU-8mrkQBNkcwvLBbG8pvM%2BHkGxccjL-5Hg%3DUiEo1r6ghaA%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/CAC9wNazEbXnVZYQJ-d2v%3D6LkZ8uFjJk4%3DC3L1-d74FAb%2BvhKPw%40mail.gmail.com.

[EVENT]: Pre-FOSDEM workshops & Contributor Summit

[Alyssa Tong]

Hello,

FOSDEM is always an exciting time for those of us in the open source. If
you are attending FOSDEM, those of us in Jenkins project will be doing a
couple of activities starting Thursday, 30 Jan through Sunday, 2 Feb :

On* Thursday, 30 Jan,* there will be 2 workshops. Pls note that
registration is required so we may plan for proper seating and food/bev:

   - *Jenkins Pipeline Fundamentals
   *. Learn to create and
   run Declarative Pipelines with Jenkins. You’ll learn the structure of
   Declarative Pipeline, how to control the flow of execution, how to save
   artifacts of the build, and get practice using some of the features that
   give fit and finish to your Pipeline.


   - *Cloud-Native Kubernetes-First Serverless Continuous Delivery With...
   * Jenkins X enables the
   rapid creation, delivery and orchestration of cloud native applications
   based on continuous delivery best practices and the proven Kubernetes
   platform. By combining the power of Jenkins, its community and the power of
   Kubernetes, the Jenkins X project provides a path to the future of
   continuous delivery for microservices and cloud native applications.

On *Friday, 31* Jan, there will be a Jenkins contributor summit. More
details HERE 

On *Saturday, 1 Feb and Sunday, 2 Feb* we will be busy staffing the Jenkins
stand in building K (2nd level). Stop by to say "Hi" and grab some stickers.

hope you see you there!
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/CAC9wNayTz%2BgAJp%3DOTUZY1qQJ%3D8VvwzXx7QX6ewBHVfR0NnTVDw%40mail.gmail.com.

Beta releases of new UI modules available

[James Nord]

I was looking at how old and outdated the junit test result charts looked next 
to you new charts.
ild love to try and update junit charts but that you is in the core so I feel 
this would be a step to far for my lack of frontend skills.

but amazing results!

-- 
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/29e96d2f-b228-439e-8e5b-51141c679652%40googlegroups.com.

Re: Adopt a plugin request

[Oleg Nenashev]

Sorry, did not get to it. Will try to do the transfer tomorrow

On Thu, Jan 16, 2020, 15:05 Oleg Nenashev  wrote:

> Thanks for the ping!
> I will do the permission transfer today
>
> On Thursday, January 16, 2020 at 2:59:25 PM UTC+1, Terry Moreland wrote:
>>
>> Just posting a follow up on this request, it's now been over 2 weeks
>> (with some extra padding to accommodate the holiday period), As there is no
>> e-mail for the original maintainers account I've been unable to e-mail but
>> have mentioned @nbugash in 3 comments on the pull request to this
>> repository none of which have received any response.  I also attempted to
>> reach out via Linked-In profile but again no response.
>>
>> For reference this is for:
>> jenkinsci:  https://plugins.jenkins.io/jenkinsci-appspider-plugin
>> github:  https://github.com/rapid7/jenkinsci-appspider-plugin
>> pull request: https://github.com/rapid7/jenkinsci-appspider-plugin/pull/5
>> github id: tsmoreland
>> jenkins id: tmoreland
>>
>>
>> On Friday, 20 December 2019 09:15:41 UTC, Terry Moreland wrote:
>>>
>>> I've also added a comment to the current pull request pinging his
>>> personal github account which is the one he associated with the plugin.  As
>>> of yet no reply either there or via linked in
>>
>> --
> 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/c2nWqrqzrNg/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/674d4170-efef-4fda-a415-9466c2ffb224%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/CAPfivLAnzbH86N%2BX4ZvaZ0Y_1sWoQw%2BwvyGDajWjELUBkO%2BSsw%40mail.gmail.com.

Re: Proposal: Implementing sensible fine grained permissions to allow an administer to securely delegate some aspects of jenkins configuration

[Matt Sicker]

That would assuage my concerns significantly.

On Thu, Jan 16, 2020 at 3:43 AM Daniel Beck  wrote:
>
>
>
> On Wed, Jan 15, 2020 at 9:00 PM Matt Sicker  wrote:
>>>
>>> Plugins that contribute to the settings on on the Configure Jenkins page 
>>> should carefully consider if allowing a user with only Jenkins.CONFIGURE 
>>> could result in an unintended privelege escalation.
>>
>>
>> To me, this sounds like a fairly onerous requirement for plugins. Based on 
>> the numerous published security advisories just around plugins not bothering 
>> with a permission check in the first place, this sounds like a fairly large 
>> hole. How could we mitigate that?
>
>
> The difference is that much of that comes from bad (permissive) defaults. 
> This would be opt-in, and with good documentation about security 
> considerations, plugin maintainers will be given the tools to understand 
> whether it makes sense to make this available, or 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/CAMo7PtL5X07BBvtorwR5t8%3DO%3D8mHdGkkX79YqKYrMixoF7yLrw%40mail.gmail.com.



-- 
Matt Sicker
Senior Software Engineer, CloudBees

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

Re: S3 plugin maintainership status

[Baptiste Mathus]

To circle back, here's the permission PR, thanks Evaristo for filing it!

https://github.com/jenkins-infra/repository-permissions-updater/pull/1400

Le mer. 15 janv. 2020 à 11:15, Francisco Javier Fernandez <
fjfernan...@cloudbees.com> a écrit :

> I'm interested as well
>
> Github: fcojfernandez
> JIRA: fcojfernandez
>
> El miércoles, 15 de enero de 2020, 11:14:13 (UTC+1), Evaristo Gutierrez
> escribió:
>>
>> Thanks Oleg and everyone!
>>
>> Github: varyvol
>> JIRA: egutierrez
>>
>> On Monday, January 13, 2020 at 5:01:28 PM UTC+1, Evaristo Gutierrez wrote:
>>>
>>> Hi all,
>>>
>>> Nearly a month ago I raised [PR #124|
>>> https://github.com/jenkinsci/s3-plugin/pull/124] on the S3 plugin. It
>>> has not been reviewed or merged yet. I also noticed that there are quite a
>>> lot of open PRs and that the plugin hasn’t been released for more than a
>>> year and half.
>>>
>>> Possibly it is bad timing because of the holiday season. However if this
>>> is not the case, CloudBees would be more than happy to provide help and
>>> support with keeping the plugin up to date and secure. We would like to
>>> request co-maintainership for the plugin, unless there are active plans to
>>> make a new release of the plugin.
>>> CloudBees see the S3 Plugin as being a critical plugin for Jenkins users
>>> that want to run their builds on AWS.
>>>
>>> Best regards.
>>>
>> --
> 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/66ff5cef-6cc6-44d4-984b-06e432dcc801%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/CANWgJS4jqJ3f_dgJAQnCXD3oFjLkAsGB6nf1xEdMgv1RWsM53g%40mail.gmail.com.

Re: Proposal: Jenkins funding page on CommunityBridge

[Oleg Nenashev]

Beta testing of the new funding page was approved at the yesterday's Governance 
Meeting , thanks to all for 
the feedback!
I will get the agreements implemented and report back once the reference 
implementation is ready.


On Friday, December 27, 2019 at 11:47:21 AM UTC+1, Ullrich Hafner wrote:
>
> +1
> I like the idea as well. 
>
> Am 26.12.2019 um 13:35 schrieb Oleg Nenashev  >:
>
> Hi all,
>
> I am working on the Jenkins donations page  
> update 
> at the moment (INFRA-2396 
> ), and I would like to 
> propose some changes there so that we can have a funding source once SPI 
> retires the Jenkins donations as a part of our transition to CDF. Jenkins 
> funding helps us to run outreach programs and to cover some infrastructure 
> costs, and as a board member I think it is really important to keep it 
> running and, ideally, to facilitate funding and using the money in the 
> project.
>
> *TL:DR:* Let's use CommunityBridge  as 
> a SPI replacement to raise funds. It is maintained by Linux Foundation, and 
> it is recommended for all projects within LF or sub-foundations like CDF. 
> Examples: CHAOSS , 
> Manjaro  or KiCAD 
> 
>  
>
> *Background.* Jenkins project operates thanks to contributions and 
> sponsorship (infra, meetups, swag, etc, etc.). Historically we did not have 
> high cash flows in the project, we mostly spend money on infra and on 
> outreach programs (swag, travel grants, Outreachy and Community Bridge in 
> 2019). Sponsorship covered the most of our "big" expenses (e.g. Azure, 
> meetup.com, contributor summits, etc.), but there is a tendency to 
> formalize such donations through CDF. Currently sponsorship through CDF is 
> a lengthy process not suitable for small donations, and it would be great 
> to have a simple process so that we can raise money to facilitate the 
> changes in the project.
>
> *Current state*
>
>- https://jenkins.io/donate/ documents the donations policy. 
>   - This page has not been updated for a while, working on it 
>   - This page basically designates donations to be consumed for 
>   Jenkins Infra, 
>   - There is an explicit statement that "Your contribution is not 
>   used for paying personnel.". Arguably, this is what we do for Outreachy 
> and 
>   CommunityBridge though stipend for outreach projects != salary
>- Jenkins uses SPI to accept donations. Soon SPI will no longer accept 
>donations to Jenkins due as a part of the transition to CDF. The exact 
> date 
>is TBD, but the decision has been already made in Spring 2019 as 
>communicated by Tracy Miranda
>- We also accept donations through ffis.de, but the status is unknown (
>WEBSITE-703  tracks 
>the investigation). It is also not clear whether they have Jenkins money 
> on 
>their accounts and how to access them
>- CommunityBridge Funding site 
> is enabled for 
>mentorship donations only as a part of Governance Meeting decisions in 
> July 
>2019). We used it to dry-run the JCasC Dev Tools project 
> this year, and it works 
>pretty well (except the SPI => LF transfer part which was the major 
>obstacle for the mentee payments).
>
>
> *Suggested changes*
>
>- Update "Your contribution is not used for paying personnel " to be 
>explicit that the Jenkins project might use money to sponsor limited-term 
>work on the project: outreach initiatives, addressing mission-critical 
>topics (e.g. INFRA needs) or facilitating projects required for the 
> Jenkins 
>future' (e.g. JCasC, Cloud Native Jenkins, etc.) 
>   - All such projects will need to be approved by the Governance 
>   meeting 
>   - The payments should be limited to reasonable amounts so that it 
>   is "facilitating contributions / mentorship" but not a fully-paid job. 
> E.g. GSoC 
>   stipends 
>    
> could 
>   be used as a reference
>- Enable CommunityBridge-based sponsorship for all available 
>categories: Development, Marketing, Meetups, Bug Bounty, Travel and 
>Documentation. We update documentation to mark it as a default donations 
>way.
>   - It will enable organization payments and also small monthly 
>   donations by individuals in the Patreon style. E.g. see CHAOSS 
>   , Manjaro 
>    or

Re: Proposal: Jenkins funding page on CommunityBridge

[Oleg Nenashev]

Beta testing of the new funding page was approved at the yesterday's Governance 
Meeting , thanks to all for 
the feedback!
I will get the agreements implemented and report back once the reference 
implementation is ready.


On Friday, December 27, 2019 at 11:47:21 AM UTC+1, Ullrich Hafner wrote:
>
> +1
> I like the idea as well. 
>
> Am 26.12.2019 um 13:35 schrieb Oleg Nenashev  >:
>
> Hi all,
>
> I am working on the Jenkins donations page  
> update 
> at the moment (INFRA-2396 
> ), and I would like to 
> propose some changes there so that we can have a funding source once SPI 
> retires the Jenkins donations as a part of our transition to CDF. Jenkins 
> funding helps us to run outreach programs and to cover some infrastructure 
> costs, and as a board member I think it is really important to keep it 
> running and, ideally, to facilitate funding and using the money in the 
> project.
>
> *TL:DR:* Let's use CommunityBridge  as 
> a SPI replacement to raise funds. It is maintained by Linux Foundation, and 
> it is recommended for all projects within LF or sub-foundations like CDF. 
> Examples: CHAOSS , 
> Manjaro  or KiCAD 
> 
>  
>
> *Background.* Jenkins project operates thanks to contributions and 
> sponsorship (infra, meetups, swag, etc, etc.). Historically we did not have 
> high cash flows in the project, we mostly spend money on infra and on 
> outreach programs (swag, travel grants, Outreachy and Community Bridge in 
> 2019). Sponsorship covered the most of our "big" expenses (e.g. Azure, 
> meetup.com, contributor summits, etc.), but there is a tendency to 
> formalize such donations through CDF. Currently sponsorship through CDF is 
> a lengthy process not suitable for small donations, and it would be great 
> to have a simple process so that we can raise money to facilitate the 
> changes in the project.
>
> *Current state*
>
>- https://jenkins.io/donate/ documents the donations policy. 
>   - This page has not been updated for a while, working on it 
>   - This page basically designates donations to be consumed for 
>   Jenkins Infra, 
>   - There is an explicit statement that "Your contribution is not 
>   used for paying personnel.". Arguably, this is what we do for Outreachy 
> and 
>   CommunityBridge though stipend for outreach projects != salary
>- Jenkins uses SPI to accept donations. Soon SPI will no longer accept 
>donations to Jenkins due as a part of the transition to CDF. The exact 
> date 
>is TBD, but the decision has been already made in Spring 2019 as 
>communicated by Tracy Miranda
>- We also accept donations through ffis.de, but the status is unknown (
>WEBSITE-703  tracks 
>the investigation). It is also not clear whether they have Jenkins money 
> on 
>their accounts and how to access them
>- CommunityBridge Funding site 
> is enabled for 
>mentorship donations only as a part of Governance Meeting decisions in 
> July 
>2019). We used it to dry-run the JCasC Dev Tools project 
> this year, and it works 
>pretty well (except the SPI => LF transfer part which was the major 
>obstacle for the mentee payments).
>
>
> *Suggested changes*
>
>- Update "Your contribution is not used for paying personnel " to be 
>explicit that the Jenkins project might use money to sponsor limited-term 
>work on the project: outreach initiatives, addressing mission-critical 
>topics (e.g. INFRA needs) or facilitating projects required for the 
> Jenkins 
>future' (e.g. JCasC, Cloud Native Jenkins, etc.) 
>   - All such projects will need to be approved by the Governance 
>   meeting 
>   - The payments should be limited to reasonable amounts so that it 
>   is "facilitating contributions / mentorship" but not a fully-paid job. 
> E.g. GSoC 
>   stipends 
>    
> could 
>   be used as a reference
>- Enable CommunityBridge-based sponsorship for all available 
>categories: Development, Marketing, Meetups, Bug Bounty, Travel and 
>Documentation. We update documentation to mark it as a default donations 
>way.
>   - It will enable organization payments and also small monthly 
>   donations by individuals in the Patreon style. E.g. see CHAOSS 
>   , Manjaro 
>    or

Re: Adopt a plugin request

[Oleg Nenashev]

Thanks for the ping!
I will do the permission transfer today

On Thursday, January 16, 2020 at 2:59:25 PM UTC+1, Terry Moreland wrote:
>
> Just posting a follow up on this request, it's now been over 2 weeks (with 
> some extra padding to accommodate the holiday period), As there is no 
> e-mail for the original maintainers account I've been unable to e-mail but 
> have mentioned @nbugash in 3 comments on the pull request to this 
> repository none of which have received any response.  I also attempted to 
> reach out via Linked-In profile but again no response.
>
> For reference this is for:
> jenkinsci:  https://plugins.jenkins.io/jenkinsci-appspider-plugin
> github:  https://github.com/rapid7/jenkinsci-appspider-plugin
> pull request: https://github.com/rapid7/jenkinsci-appspider-plugin/pull/5
> github id: tsmoreland
> jenkins id: tmoreland
>
>
> On Friday, 20 December 2019 09:15:41 UTC, Terry Moreland wrote:
>>
>> I've also added a comment to the current pull request pinging his 
>> personal github account which is the one he associated with the plugin.  As 
>> of yet no reply either there or via linked in
>
>

-- 
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/674d4170-efef-4fda-a415-9466c2ffb224%40googlegroups.com.

Re: Adopt a plugin request

[Terry Moreland]

Just posting a follow up on this request, it's now been over 2 weeks (with 
some extra padding to accommodate the holiday period), As there is no 
e-mail for the original maintainers account I've been unable to e-mail but 
have mentioned @nbugash in 3 comments on the pull request to this 
repository none of which have received any response.  I also attempted to 
reach out via Linked-In profile but again no response.

For reference this is for:
jenkinsci:  https://plugins.jenkins.io/jenkinsci-appspider-plugin
github:  https://github.com/rapid7/jenkinsci-appspider-plugin
pull request: https://github.com/rapid7/jenkinsci-appspider-plugin/pull/5
github id: tsmoreland
jenkins id: tmoreland


On Friday, 20 December 2019 09:15:41 UTC, Terry Moreland wrote:
>
> I've also added a comment to the current pull request pinging his personal 
> github account which is the one he associated with the plugin.  As of yet 
> no reply either there or via linked in

-- 
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/556b5b85-b8bf-4f58-ac7d-93c51e174cf7%40googlegroups.com.

Jenkins 2.204.2 LTS RC testing started

[Oliver Gondža]

Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Final 
release is scheduled for 2020-01-29.


Please, report your findings in this thread.

Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.204.2/jenkins.war


Thanks!
--
oliver

--
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/88d47b08-44b6-47cb-bc6d-fd059e5ec7cf%40gmail.com.

Re: Re: Governance meeting on Jan 01. Should we cancel it and reschedule next meetings?

[Oleg Nenashev]

Update from the yesterday's governance meeting 

.
We decided to keep the current time for now, the voting in 
https://doodle.com/poll/pq2g45anu92yz2b8 is still open if somebody wants to 
get the meeting time changed


On Monday, December 30, 2019 at 3:09:37 PM UTC+1, Peter Rader wrote:
>
> Sorry, wrong mail folder ;D
>  
> Kind regards
>
> Peter Rader
> --
> Fachinformatiker AE / IT Software Developer
> Peter Rader
> Wilsnacker Strasse 17
> 10559 Berlin - GERMANY
> Tel: 0049 (0)30 / 20 9930560
> Fax: 0049 (0)30 / 20 9930561
> Handy: 0049 (0)176 / 8 7521576
>   
>   
> *Gesendet:* Montag, 30. Dezember 2019 um 15:08 Uhr
> *Von:* "Peter Rader" >
> *An:* jenkin...@googlegroups.com 
> *Betreff:* Aw: Re: Governance meeting on Jan 01. Should we cancel it and 
> reschedule next meetings?
> Prov Gov is not! Neither Parl. meeting nor Exord. Nxt Exord is in June.
>  
> Kind regards
>
> Peter Rader
> --
> Fachinformatiker AE / IT Software Developer
> Peter Rader
> Wilsnacker Strasse 17
> 10559 Berlin - GERMANY
> Tel: 0049 (0)30 / 20 9930560
> Fax: 0049 (0)30 / 20 9930561
> Handy: 0049 (0)176 / 8 7521576
>   
>   
> *Gesendet:* Montag, 30. Dezember 2019 um 12:15 Uhr
> *Von:* "Oleg Nenashev" >
> *An:* "Jenkins Developers" >
> *Betreff:* Re: Governance meeting on Jan 01. Should we cancel it and 
> reschedule next meetings?
> OK, let's cancel the meeting then. 
>
>- Agenda for Jan 15: 
>
> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.vylsknw2s91m
>  . 
>I suggest we meet at 6PM UTC as usual so that we approve the meeting time 
>change 
>- Doodle for the new meeting slots: 
>https://doodle.com/poll/pq2g45anu92yz2b8 .  
>   - I have selected timeslots with EMEA/Americas and APAC/Americas 
>   overlap. Since we have 2 board members in EMEA now, in the future we 
> could 
>   consider running meetings in another timezone on-demand 
>
> BR, Oleg
>
> On Monday, December 30, 2019 at 11:48:18 AM UTC+1, Ullrich Hafner wrote: 
>>
>> Yes, +1 for the next meeting on 15th.  
>>  
>> I think it makes sense to set up a doodle for a better time on Wednesday. 
>>  
>>   
>>
>> Am 29.12.2019 um 17:01 schrieb Marky Jackson :
>>   
>> I am +1 on canceling 
>>   
>>
>> On Dec 29, 2019, at 7:48 AM, Oleg Nenashev  wrote:
>>   
>> Hi all, 
>>  
>> the next governance meeting is scheduled to Jan 1st. I suggest cancelling 
>> it, because there is no urgent topics in the agenda. Jan 15th would be the 
>> next meeting then. The next meeting would be Jan 15th then
>>  
>> Regarding the next meetings, we could run Doodle to find a new time if 
>> the current one (6PM UTC on Wednesdays) is not convenient to 
>> contributors who are interested to participate in the Governance meetings. 
>> Current time is not ideal for Europe, and barely suitable for the APAC 
>> region. If anyone wants the meeting to be rescheduled, please respond to 
>> this thread.
>>  
>> Best regards,
>> Oleg
>>  
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkin...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCZUZafm_78trRvGVE2TdE70kJe3NVUDxMBRkrx-nW-8Q%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 jenkin...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/EDB02FAD-5670-4966-8DFD-A56DF5CACB10%40gmail.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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/ad2b0bff-533c-42b2-b469-4ef0932a9e11%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 jenkin...@googlegroups.com .
> To view this discussion on the web 

Re: JAMS in meetup account disappearing

[Oleg Nenashev]

Just a quick update here, yesterday both topics were approved by the 
Governance board:

   - Approve the suggested process in general && delegate the final process 
   decision to the event officer and Advocacy and Outreach SIG 
   (immediate/short-term stepdown for meetups which never happened, grace 
   period for stale ones)
   - Approve archiving of jenkinsci-jam and events mailing lists mailing 
   lists in favor of Advocacy & Outreach channels

We will proceed at Advocacy&Outreach SIG meeting on 16th 

 with 
these topics

Best regards,
Oleg

On Wednesday, January 15, 2020 at 11:02:09 AM UTC+1, ogondza wrote:
>
> +1 from me on doing the cleanup. Meetup groups come and go. Great to see 
> a documented way to gring them back to life. 
>
> On 14/01/2020 14.59, Oleg Nenashev wrote: 
> > Thanks a lot for the notice Alyssa! 
> > 
> > If my message is too long, *TL;DR: *the meetups will be restored, but it 
> > is time to clean up the inactive meetups. There is a proposal below 
> > 
> > Some updates there: 
> > 
> >   * As communicated by Tracy, the root cause is that meetup.com support 
> > removed more meetups than it was requested by CDF. 
> >   * Last week we had a meeting with CDF where we discussed the issue. 
> > Participants: Alyssa Tong (Jenkins Event Officer), Jacqueline 
> > Salinas (Director of Ecosystem, CDF), Tracy Miranda and me 
> >   * At this meeting we agreed that: 
> >   o Removed meetups meetups will be restored. It will take a while 
> > since it is a lengthy manual process by meetup.com support 
> >   o CDF will grant us an additional grace 3-month grace period to 
> > try restoring inactive meetups in the Jenkins community (and/or 
> > to convert them to CI/CD meetups). Heads-up about cleaning up 
> > inactive meetups was sent out on *Oct 26* to meetup organizers, 
> > so we will need to reimplement the process and do additional 
> > communications 
> >   o If meetups are not restored, CDF will use the "step down" 
> > process 
> > <
> https://help.meetup.com/hc/en-us/articles/360002882191-Stepping-down-as-the-organizer-of-a-group>
>  
>
> > instead of deleting the meetups. It will give the local 
> > communities an additional chance to restore the meetups 
> > 
> > Just to explain the reasons of the Jenkins Area Meetups cleanup: 
> > 
> >   * Running CI/CD Pro Meetup.com account 
> >  costs *12k USD per quarter*. 
> > The majority of these costs used to go to *106 *Jenkins Area Meetups 
> >   * CDF has a limited budget for Outreach programs and meetups. They are 
> > happy to sponsor active meetups, but in the case of Jenkins we 
> > accumulated a number of inactive ones 
> >   * Meanwhile, more than 60% of the meetups are dormant. Inactive 
> > meetups cost the same amount of money as active ones 
> >   o *27* JAMs groups have NEVER had a meetup on meetup.com 
> >   o *40* other JAMs did not have any events organized in 2019 
> >   * Dormant JAMs prevent CDF from... 
> >   o Sponsoring swag/food/venue for meetups and other events 
> >   o Onboarding new CI/CD and Jenkins meetups in active local 
> communities 
> >   o Organizing other events and running outreach programs 
> > 
> > So you may see there is a good reason to cleanup meetups which are 
> > really inactive. Some of us might be mentally attached to these meetups 
> > (e.g. I was a co-org in several removed meetups), but IMO we need to 
> > face the reality and adjust our meetup program. I would suggest the 
> > following process: 
> > 
> >  1. Wait till meetups are restored 
> >  2. Do a best effort attempt to revive the meetups 
> >   * Communicate the incoming deprecation/cleanup of meetups AGAIN to 
> > meetup organizers and all meetup members 
> >   * For meetups that never happened 
> >   o CDF steps down 
> > <
> https://help.meetup.com/hc/en-us/articles/360002882191-Stepping-down-as-the-organizer-of-a-group>
>  
>
> > as an organizer immediately after the meetup recovery. 
> > Current meetup leaders can take it over. If it does not 
> > happen, all meetup members will have 2 weeks to react and 
> > take over the meetups 
> >   o If reactivated, meetups can rejoin again by following the 
> > process defined by CDF <
> https://github.com/cdfoundation/meetups> 
> >   * For meetups with at least one event in the past 
> >   o 3-month grace period is applied 
> >   o During this period we will try to contact meetup organizers 
> > and members through community channels and get the meetups 
> > scheduled 
> >   o If there are no meetups happen/get announced, CDF steps down 
> >   

Re: Proposal: Implementing sensible fine grained permissions to allow an administer to securely delegate some aspects of jenkins configuration

[Daniel Beck]

On Wed, Jan 15, 2020 at 9:00 PM Matt Sicker  wrote:

> Plugins that contribute to the settings on on the Configure Jenkins page
>> should carefully consider if allowing a user with only Jenkins.CONFIGURE
>> could result in an unintended privelege escalation.
>>
>
> To me, this sounds like a fairly onerous requirement for plugins. Based on
> the numerous published security advisories just around plugins not
> bothering with a permission check in the first place, this sounds like a
> fairly large hole. How could we mitigate that?
>

The difference is that much of that comes from bad (permissive) defaults.
This would be opt-in, and with good documentation about security
considerations, plugin maintainers will be given the tools to understand
whether it makes sense to make this available, or 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/CAMo7PtL5X07BBvtorwR5t8%3DO%3D8mHdGkkX79YqKYrMixoF7yLrw%40mail.gmail.com.

Re: Happy Holiday

[Daniel Beck]

On Wed, Jan 15, 2020 at 8:58 PM Joseph P  wrote:

> Here's a crazy thought, use GitHub?
>
> It's a matter of creating appropriate repos and using GitHub issues / pull
> requests.
>
> For announcement see
> https://github.com/dotnet/announcements/issues
>
> if you need some structure create a repo with the desired content
> structure.
>
> GitHub can get pretty chatty.
> If your discussing a persisted topic, create pull request, add a review to
> the topic line and let the thread messaging commence 🥰👏
>

https://en.wikipedia.org/wiki/Law_of_the_instrument ?


> If you need to chat with your team? Create proper team structure and use
> GitHub Team Discussion (which atm is currently disabled in most teams
> https://github.com/orgs/jenkinsci/teams/core )
>

Disabled for the entire org, because I consider per-repo teams to be
ephemeral due to quite a bit of cleanup I did a while back.

-- 
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/CAMo7Pt%2BkNAxeouFnkD-HmGVadJbTcB%2BW7XixC3HANX%3D2o3%3DrhQ%40mail.gmail.com.