Noticing, tracking and debugging errors should be easy. A Wikimedia developers and users should be able to easily notice new errors (possibly only a subset of them that they are interested in), find out details, and share with others. At the same time security and privacy standards should be enforced.
- Mentioned In
- T227493: Error on tokenise method doesn't allow auto-saving or publishing of article
T167699: [EPIC] Enable JS error reporting in the mobile website
T171577: Develop a long term vision for community managed scripts and gadgets
T108282: Update broken gadgets on WMF wikis (tracking)
- Mentioned Here
Being bold and adding the Developer-Wishlist tag.
If I understand correctly what this technology does, deploying it will help me a lot, both as a developer of Gadgets and as a developer of MediaWiki features and extensions that are deployed on a lot of sites and clash with local gadgets much more frequently than anybody would like to.
For what is worth, I believe that the Developer-Wishlist (2017) can be used to grasp the level of interest of an idea. We told ourselves that we would allow some experimentation.
The title for the survey could be "Agree on a plan to use Sentry in production". The possible plans agreed could be many, included "Not in the next 18 months", but at least there would be a discussion in the good direction.
This proposal is selected for the Developer-Wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) of the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title "Description," to your content. Please do so before February 5th, 12:00 pm UTC.