-
Notifications
You must be signed in to change notification settings - Fork 52
Open
Description
Follow-up from #192.
Requirements
Per Requirements for incoming repositories
- ✅ All maintainers (people with release permissions) agree to the transfer - Transfer to Django Commons #205 (comment)
- ✅ New admins and maintainers are identified: @thibaudcolas @knyghty (might add more later)
- ✅ Tests that run in CI thanks to Update all the things #196
- ✅ Maintained documentation
- ✅ Adopt Django Commons's Code of Conduct bf3ae04
- ⌛️ After transferring, switch to PyPI's "Trusted Publisher"
process (see example in django-commons-playground) - N/A - django-commons should be added as maintainer to the readthedocs project
Repository requirements
Tests
- ⌛️ [Required] Clear instructions on how to run tests
- ⌛️ [Required] Tests run with at least oldest supported LTE versions of Django and Python
- ⌛️ [Suggested] Good test coverage (>70%)
Documentation
- ⌛️ [Required] How to install and use the project
- ⌛️ [Required] How to contribute
- ⌛️ [Required] Organized and maintainable
- ⌛️ [Suggested] Contains architecture documentation
Code of Conduct
- ✅ [Required] Repository contains
CODE_OF_CONDUCT.md
that links to Django Commons's Code of Conduct. See django-commons-playground for an example
Maintainer requirements
- ✅ [Required] All maintainers (release permission) agree to transfer project
- ❌ [Required] The repository will be transferred to the django-commons GitHub organization
- ❌ [Required] The Django Commons PyPI admin team (
cunla
andstormheg
) is added as owners to PyPI and Test PyPI projects - ✅ [Required] Any previous maintainers who are not repository admins are removed as owners on PyPI and Test PyPI projects
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Backlog