Paying for Dockerhub pro plan

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Paying for Dockerhub pro plan

Olblak-2
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5804a3e6-ebf2-4707-9824-90eb02fcc6ad%40www.fastmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Paying for Dockerhub pro plan

Tim Jacomb
+1

On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieEdCXfZmp%2Bt2p3fHU_O9YNeY--%3DkCgZ0%2BcBLTu24HqXw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Paying for Dockerhub pro plan

Tim Jacomb
Fixing infra mailing list cc

On Fri, 30 Oct 2020 at 13:57, Tim Jacomb <[hidden email]> wrote:
+1

On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifxsfSmBo2K%3D1T5whoHTsBQ0Ts3EpnZXHHrqgZkvFVfjQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Paying for Dockerhub pro plan

Oleg Nenashev
+1 for removing the listed contributors, they have not been working on Jenkins Docker images recently. We can add other contributors back later if needed.

>  I would like to pay (be reimbursed) for at least the first month 

Could you please provide a cost estimation so that we could approve it in the mailing list? AFAIK the cost is pretty low, and I do not see a problem if it is below 100 USD per momth.

Best regards,
Oleg




 


On Friday, October 30, 2020 at 2:58:52 PM UTC+1 [hidden email] wrote:
Fixing infra mailing list cc

On Fri, 30 Oct 2020 at 13:57, Tim Jacomb <[hidden email]> wrote:
+1

On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/aca7f49d-e17a-482f-866d-d335dc716380n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Paying for Dockerhub pro plan

Marky Jackson
In reply to this post by Olblak-2
+1

> On Oct 30, 2020, at 6:49 AM, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
> 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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0DB00077-3A87-4D90-B7AB-2BF1F553035B%40gmail.com.

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Paying for Dockerhub pro plan

Olblak-2
This would be 7$ per month paid for following users:
on Jenkinsci (21$)
* me
* oleg Nenashev
* jenkinsinfraadmin

I also would like to pay for jenkins-infra organisation for following people
on Jenkins-infra (21$)
* me
* Mark Waite
* jenkinsinfraadmin

I wouldn't pay for jenkinsci4eval

Again I more see this as a temporary solution while we find a better solution
 

> +1
>
> > On Oct 30, 2020, at 6:49 AM, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
> > 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 Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [hidden email].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/0DB00077-3A87-4D90-B7AB-2BF1F553035B%40gmail.com.
>
> Attachments:
> * signature.asc

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f6b4014b-d3ad-44c0-8a8c-1ada957b7c1c%40www.fastmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Paying for Dockerhub pro plan

Marky Jackson
@Olblak,
I can help pay too.

> On Oct 30, 2020, at 7:41 AM, 'Olblak' via Jenkins Infrastructure <[hidden email]> wrote:
>
> This would be 7$ per month paid for following users:
> on Jenkinsci (21$)
> * me
> * oleg Nenashev
> * jenkinsinfraadmin
>
> I also would like to pay for jenkins-infra organisation for following people
> on Jenkins-infra (21$)
> * me
> * Mark Waite
> * jenkinsinfraadmin
>
> I wouldn't pay for jenkinsci4eval
>
> Again I more see this as a temporary solution while we find a better solution
>
>> +1
>>
>>> On Oct 30, 2020, at 6:49 AM, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
>>> 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 Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to [hidden email].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/0DB00077-3A87-4D90-B7AB-2BF1F553035B%40gmail.com.
>>
>> Attachments:
>> * signature.asc
>
> --
> 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 [hidden email].
> To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/f6b4014b-d3ad-44c0-8a8c-1ada957b7c1c%40www.fastmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5FBC9CAC-321E-443E-A49B-2090080B1D63%40gmail.com.

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Paying for Dockerhub pro plan

Oleg Nenashev
Are you sure about "jenkinsci"? The main DockerHub org is "jenkins". 
  1. We still have some stuff on the legacy "jenkinsci" org, most notably Blue Ocean images. I do not think we should keep paying for this account, but there might be some user impact. Docker installation guide cleanup PR in https://github.com/jenkins-infra/jenkins.io/pull/3852 should be merged ASAP. 
  2. Could we also keep Mark Waite, Tim Jacomb and Alex Earl on the list for the jenkins org? There are official Docker image CI/CD flows on DockerHub, and a direct access might be needed to fix deliveries and/or to add new configurations.
For payments we should finally reimburse any personal payments from the Jenkins account. We can do it through SPI or CommunityBridge.

Best regards,
Oleg






On Fri, Oct 30, 2020 at 3:43 PM Marky Jackson <[hidden email]> wrote:
@Olblak,
I can help pay too.

> On Oct 30, 2020, at 7:41 AM, 'Olblak' via Jenkins Infrastructure <[hidden email]> wrote:
>
> This would be 7$ per month paid for following users:
> on Jenkinsci (21$)
> * me
> * oleg Nenashev
> * jenkinsinfraadmin
>
> I also would like to pay for jenkins-infra organisation for following people
> on Jenkins-infra (21$)
> * me
> * Mark Waite
> * jenkinsinfraadmin
>
> I wouldn't pay for jenkinsci4eval
>
> Again I more see this as a temporary solution while we find a better solution
>
>> +1
>>
>>> On Oct 30, 2020, at 6:49 AM, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
>>> 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 Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to [hidden email].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/0DB00077-3A87-4D90-B7AB-2BF1F553035B%40gmail.com.
>>
>> Attachments:
>> * signature.asc
>
> --
> 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 [hidden email].
> To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/f6b4014b-d3ad-44c0-8a8c-1ada957b7c1c%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 [hidden email].
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/5FBC9CAC-321E-443E-A49B-2090080B1D63%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAe1%3DZ2YgvTGdmETBODUxxmQWNyVND4WrQ%2BSBM570qX8w%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

