Community Tech/Who Wrote That revision search tool
This is the project page for Who Wrote That revisions search tool, the #4 wish in the 2017 Community Wishlist Survey (formerly called the "Blame tool.") You can follow this page and get updates as the Community Tech team starts working on this wish.
The purpose of this project is to give editors the ability to easily discover which user is responsible for a specific piece of text, without digging through every revision in the history. The user should be able to specify the wiki, the page and the text string that they're interested in, and the tool will locate the specific diff where that string first appeared on the page.
March 27, 2019
This project is on a brief hold while we put together an interactive prototype and perform user testing on it. As the prototype becomes available, I will post a link to it here so everyone gets a chance to look at it.
February 20, 2019
We have a mockup ready for what the feature will look like, once complete. You can see it below. The colors and fonts you see in the mockup are only meant to indicate that it is a rough design. The main workflow we are looking at for this tool is:
- On a given page, the user can click a button (or link) to enter the "Who Wrote That" mode, where they will be able to use the feature
- The user can click on any word and it will be highlighted, along with any other words that were added in the same diff.
- A popup will be shown with the following information:
- Name of the user who added the word
- Link to the diff where the word was added
- Timestamp of when it was added
- Links to the user's contributions and talk pages
Note: We may end up adding more or less information than what's listed above. We are in the process of figuring out what is feasible and what isn't, from a technical standpoint.
Please leave feedback and comments on the talk page.
January 15, 2019
We're getting the ball rolling on this project now. We are in the research phase of the project and are looking into using WikiWho/WhoColor as a starting point for creating this tool.
March 16, 2018
No progress has been made on this project. We are still focusing on completing other Wishlist projects at the moment before we start anything new. This is next up and we anticipate to begin development in April or May 2018.
February 23, 2018
We took this investigation out of our sprint, as we want to limit our projects in process by completing what's already started before starting anything new.
February 21, 2018
Our investigation (T184144) is in our current sprint and we hope to complete it by the end of February. Once the investigation has been complete we can proceed with deciding to improve an existing tool or creating a new tool.
Jan 2, 2018
First discussion with the team.
As noted in the discussion and voting, there are some existing tools.
- WikiBlame tool by Flominator
- WikiWho by faflo, maribelacosta, bitnik
- There was a Blame feature in the previous version of XTools that was decommissioned in the recent update.
The task for this wish is to figure out what works and what doesn't with the existing tools, and either fix or rewrite one.
WikiBlame tool could use some UI help -- the results are presented in a confusing way.
Do we build this on Toolforge or as an extension on wiki? It's an expensive inquiry, and it'll involve caching lots of data to be performant. This would probably be easier on Toolforge.
What's not working about the existing tool? Accuracy, speed? On an initial test, it performs on some queries and bails on others.
Also: we should figure out another name for it. "Blame" comes from version control on Git -- it's developer humor which won't necessarily translate to other users, especially across languages. "Praise tool" was suggested. We may want something that's more descriptive of what the tool is used for.
Investigation ticket: T184144
December 13, 2017
The team will start investigating this project early in 2018. If you've got suggestions or questions, please write your thoughts on the talk page!
- Wishlist proposal, discussion and votes
- Phabricator tickets tracking the work: T2639
- Investigation ticket: T184144