mozilla / OpenDesign

Mozilla Open Design aims to bring open source principles to Creative Design. Find us on Matrix: chat.mozilla.org/#/room/#opendesign:mozilla.org

Home Page:https://blog.mozilla.org/OpenDesign

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Use GitHub labels for deadlines

Ryuno-Ki opened this issue · comments

Hi,

just a thought which came to me right now: What about using Custom GitHub labels for each month?
This way, browsing the open issues would allow to see at a glance, which issues have a near deadline. (Assuming all of them have to be done in less than a year).

What do you think?

hhmm ... thats good idea. but how do you label it, month / or urgent level?

I think we can add labels for [Whenever, 3 months, 2 months, 1 month, 3 Weeks, 2 Weeks, 1 Week, ASAP].

Labels are not designed for that honestly. Milestones are designed for deadlines, so if anyone can create a milestone, that would be ideal.

I think we can add the "Create a Milestone" in the Readme, under Deadline:

Along with the link.

I'd rather use Labels for [Mar 19, Apr 19, May 19] etc.
I couldn't find an indicator, how Milestone would behave if they're overdue.

thats include "design review" too ?, if we use milestone @elioqoshi ?

I'd rather use Labels for [Mar 19, Apr 19, May 19] etc.

Yes, but personal preference shouldn't be an argument here. Any specific reasons why that would be a better approach? You'd have to clutter the whole label space with specific dates which will never be used again and ideally needed to be removed (which also defeats the purpose of labels if deleting them is part of the process).

I couldn't find an indicator, how Milestone would behave if they're overdue.

I just gave this issue a test milestone. You can see that it says "Past due by 1 day"

thats include "design review" too ?, if we use milestone @elioqoshi ?

Sure

I'd rather use Labels for [Mar 19, Apr 19, May 19] etc.

Yes, but personal preference shouldn't be an argument here.

Agree. It was my motivation for this ticket (that is, why I suggested label instead of milestone).

Any specific reasons why that would be a better approach?

They stand more out in the issue overview:

milestone-vs-label

You'd have to clutter the whole label space with specific dates which will never be used again and ideally needed to be removed (which also defeats the purpose of labels if deleting them is part of the process).

What about using a label for the year and another one for the month then?
You can actually filter for both in an issue search.

I couldn't find an indicator, how Milestone would behave if they're overdue.

I just gave this issue a test milestone. You can see that it says "Past due by 1 day"

True, but only in the milestone detail view.

What about using a label for the year and another one for the month then?

How would that be helpful? There are 30 different possibilities inside a month and some projects need to have a specific one.

True, but only in the milestone detail view.

No, also in the projects view (which is not enabled here).

GitHub simply does not support any due dates and anything closest to it is milestones. Using Labels is very very far fetched and comes up with a bigger set of other problems which I mentioned before.

If you want to use labels for prioritizing things, that can be done. Have a look at how I set up project management at our company:

https://github.com/uracreative/works/labels

I agree with @elioqoshi here. Creating labels for deadlines isn't very convenient and Milestones can work better than a label for such purposes! Closing this issue.