PM Methodology

The aim of this doc is to standardize the way of work with github repos to encourage community contributions.

Labels

• Labels should be as short as possible Ethereum Aragon solidity

Issues

Flow

Creation

• Create issue before start to code
• New issue should be well explained
• All discussions must be on github

Assignation

• Issue assignation means work in progress, so 1 person only can have 1 open issue assigned at any time.
• If the issue is suspended, it must be unassigned and labeled as suspended

Work

• if the issue is not completed after a period of time, it will be unassigned

Clossing

• 1 issue should be close by one PR with standard naming: Example Issue Description - Closes #issue

Tips

Priorities

• The order of issues tagged to a milestone reflects the priority

Grouping

Grouping helps to represent related issues

• to group issues, use parent and child labels
• parent should contain an explanation and a todo list with each child issue. Example
• child issues should contain a reference to parent issue and all the details and labels. Example

Milestones

Contains all the work needed (assign or not) to complete the release version Title x.y.z

When a milestone is closed, it should be available to explore the content (check why is not possible right now in some repos like contracts)

Projects

Visual representation of the status of the issues either to complete a sprint or to release a new feature

By Sprints / Version release

Columns

• Previous issues
• Sprint issues
• Closed issues
• Open PRs
• Merged PRs Lisk Example

By Features

Columns

• Backlog
• Ready
• In Progress
• Done

Ethereum Example