You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Find pkgsite removal issues. Extract the requested path(s) to remove.
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.
Send an internal auto-submit CL to the tools team to process the removal.
Comment and close the issue.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: