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

x/pkgsite: automate trivial package removal requests #70714

Open
findleyr opened this issue Dec 6, 2024 · 1 comment
Open

x/pkgsite: automate trivial package removal requests #70714

findleyr opened this issue Dec 6, 2024 · 1 comment
Labels
Friction Nuisances that make good candidates for our "friction" fix-it weeks pkgsite

Comments

@findleyr
Copy link
Member

findleyr commented Dec 6, 2024

This is a reminder issue for a future team friction fixit week: we could reduce toil significantly by automating pkgsite removal requests.

Right now, the pkgsite removal process requires users to file an issue requesting the removal of a package from pkgsite. Our triage person handles this request by (1) verifying some form of ownership for the relevant paths, and (2) sending an internal CL to exclude the paths from pkgsite. We get a steady stream of these requests, on the order of a few a week. They are almost all trivial, but still a source of interrupts and toil. Additionally, sometimes it takes several days (or even more than a week) to get to them, which is not a great experience for the requester.

We have considered completely changing the removal process to be more self-service, but one of the goals of the current process is to preserve an audit log, and github issues are (for better or worse), the canonical audit log for changes to the Go project. We thought that module retractions would be a self-service way to remove content from pkgsite, but they only hide packages from search. Also, in the common case the repo has been deleted, so retractions are onerous on authors. For this reason, retractions do not seem to have reduced the number of removal requests we receive.

We could keep the current process, and reduce most of the toil, with automation:

  1. Find pkgsite removal issues. Extract the requested path(s) to remove.
  2. Check for ownership. It may suffice to check that the requester is the owner of repos containing the paths, though in some cases we need to check for organization membership.
  3. Send an internal auto-submit CL to the tools team to process the removal.
  4. Comment and close the issue.
@findleyr findleyr added the Friction Nuisances that make good candidates for our "friction" fix-it weeks label Dec 6, 2024
@findleyr findleyr added this to the pkgsite/backlog milestone Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Friction Nuisances that make good candidates for our "friction" fix-it weeks pkgsite
Projects
None yet
Development

No branches or pull requests

3 participants