Mark Waite-2
In reply to this post by Olblak-2
+1 from me.  I've already registered a personal account with DockerHub for my email address.  Do we need to register me with the Jenkins org if I'm already paying them for an account myself?

On Fri, Oct 30, 2020 at 8:41 AM 'Olblak' via Jenkins Infrastructure <[hidden email]> wrote:
This would be 7$ per month paid for following users:
on Jenkinsci (21$)
* me
* oleg Nenashev
* jenkinsinfraadmin

I also would like to pay for jenkins-infra organisation for following people
on Jenkins-infra (21$)
* me
* Mark Waite
* jenkinsinfraadmin

I wouldn't pay for jenkinsci4eval

Again I more see this as a temporary solution while we find a better solution

> +1
>
> > On Oct 30, 2020, at 6:49 AM, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].
> > 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 Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [hidden email].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/0DB00077-3A87-4D90-B7AB-2BF1F553035B%40gmail.com.
>
> Attachments:
> * signature.asc

--
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 [hidden email].
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/f6b4014b-d3ad-44c0-8a8c-1ada957b7c1c%40www.fastmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH83ksjf9SoJXyf6VEAjc7nKMyqcjjW5Ph7cyccdkfwSw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

Olblak-2
In reply to this post by Tim Jacomb
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 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.


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 <[hidden email]> wrote:
Fixing infra mailing list cc

On Fri, 30 Oct 2020 at 13:57, Tim Jacomb <[hidden email]> wrote:
+1

On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/950effd9-d9c5-494c-ba31-52dfea021e8f%40www.fastmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

Richard Bywater-3
Not sure if it's just me, but does "Document that Docker Engine or Docker Desktop are required to run their whitelisted images" concern anyone else?

I mean as a supplier who is providing "free" stuff to an open source project I agree they should get full attribution etc. for providing their services, but having to document something which says that using Docker products is required to run the images seems a bit anti-competitive. 

Perhaps it's just me having a bad day or reading way too much into it :)

Richard.

On Mon, 2 Nov 2020 at 20:22, 'Olblak' via Jenkins Infrastructure <[hidden email]> wrote:
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 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.


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 <[hidden email]> wrote:
Fixing infra mailing list cc

On Fri, 30 Oct 2020 at 13:57, Tim Jacomb <[hidden email]> wrote:
+1

On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/950effd9-d9c5-494c-ba31-52dfea021e8f%40www.fastmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcw%2B82o6Uu0VaXt7681yEzQk0p0Ljj23_%3DaH9mZRfvU7Q%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

Olblak-2
Hi Richard,

Thanks for your input, you are raising a good concern which need clarification. I'll ask the question and I'll share what I found here once I get it.

On Mon, Nov 2, 2020, at 9:25 AM, Richard Bywater wrote:
Not sure if it's just me, but does "Document that Docker Engine or Docker Desktop are required to run their whitelisted images" concern anyone else?

I mean as a supplier who is providing "free" stuff to an open source project I agree they should get full attribution etc. for providing their services, but having to document something which says that using Docker products is required to run the images seems a bit anti-competitive. 

Perhaps it's just me having a bad day or reading way too much into it :)

Richard.

On Mon, 2 Nov 2020 at 20:22, 'Olblak' via Jenkins Infrastructure <[hidden email]> wrote:

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 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.


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 <[hidden email]> wrote:
Fixing infra mailing list cc

On Fri, 30 Oct 2020 at 13:57, Tim Jacomb <[hidden email]> wrote:
+1

On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55598610-2c38-4fe1-a535-bde1b81e398f%40www.fastmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

Olblak-2
Quick update here, the sponsoring plan has been validated on Docker side but atm there is nothing on the inferface which tell that we are using an OSS plan.

Regarding, the "Document that Docker Engine or Docker Desktop are required to run their whitelisted images", I have been told that's it's an issue.

On Mon, Nov 2, 2020, at 11:31 AM, 'Olblak' via Jenkins Developers wrote:
Hi Richard,

Thanks for your input, you are raising a good concern which need clarification. I'll ask the question and I'll share what I found here once I get it.

On Mon, Nov 2, 2020, at 9:25 AM, Richard Bywater wrote:
Not sure if it's just me, but does "Document that Docker Engine or Docker Desktop are required to run their whitelisted images" concern anyone else?

I mean as a supplier who is providing "free" stuff to an open source project I agree they should get full attribution etc. for providing their services, but having to document something which says that using Docker products is required to run the images seems a bit anti-competitive. 

Perhaps it's just me having a bad day or reading way too much into it :)

Richard.

On Mon, 2 Nov 2020 at 20:22, 'Olblak' via Jenkins Infrastructure <[hidden email]> wrote:

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 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.


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 <[hidden email]> wrote:
Fixing infra mailing list cc

On Fri, 30 Oct 2020 at 13:57, Tim Jacomb <[hidden email]> wrote:
+1

On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers <[hidden email]> 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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].


--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8b5a8d17-c05c-4b9c-9220-eec1f0f6f30c%40www.fastmail.com.