Skip to content

2020 Node.js Contributor Survey #33583

Closed
Closed

Description

@jasnell

Hello and @nodejs/collaborators and nodejs GitHub organization @nodejs/members!

I'd like to invite you all to complete the first Node.js Contributor Survey for current, former, and prospective new contributors.

https://forms.gle/4UvPq5HF3vxcugHB9

The intent of this survey is to provide feedback as to how contributors feel the project is progressing, the things we're doing well on, and the things we need to improve.

We invite anyone who contributes to the project in any way to participate. This means more than just code! If you contribute documentation, if you participate in the @nodejs/community-committee, if you contribute to discussions in the issue tracker --- however you choose to contribute to the project, we want to hear from you!

Are you a former contributor? We'd definitely like to hear from you also!

The survey should not take too long to complete (maybe about 20 minutes) and the results will be published in a summary document in the https://github.com/nodejs/tsc repo. We will keep the survey open for two weeks from today.

Thank you all for your contributions to Node.js!

Activity

  1. pinned this issue on May 27, 2020
  2. ljharb commented on May 28, 2020

    @ljharb
    SponsorMember

    "What areas of Node.js do you contribute to?" doesn't contain the Modules working group.

  3. benjamingr commented on May 28, 2020

    @benjamingr
    Member

    IIUC modules is not a working group (is it?).

    I definitely think it's worth a mention and "other" would have also been an appropriate option IMO.

  4. richardlau commented on May 28, 2020

    @richardlau
    Member

    Yes, the modules team is not a working group.

    I'd be careful about being too specific with regards to "What areas of Node.js do you contribute to?". It's been pointed out to me that it is possible to identify some individuals based on the combination of answers selected for that question.

  5. jasnell commented on May 28, 2020

    @jasnell
    MemberAuthor

    Good points. The specific combinations of answers for the survey per person will not be published in the results btw.

  6. jasnell commented on May 28, 2020

    @jasnell
    MemberAuthor

    @ljharb ... I didn't include more specific teams in the contribution list specifically because doing so would make it far more likely to fingerprint specific responses from individual contributors. As @richardlau points out, there's already a concern there that I will be working to address when I publish the survey results to help ensure that things are suitably anonymized in the report.

  7. ljharb commented on May 28, 2020

    @ljharb
    SponsorMember

    That all makes sense; i was confused by seeing the package maintenance WG and not the modules group/team/whatever.

  8. bnoordhuis commented on May 29, 2020

    @bnoordhuis
    Member

    I'm missing a "10 years or more" option for the first question. 🙃

  9. zeusdeux commented on May 29, 2020

    @zeusdeux
    Contributor

    Haha OG flex @bnoordhuis

  10. jasnell commented on Jun 3, 2020

    @jasnell
    MemberAuthor

    Quick update... we currently have 81 responses to the contributor survey. It will remain open for another week just to give additional people time to weigh in. Once it is closed, I will be working on producing a report of the results that will be posted to the nodejs/tsc repo in a pull request.

  11. jasnell commented on Jun 12, 2020

    @jasnell
    MemberAuthor

    The survey has now been closed. We had 97 responses which is excellent! I will be working on a report of the results and will post that to the TSC repository in the next week. Thank you all!

  12. unpinned this issue on Jun 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions