Proposition: setup the same label and milestones system as in stack repo

[rvion]

I suggest we use the same label system as for stack repo.

As of now, it's harder to understand where the project is going without them.

Milestones

https://github.com/commercialhaskell/stack/milestones

Labels

• copy-paste labels (keep color scheme)
• create milestones
• tag existing issues with labels
• give repo access to some people to speedup the tagging process

[mgsloan]

+1!

[bitemyapp]

👍

[alanz]

+1, @rvion I have added you to the project, can you do this?

[rvion]

Thanks, yes, I'll do this :)

[rvion]

I tweaked labels a little bit.
I also kept only 3 Milestones (I think that "Support" can either go in P1 or P2, and "Future" can go in P3)

[alanz]

Thanks. Is there documentation around the process we can bring over too?

[rvion]

I don't know. I don't think there is yet.
I plan to write some documentation soon (maybe this evening, I'm GMT +1 :) )
I also plan to make a few more changes in the readme, add contribution guidelines, etc.
I just can't do it right now cause I'm at work :)

[alanz]

Ok. I think https://github.com/commercialhaskell/stack/blob/master/CONTRIBUTING.md might be useful, and also to consider the process used in haskell-mode, but not using the wiki as people are more happy to engage if there is a PR for docs.

See also #13 cc @gracjan

[alanz]

I actually think I prefer "well defined task" to "help wanted"

[gracjan]

👍

I would love labels to mean 'what is supposed to happen with this issue?'. So only labels that are actionable.

[alanz]

I also know that "well defined task" is a thing that haskell-mode uses to great effect to encourage initial contributions.

"help wanted" does not say anything about how difficult/complex the task is

[gracjan]

Well defined task has also this nice property that it forces project leaders to actually write up properly what they want :)