search

sphinx-doc / alabaster

Lightweight, configurable Sphinx theme
http://alabaster.readthedocs.io/
Other
723 stars 185 forks source link

Transfer ownership to sphinx-doc from bitprophet #177

Closed asmeurer closed 3 years ago

asmeurer commented 3 years ago

The most recent commit on this repository (from January 2020) says "Last ever LICENSE copyright update". https://github.com/bitprophet/alabaster/commit/3b68afcfe55a80508254b22904294100a160e6a7

Does that mean that you no longer intend to maintain this project any more, or am I misunderstanding the meaning of that commit message? I don't see any other indication that that's the case. The lack of activity over the past year is also concerning, but if that's just because you haven't had time I understand that.

If it is the case that you no longer want to maintain this, I wonder if it would make sense to move this repository into the sphinx-doc user space, or into Sphinx itself, given that it is a hard dependency and the default theme for new Sphinx projects. I apologize if any of this has already been discussed before. I couldn't find any prior discussions.

bitprophet commented 3 years ago

No, that was extremely poor language choice on my part, intended to reflect that I'm just done with the annual copyright update (it's just not legally necessary). I haven't had time to focus on this repo in some time but it's not abandoned. I HAVE been meaning to discuss altering ownership with the Sphinx team at some point and that will happen at some point for sure.

Thanks for asking!

asmeurer commented 3 years ago

OK thanks for answering. I would love to see ownership moved if that would lead to better maintenance. I really like this theme, and would hate to see it go by the wayside.

AA-Turner commented 1 year ago

@bitprophet -- would you be open to transferring the repo to @sphinx-doc so that the Sphinx team can also update it?

A

bitprophet commented 1 year ago

@AA-Turner That sounds like a great idea! I'll look at doing that once the dust settles on some inflight stuff in my other projects. I may take a final whack at it on my end and do some of the administrative updates I'm doing elsewhere - drop Python 2 support, move CI (basic as it is) to Circle-CI, etc. During that sort of shakeup, transferring it to sphinx-doc org should work well as part & parcel.

AA-Turner commented 1 year ago

Very happy to tackle the admin if you'd like! Could you add me as an admin to this project in the meantime? My GH username and PyPI usernames are both AA-Turner.

Thanks!

A

bitprophet commented 1 year ago

Invitations sent on both! Re: admin: if you look at recent commits I've made to eg https://github.com/bitprophet/releases / https://github.com/bitprophet/pytest-relaxed / https://github.com/pyinvoke/invocations, you'll see the kinds of things I mean - nuking support for Python <3.6 and everything else that entails; readme tweaks; a .circleci/config.yml (I might need to twiddle something on their end for that to work 100%, until the repo gets moved).

AA-Turner commented 1 year ago

@bitprophet

drop Python 2 support

Done

Move CI (basic as it is) to Circle-CI

Done; moved to GitHub Actions for integration with the UI.

readme tweaks

Wasn't sure what you envisaged here.

Please let me know when you put the transfer request to @sphinx-doc through!

A

asmeurer commented 1 year ago

I would suggest including a screenshot in the README.

bitprophet commented 1 year ago

See some comments I left under sphinx-doc/sphinx#195 / sphinx-doc/sphinx#196 / sphinx-doc/sphinx#197, @AA-Turner - had a branch snafu but also had some other unrelated changes to put in, and release.

Will be trying to push out 0.7.13 (or some other version, depending on what modern Sphinx does re: my shortsighted alabaster version pin back in the day, sob) very shortly, then back to the "let's move it over to the org & I take my hands mostly off the wheel" plan.

@asmeurer That's a good idea but suspect it belongs in its own ticket!

not-my-profile commented 1 year ago

It's nice to have some activity again in alabaster, however the deletion of the master branch (in the process of switching to main) has closed all the pull requests that were open, which were dozens that have all been left unanswered for years prior.

I just reopened my PR sphinx-doc/sphinx#198 to fix the width issue from 2018 but I assume that the other PRs will remain closed ... it would be nice if someone could at least merge the commits from the PRs I listed in https://github.com/sphinx-doc/alabaster/issues/214.

bitprophet commented 1 year ago

@AA-Turner It looks like I can't initiate the transfer to the Sphinx org myself, as I lack repo create permissions there. I'm also guessing you can't do it as you're a collab here but not an owner (as it's a personal repo). Can you confirm this?

Assuming I'm right, then figure one of:

a) I get added briefly over on Sphinx w/ repo create, transfer, and then my privs get revoked (or at least limited to the transferred alabaster repo);

or b) we launder the repo through an org I create for that purpose, as I could then add you to that org as an admin and you'd gain transfer permissions that way (though this seems likely to be more frustrating for users, and I'm not even positive that watchers/forks/etc would survive such a double-transition, though I think they ought to).

EDIT: feel free to email me (link in profile) directly if you want to expedite anything.

AA-Turner commented 1 year ago

Thanks for the update, I've added you to the @sphinx-doc organisation, that should enable the transfer. I'll then move you just to sphinx-doc/alabaster afterwards.

A

bitprophet commented 1 year ago

@AA-Turner - just transferred! and confirming via this comment that the redirect is functioning 🎉

bitprophet commented 1 year ago
bitprophet commented 1 year ago

image

Something for @AA-Turner or another actual Sphinx admin to think about. That's an orb I authored which lives in the Invoke GH org.

bitprophet commented 1 year ago

Aside from having my perms tightened back down to just Alabaster, getting CI working again per above, and sorting out Tidelift, this is done! Excited to see where things go from here.