-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Stop using GitHub projects #1898
Comments
Contributors can't do this right now (requires repo write permissions), need to investigate as part of #1898 (projects v1 vs v2 results may differ)
Separately working on labeling everything and filing tracking issues as discussed. For project columns, the result is: "Blocking issues" -> gone, we haven't been using it "Questions" -> "leads questions" label, open: https://github.com/carbon-language/carbon-lang/issues? q=is%3Aissue+is%3Aopen+label%3A%22leads+question%22 "Resolved" -> "leads questions" label, closed: https://github.com/carbon-language/carbon-lang/issues?q=is%3Aissue+is%3Aclosed+label%3A%22leads+question%22+ "Needs proposal" -> file a tracking issue, remark on the linked issue "Deferred" -> add the "long term" label: https://github.com/carbon-language/carbon-lang/issues?q=is%3Aissue+is%3Aopen+label%3A%22leads+question%22+label%3A%22long+term%22 Note the "long term" label overlaps with the automation that reminds people when we're inactive, so it's two birds, one stone. This is part of #1898
After talking with chandlerc, we decided to disassemble the project boards in favor of only having labels to track. The problem with GitHub is that projects v1 is clearly on its way out and we can't grant access separate from repo write access, while projects v2 isn't ready yet (lacks events to trigger on). So the thought is labels with maybe some action helpers is the right path forward, and using projects was a misstep based on the support level. #1981 does this for proposals. Note we already had information in labels, it's just that the project had been getting treated as the source of record, and now labels will now be the only source. Proposals will generally have two labels: "proposal" to easily search them all, and "proposal " (e.g. "proposal rfc") to designate their state. #1995 describes this for leads questions: "Blocking issues" -> gone, we haven't been using it |
Also #2019 |
I think GitHub's new project are necessary to get contributions going correctly (it seems v1 ACLs don't work right for triage). Notes:
The text was updated successfully, but these errors were encountered: