Fri, Feb 7
Fri, Jan 31
Jan 24 2020
Fixed Graph 1, Series B by running aliasSub() after aliasByNode()
Jan 10 2020
Dec 12 2019
Dec 11 2019
Dec 6 2019
Nov 29 2019
Nov 22 2019
@awight Can this be marked as resolved or do you still want to have another look?
Nov 15 2019
Seemed to be some weird glitch with Grafana/Graphite, I don't believe the problem still occurs with the new graphs.
Other minor suggestions:
- Would be nice to have a legend, maybe with the average for each group over the timespan.
- It might be impossible, but can be groups be given names which naturally collate in an order that makes sense? We should have thought of this at coding time, it might be annoying now.
I don't know of any easy way way that wouldn't affect performance and/or readability
- "User Contribution Score" is usually "by Editor Experience"
- Null value handling (Display tab) should probably be "zero" or "connected", depending on the metric. Otherwise we have discontinuities.
- aliasByNode can usually be aliasByMetric, then you don't have to specify the node position.
Using aliasByMetric after asPercent appears to result in an empty alias so I opted for aliasByNode
Taking into account the metrics added in T236886 (editor experience = anon, under11, over10, over100, or over200) we can answer the following questions:
- What % of edit conflicts experienced using TwoColConflict are resolved, grouping by editor experience?
- What % of edit conflicts experienced using the default interface are resolved, grouping by editor experience?
- What % of edit conflicts experienced using TwoColConflict are left unresolved, grouping by editor experience?
- What % of edit conflicts experienced using the default interface are left unresolved, grouping by editor experience?
Nov 8 2019
Added the following graphs:
Oct 25 2019
Oct 16 2019
Sep 30 2019
@Dzahn Sure, the SSH public key is this one P9126 (created exclusively for production):
Sep 25 2019
Verified by import from test2 to testwiki:
Verified by import from test2 to testwiki, see edit summaries on test2:
Sep 18 2019
Sep 11 2019
Jul 12 2019
Jul 11 2019
I noticed that if we would like to use Interwiki links in the summaries instead of plain URLs, and continue to support third-party wikis, we would need to make use of the Interwiki API endpoint on the source wiki. This would allow us to determine which prefix should be used to represent the destination wiki and then use that prefix when building the edit summary. An example where this API endpoint was used is https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/FileImporter/+/520197/.
Jul 3 2019
Jul 2 2019
Jul 1 2019
Jun 26 2019
Jun 19 2019
Jun 5 2019
I might be missing something here but couldn't we simply do the following:
May 29 2019
May 22 2019
Apr 30 2019
Apr 24 2019
Apr 11 2019
Mar 20 2019
Looks fine from my side, @thiemowmde?