Skip to content

Document the survey process #274

@marco-ippolito

Description

@marco-ippolito

We would like to formalize the process of creating the next-10 survey for Node.js.
The main issue is that we didnt define clearly a deadline after which the survey should not be modified.
My proposal is to document this process so that:

  • One champion opens the PR with the question copy pasted from the previous
  • We decide a deadline where the PR gets merged and questions cannot be added/removed (unless a reason important enough at discretion of the champion)
  • Collaborators and TSC review the questions, ask for changes etc... and approve
  • PR cannot be merged with changes requested, needs approval
  • A test-survey is then created to make sure there are no typos, errors on the platforms used on the survey etc...
  • After x days the survey goes live
  • After x days the survey is closed

@kyliewd will help us to define guidelines on how to prepare a survey, (lenght, open questions etc...)

ping @nodejs/next-10

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions