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
Add support for a 'stats' API, which will give access to various projects statistics. We require at least the following:
Number of submitted patches over given time period (day, week, month, year)
Number of replies to patches over same periods
Ideally we should also be able to do this for series, but this relies on the work being undertaken by @dlespiau so it will need to wait.
Dependencies
This feature may depend on the integration of a REST API, else the XML-RPC interface can be used (though this has downsides).
Additional Work Items
We will need to add support for additional statistics as they become available (i.e. series). We may also wish to add some graphs to make these visualize these statistics for user.
Alternatives
There is no alternative to this in patchwork itself. If you have access to the database, you could theoretically write your own queries but they won't be public. The best alternative is through the use of Mailman. Mailman 3.0 comes with a REST API that we can parse much of the information from. However, in most mailing lists patches are mixed with other development questions so the statistics that Mailman would return will need some work. A distinct patchwork API would complement the Mailman API quite nicely.
Useful resources
Copied from original issue: stephenfin/patchwork#20
The text was updated successfully, but these errors were encountered:
From @stephenfin on June 29, 2015 21:15
Overview
Add support for a 'stats' API, which will give access to various projects statistics. We require at least the following:
Ideally we should also be able to do this for series, but this relies on the work being undertaken by @dlespiau so it will need to wait.
Dependencies
This feature may depend on the integration of a REST API, else the XML-RPC interface can be used (though this has downsides).
Additional Work Items
We will need to add support for additional statistics as they become available (i.e. series). We may also wish to add some graphs to make these visualize these statistics for user.
Alternatives
There is no alternative to this in patchwork itself. If you have access to the database, you could theoretically write your own queries but they won't be public. The best alternative is through the use of Mailman. Mailman 3.0 comes with a REST API that we can parse much of the information from. However, in most mailing lists patches are mixed with other development questions so the statistics that Mailman would return will need some work. A distinct patchwork API would complement the Mailman API quite nicely.
Useful resources
Copied from original issue: stephenfin/patchwork#20
The text was updated successfully, but these errors were encountered: