Open BurningEnlightenment opened 3 weeks ago
Hi @BurningEnlightenment,
I have sent you all an invitation to join the GitHub org. After you accept that, you should be able to move the repo yourself (please review the naming convention suggestions at the end of the readme https://github.com/sphinx-contrib/github-administration).
After the move, you may need me to re-grant you admin permission on the repo. If that's the case, comment here on this ticket and let me know.
When we're all done, and you have the permissions you need, we can close this ticket.
Welcome, and thank you for contributing!
Thanks, I just accepted the invitation. I'll move the repo later this week.
What is the usual way to handle PyPI package ownership for sphinx-contrib
? Is there a spinx-contrib
PyPI organization? I guess my first ToDos are to migrate the Travis CI to GitHub Actions and to implement a publishing workflow based on Trusted Publishing as this will involve Jan Holthuis one way or the other.
What is the usual way to handle PyPI package ownership for
sphinx-contrib
? Is there aspinx-contrib
PyPI organization? I guess my first ToDos are to migrate the Travis CI to GitHub Actions and to implement a publishing workflow based on Trusted Publishing as this will involve Jan Holthuis one way or the other.
Pretty much that yes. The org currently exists more as a way to publicize projects than share effort maintaining them (like github.com/jazzband is for). That may change organically in the future but it hasn't yet
Hello everyone,
the original creator of
sphinx-multiversion
no longer has time to maintain his extension and doesn't oppose appointing other maintainers. We thought it makes sense to move this extension with 149 stars to thesphinx-contrib
organization to signify the change in maintainership. See Holzhaus/sphinx-multiversion#88sphinx-multiversion
is an extension to build and cross-reference multiple versions of a documentation for self-hosting, e.g. on GitHub pages. See also docsSo please invite @Holzhaus, @d33bs and me.