-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Anaconda Terms Of Service (TOS) #3
Comments
Which channels are you using? https://www.anaconda.com/pricing/terms-of-service-faqs
|
Thanks. I use the default rcc setup which is conda-forge repository.
Is that mean RCC does not connect to anaconda.com at any point?
czw., 5 gru 2024, 14:10 użytkownik Simon Meggle ***@***.***>
napisał:
… Which channels are you using?
I understand that community channels like conda-forge are not affected by
this.
https://www.anaconda.com/pricing/terms-of-service-faqs
Do I have to pay if I use Miniconda?
Because Miniconda is a minimal Anaconda distribution installer that points
to the Anaconda repositories by default, the need to pay depends on the
package channels you use. If you use the default channel (named “defaults”
and points to the Anaconda Repository) and your company has 200 or more
employees, you need to purchase a license.
However, if you use community-maintained package channels on anaconda.org
(like *conda-forge* and bioconda) as your preferred channel, you don’t
need a license.
Do commercial fees apply to conda-forge?
No. Our commercial fees do not apply to the user-uploaded packages at
anaconda.org, which includes conda-forge. We do not build these packages.
We host them as a free service to the community – something we’ve done for
over 10 years. While commercial fees don’t apply, our Terms of Service do
still apply to conda-forge, as they do for any third-party content we host,
which is typically the case when an internet service provider hosts
third-party content. For example, by using anaconda.org, users agree not
to share content that is illegal, harmful, threatening, abusive, harassing,
defamatory, obscene, pornographic, offensive, invades another’s privacy, or
promotes bigotry, racism, hatred or harm against any individual or group.
cat conda.yaml
channels:
- conda-forge # <----
...
—
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADCMCAQY5AWRD7VSNNMNHK32EBGGBAVCNFSM6AAAAABS73C6DCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRQGI4DMOJWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
It does. |
I guess rcc connects with Anaconda.org not anaconda.com. Right?
czw., 5 gru 2024, 14:32 użytkownik Simon Meggle ***@***.***>
napisał:
… It does.
But as long as the *community*-maintained channels are used (like
*conda-forge*, see the FAQ), I do not see a need for a license.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADCMCAR5B4OKJYL5JSKSGIT2EBIXBAVCNFSM6AAAAABS73C6DCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRQGMZTONZTHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Anaconda changed its Terms Of Service (TOS), requiring a Business or Enterprise license from organizations with 200 or more employees. It means the usage of repo.anaconda.com and repo.anaconda.cloud requires a commercial license.
Could you please clarify how this affects the usage of RCC?
The text was updated successfully, but these errors were encountered: