|
Marc Johnson 2 hours ago
> It would be kind of nice to have old images pruned automatically, but of course some module images may not change often enough, especially as we get more stable.
That could have implications for the reproducible builds of older quarterly releases.
Once FOLIO decides upon it's long term support model, it is likely that some releases will remain valid for at least a year and more likely multiple years. (edited)
Peter Murray 2 hours ago
Oh, good point.
Wayne Schneider 2 hours ago
Right. And if we publish module descriptors that refer to old images, that's also kind of breaking an implied contract.
Marc Johnson 1 hour ago
We may well want a curation process for removing old module version artefacts.
We may not want a third party doing part of that on a different timeframe to what FOLIO needs.
Peter Murray 6 minutes ago
I can look into getting something beyond the Free plan. It sounds like we are going to need it for our long-term-support versions of FOLIO.
|
|
Sent to Docker:
Do you offer discount or /gratis/ Docker Hub pricing for open source projects?
The FOLIO Projects is part of the Open Library Foundation (www.openlibraryfoundation.org). We are a community of libraries and service providers that build open source tools that enhance service offerings for libraries and library consortia. FOLIO (hub.docker.com/u/folioorg and hub.docker.com/u/folioci) makes extensive use of Docker containers as part of its microservices architecture. Our release structure (wiki.folio.org/display/TC/FOLIO+Release+Numbering+Policy) specifies long-term-support releases that go beyond the 6 month retention policy in the recently announced update to the terms of service.
I would welcome the opportunity to talk to someone about options for the FOLIO project and other projects that are a part of the Open Library Foundation.
|
|
Receive from Docker:
Hello,
Docker offers numerous free services to our growing community of users and will continue doing so in the future. In order to scale this, we are making two policy updates in our terms of service. You’re receiving this email so that you’re aware of these updates, as they may impact you.
The first policy update is regarding retention of inactive images. Starting November 1, 2020:
- Free accounts may retain inactive images for up to 6 months
- Pro and Team subscriptions may retain inactive images indefinitely
The second policy update is regarding limits on the number of image pulls in a six-hour period. Again, starting November 1, 2020:
- Free accounts, intended for individual developers, will have an upper limit on the number of image pulls in a six-hour period
- Pro and Team subscriptions do not have limits
For details please see the FAQ and our recent blog posts regarding inactive image retention and pull rate limits.
If you have a free account you may upgrade to a Pro or Team subscription here.
The updated Docker Terms of Service are available here.
Thank you for using Docker.
|
|
Notable bits:
What is an “inactive” image?
An inactive image is a container image that has not been either pushed or pulled from the Docker Hub image repository in 6 or more months.
How can I view the status of my images?
Within a Docker Hub repository, each tag (and the latest image linked to the tag) has a “Last pushed” date that can easily be accessed in the Repositories view when logged into your account. A new dashboard will also be available in Docker Hub that offers the ability to view the status of all images in all repositories within your account, including the most recent tag and any previous versions of a tag. Account owners will also be notified by email of “inactive” images that are scheduled for deletion.
What will happen to inactive images once the expiration date is reached?
Beginning November 1, 2020, any images that are marked as “inactive” will be scheduled for deletion. Account owners will also be notified by email of “inactive” images that are scheduled for deletion.
Will Docker offer dedicated plans for open source projects?
Yes, as part of Docker’s commitment to the open source community, we will be announcing the availability of new open source plans. To apply for an open source plan, complete our application at: https://www.docker.com/community/open-source/application.
I'm in the process of applying for the open source plans for the OLF projects.
|
|
Resubmitted the FOLIO organization to Docker via their Google Form.
|
|
Got this back from Docker over the weekend.
Congratulations! After reviewing your submission for the Docker Open Source Community Application, we are pleased to inform you that we are moving forward with your application. We appreciate your taking the time to fill out this application, and apologize that it has taken us this long to get back to you. The policies that we announced in August will create a significant impact for the entire Docker community, and we thank you for your patience as we went through the process of learning how these policies affect the different cohorts within our community.
Docker New Image Retention and Data Egress Policies
In August, we announced to our dedicated community that we are creating new policies for image retention and data pull rates. We made these changes to make Docker a sustainable business for the long term, so that we can continue supporting the community and ecosystem that depends on the Docker platform. We got great feedback from our extensive user base, and adjusted our policies to suspend the policies on image retention. The plan for data pull rates is moving forward, and starting on Nov 2 -
- Unauthenticated users will be restricted to 100 pulls every 6 hours
- Authenticated free users will be restricted to 200 pulls every 6 hours
Docker Open Source Policy
Docker remains highly committed to providing a platform where the non-commercial open source developers can continue collaborating, innovating and pushing this industry into new directions. For the approved, non-commercial, open source namespaces, Docker will suspend data pull rate restrictions, with no egress restrictions applying to any Docker users pulling images from those namespaces
Open Source Qualification Criteria
To qualify for the Open Source Project status, all the repos within the Publisher’s Docker namespace must -
- Be non-commercial
- Meet 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
- Be distributed through public repos
- Distribute images under OSI approved open source license
- Produce Docker images used to run applications
Review and Approval
The process for applying for Open Source status is summarized below -
- The Publisher submits the Open Source Community Application form.
- Docker reviews the form, and determines if the Publisher qualifies for open source status.
- If the Partner qualifies, Docker will waive the pull rate policy for the Publisher’s namespace, for a period of one year
- Every 12 months, Docker will review if the Publisher’s namespace qualifies with the Docker Open Source project criteria, and extend the Open Source project status for another 12 months.
- Docker may, at its discretion, also review eligibility criteria within the 12-months period
- The publisher may have other namespaces, that either partially comply or do not comply with open source policy requirements, and therefore, will not qualify for open source status
Joint Marketing Programs
While the publisher retains the Open Source project status, the Publisher agrees to -
- Become a Docker public reference for press releases, blogs, webinars, etc
- Create joint blogs, webinars and other marketing content
- Create explicit links to their Docker Hub repos, with no ‘wrapping’ or hiding sources of their images
- Document that Docker Engine or Docker Desktop are required to run their whitelisted images
- Give Docker full attribution
Please let me know if you have any questions on anything in this letter.
Please reply to this email if your open source project complies with the above criteria, and if you would like to move forward with your Docker Open Source Project.
Thank you for all your support for Docker and the Docker community.
|
|
Wrote back:
From: Peter Murray <peter.murray@openlibraryfoundation.org>
Date: Nov 2, 2020, 3:34 PM -0500
To: Marina Kvitnitsky <opensource@docker.com>
Subject: Re: Welcome to Docker Open Source Program
Hello! I can confirm that https://hub.docker.com/u/folioorg and https://hub.docker.com/u/folioci meet the criteria and we are happy to participate in the joint marketing programs. I have already added Docker to the FOLIO Project's "Thanks" page (https://dev.folio.org/about/thanks/).
|
|
We're in!
From: Marina Kvitnitsky <marina.kvitnitsky@docker.com>
Date: Nov 3, 2020, 8:54 PM -0500
To: Peter Murray <peter.murray@openlibraryfoundation.org>
Subject: Re: Welcome to Docker Open Source Program
Hello Peter,
Congratulations! We have added your namespaces, folioorg and folioci, to the Docker Open Source program. folioorg and folioci are now whitelisted namespaces, which means that all Docker users can pull images from there, without the limits of new Docker data pull rates.
Thank you for adding us to your Attribution page. We look forward to working with you
Please let me know if you have any questions about Docker Open Source policies, and check our blog for more details about this program.
Many thanks,
Marina
|
Generated at Thu Feb 08 23:22:45 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.