Manage labels to fit our current need

[kaichih]

We need to manage "labels" to label our issues in our Github issue here. I will propose some labels here, and need your reviews later.

[gangit]

Hi All,

Thank for the sharing.

Just to let know that an interesting presentation is actually live stream
on some e-health projects at

*http://www.odess.io/streaming-en.html
http://www.odess.io/streaming-en.html *

Best,

ganesh

On 4 July 2016 at 14:02, Kevin Hu [email protected] wrote:

We need to manage "labels" to label our issues in our Github issue here. I
will propose some labels here, and need your reviews later.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#7, or mute the thread
https://github.com/notifications/unsubscribe/ACvZGfQqvjyBvqyUDNynEGeq6vdvPjuZks5qSNo3gaJpZM4JEOik
.

[kumarrishav]

Thanks for filling this @kaichih .

Sorry @gangit for late update, we are combining all the stuff and resources what we planned during London all hands. We will update you with all the new details very soon. Thanks for the patience.

[gangit]

Thanks Kumar...

No worries

Best

On 4 July 2016 at 15:42, Kumar Rishav [email protected] wrote:

Thanks for filling this @kaichih https://github.com/kaichih .

Sorry @gangit https://github.com/gangit for late update, we are
combining all the stuff and resources what we planned during London all
hands. We will update you with all the new details very soon. Thanks for
the patience.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ACvZGSXshMTVaSpBOsBax0T_8pXtkMOYks5qSPGXgaJpZM4JEOik
.

[snowmantw]

I suggest that we at least need some functional labels like:

1. discussions: for discussions like this, rather than implementation issues from those decisions already made. So by default, any issue without this label would be implementation issue, which mean they are expected to be solved within reasonable period. For example, 3 days.
2. meta: once we have some plans or milestones, no matter whether they're technical or not, we may need a meta label to mark it for tracking and further discussions. This kind of issues are not expected to be solved but should come with dependencies.
3. wontfix, duplicate, assigned, invalid

And we could take a look at this reference as well:

https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/

Besides that, after we have more clear model about how this project (and its sub-projects) works, we should have regular triage to update progress and scan all unnoticed issues.

[snowmantw]

Also, we may need some bots to work on labels automatically. For example, the triaging could be helped by automatically collecting unassigned implementation issues.

[snowmantw]

So @kaichih , since you own this issue, you can just create all the labels and close this issues. For the bots I would fire another issue.

[kaichih]

I was thinking to use labels to represent the timeline and use it to manage our issues. But, later, I think it's better to use milestone. I will create another issue to explain it to you guys.

[kaichih]

Due to #12, this should be resolved in milestone 1.

[kumarrishav]

Purpose of labels can be different. Labels Like: Discussion wanted, bug, feature, documentation, easy bug,Q/A wanted, UI/UX/Design help etc. So that we can use this label for the issues (if required i.e each issue doesn't need to have a label)

[kaichih]

Yes, label should be like what you said, and it is used to indicate what kinds of issues they are.