django-commons / django-commons/controls
Define suggested funding opportunities for packages in best-practices
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
@cunla has worked with thanks.dev to arrange a way for packages to receive funding directly to the maintainers rather than to the django-commons org 🎉
The suggested security policy from #76 will be sufficient for Tidelift's security policy and should be another recommended option. The last one that we can recommend is configuring EthicalAds through ReadTheDocs.
- Define template funding.yml (sp?) for repos. @cunla can you link this to the right place?
- Define funding documentation
- Mention tidelift
- Mention ethical ads through ReadTheDocs
- Include default option to have these funds go directly to the Django Software Foundation without hitting people's accounts to avoid tax obligations
If folks have other recommendations or suggestions, please add them here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the best-practices materials and any existing funding.yml templates or documentation. Define the repository funding.yml template, document Tidelift and EthicalAds through ReadTheDocs, and include the Django Software Foundation option described in the checklist; confirm the location and format with the linked context from #76.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100