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
Proposal: django-payments #203
Comments
I'd like to chime to clarify I'm currently working on minor improvements for this project and am willing to continue maintaining it. Since I've moved some production projects with steady sales rely on it already (as of last weekend), it's unlikely I'll stop working on it. Interest for it seems to have been consistent over the year too. Docs actually do exist. I've some stashed changes locally to improve this further too. Notes: handoff for rtd, transifex and pypi should also be handled. Thanks all! |
@patrys Thanks, this seems indeed great, and already has some docs which just need to be extended a bit. Feel free to join Jazzband on https://jazzband.co/join and then transfer the repo using GitHub's regular transfer functionality. A ticket to track the specific TODOs will be automatically created after the transfer. @WhyNotHugo I'm glad to hear that you have some documentation updates planned, which would solve the documentation requirements. |
The TODO issue is jazzband/django-payments#228 |
This is done. |
Project Proposal
Project Details
https://github.com/mirumee/django-payments
Project Description
Django Payments is a unified API for integrating PSP (payment service provider) gateways with Django projects.
Project Leads
@WhyNotHugo
Confirmation of Guidelines
Please confirm the following:
I am the project owner, or have permission from the project owner, to request a transfer.
This project is a viable candidate for Jazzband.
This project fulfills the documentation requirements.
This project is tested.
I am happy to adopt Jazzband's code of conduct in this project.
I am happy to include Jazzband's contributing guidelines in this project.
The text was updated successfully, but these errors were encountered: