Dear Stefano, I am not sure what you mean by "last point", anyhow no reply so far by Aurelien. I am sure that FIWARE Foundation is eligible for the Open Source programme, and that may be a way to go (see option 1). In general, the limitations introduced may cause different problems, but the one I think that is i see more impacting to FIWARE is that for GEs hosted on single organisations (e.g. Martel, UPM, ect) docker hub repository the following limitations apply: - 100 pulls for not registered users - 200 pulls for registered users So beyond 100 daily pull from a repository (if unregistered as in most of the cases when just using containers), people will get an error... Think for example if we organize a hackathon: the treshould will be reached in seconds :/ Cheers, *Dr. FEDERICO MICHELE FACCA* *CTO, Head of Martel Lab* +41 788075838 *MARTEL INNOVATE* <https://www.martel-innovate.com/> - INNOVATION, WE MAKE IT HAPPEN Click *HERE* to download Martel reports and white papers! <https://www.martel-innovate.com/premium-content/> Follow us on *TWITTER* <https://twitter.com/Martel_Innovate> On Thu, 19 Aug 2021 at 17:06, Stefano De Panfilis < stefano.depanfilis at fiware.org> wrote: > dear federico, > > did you get an answer from aurélien about your last point which is > definitely quite tricky? > > ciao, > stefano > > On Thu, 19 Aug 2021 at 10:21, Federico Michele Facca < > federico.facca at martel-innovate.com> wrote: > >> Dear All, >> recently terms and conditions of Docker Hub usage changed a lot, and >> unless willing to pay, this is going to affect all organisations with free >> accounts that >> use Docker Hub to distribute docker images of their FIWARE GEs. >> >> Options I see: >> - All official GEs are just hosted under FIWARE Docker Hub repo. >> -> Pro: FIWARE Foundation should be able to get the OS status >> recognition, and so no limitation will apply. >> -> Cons: maintainers will lose visibility, and users will need to be >> duly informed of changing the repo to use docker images. >> >> - Maintainers move to alternative solutions to Docker Hub. >> -> Pro: Maintainers will retain visibility. >> -> Cons: Users will need to be duly informed of changing the repo to >> use docker images. >> >> *Dr. FEDERICO MICHELE FACCA* >> *CTO, Head of Martel Lab* >> +41 788075838 >> *MARTEL INNOVATE* <https://www.martel-innovate.com/> - INNOVATION, WE >> MAKE IT HAPPEN >> Click *HERE* to download Martel reports and white papers! >> <https://www.martel-innovate.com/premium-content/> >> Follow us on *TWITTER* <https://twitter.com/Martel_Innovate> >> >> >> ---------- Forwarded message --------- >> From: Federico Michele Facca <federico.facca at martel-innovate.com> >> Date: Thu, 19 Aug 2021 at 10:14 >> Subject: Re: Your eligibility for the Docker Open Source Program >> To: Aurelien Suarez <aurelien-suarez at docker.com> >> Cc: Juanjo Hierro <juanjose.hierro at fiware.org>, Ulrich Ahle < >> ulrich.ahle at fiware.org> >> >> >> Dear Aurelien, >> The components we deliver open source are part of the FIWARE Open Source >> platform which is backed by a non profit organization: the FIWARE >> Foundation. >> Simply as a way of working FIWARE does not force to transfer repositories >> under the control of the association, they just mirror them. >> You can check, for example, that quantumleap is listed here: >> https://www.fiware.org/developers/catalogue/ >> >> This is the case for the projects part of FIWARE (e.g. Context Broker, >> maintained by Telefonica), unless maintained and developed by the FIWARE >> Foundation itself. >> Clearly, if contributors like us, cannot benefit, that's gonna affect >> large part of the project of parf of FIWARE, unless the single organisation >> are willing to pay Docker hub subscriptions. I assume, being a lot of >> them SMEs, it's easier that they will give up on Docker hub. >> >> @Juanjo Hierro <juanjose.hierro at fiware.org> @Ulrich Ahle >> <ulrich.ahle at fiware.org> I guess this is something we can put in the >> Agenda of the next Board of Directors of the Foundation, to decide a common >> strategy >> to tackle the issue. >> >> Best, >> Federico >> >> PS: I would also argue that following your approach in a strict sense, >> you should not accept even projects from Apache or other OS foundations, if >> they are supported >> by commercial organizations (which is the case for 100% of them, >> basically). >> >> >> *Dr. FEDERICO MICHELE FACCA* >> *CTO, Head of Martel Lab* >> +41 788075838 >> *MARTEL INNOVATE* <https://www.martel-innovate.com/> - INNOVATION, WE >> MAKE IT HAPPEN >> Click *HERE* to download Martel reports and white papers! >> <https://www.martel-innovate.com/premium-content/> >> Follow us on *TWITTER* <https://twitter.com/Martel_Innovate> >> >> >> On Thu, 19 Aug 2021 at 10:00, Aurelien Suarez <aurelien-suarez at docker.com> >> wrote: >> >>> Hello Federico, >>> >>> Thank you once again for submitting your application to the Docker Open >>> Source Program. The Docker Open Source program is designed to help >>> non-commercial members of the open-source continue driving the adoption of >>> their software. Among other benefits, for approved Open Source Program >>> contributors, we whitelist their organizations’ namespaces so that pulls >>> from their users are not subject to the policies for data pull rates. >>> >>> We have designed this program to help individual contributors, >>> nonprofits and educational institutions. Because your project is backed by >>> a commercial organization, we regret to inform you that your Docker >>> namespace is not eligible. For the ISVs ineligible for our Open Source >>> Program, we offer competitively priced services for low-friction >>> distribution of ISVs’ software. >>> >>> Please let us know if the Docker new policies for data pull rates are >>> impacting your business operations, and we will connect you with the >>> appropriate support. >>> >>> We appreciate all your support for the Docker open-source community. >>> >>> Many thanks, >>> >>> Aurélien Suarez >>> >>> Community Marketing Intern >>> >>> Docker. >>> >> >> __________________________________________________________________________________________ >> >> You can get more information about our cookies and privacy policies on >> the following links: >> - https://wiki.fiware.org/FIWARE_Privacy_Policy >> - https://wiki.fiware.org/Cookies_Policy_FIWARE >> >> >> fiware-technical-committee mailing list >> fiware-technical-committee at lists.fiware.org >> >> To unsubscribe from fiware-technical-committee mailing list, go to the >> information page of the list at: >> https://lists.fiware.org/listinfo/fiware-technical-committee >> >> > > -- > Stefano De Panfilis > Chief Operating Officer > stefano.depanfilis at fiware.org <charlotte.kotterman at fiware.org> > www.fiware.org > Mob: +393357542567 > Skype: depa01 > twitter: depa01 > > <https://twitter.com/fiware> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20210819/17d6823e/attachment-0001.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy