-
Notifications
You must be signed in to change notification settings - Fork 1k
Project detail statistics: support multiple statistics providers #12789
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
Comments
Also worth considering: it's not a great idea to make too many assumptions about the bandwidth and resource capacity of statistics providers. Although most of the major providers are likely well-resourced, PyPI itself may receive significant inbound traffic, and since subsequent outbound requests are made from the frontend application -- by geographically disparate users -- it could be challenging for providers to filter that traffic. |
Issue: pypi#12789 Signed-off-by: Yuri Konotopov <[email protected]>
Issue: pypi#12789 Signed-off-by: Yuri Konotopov <[email protected]>
* Initial implementation of GitLab statistics Issue: #12789 Signed-off-by: Yuri Konotopov <[email protected]> * project-data: fixed Gitlab's repository icon * csp: limit Gitlab urls to /api/ * gitlab: use "starrers" term instead of "stargazers" and "followers" * gitlab: `MR` abbreviation revealed * gitlab: log errors to console instead of hiding them completely --------- Signed-off-by: Yuri Konotopov <[email protected]>
Fixed in #15931. |
Nice! Thank you, @nE0sIghT! |
What's the problem this feature will solve?
The project detail page displays release-related statistics which can be useful for consumers who would like to gauge project popularity and community size.
Currently, GitHub is the sole supported statistics provider, but there are a number of other source code forges that host FOSS projects and provide statistical information about them.
Describe the solution you'd like
Extend the stats URL detection logic to support multiple source control forges.
Additional context
Different forges are likely to use different naming terminology for their statistics; PyPi could choose to decide upon a standard naming format, and may omit statistical fields from display if they are not relevant or available from a provider.
Each additional provider would likely require an associated
connect-src
entry for the frontend application's content security policy.This repository's test data file (
dev/example.sql.xz
) could provide a way to help figure out potential providers to support.Relates to #4384.
The text was updated successfully, but these errors were encountered: