mirror of https://github.com/nodejs/node.git
doc: add info on contributor spotlight program
Refs: https://github.com/nodejs/TSC/issues/1474 Signed-off-by: Michael Dawson <midawson@redhat.com> PR-URL: https://github.com/nodejs/node/pull/52598 Reviewed-By: Yagiz Nizipli <yagiz.nizipli@sentry.io> Reviewed-By: Paolo Insogna <paolo@cowtech.it> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Ruy Adorno <ruy@vlt.sh> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>pull/52628/head
parent
a596af0819
commit
44f81a1b7d
|
@ -0,0 +1,46 @@
|
|||
# Recognizing Contributors
|
||||
|
||||
The project looks to recognize and thank contributors for their contributions
|
||||
as one of the ways we can help them continue to contribute to the project.
|
||||
|
||||
This document captures some of the processes we have in place to do that.
|
||||
|
||||
Some of the benefits we hope to achieve through these programs include:
|
||||
|
||||
* Ensuring people know that the project appreciates their work
|
||||
* Encouraging people to repeat/grow their contributions
|
||||
* Helping people demonstrate to their managers the value of the
|
||||
contributions they are making, which in terms helps their manager support
|
||||
their employer investing in the project (unfortunately this is
|
||||
something that matters)
|
||||
* Highlighting the new features in Node.js and showing that they are
|
||||
being added by individuals like those mentioned. This should encourage
|
||||
other people to get involved and make similar contributions.
|
||||
* Highlighting those leading efforts/initiatives and they are being
|
||||
done by individuals or teams like those mentioned. This should
|
||||
encourage other people to get involved and make similar contributions
|
||||
|
||||
## Bi-monthly contributor spotlight
|
||||
|
||||
The contributor spotlight program showcases individual(s) or teams who have
|
||||
made signification contributions to the project. Anybody who has made a
|
||||
notable contribution to the project can be nominated. They DO NOT need
|
||||
to be a collaborator, team member etc.
|
||||
|
||||
The work of the team or individual(s) will be showcased on the
|
||||
Node.js social channels and, if warranted, through a blog post created by the
|
||||
OpenJS marketing staff along with the team or individual(s) which will
|
||||
be published on [openjsf.org](https://openjsf.org/).
|
||||
|
||||
Nominations can be made through this web form:
|
||||
[Contributor Spotlight nomination](https://forms.gle/dXBXZn8yu83HLJ57A)
|
||||
|
||||
Nominations will be reviewed/approved by the Technical Steering Committee (TSC)
|
||||
on a regular basis as scheduled by the TSC chair. The TSC will also
|
||||
recommend the order in which approved nominations are processed
|
||||
by the OpenJS marketing staff.
|
||||
|
||||
Before any work proceeds on an approved nomination the individual(s)
|
||||
or team will be contacted to confirm they want to participate. Social
|
||||
content and or spotlight blog post will only be published after the
|
||||
team or individual(s) have confirmed they are happy with the content.
|
Loading…
Reference in New Issue