-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Shorten sentence about defaults
#2436
Conversation
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -22,7 +22,7 @@ You can [search](https://anaconda.org/) for packages online. Look out for packag | |||
|
|||
## Why conda-forge? | |||
|
|||
The packaging team from [Anaconda, Inc.](https://anaconda.org/), packages a multitude of packages and provides them to all users free of charge in their `defaults` channel. | |||
The packaging team from [Anaconda, Inc.](https://anaconda.org/) provides a multitude of packages on their `defaults` channel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was likely written a long time ago. Given ToS, this really shouldn't say free of change to all users
However don't want to get into all of that in an intro. So just shortened this instead
Honestly this whole section may benefit from a revamp. In interim this seems like a small reasonable change
We need to fix the dockerhub links in another PR. :/ |
Thanks Matt! 🙏 Agreed. Yeah there are plenty of opportunities here to improve the docs Think a lot of this was written in the mid to late 2010s. Would probably write different things now For example we are explaining why conda-forge should exist from a standpoint of its creation. Well it does exist and it has so for a while So maybe we would do better to talk about the communities we are serving This is just one example 😉 |
PR Checklist:
docs/
orcommunity/
, you have added it to the sidebar in the corresponding_sidebar.json
file