How do we know people have read our contributing guide?
- Dominant language
- No language data
- Stars
- 91
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Step 4 of the **Seven Steps** in https://github.com/dwyl/hq/issues/147 is to :star: this repo.
# Why?
encouraging (_requiring_) people to :star: the repo to _confirm_ they have read/understood and intend to _follow_ the process is the _only_ way I could _think_ of to foster the _necessary_ behaviour for success in 2017.
The prospect of getting $300 Headphones is a pretty _decent_ ["_carrot_"](https://en.wikipedia.org/wiki/Carrot_and_stick) when you consider that reading the `README.md`. will take no more than **10 minutes**.
> We have _collectively_ wasted _countless **hours**_ of Dev & QA time over the past year
because people have not been `require`d to follow process. ⌛️ 💸 🔥
Hours that _should_ have been spent on the _craft_/_features_.
Which would have made users/stakeholders/clients happy.
It's _my_ fault for not making _sure_ we had a _clearer_ "_onboarding_" process...
We're going to _fix_ it in 2017.
DWYL will be a well-oiled _machine_ running on a hydrogen fuel-cell producing _water_ in the _desert_! 👍
Contributor guide
Assessment
This issue has not been assessed yet.