Hey, Considering that the Dockerhub sponsoring way is ongoing, I didn't pay for anythin and I prepare to wait few days. So if something goes wrong, we know where to look
On Sat, Oct 31, 2020, at 9:14 AM, 'Olblak' via Jenkins Infrastructure wrote: > Hi Everybody, > > It seems that things are moving positively for us on the sponsoring program > side. I just received this email from Docker. > Obviously I asked to move forward with our application but at this stage, I > don't know when it will be effective. > > Anyway I am going to do some clean up in the Dockerhub organisation member. > > Cheers > > >> Hello Olivier, >> >> 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 >> <https://www.docker.com/blog/scaling-dockers-business-to-serve-millions-more-developers-storage/> >> and data pull rates >> <https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/>. >> 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 >> <https://www.docker.com/blog/docker-hub-image-retention-policy-delayed-and-subscription-updates/> >> 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 >> <https://opensource.org/docs/osd>), 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 >> <https://opensource.org/licenses/alphabetical> >> * 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 >> <https://www.docker.com/community/open-source/application>. >> * 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. >> >> Many thanks >> William Quiviger >> Sr. Community Relations Manager > > > On Fri, Oct 30, 2020, at 4:09 PM, Baptiste Mathus wrote: >> LGTM. I'm not active anymore on the infra side these days. >> >> Thanks >> >> On Fri, Oct 30, 2020 at 2:58 PM Tim Jacomb <timjaco...@gmail.com> wrote: >>> Fixing infra mailing list cc >>> >>> On Fri, 30 Oct 2020 at 13:57, Tim Jacomb <timjaco...@gmail.com> wrote: >>>> +1 >>>> >>>> On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers >>>> <jenkinsci-dev@googlegroups.com> wrote: >>>>> Hi Everybody, >>>>> >>>>> The Dockerhub policy change start on Sunday unfortunately I couldn't make >>>>> significant progress on this. >>>>> Either by being sponsored by Docker or having a proper way to be >>>>> reimbursed by LF. >>>>> >>>>> I would like to pay (be reimbursed) for at least the first month and >>>>> remove the none critical people in order to reduce the cost. >>>>> >>>>> I would remove the following people: >>>>> * Kohsuke Kawaguchi >>>>> * Nicolas Deloof >>>>> * Baptiste Mathus >>>>> * Tyler Croy >>>>> * Carlos Sanchez >>>>> * Jesse Glick >>>>> * Michael Neale >>>>> * Oliver Gondza >>>>> >>>>> Cheers >>>>> >>>>> -- >>>>> 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 >>>>> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/5804a3e6-ebf2-4707-9824-90eb02fcc6ad%40www.fastmail.com. >>> >>> -- >>> 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-3BifxsfSmBo2K%3D1T5whoHTsBQ0Ts3EpnZXHHrqgZkvFVfjQ%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkins-infra/CAH-3BifxsfSmBo2K%3D1T5whoHTsBQ0Ts3EpnZXHHrqgZkvFVfjQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. >> >> -- >> 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/CAPyTVp07Po2su%2B-DSc2G52-gF97NPXL8aoymjbv1%3DT%3DnNcjUGQ%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkins-infra/CAPyTVp07Po2su%2B-DSc2G52-gF97NPXL8aoymjbv1%3DT%3DnNcjUGQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. > > > -- > 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/56f9d6b1-2e6e-4062-a841-3b2ad928066d%40www.fastmail.com > > <https://groups.google.com/d/msgid/jenkins-infra/56f9d6b1-2e6e-4062-a841-3b2ad928066d%40www.fastmail.com?utm_medium=email&utm_source=footer>. -- 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/950effd9-d9c5-494c-ba31-52dfea021e8f%40www.fastmail.com.
