dblock / dblock/code.dblock.org
Why Artsy cares about Reference Calls
Open
Nobody has claimed this yet.
post topic suggestion
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
I've read our playbook, but I think it'd be nice to explain why we consider our reference calls offensive instead of defensive.
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
Start by reading the repository's playbook and locate the section describing reference calls. Add an explanation of why Artsy considers the calls offensive rather than defensive; done means the playbook clearly communicates that rationale.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100