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

Additional maintainers #73

Open
aucampia opened this issue Apr 25, 2022 · 2 comments
Open

Additional maintainers #73

aucampia opened this issue Apr 25, 2022 · 2 comments

Comments

@aucampia
Copy link

Would you consider adding more maintainers to this repo, or potentially transferring it to some group where you can add more maintainers?

@aucampia
Copy link
Author

aucampia commented Aug 7, 2022

@hugovk I think given that this project is still mostly unmaintained isodate2 will eventually be needed again if we want type hints (like @eggplants tried to add here) and other enhancements, maybe it would be best to unarchive it?

@hugovk
Copy link
Contributor

hugovk commented Aug 17, 2022

Can do!

Or: after this repo was revived, looks like I reused the isodate org I created for something else and removed my fork from it. I think I still have a local clone on another machine so can re-upload it.

However I don't have time to maintain a fork at the moment, so you and/or others would need to do that, but I could help get it up and running and share/handover access to https://pypi.org/project/isodate2/.

The difficult bit is: as this repo is sort semi-maintained/semi-unmaintained, should the fork just go its own way (the easy choice for a completely unmaintained repo), or should it try and remain somewhat in sync with upstream...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants