Last modified: 2014-04-20 18:47:22 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T52867, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50867 - Add a way to thank page patrollers for reviewing a page I created
Add a way to thank page patrollers for reviewing a page I created
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Thanks (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 58485
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-06 15:40 UTC by Technical 13
Modified: 2014-04-20 18:47 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Technical 13 2013-07-06 15:40:41 UTC
There should be a way of thanking NPP patrollers for reviewing my creations.  I think this would improve moral of reviewers and encourage more reviewers since I am sure there is always a backlog.
Comment 1 Liangent 2013-07-06 15:42:05 UTC
So a more generic "thank for log entries"?
Comment 2 Technical 13 2013-07-06 15:58:18 UTC
I was thinking a simple link in the notification for the review.
Comment 3 Nemo 2013-10-07 10:11:37 UTC
(In reply to comment #2)
> I was thinking a simple link in the notification for the review.

Are there log entries for such reviews? Or can we just use patrol/patrol?
Comment 4 John Mark Vandenberg 2013-11-11 08:25:52 UTC
The 'patrol' action doesnt always mean the page patroller has accepted the created page.  They may have tagged it for deletion and then marked it as patrolled to remove it from the patrol queue.

As a result the page creator needs to see what actions have been taken before they thank the page patroller, otherwise they will be thanking the patroller for deleting the page, which is not what they wanted to do.

One approach is to wait until echo understands negative feedback, like prod, csd and afd.

https://www.mediawiki.org/wiki/Echo_%28Notifications%29/Feature_requirements#Started_Page_-_Tagged

https://www.mediawiki.org/wiki/Echo_%28Notifications%29/Feature_requirements#Started_Page_-_Marked_for_deletion

The simplest solution is to take the creator to the history tab, where the reader can see the current status, and the 'thanks' buttons are ready to use.

I've mentioned that here:

https://www.mediawiki.org/wiki/Talk:Echo_%28Notifications%29/Testing#Links_in_notification_text

Another idea is to have a streamlined UI for the article creator to give a specific 'thanks for reviewing my page' WikiLove to a page patroller.
Comment 5 Nemo 2013-11-11 08:35:45 UTC
(In reply to comment #4)
> The 'patrol' action doesnt always mean the page patroller has accepted the
> created page.  They may have tagged it for deletion and then marked it as
> patrolled to remove it from the patrol queue.
> 
> As a result the page creator needs to see what actions have been taken before
> they thank the page patroller, otherwise they will be thanking the patroller
> for deleting the page, which is not what they wanted to do.

Why not? Some feedback is better than no feedback; we're supposed to be here for a shared goal, if the patrolling action was correct everyone should be happy. We also see people thanking for reverts of their own edits, as far as I know.

More in general, I suppose the assumption of the thanks feature is that people are able to discern and have enough context to judge the actions they click "thank" for; if not, why would this feature even exist?

> The simplest solution is to take the creator to the history tab, where the
> reader can see the current status, and the 'thanks' buttons are ready to use.

So your proposal to give users more context is appropriate, but it's a separate enhancement request (doesn't block not is blocked by this one).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links