Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rationalise Issue Labels #1477

Closed
3 tasks
ajj opened this issue Mar 18, 2020 · 5 comments
Closed
3 tasks

Rationalise Issue Labels #1477

ajj opened this issue Mar 18, 2020 · 5 comments
Assignees
Labels
Good First Issue Issues that are appropriate for newbies Infrastructure GitHub, project structure, community etc Slicers Concerns slicer functionality Stale Mark for potential close: issue no longer seems relevant / probably complete / probably not doable.

Comments

@ajj
Copy link
Member

ajj commented Mar 18, 2020

Need to have common labels across repos
Need to have pared down list

  • Inventory existing labels
  • Propose new list
  • Implement new list
@ajj ajj self-assigned this Mar 18, 2020
@butlerpd
Copy link
Member

A couple of points. The simple one -- can we use a checklist for the above three tasks?

Beyond that, aside from the problem of too many labels ... and confusing labels across repos and redundant labels, there is the issue that the labels imported from trac which had several sets of mutually exclusive labels (like importance vs work package vs type -defect/enhancement) which were enforced via dropdowns. Not sure we can enforce as easily with github (not even sure zenhub or the like would do though worth exploring more). I was wondering if templates might help but not had a chance to explore those either. It also would be good to be able to ensure that all labels are in a required category .. like milestone maybe either with an enforcement and/or an easy way to list all that are not in any of items in the category (e.g. not against any milestone). This helps ensure one doesn't completely lose track of issues that accidentally did not get listed against a "milestone"

Those are my thoughts so far .. which does not in fact satisfy even item 1 of the list but maybe suggests ways to look at point 2?

@ajj ajj added the Slicers Concerns slicer functionality label Mar 18, 2020
@ajj ajj added this to the Admin Tasks milestone Mar 18, 2020
@ajj
Copy link
Member Author

ajj commented Mar 18, 2020

Starting wiki page https://github.com/SasView/sasview/wiki/Labels to track info

@lucas-wilkins
Copy link
Contributor

Vote to close with my recent changes applied (almost done) ??? @wpotrzebowski @butlerpd @pkienzle

@lucas-wilkins lucas-wilkins added Infrastructure GitHub, project structure, community etc Good First Issue Issues that are appropriate for newbies Stale Mark for potential close: issue no longer seems relevant / probably complete / probably not doable. and removed good first infrastructure issue labels Jul 19, 2022
@butlerpd
Copy link
Member

I would say it is a work in progress but to the extent that it is being actively worked on (I think there is still a way to go to make things properly useful) I'm happy to close this for now.

@lucas-wilkins
Copy link
Contributor

It's done on sasview. I might start elsewhere next time I find tedious-admin-job time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good First Issue Issues that are appropriate for newbies Infrastructure GitHub, project structure, community etc Slicers Concerns slicer functionality Stale Mark for potential close: issue no longer seems relevant / probably complete / probably not doable.
Projects
None yet
Development

No branches or pull requests

4 participants