Apply to Docker Open Source Program

[lemeurherve]

To avoid being rate limited in our pipelines, we should apply to Docker Open Source Program in order to benefit from unlimited pulls and unlimited egress.

https://www.docker.com/blog/expanded-support-for-open-source-software-projects/

https://www.docker.com/community/open-source/application/

Docker is committed to supporting the Open Source community. The Docker Open Source Program provides a platform to help non-commercial open source developers continue to collaborate, innovate and push their projects forward.

For your project namespace on Docker Hub, Docker offers unlimited pulls and unlimited egress to any and all users, with no egress restrictions applying to any Docker users pulling images from that namespace. In addition, if your project uses Autobuild capabilities, you can continue using them for free. You are also free to continue to use Docker Desktop via the Docker Personal subscription.

Qualification Criteria

To qualify for the program, your project namespace:

• Must be shared in public repos.
• Is not funded by a commercial company or organization.
• Meets the Open Source Initiative definition (defined here), including definitions for Free distribution, source code, derived works, integrity of source code, licensing and no tolerance for discrimination Distributes images under an OSI approved open source license.

Originally posted by @lemeurherve in #2837 (comment)

[timja]

I thought we already had this, cc @olblak

[olblak]

yes we are in

[dduportal]

We are, but which account ? Jenkinsciinfra ? (Because i’m almost sure that jenkins4eval i ms not)

[olblak]

I am forwarding the email thread to @dduportal and @lemeurherve

[timja]

just the jenkins org I think

[dduportal]

Additional point: I assume that any "open source subscription" allow to generate DockerHub APi token with the read-only mode, is that correct?

[timja]

no idea, I couldn't see anything on the org that showed it tbh

[olblak]

And when I asked, They told me that we couldn't see it on our side

[olblak]

All we see is from the default free plan

[dduportal]

• Application form filled for the jenkinsciinfra and jenkins4eval org (it did not exist back in 2020) to provide a "normal process" and "numbers" to Docker Inc.
• Tried to contact the person that @olblak exchanged with in Nov. 2020 but this person does not work for Docker anymore (cced the private mailing list jenkins-infra-team)
• Asked someone at Docker that I know if this is the "standard" procedure

[dduportal]

For information, found some key issues on the DockerHub public roadmap:

• [Docker Hub] Official REST API docker/roadmap#20 (comment)
• Fine grained permission/scopes on personal access token docker/roadmap#115
• feature request: provide way to update a repo's description and full_description docker/hub-tool#172
• [Docker Hub] Support more granular access tokens docker/roadmap#165

[timja]

jenkins4eval has been around a long time (i.e. pre 2020) and is not used much

[dduportal]

jenkins4eval has been around a long time (i.e. pre 2020) and is not used much

Yes, but if under the open source program umbrella, it would be the perfect org. to provide read-only token for different users (to be used for docker pulls), avoiding to create addition accounts

[dduportal]

OK, good news, I was able to get another contact at Docker Inc.. Email sent with the jenkins-infra-team (private) mailing list in Cc.

[dduportal]

Update:
We had email exchanges + an interview with Sharon Chang and Britney Blodget at Docker Inc..

• The organizations jenkins4eval and jenkinsciinfra are accepted to be part of the Open Source Program
• ETA undefined, as Docker Inc. is going through a major conference (DockerCon) + program revamp for Open Source, so it slows down their ability to add us, but it's ongoing and should happen soon
• They are REALLY interested in a blog post about "BuilldX Bake".

[dduportal]

• Closing this issue has we are now part of the Open Source Program. It gives us the following benefits:
  • Labelled as "Open Source Program"
  • All the images from these organisations (jenkinsci, jenkinsciinfra and jenkins4eval) are not counted in consumer's API rate limits, including ourselves: it removes the risks for ci.jenkins.io to break due to pod agents being rate limited.
• Though, the Open Source program does NOT solve the following issues:
  • API Rate limit for the builds using Docker on ci.jenkins.io, because these builds are pulling the official images for our base images, which ARE rate limited: following up in DockerHub rate limiting #2961
  • More than 3 user seats per organization (which means only 2 humans with 2 MFA and 1 technical user).