-
-
Notifications
You must be signed in to change notification settings - Fork 989
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
Read-only API for retrieving Trac data #1657
Comments
I’d love to see this happen, as this kind of API endpoint seems to be the only reliable way to check people’s commenting and triaging activity. For example, this would help in assessing people’s eligibility as candidates for Steering Council elections, as triaging contributions are one of the areas where we acknowledge candidates’ work:
So I need a way to assess how often someone helps by:
In the meantime I’m using |
An idea was discussed in the DSF office hours to have a GitHub action for So for example, adding a "needs review" label (which would check the ticket from the title and needs_docs=0, needs_tests=0, patch_needs_improvement=no), a "needs tests" label etc. Having an api which includes these flags for tickets would be really great 💚 I don't mind working on this but would appreciate an agreement on what would be the minimum work required to get this accepted |
Per discussion in django/code.djangoproject.com#198 (comment).
The same XmlRpcPlugin for Trac that we removed in django/code.djangoproject.com#198 was also responsible for the JSON RPC (
/jsonrpc
endpoint). The endpoint seems useful for extracting data to gain insights, e.g.Instead of restoring the old API, which relies on an old Trac plugin and does not give us full control over the output, we probably want to create our own API.
There is a draft PR at #1656.
For now, I think it's OK to limit the scope of the API to be read-only. If we find use cases for a write API, we can file a separate issue.
The text was updated successfully, but these errors were encountered: