LoopBack is an open, inclusive, and tolerant community of people working together to build a world-class Node framework and tools. We value diversity of individuals and opinions, and seek to operate on consensus whenever possible. We strive to maintain a welcoming, inclusive, and harassment-free environment, regardless of the form of communication. When consensus is not achievable, we defer to the owners of each individual module; the powers of the individual owner are kept in check by the ability of the community to fork and replace dependencies on the individual module and maintainer.
Each repository has one or more core maintainers responsible for:
- Daily operations: approving pull requests, responding to new issues, guiding discussions, and so on.
- Seeking consensus on technical decisions.
- Making the final decisions when consensus cannot be achieved.
Core maintainers have npm publishing rights for modules and the final say on releasing new versions.
Besides core maintaners working on LoopBack full-time, there is also a growing group of voluntary maintainers from our community.
CODEOWNERS file in each repository for the list of all active maintainers.
Other core maintainers include:
Previous project architects:
The LoopBack project uses ZenHub, an agile development tool built on the GitHub API. ZenHub provides an easy way to track work and provide project transparency in real time. We use it to groom and maintain our backlog and track what the team and community are working on in each sprint.
Tip: LoopBack switched from using Waffle to ZenHub for its scrum board in early 2017.
ZenHub uses “Pipeline” to track the status of issues from “new” through “in progress” to “done”.
|New issues are placed into this column by default.
|The issue is being triaged to ensure we have enough information to understand the problem and reproduce it on our machines.
|The issue is accepted as a bug/feature and waiting to get prioritized.
|The issue requires discussion to settle on the direction of the solution.
|The issue has acceptance criteria and ready to be estimated.
|A curated list of items we want to work on in the near future.
|A short list of issues that are either the stretch goal of the current sprint or what we are planning to work on in the coming sprint.
|Stories committed to the current sprint.
|Issues that we are actively working on
|Items waiting for peer review. Pull requests are automatically being placed in this column.
|Finished stories end up in this column.
Our sprint spans for a month. All the committed tasks and stretch goals of the milestone are being placed in the
Planning in the Pipelines, with respectively.
In order to allow users without ZenHub to know about our progress, a GitHub issue with
Monthly Milestone label is being created for each month. See https://github.com/strongloop/loopback-next/labels/Monthly%20Milestone for examples.
Besides the monthly milestone, we also plan for a quarterly roadmap. Before the quarterly roadmap is determined, a pull request with
roadmap label is created to get feedback from maintainers and our users.