Skip to content
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

Dropping maintenance, takeovers welcome #79

Closed
andreasabel opened this issue Dec 16, 2022 · 12 comments
Closed

Dropping maintenance, takeovers welcome #79

andreasabel opened this issue Dec 16, 2022 · 12 comments
Labels
admin Project management, maintenance organization

Comments

@andreasabel
Copy link
Collaborator

Dear cabal-doctest users,
I am dropping my dependency on cabal-doctest and thus have no material interest in maintaining it.
So I am happy for a new maintainer to take over.
Express your interest in the comments below, maybe with a short motivating statement.

@ulidtko
Copy link
Owner

ulidtko commented Aug 18, 2023

Hi @andreasabel, I did a cursory review of the package — on a background of having fiddled with Cabal-the-library, it does make some sense to me.

I'm also aware of its deprecation on hackage, and the general pain-point of doctests, as in haskell/cabal#2327. Although I don't yet see the entire doctesting landscape — I do write Haskell daily, and exploring it as-needed shouldn't be a big problem.

Am cautiously willing to rotate-in for maintainership.

AFAICS, the CI here doesn't do hackage uploads; I guess you'd want to add me to uploaders group, and at Maintain or Admin role in the github repo.

cc @phadej

@andreasabel
Copy link
Collaborator Author

@ulidtko Thanks, Maxim, for volunteering! Great to have a new maintainer.

My work on this package was limited to keep it working with new releases of Cabal and GHC. Cabal-3.6 needed a release (1.0.9), from then, revisions on Hackage were sufficient.

I'm also aware of its deprecation on hackage

Maybe the deprecation was done in expectation of an integration of doctest support into cabal, but this never happened, so it could be un-deprecated.

The @haskellari organization is owned by @phadej, I cannot add new collaborators here myself. Oleg is also co-maintainer on Hackage. So he can give you the rights in this repo and the rights to upload and revise on Hackage.

@ulidtko : What is your hackage account?

@phadej, could you add Maxim here and on hackage?

@ulidtko
Copy link
Owner

ulidtko commented Aug 20, 2023

@ulidtko : What is your hackage account?

It's ulidtko there too

@phadej
Copy link
Collaborator

phadej commented Sep 21, 2023

@ulidtko I'll be happy to transfer the repository out of haskellari organization.

@Bodigrim
Copy link

@andreasabel @phadej @ulidtko was there any conclusion about transfer of cabal-doctest?

@phadej
Copy link
Collaborator

phadej commented Jun 14, 2024

All the discussion is in this issue...

@ulidtko
Copy link
Owner

ulidtko commented Jun 14, 2024

@Bodigrim thanks for the ping.

@phadej you can now transfer to ulidtko/doctest

@andreasabel please add me to maintainers

@phadej
Copy link
Collaborator

phadej commented Jun 14, 2024

@ulidtko "ulidtko/cabal-doctest already exists". I cannot transfer the repository to you because of that.

@ulidtko
Copy link
Owner

ulidtko commented Jun 14, 2024

@phadej OK, removed. Please retry

@phadej
Copy link
Collaborator

phadej commented Jun 14, 2024

@ulidtko GH still complains, "You can only transfer a repository from an organization to yourself at this time". I added you as an admin to this repo, so you hopefully should be able to transfer it yourself.

@ulidtko
Copy link
Owner

ulidtko commented Jun 14, 2024

@phadej Yes, that worked. 🎉 Neat

@andreasabel andreasabel added the admin Project management, maintenance organization label Jun 25, 2024
@andreasabel
Copy link
Collaborator Author

Sorry, was travelling for two weeks. I added @ulidtko to the Hackage maintainers.
Thanks, Maxim, for taking over!

@ulidtko ulidtko unpinned this issue Jun 26, 2024
@ulidtko ulidtko mentioned this issue Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin Project management, maintenance organization
Projects
None yet
Development

No branches or pull requests

4 participants