Skip to content

git labels / assignees convention  #4

@nameles-admin

Description

@nameles-admin

I find that it's best to have a very clear convention for 'Labels' and use it diligently. I suggest that we category things in to 'bugs' and 'features' first, where they are handled in a prioritized order

  1. critical bugs (dark red)
  2. bugs (red)
  3. must have (orange)
  4. nice to have (yellow)
  5. future work (light yellow)

Maybe in addition we could have "call for contribution" (green) and then if you think some others should be included as well, or otherwise could add more as we go.

What do you think?

Also we should be very flexible in using assignee, where everyone who can contribute the initial conversation are assigned, and then people can drop out or further assign based on that.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions