Re: License for library plugins

[Olivier Lamy]

Regarding Apache librairies this can be anything but maybe better to
stick with original license if possible.

Please note for trademark reasons, the real name to use when
mentioning Apache software is not commons-foo but Apache commons-foo
Furthermore, it would be nice to include the LICENSE file in the
distributed hpi. I can't see it

unzip -l commons-text-api-1.11.0-95.v22a_d30ee5d36.hpi
Archive:  commons-text-api-1.11.0-95.v22a_d30ee5d36.hpi
  Length  DateTimeName
-  -- -   
0  12-05-2023 16:35   META-INF/
 1082  12-05-2023 16:35   META-INF/MANIFEST.MF
0  12-05-2023 16:35   WEB-INF/
0  12-05-2023 16:35   WEB-INF/lib/
0  12-05-2023 16:35   META-INF/maven/
0  12-05-2023 16:35   META-INF/maven/io.jenkins.plugins/
0  12-05-2023 16:35
META-INF/maven/io.jenkins.plugins/commons-text-api/
   246659  12-05-2023 16:35   WEB-INF/lib/commons-text-1.11.0.jar
 2622  12-05-2023 16:35   WEB-INF/lib/commons-text-api.jar
  947  12-05-2023 16:35   WEB-INF/licenses.xml
 2362  12-05-2023 16:35
META-INF/maven/io.jenkins.plugins/commons-text-api/pom.xml
   88  12-05-2023 16:35
META-INF/maven/io.jenkins.plugins/commons-text-api/pom.properties
- ---


It's in the git repo, but it is not included in the distribution,
which is usually a good idea when redistributing Apache software or
even in this case, when the repackaging is under Apache license.



On Tue, 12 Dec 2023 at 05:50, Basil Crow  wrote:
>
> Library plugins are inconsistently licensed: sometimes, they adopt the
> license of the wrapped library, while in other cases, they follow the
> MIT license as normally used by Jenkins plugins. Does anybody have a
> preference as to what we should recommend?
>
> --
> 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/CAFwNDjrSPdWJFoJpxx3YtyqKuQ7r49Cai30mfvXg1yUP2CcFQw%40mail.gmail.com.

-- 
Olivier

-- 
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/CAPoyBqR28zvbzOKQnBrJ8vhWy5nifPYbRKhJQFrgjhfqTjw_rA%40mail.gmail.com.

Re: Artifactory brownout Wed 6 Dec 2023 1:00 PM UTC - 3:00 PM UTC

[Basil Crow]

+1, I think we have done all the preparation we can for this change.

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

Re: Artifactory brownout Wed 6 Dec 2023 1:00 PM UTC - 3:00 PM UTC

[Mark Waite]

On Monday, December 4, 2023 at 7:22:51 AM UTC-7 Mark Waite wrote:

The Jenkins infrastructure team will remove the jcenter and jcenter-cache 
repositories from the definition of the `*public*` virtual repository 
 as part of the effort to 
reduce bandwidth consumption by repo.jenkins-ci.org.

We will perform a two hour "brownout" test Wednesday December 6, 2023 from 
1:00 PM UTC to 3:00 PM UTC.  During that two hour period, the jcenter and 
jcenter-cache repositories will not be included in the public virtual 
repository.  At the end of the two hour brownout, we will insert the 
jcenter and jcenter-cache repositories into the public virtual repository 
again.

During the brownout, we'll perform specific tests as described in help desk 
ticket 3842 .  The 
Jenkins infra team will be performing those tests.  If others would like to 
join the tests, they are welcome to comment in the Jenkins infra chat 
channel .

After the brownout is complete, we'll analyze the results.  If the results 
show no failures, we'll plan to implement the production change next week.  
If the results show failures, we'll resolve the failures and plan for a 
second brownout to confirm that the failures are resolved.


The brownout was a success.  It showed us a few changes that we need to 
make and it confirmed that we're on the right path.

Changes to be made:

   - Add a cache of the Atlassian open source public repository 
    to the 
   public virtual repository so that Jenkins plugins can access the open 
   source Jira integration libraries used in plugins like the Jira plugin.  
   This can be done immediately
   - Remove the jcenter and oss.sonatype.org-releases repositories from the 
   public virtual repository so that Maven Central is used for artifacts 
   provided by Maven Central.  This will be done on Friday

I believe that those are small enough changes that we don't need a second 
brownout to test them.

I propose that we make the production change this Friday at about 2:00 PM 
UTC.  I'll check with the Jenkins infrastructure team tomorrow to confirm 
that Friday works with their schedule.

If the change surprises us with issues,  we'll revert the change and try 
again next week.

