essbante-io
commented
3 months ago @mkbreuningIOHK, can you elaborate on these labels: marketing, product, and management? Who will be on the management and product team at Identus?
Closed mkbreuningIOHK closed 2 months ago
essbante-io
commented
3 months ago @mkbreuningIOHK, can you elaborate on these labels: marketing, product, and management? Who will be on the management and product team at Identus?
mkbreuningIOHK
commented
3 months ago @mkbreuningIOHK, can you elaborate on these labels: marketing, product, and management? Who will be on the management and product team at Identus?
@essbante-io , the labels are to triage but if there is nobody behind those labels, we might reconsider and start with a smaller number of labels.
Is your feature request related to a problem? Please describe. As the number of contributors is growing, the number of issues is growing. We need a triage process with a labelling system in place.
Describe the solution you'd like Labels to be added in contributing.md (or another file that will be referred in contributing triage part) in Identus repo. Each label should have a prefix: for example:
Colors for labels should follow a rule to be described. Each label should have a description associated to it.
All Identus repos will use the same labels. Triage process needs to be written down: Have a look at Identus Technical Charter as reference first.
Describe alternatives you've considered We need to check if the status are labels or customised fields. Best practices to be looked at as well so the solution is practical.
Additional context The triage should be efficient and regularly done (recommendation is every 2 days) and it should be linked closely to the release process and cadence. Follow: https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels Use Conventional commit to match some labels