How do we know people have read our contributing guide?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github
- Domain
- documentation
Research direction
Read the Seven Steps in dwyl/hq issue 147 and the repository README.md first, then examine how GitHub stars are being used as confirmation. Define and document an onboarding mechanism that confirms contributors have read, understood, and intend to follow the process; done means the confirmation is clear and usable.
Written by the indexing model from the issue text.
Description
Step 4 of the Seven Steps in https://github.com/dwyl/hq/issues/147 is to ⭐ this repo.
Why?
encouraging (requiring) people to ⭐ 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 beenrequired 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! 👍
- Dominant language
- No language data
- Stars
- 91
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
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.
More from dwyl/contributing
-
bug chore starter
Difficulty 1/5 Under an hour Newbie friendliness 38/100
dwyl/contributing#119 · 1 reaction ·
-
enhancement starter
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
dwyl/contributing#118 · 1 reaction ·
-
discuss enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
dwyl/contributing#113 · 2 reactions ·
-
discuss enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
dwyl/contributing#112 · 1 reaction ·
-
Draft Pull Requests! Opendiscuss enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
dwyl/contributing#111 · 2 comments · 3 reactions ·
All issues in dwyl/contributing
Similar issues
-
content
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GDQuest/learn-gdscript#1395 ·
-
rules
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
HttpClient
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
symfony/symfony-docs#23092 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
huggingface/sentence-transformers#4074 ·