optics-dev / optics-dev/Monocle
Communication strategy
Open
Nobody has claimed this yet.
3.x
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 207
- Avg merge
- 7h 59m
- Merged PRs (30d)
- 5
Description
I think the website, scaladoc, code/variable naming, import interface and compiler error messages all have to form one coherent, clearly stated communication strategy for 3.0 release. They all have to make sense with respect to each other, not just themselves.
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
Review the website, scaladoc, code and variable naming, import interface, and compiler error messages together. Define a coherent communication strategy for the 3.0 release and document how these surfaces should relate; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- developer-experience, documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100