-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Move (most of) /docs/orga/
under /community
#2093
Conversation
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Could we cleanup the commit history a bit and exclude the pure file moves from ref: https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/ |
We're squashing all these big PRs so I'm not sure how much that'd help. The idea is that if someone is looking into the git history, they'll find the squashed merge, but they can check the PR for individual bits. Edit: I see some PRs have been merged with a regular merge commit. I'll add the ignore rev file once we are done with the overhaul. |
PR Checklist:
note any issues closed by this PR with closing keywords
if you are adding a new page under
docs/
, you have added it to the sidebar indocs/sidebar.json
put any other relevant information below
Part of Redesigning conda-forge.org #1971
Moves the "Organisation documentation" over to a new section under
/community
. This helps keeping things tidy in terms of scope, and should also provide better search results once Algolia learns the new structure.I didn't move the "orga/guidelines" page and instead put it under "docs/maintainer", where it fits better.
I added a brief Code of Conduct page with the same contents as we have in the README for now.
I added a small index page for the meeting minutes, with the same info about the meetings we already had in the README.