Github Label System Explained
#2
(01-16-2017, 02:20 AM)sphinxc0re Wrote: I agree with all of you. I also think that if we want to get a little bit more serious about this project that we should start organizing and prioritizing issues so that we can easily distinguish between easy and hard, important and unimportant. That would mean putting issues into GH projects but also touching the messy labels. I like how ruma manages their labels: https://github.com/ruma/ruma/labels

I don't think our labels are messy. In fact they are similar to your example, except the prefixes are omitted from Github. I can add them if you'd like. Also, our "component/" prefix needs to be a lot more finegrained than Ruma's because we have a lot more components and this facilitates fast lookups. So our "component" is "ingame + poweruser + internals".

We don't need a finegrained "type/" because most issues have overlapping types and we've tried this before. It's both messy and meaningless. We rarely need to lookup by type either.

We have no "effort/" currently.
Reply
Thanks given by:


Messages In This Thread
Github Label System Explained - by LogicParrot - 01-16-2017, 03:39 AM
RE: Github Label System Explained - by LogicParrot - 01-16-2017, 03:55 AM
RE: Github Label System Explained - by sphinxc0re - 01-16-2017, 06:54 AM



Users browsing this thread: 3 Guest(s)