You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should implement the all-contributors specification to recognize all people who contribute to our project, not just code contributors. This will help us acknowledge various types of contributions including documentation, design, testing, and more.
Motivation
Properly recognize all contributors regardless of contribution type
Create a more inclusive environment that values all forms of contribution
Provide clear documentation of who has helped with the project and how
Encourage more diverse contributions by showing we value all types of help
Implementation Plan
Initialize the specification: npx all-contributors init
Add existing contributors using the CLI: npx all-contributors add <username> <contribution-type>
Set up a .all-contributorsrc configuration file
Add the contributors table to our README.md
Document the process for adding new contributors in CONTRIBUTING.md
Additional Details
Contribution types to recognize: code, doc, design, bug, test, ideas, review, talk, tutorial, etc.
CLI will maintain both .all-contributorsrc and README.md files automatically
We can configure the bot to automatically suggest adding new contributors
Questions
Should we use the all-contributors bot for automated PRs?
What emoji/acknowledgment style should we use for the contributors table?
Should we include the contributors table at the top or bottom of the README?
Uh oh!
There was an error while loading. Please reload this page.
Description
We should implement the all-contributors specification to recognize all people who contribute to our project, not just code contributors. This will help us acknowledge various types of contributions including documentation, design, testing, and more.
Motivation
Implementation Plan
npx all-contributors init
npx all-contributors add <username> <contribution-type>
Additional Details
Questions
Resources
The text was updated successfully, but these errors were encountered: