Open froschdesign opened 7 years ago
@froschdesign IMHO, It would be much easier if we define here all label set and then write the script to update the labels in all repositories. We can use script you provided or write simply script (using https://github.com/KnpLabs/php-github-api) to update labels from template for all repos. So it would be generic script and everyone would be able to use it for own repository if needed :)
I've wrote script to fetch all labels and generate html table with them: https://github.com/webimpress/github-labels
Result for zendframework
org we can see here:
https://webimpress.github.io/github-labels/zendframework.html
And here is it for zfcampus
:
https://webimpress.github.io/github-labels/zfcampus.html
Not sure if it will be possible to set the same labels for all repositories. Definitely we can do something to improve these labels between all repositories.
@froschdesign any thoughts?
@webimpress First: sorry for the late response.
It would be much easier if we define here all label set and then write the script to update the labels in all repositories.
Very nice idea!
Not sure if it will be possible to set the same labels for all repositories.
Why not? The solution should be as simple as possible. It is not necessary to use all labels, but we should have the same labels in all repositories.
@froschdesign
Very nice idea!
Are you going then propose list of common labels? 😄
Why not? The solution should be as simple as possible. It is not necessary to use all labels, but we should have the same labels in all repositories.
Have you seen https://webimpress.github.io/github-labels/zendframework.html? Probably we don't want to have all lables from zf1 everywhere else
Are you going then propose list of common labels?
I will create a list.
Have you seen https://webimpress.github.io/github-labels/zendframework.html? Probably we don't want to have all lables from zf1 everywhere else
Sorry, I mean not all labels from all repositories. I mean only all relevant labels should be synchronize for all repositories.
My suggestion:
Label name | Color | Description | Comment |
---|---|---|---|
awaiting author updates | #e11d21 |
||
awaiting maintainer response | #fbca04 |
||
bc break | #e11d21 |
||
bug | #fc2929 |
Something isn't working | |
documentation | #207de5 |
||
documentation needed | #c7def8 |
||
duplicate | #cccccc |
This issue or pull request already exists | |
easy fix | #02d7e1 |
should be removed; see my comment below | |
enhancement | #84b6eb |
||
feature removal | #eb6420 |
||
feature request | #0052cc |
||
good first issue | #7057ff |
Good for newcomers | proposal from GitHub |
help wanted | #159818 |
proposal from GitHub – we already use this | |
invalid | #e6e6e6 |
This doesn't seem right | |
question | #cc317c |
Further information is requested | |
revert needed | #e11d21 |
||
review needed | #ff9500 |
||
unit test needed | #eb6420 |
||
work in progress | #0b02e1 |
||
won't fix | #ffffff |
This will not be worked on |
What about "wontfix" #ffffff
? I've seen it used couple of times, for example:
https://github.com/zendframework/zend-code/issues?q=label%3Awontfix+is%3Aclosed
Just forget. I updated the list.
Another suggestion, maybe we can have consistent label texts, for example, now we have:
needs documentation
needs revert
unit test needed
maybe needs unit test
or all with ... needed
(we have also help wanted
...).
I think we can and should remove the label "easy fix". The label can be replaced with "good first issue" and "help wanted", because these labels are supported by GitHub and the wording is much better for the end user and what he can do.
The new component zend-expressive-session-cache includes already some descriptions for the labels:
https://github.com/zendframework/zend-expressive-session-cache/labels
Problem
At the moment we must add and edit all the labels with name and color (code) by hand. This results in different labels across the entire "zendframework" account.
Target
Suggestion
Synchronize all labels between the different repositories by script. And if we do not want to reinvent the wheel: Piwik already has a script.