PyCon CZ design/print guidelines
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 18
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 5
Description
It's good to have design/print guidelines for suppliers. Examples from 2019:
- https://docs.google.com/document/d/1vGGBXNbMY5mF_eChEds1ua0kGd_Bcy4mffKuIh7jQHc/edit#heading=h.wsbhmqcv5xej
- https://docs.google.com/document/d/1tkydFtS-N5ka2I_uXQFYBK7L3GC-bbJVNq-xI2T7XGU/edit
It would be nice to have these saved as templates and to have meta information in the docs about what should be written in the guidelines etc.
@benabraham can help; see also the Slack thread here.
Contributor guide
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
Review the two linked 2019 Google Docs and the referenced Slack thread to determine the expected guideline content and template format. Then locate the project's documentation structure and save reusable supplier guidelines with metadata describing what each guideline should contain; done when the templates are available in the project docs.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100