x/pkgsite: consider surfacing fork status and activity details vs upstream #61306
Labels
Milestone
Comments
|
The tricky part is the source of the information is proxy.golang.org, which doesn't have sufficient info to tell which is a fork. In theory, the pkgsite may try to check the source repository (heuristically) and query hosting sites (if they offer apis). But I wonder if it's better to investigate we could get better signals from proxy to improve search ranking instead. |
|
Thanks for having looked! I think it may be related tangentially related to #36952 as that one would also need to pull meta information for github and not just the proxy (or the proxy could as it's pulling from github in the end?) |
adonovan
modified the milestones:
Unreleased,
pkgsite/later,
Unplanned,
pkgsite/unplanned
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While in some cases a fork may actually be the better, more maintained, more adopted version, when the parent does have more activity than the fork, it would probably be helpful to show the parent in the Links or elsewhere in the header section of the pkg page
Somewhat related also would be to rank it lower in search results
Example:
https://pkg.go.dev/search?q=fortio&m=
shows
https://pkg.go.dev/github.com/lemonlinger/fortio
and
https://pkg.go.dev/github.com/CrowdStrike/fortio
and
https://pkg.go.dev/github.com/MUzairS15/fortio
all stale forks with minor to no updates and not the original
https://pkg.go.dev/fortio.org/fortio
which isn't at all on the list (only sub packages are somehow)
Screenshot
What did you expect to see?
The text was updated successfully, but these errors were encountered: