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

[pre-]populating with GitHub labels #69

Open
plehegar opened this issue Nov 9, 2017 · 3 comments
Open

[pre-]populating with GitHub labels #69

plehegar opened this issue Nov 9, 2017 · 3 comments
Assignees

Comments

@plehegar
Copy link
Member

plehegar commented Nov 9, 2017

There is no way to import labels to a [new] repo. Instead, one has to add them by hand.

This would allow WGs to reuse the same labels and to provide on top of that a consistent tool that would output a disposition of comments.

Labels are also listed here
https://w3c.github.io/issue-metadata.html

@dontcallmedom
Copy link
Member

some thoughts:

  • for new repos, ash-nazg might be a logical place to set default labels
  • for existing repos, ash-nazg could help when importing; and maybe we make it available independently of importing (and make ash-nazg a generic repo manager, not just from an IPR perspective?)
  • we could also add a test in the repo validator to check which repos have aligned their labels or not

@tripu
Copy link
Member

tripu commented Nov 23, 2017

“There is no way to import labels to a [new] repo. Instead, one has to add them by hand.”

I'm not saying groups should do this (it's cumbersome) but, for the record, @sandhawke documented a way to import labels programmatically, and suggested an initial set of labels of his own.

“This would allow WGs to reuse the same labels and to provide on top of that a consistent tool that would output a disposition of comments.”

There was more or less agreement about merging Sandro's labels with the ones already in this repo. Anyway, the set here has been extended and redefined in the meantime, so I propose we consider the suggested labels good enough, and forget about them until we get significant feedback after some time.

Anyway, +1 to @dontcallmedom's suggestion about doing this from the Repo Manager at some point.

@plehegar plehegar self-assigned this Nov 27, 2017
@plehegar
Copy link
Member Author

plehegar commented Jun 7, 2018

@tripu should this be co-assigned to you if you're looking at ash-nazg?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants