Page MenuHomePhabricator

Find a way to collect user feedback on Wikimedia's technical wikis
Closed, ResolvedPublic

Description

We need a way to collect the user feedback about our technical documentation. Feedback from users will lead to improved current documentation and will help us to understand the problems.

There are two requirement:

  1. User should able to give feedback on quality of documentation
  2. User should able to leave generic positive/negative feedback with description

Method 1: Feedback gadget with event logging

In this way, we can use Gadget-userfeedback.js to collect feedback.

But this method had very limited impact. Example: On API documentation, only 38 responses were received out of 67,000+ pageviews. Also, it requires someone from WMF staff to query the feedback as data is being stored on Wikimedia’s hive which requires privileges.

Method 2: Collect feedback on centric JSON page

In this way, we can create a Gadget that will collect feedback from users on the page and will store the data on a centric JSON page on the wiki through AJAX.

It has some privacy issues as we can store the data only for 90 days. Also, all feedback will be public so there will not be any chance to delete data after 30 days.

Method 3: Redirect them to a centric talk page

In this way, we can create a template and put it on every page. In template, we will ask users to go to a centric talk page like Manual_talk:Maintenance_scripts and leave the feedback there.

Method 4: Collect through Google Form

Create a Google form and send it to mailing lists, village pump, and user’s talk pages. In this way, we can collect the data but this is not sustainable and it can be used for a very limited time. Also, users will not be able to give feedback any time as Google form will have closing dates at some point.

Related Objects

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Method 1: See T290018: Plan for feedback gadget - the number of users leaving actionable (!) feedback has been too small to be useful, plus having to scroll to the very bottom of a page isn't very discoverable.
Personally speaking, Method 3 makes most sense to me, in combination with clear commitments who plans to watch a page.
Before thinking about any of this though, I'd be the devil's advocate asking who is supposed to look at feedback and then... "act" on it, somehow. There are already many places where feedback is given, so "improve current documentation and help us to understand the problems" would already be possible, IMHO? In different words, is there a deeper definition of the problem to solve available, before talking about potential solutions? :)

Jayprakash12345 claimed this task.

We decided to go with Method 4 (Google Form).