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

Call for Maintainers #105

Open
paltman opened this issue Dec 3, 2022 · 4 comments
Open

Call for Maintainers #105

paltman opened this issue Dec 3, 2022 · 4 comments
Labels

Comments

@paltman
Copy link
Member

paltman commented Dec 3, 2022

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

@powderflask
Copy link

@paltman - I already maintain more packages than I ought to, but I'm willing to at least keep this one maintained. At a minimum I can commit to processing the outstanding PR's and upgrading the package to run on Py3.11 and Dj4.2. Can't promise to handle support or enhancement requests, but at least I could keep it alive. Let me know. My PyPi name is same.

@andharris
Copy link

@powderflask thanks for offering to help. I'm working on an app that is blocked on upgrading to Dj4.2 because of this library. Have you made any progress on updating to support Dj4.2? Please let me know if there is anything I could do to support updates needed to for Dj4.2.

@powderflask
Copy link

Yes. I have a PR ready to go. Using it in production, all working as expected.
You can get it here:
https://github.com/powderflask/pinax-notifications/tree/django4.2
I see several other attempts in the PR queue, so I didn't want to confuse things by adding another PR to the queue until someone is processing them.

@andharris
Copy link

@paltman any way we might be able to all @powderflask to start processing the outstanding PRs?

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

No branches or pull requests

3 participants