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

Stop using GitHub projects #1898

Closed
9 tasks
jonmeow opened this issue Aug 3, 2022 · 3 comments
Closed
9 tasks

Stop using GitHub projects #1898

jonmeow opened this issue Aug 3, 2022 · 3 comments
Labels
infrastructure needs admin Requires an admin to work on it.

Comments

@jonmeow
Copy link
Contributor

jonmeow commented Aug 3, 2022

I think GitHub's new project are necessary to get contributions going correctly (it seems v1 ACLs don't work right for triage). Notes:

  • Add v2 projects to org as "xyz v2" or similar
  • Mirror columns over
  • Add v2 projects to repo
  • Mirror tasks over
  • Disable (or immediately replace) proposal project actions
  • Remove v1 projects
  • Rename v2 projects to v1 names
  • Figure out new proposal project actions
  • Update new_proposal.py to set v2 project
@jonmeow jonmeow self-assigned this Aug 3, 2022
@jonmeow jonmeow removed their assignment Aug 3, 2022
@jonmeow jonmeow added the needs admin Requires an admin to work on it. label Aug 3, 2022
chandlerc pushed a commit that referenced this issue Aug 6, 2022
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)
@jonmeow jonmeow changed the title Switch to GitHub's projects v2 Stop using GitHub projects Aug 12, 2022
jonmeow added a commit that referenced this issue Aug 12, 2022
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
@jonmeow
Copy link
Contributor Author

jonmeow commented Aug 12, 2022

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
"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

@jonmeow
Copy link
Contributor Author

jonmeow commented Aug 12, 2022

Had some permissions issues I figured out after a few tries (#2012 #2013 #2014), and I think this is now done.

@jonmeow jonmeow closed this as completed Aug 12, 2022
@jonmeow
Copy link
Contributor Author

jonmeow commented Aug 12, 2022

Also #2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure needs admin Requires an admin to work on it.
Projects
None yet
Development

No branches or pull requests

1 participant