dj-rest-auth
dj-rest-auth copied to clipboard
Implement Jazzband guidelines for dj-rest-auth
This issue tracks the implementation of the Jazzband guidelines for the project dj-rest-auth
It was initiated by @iMerica who was automatically assigned in addition to the Jazzband roadies.
See the TODO list below for the generally required tasks, but feel free to update it in case the project requires it.
Feel free to ping a Jazzband roadie if you have any question.
TODOs
- [x] Fix all links in the docs (and README file etc) from old to new repo
- [x] Add the Jazzband badge to the
READMEfile - [x] Add the Jazzband contributing guideline to the
CONTRIBUTING.mdorCONTRIBUTING.rstfile - [x] Check if continuous testing works (e.g. Travis CI, CircleCI, AppVeyor, etc)
- [x] Check if test coverage services work (e.g. Coveralls, Codecov, etc)
- [x] Add
jazzbandaccount to PyPI project as maintainer role (e.g. URL: https://pypi.org/manage/project/dj-rest-auth/collaboration/) - [x] Add
jazzband-botas maintainer to the Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/dj-rest-auth/users/) - [x] Add incoming GitHub webhook integration to Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/dj-rest-auth/integrations/)
- [x] Fix project URL in GitHub project description
- [x] Review project if other services are used and port them to Jazzband
- [x] Decide who is project lead for the project (if at all)
- [x] Set up CI for Jazzband project releases if needed and open ticket if yes
Project details
| Description | Authentication for Django Rest Framework |
| Homepage | https://dj-rest-auth.readthedocs.io/en/latest/index.html |
| Stargazers | 0 |
| Open issues | 0 |
| Forks | 0 |
| Default branch | master |
| Is a fork | True |
| Has Wiki | True |
| Has Pages | False |
All done 👍 . Thank you!
I'm going to close this. Feel free to re-open if I missed something @jezdez .
Hey @iMerica, I'm reopening this since I'm porting all Jazzband projects to GitHub Actions at the moment and want to reduce the reliance on 3rd party platforms more. That also includes the use of Circle CI here.
Above you hadn't specified who would be the project lead, and I'm basically assuming you are since you have also your PyPI release hooked up with GitHub actions already. To have a better handling for all projects I'd like to make this project also use the Jazzband staging package index, so project leads can confirm releases instead of pushing to PyPI directly. That would help making sure this is maintained long-term.