-
Notifications
You must be signed in to change notification settings - Fork 356
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
Call for Maintainers #368
Comments
I can't commit to being a long-term maintainer, but I can at least do some issue and PR triage, merge a few PRs, and publish a new release or two. I've been the maintainer of a few different open source projects/packages over the years, I'm an active Django user, I've been a user of django-user-accounts for roughly ten years, I have an open PR, I've reviewed some other PRs and issues, and I occasionally pop onto the Pinax Slack workspace. I'm also blag on PyPI and Slack. |
@blag thanks so much! added! I'll leave this open in case anyone else once to join you. |
@paltman Add me to this too please. |
I saw the PyPI invite but not a GitHub invite yet. |
You look all set to me now. Guessing it eventually came through? |
@uhurusurfa added! I'll leave it to you and @blag to figure out how you'll want to coordinate. |
Yep, turns out it was a PEBCAK, sorry for the noise. @uhurusurfa I will likely have some time this weekend to start merging PRs. |
I would also be interested |
@agilili - I have added you |
Looking for maintainers!
There is a lot of pull requests and open issues that the current maintainers, myself included, are just not finding the time to properly get to.
Maybe you've submitted some PRs and are frustrated with the lack of attention. Maybe you use this project in one or more of your projects and want to see that it is properly carried forward.
Whatever you reasons may be, let me know if you have interest and I'll add you to the repo and to PyPI (will need your PyPI name).
Preference will go to those who have commits on this repo and/or have shown an active interest in the issues.
Thanks!
Patrick
The text was updated successfully, but these errors were encountered: