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/build: surface port maintainers on dev.golang.org #50933

Closed
bcmills opened this issue Jan 31, 2022 · 3 comments
Closed

x/build: surface port maintainers on dev.golang.org #50933

bcmills opened this issue Jan 31, 2022 · 3 comments
Labels
Builders FeatureRequest NeedsInvestigation
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Jan 31, 2022

https://dev.golang.org/owners currently lists code owners for a large subset of packages in the Go project.

However, when it comes to tracking down build and test failures, code owners are only half of the story. Our requirements for a new port also require that “[a]t least one developer must be named (and agree) to maintain the port, by making required updates in a timely manner as architecture or operating system requirements change.”

When we spot a port-specific issue, we need to know who to loop in to make the updates needed to resolve that issue.

Some of that information is currently embedded in the Owners field for the builder information in x/build/dashboard/builders.go, but:

  • that information is difficult to find within the file,
  • the file itself is not particularly discoverable, and
  • nothing guarantees that the owner of the builder is the owner for the corresponding port.

Either dev.golang.org/owners or a similar page on dev.golang.org should identify port owners explicitly by GOOS and GOARCH.

(CC @golang/release for prioritization)

@bcmills bcmills added NeedsInvestigation FeatureRequest labels Jan 31, 2022
@bcmills bcmills added this to the Backlog milestone Jan 31, 2022
@gopherbot gopherbot added the Builders label Jan 31, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented Jan 31, 2022

(This issue may be a duplicate, but if so I couldn't find the issue it's a duplicate of. 😅)

@seankhliao
Copy link
Member

@seankhliao seankhliao commented Jan 31, 2022

this? #28596

@bcmills
Copy link
Member Author

@bcmills bcmills commented Jan 31, 2022

Duplicate of #28596

@bcmills bcmills marked this as a duplicate of #28596 Jan 31, 2022
@bcmills bcmills closed this as completed Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Builders FeatureRequest NeedsInvestigation
Projects
None yet
Development

No branches or pull requests

3 participants