by VM (Vicky)
Vicky talked about the importance non-committing contributors but the primary
focus is on committing contributors due to time limits.
Covered the different types of drive-thru contributors and why they show up.
- Scratching an itch.
- Unwilling / Unable to find an alternative to this project
- They like you.
Why do they leave?
- Itch has been sratched.
- Not enough time.
- No longer using the project.
- Often a high barrier to contribution.
- Absence of appreciation.
- Unpleasant people.
- Inappropriate attribution.
- It takes more time to help them land patches
- Reluctance to help them "as they're not community".
It appears to be that many project see community as the foundation but Vicky
contended it is contributors.
More drive-thru contributors are a sign of a healthy project and can lead to a
- Have better processes in place.
- Faster patch and release times.
- More eyes and shallower bugs
- Better community, code and project reputation.
Leads to a healthier overall project.
Methods for Maxmising drive-thru contributions:
- give your project super powers.
- Ensures efficient and successful contributions.
- Minimises questions.
- Standardises processes.
- Vicky provided a documentation quick start guide.
- Code review.
- "Office hours" for communication.
- New contributor events.
- Tag starter bugs
- Contributor SLA
- Use containers / VM of dev environment
- Value contributions and contributors
- Culture of documentation
- Default to assistance
Institute the "No Asshole" rule.