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

[Maintainance] Willing to maintain tomlkit #62

Closed
frostming opened this issue Sep 20, 2019 · 2 comments
Closed

[Maintainance] Willing to maintain tomlkit #62

frostming opened this issue Sep 20, 2019 · 2 comments

Comments

@frostming
Copy link
Contributor

frostming commented Sep 20, 2019

I sent an email to Sebastien a month ago but got no reply. Here I request again to be a maintainer of tomlkit.

I am also a maintainer of Pipenv which depends on tomlkit heavily, but due to some bugs(#56 ), things get broken. This project hasn't seen any new activities for the last months, so I volunteer to pick it up. PyPI access would be even greater.

I appreciate for your great work in so many wonderful projects @sdispater

@frostming
Copy link
Contributor Author

I am currently maintaining a fork: https://github.com/frostming/atoml that includes a lot of fixes, some of which are still around in tomlkit: #145, #146, #148

@sdispater ping again, may I have the access to maintain this project? I will merge the changes made in atoml back. However, the codebase of atoml is python 3.6+ so I would like to know if you are okay with this chanage.

@frostming frostming changed the title [Maintainance]May I have the honor to maintain tomlkit? [Maintainance] Willing to maintain tomlkit Dec 16, 2021
@sdispater
Copy link
Member

Hi @frostming, thanks for reaching out again 🙂 And I'm glad you did.

Yes, ì can make you a co-maintainer of the project. tomlkit needs some love that I don't have time to give at the moment.

And I have no issue making it compatible with 3.6+ (and even 3.7+) only. We just need to make a 0.7 branch in case we need to fix critical/security issues.

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