-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: replace developer meeting with contributor community page #48990
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
Conversation
We currently have some manual setup for redirects in conf.py, but tailored to generated API pages. Either you could adapt that a bit to work with generic pages, or otherwise we can use some sphinx extension (eg https://documatt.gitlab.io/sphinx-reredirects/index.html) |
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.
small comments, overall setup looks good to me
# Conflicts: # doc/source/development/community.rst
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.
Lgtm.
a General thought: I think potential new contributors would benefit from this being visible on the stable docs
any thoughts on backporting?
I think I just added the redirect – but check me 😉 |
Looks good, labelling 1.5.1 for now so that we can backport if there aren't any objections from others |
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.
Thanks a lot for writing up this page! That's really useful content. Just a few tiny comments
The doc build failure seems to be related:
The |
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.
Thanks!
Generally we don't do the effort of backporting doc fixes, but given that it would be useful to have this updated soon and this shouldn't give conflicts, sounds good to me. |
…tributor community page
…th contributor community page) (#49067) Backport PR #48990: DOC: replace developer meeting with contributor community page Co-authored-by: Noa Tamir <[email protected]>
Updating the developer meeting page to include the new contributor meeting and slack
Along the way, I decided to include other communication channels and did my best to describe them, making this more of an internal contributor community page.
Inspired by SciPy and NumPy's community pages, and Matplotlib's home page resources and meeting documentation, and readme.
I tried to keep this pandas' community page as much as possible. Please provide feedback on what you would like to see changed, so it's more appropriate.
I would suggest we add redirects for the old page to this one. If you have an example for how this was done before, I could add it to this PR. Otherwise, I will investigate if Sphinx supports this.