Mark Waite
 

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

License for library plugins

[Basil Crow]

Library plugins are inconsistently licensed: sometimes, they adopt the
license of the wrapped library, while in other cases, they follow the
MIT license as normally used by Jenkins plugins. Does anybody have a
preference as to what we should recommend?

-- 
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/CAFwNDjrSPdWJFoJpxx3YtyqKuQ7r49Cai30mfvXg1yUP2CcFQw%40mail.gmail.com.

December 11, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 7:00 PM UTC (about 6 hours from now).  
Zoom link is 
https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Here is the draft agenda:

Upcoming Calendar 
   
   - Next LTS: 2.426.2, December 13, 2023
  - Kris Stern is the release lead, backporting pull request 
   submitted
  - Release candidate delivered Wednesday November 29, 2023
   - Next weekly release: 2.436
   - Two week break in LTS schedule: 2.426.3, January 24, 2024 (6 weeks 
   after 2.426.2 instead of the usual 4 weeks)
  - Refer to developer mailing list discussion 
   
for 
  details
  - No break expected in weekly release schedules
   - Next major events:
  - FOSDEM 2024 - February 2-4, 2024
 - Jenkins Contributor Summit Friday February 2, 2024
- Jean-Marc Meessen collecting agenda topics in community forum 


 - FOSDEM conference Saturday and Sunday February 3-4, 2024
  
AgendaAction Items
   
   - Basil create the attribution entries for the downloads page
   - Damien create issue to switch agent implementation to virtual machines 
   (*done*)
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023 (*done*)
  - Timeline
 - Blog post 
 
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
   - Retire the Chinese Jenkins site (Kevin Martens)
  - Kevin has started his local Kubernetes development environment to 
  prototype the transition
  - Mark still needs to start his local Kubernetes development 
  environment to prototype the transition
  - Once prototyped, then Kevin and Mark meet with Damien Duportal to 
  review next steps
  - Kevin Martens (Docs Officer) tracking help desk ticket 
   to replace 
  the Chinese pages with redirects to the English pages
 - Kevin working with the infrastructure team on the Helm charts 
 implementing the Chinese site
  - Mark Waite draft a proposal to the board for license policy and 
   phrasing changes
  - Basil submitted a governance document pull request 
   to accept 
  public domain licenses
 - Board approval of the addition of public domain licenses to the 
 governance document
 - Allows the public domain json library and others to be used
  - What license should be used for a library plugin?
 - License of the wrapped library (if wrapped library has no 
 separate code, then seems likely)
 - MIT license as used by Jenkins plugins (if abstraction layer in 
 the plugin, then MIT for ours?)
  - Review responses from other projects to license mixture (e.g. PyPI)
 - Mostly focuses on OSI approved licenses but include a separate 
 category for other licenses
- Have categories for freeware, public domain, and more
- Reasonable precedent for allowing a wider range of licenses
- Needs more discussion, but being more permissive is working 
for PyPI
- Newer licenses may be more controversial
 
Community activity
   
   - 
   
   Jenkins contributor spotlight  - Kevin 
   Martens
   - Thanks to Kevin Martens, Kris Stern, Herve Le Meur, Cristina 
  Pizzagalli, and Alyssa Tong
  - Source repository 
  
  - Upcoming contributors to be highlighted
 - Alex Earl 
  - 
 Dec 13, 2023
 - Kris Stern 
  - 
 Dec 27, 2023
 - Ulli Hafner 
 
  - 
   
   Artifactory bandwidth reduction project - Mark Waite
   - 20 TB of bandwidth used in November, 1/3 due to cached artifacts from 
  Apache Maven Central
 - JFrog has asked that we remove the cached artifacts from the 
 Jenkins public virtual repository
  - Artifactory brownout 
   
last 
  Wednesday 6 Dec 2023
 - Jenkins core build passed during brownout
 - Repository permissions updater build failed during brownout due 
 to missing Atlassian Jira integration library
 - Top 250 most 

Re: bitbucket-plugin - why didn't my PR got released

['Jesse Glick' via Jenkins Developers]

On Sun, Dec 10, 2023 at 12:09 PM Mark Waite 
wrote:

> Apply the label to the existing pull request and then run the cd action
> from the "Actions" menu of the repository.
>
> That's worked for me in the past.
>

Please update
https://www.jenkins.io/doc/developer/publishing/releasing-cd/#releasing if
anything seems to be missing or unclear.

-- 
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/CANfRfr0G-%2BZOtN_1eKBhsNRxKwJZwnE0oEV-QNQbRd3pmy_C_A%40mail.gmail.com.