-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Potential move to @sphinx-doc #1
Comments
Heya, more than happy to for this repo. Let me think about the sphinx-action repo for a bit though, that one pretty much needs a rewrite because it's tied heavily to the sphinx version with no easy way to change it. It may be better to start from scratch for that one. |
Fab, thank you! According to the docs, transferring needs admin access in the transferee repo & ability to create repos in the destination -- I could temporarily add you as a member of the Sphinx-Doc organisation, would that work for you?
OK, I'll hold off for a while---feel free to ping me for input at any point if useful. A |
Sure, let me know when you've added me and I'll ping you after it's transferred |
Done |
Moved over https://github.com/sphinx-doc/sphinx-problem-matcher :) Feel free to remove me now |
Do you still want permissions on this repo? If so I can make you a "collaborator" rather than removing you. A |
Sure, that sounds good. |
Another Q (sorry!): Would you be willing to relicence to BSD-2-Clause (as used by Sphinx) or "Apache or MIT" (as used by e.g. Rust)? A |
Sure, I'll relicense to BSD-2-Clause. |
Hi @ammaraskar,
Would you consider moving this repo to @sphinx-doc, for much the same rationale as ammaraskar/sphinx-action#55?
If not, no worries, but I thought worth asking!
Thanks,
Adam
The text was updated successfully, but these errors were encountered: