The pilot packages are the alpha tester of this working group. They will help us to archive our WG goals:
- identifying the major problems a module have to face
- defining priorities for our todo-list
- verifying the benefits of the tools and process built
- improving all the stuff created to evangelize the community
The help provided to all these packages will be to think and to implement solutions for their problems, as helping them to migrate to newer Node.js versions.
Doing so we will create a wide range of tools in order to:
- give to all the maintainers the possibility to use them
- provide the resources to choose wisely the dependencies for business
- improve the quality and stability of the packages in the Node.js ecosystem
| Organization* | Maintainer Reference |
|---|---|
| Express | @wesleytodd |
| MQTT.js | @mcollina |
*Ordered per joining time.
The baseline to start with this work is:
- Prepare a survey to collect more information as possible
- Dispose the output directory and send the survey with all the details to the maintainer reference
- The Maintainer Reference should open a PR to this repository with the replies
- Dispelling every doubt before merge the PR
- Think out the feedback received in tasks we should do to help the package
- Brief with other pilot packages feedbacks to find common needs
- Define a roadmap
- Implement the roadmap
- Coordinates with pilot packages to try the solutions implemented and verify the benefits
- Share to the community the tools and the successful process
During this phase of work, all the docs and useful stuff must be stored
in the directory ./pilots/${package-name}/. This directory can be merged in master
whenever a main approach's step is reached.
We should produce almost:
| Docs | Description |
|---|---|
| SURVEY_ANSWER.md | Collect all the information received from the Maintainer Reference |
| TASKS.md | An initial list of tasks based on the survey's answers |
| ROADMAP.md | All the tasks that will be implemented (a list of issues links) with some target to aim |
| RESULTS.md | At the end of the pilot phase, we should recap what we learned about the package itself and how the know-how could be shared |