:clipboard: Guidelines & Workflow for people contributing to our project(s) on GitHub. Please :star: to confirm you've read & understood! :white_check_mark:
88
stars
9
forks
source link
How do we know people have read our contributing guide? #39
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" 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 required 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! 👍
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" when you consider that reading the
README.md
. will take no more than 10 minutes.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! 👍