Project Management

This page describes how NDM project is maintained.

NDM Project Management Overview

Trackers/Tools

NDM Project Management is done completely using GitHub as follows:

• GitHub Milestones provide a snapshot of short term goals
• GitHub Projects are used to track the midterm goals
• GitHub Issues are used to capture long term goals. The issues that are neither part of the milestones or projects are tagged with a label "Future Backlog"

Specifically for NDM:

• GitHub Issues (usually created under the https://github.com/openebs/openebs/issues repo) are used to track features/bugs. In some cases, users end up creating issues directly under the https://github.com/openebs/node-disk-manager/issues. There will be a corresponding tracking issue created under https://github.com/openebs/openebs/issues by the project maintainers. Every new GitHub issue will be either part of the milestone or project and tagged as Future Backlog in the Bug Triage meeting.
• GitHub Milestones will be used to track the release items. NDM releases will be aligned with the OpenEBS releases. A monthly release cadence is maintained. Minor releases that fix some user-reported issues can be made on-demand from the specific release branch. https://github.com/openebs/openebs/milestones are used to track planned items for a given OpenEBS monthly release. https://github.com/openebs/node-disk-manager/milestones milestones will be used to track the PRs targeted for the corresponding NDM release.
• GitHub Project Tracker will be used to for getting a snapshot of items planned for the immediate Major release. For NDM v1.0, the tracker is at https://github.com/orgs/openebs/projects/2

Meetings

• Daily OpenEBS Standups are used to track the readiness towards the planned release items. This sheet will be used to track the estimated due dates towards the release goals like RC builds. The sheet also will be used to track some release checklist items. OpenEBS Planning Sheet
• Weekly Bug Triage Meeting by the NDM maintainers to check on the new issues created in the past week and help the assign the issue with labels and/or include them into project/milestones. Check the sanity of projects and milestones. Though planned for weekly, the maintainers can do this as the issues come in to be more responsive.
• Bi-weekly OpenEBS meeting to help with product backlog prioritization by taking end-user and feedback from other dependent teams.

Future WIP Backlogs

This is a list of items that need to be further investigated before creating an issue. These are examples of items that came up during discussions with users and other collaborators.

1. BDC Claim Set to support claiming multiple block devices at a given time. ClaimSet operator to support zone aware scheduling of BDCs. eg: each BD should be in different zones.
2. Geolocation information to the BlockDevices.