![New axobject-query Maintainer Faces Backlash Over Controversial Decision to Support Legacy Node.js Versions](https://cdn.sanity.io/images/cgdhsj6q/production/86e6ebdea652d20da070ebbda20134b839972db7-1024x1024.webp?w=800&fit=max&auto=format)
Security News
New axobject-query Maintainer Faces Backlash Over Controversial Decision to Support Legacy Node.js Versions
A JavaScript library maintainer is under fire after merging a controversial PR to support legacy versions of Node.js.
all-contributors
Advanced tools
Readme
Read these guidelines in | English | Português | Español |
This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code.
The basic idea is this:
Use the project README (or other prominent public documentation page in the project) to recognize the contributions of members of the project community.
People are giving of themselves and their free time to contribute to open source projects in so many ways. It can be a real time sink sometimes and so they should be praised for all their contributions (code or not).
Use this project as an example implementation of the all-contributors specification (see the Contributors section below).
If you find maintaining the list of contributors tedious, try using the CLI tool to lighten your load.
If you use Atom, try out allcontributors, an atom package for the all-contributors-spec implementation.
Open source projects should include the following mandatory items in order to support the All Contributors specification:
Projects should consider the following optional items as part of their commitment to the All Contributors specification:
Emoji | Represents | Links to | Comment |
---|---|---|---|
💬 | Answering Questions (in Issues, Stack Overflow, Gitter, Slack, etc.) | ||
🐛 | Bug reports | https://github.com/${ownerName}/${repoName}/issues?q=author%3A${username} | |
📝 | Blogposts | the blogpost | |
💼 | Business Development | people who execute on the business end | |
💻 | Code | https://github.com/${ownerName}/${repoName}/commits?author=${username} | |
🖋 | Content (e.g. website copy) | where the content is used | blog posts are separate |
📖 | Documentation | https://github.com/${ownerName}/${repoName}/commits?author=${username} , Wiki, or other source of documentation | |
🎨 | Design | the logo/iconography/visual design/etc. | |
💡 | Examples | the examples | |
📋 | Event Organizers | event page | |
💵 | Financial Support | relevant page | people or orgs who provide financial support |
🔍 | Funding/Grant Finders | people who help find financial support | |
🤔 | Ideas & Planning | ||
🚇 | Infrastructure (Hosting, Build-Tools, etc) | link to source file (like travis.yml ) in repo, if applicable | |
📦 | Packaging/porting to support a new platform | ||
🔌 | Plugin/utility libraries | the repo home | |
👀 | Reviewed Pull Requests | ||
🔧 | Tools | the repo home | |
🌍 | Translation | the translated content | |
⚠️ | Tests | https://github.com/${ownerName}/${repoName}/commits?author=${username} | |
✅ | Tutorials | the tutorial | |
📢 | Talks | the slides/recording/repo/etc. | |
📓 | User Testing | user test notes | |
📹 | Videos | the video |
Contributors should be recognised as soon as the contribution is discovered to help ensure their efforts are not overlooked when the list gets updated at a later date. This can be difficult for contributions that are not the result of a commit to repository but do your best to minimise the time between the contribution and updating the list.
Being the owner or a maintainer of the repository does not mean you are solely responsible for keeping the list of contributors up to date. You should encourage contributors to add themselves to the list as much as possible. This can be in the form of a comment on the issue, blog or answer, or through more direct forms of communication where appropriate.
Many contributors may not realise that their efforts are sufficient for recognition in the contributors list. This might be because they have not read or understood the definition of a contributor as set out in this specification, or because they do not feel like it is significant enough. In these cases, you should still encourage them to add themselves, but it may be necessary for you to add the contributor yourself (though it's a good idea to do so in the form of a pull request to make sure they're ok with being added).
In the end, there are no hard and fast rules for when a contribution has to be added to the list, just do your best to be fair and to ensure all contributors are recognised.
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind are welcome!
FAQs
✨ Recognize all contributors, not just the ones who push code ✨
The npm package all-contributors receives a total of 6 weekly downloads. As such, all-contributors popularity was classified as not popular.
We found that all-contributors demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A JavaScript library maintainer is under fire after merging a controversial PR to support legacy versions of Node.js.
Security News
Results from the 2023 State of JavaScript Survey highlight key trends, including Vite's dominance, rising TypeScript adoption, and the enduring popularity of React. Discover more insights on developer preferences and technology usage.
Security News
The US Justice Department has penalized two consulting firms $11.3 million for failing to meet cybersecurity requirements on federally funded projects, emphasizing strict enforcement to protect sensitive government data.