Manual tagging of edits, for review
Open, LowPublic

Description

Author: sgwikieo

Description:
As well as having patrolled edits (ones that aren't obvious vandalism I think),
there should be suspicious edits (changing a detail for example)


Version: unspecified
Severity: enhancement

Details

Blocks
T5741: Stable Version / Review / Tagging (tracking)
Blocked By
T20670: Create ability to add / remove tags from edits / actions
Commits
Unknown Object (Diffusion Commit)
Reference
bz1189
bzimport set Reference to bz1189.
bzimport added a subscriber: Unknown Object (MLST).
bzimport created this task.Dec 24 2004, 5:36 AM

zigger wrote:

*** Bug 3299 has been marked as a duplicate of this bug. ***

robchur wrote:

How would you compute what's supicious? I'm interested, just skeptical we could
find a good enough algorithm.

ssd.wiki wrote:

Suspicious edits should be flagged by a user who saw it, but isn't sure of the
details, and does not want to (or can't) research it. This is somewhat similar
to the {{fact}} template on en:

mxn added a comment.Mar 6 2006, 12:48 AM

It could be more general, like the HELPWANTED keyword on Bugzilla, for example.

dogshed wrote:

Can we fold this into 4288?

dogshed wrote:

Can we fold this into bug 4288?

I've done some work in r17608 and r17609 to implement something similar to the
feature described in this bug.

robchur wrote:

Ultimately, I'm not sure expanding the scope of automatic edit summaries is the
way to go about addressing this request; I think it would be more effective in
the long run to introduce some sort of flag for a change, indicating it should
be double-checked. Then again, existing patrolling features (and extensions),
and forthcoming stable version tagging and reviewing features will make this
kind of thing obsolete.

Right. And the auto-summary code will be adapted to be a tag instead of an
autosummary when this tagging code comes around.

aaron added a comment.Aug 31 2007, 8:59 AM

*** Bug 8221 has been marked as a duplicate of this bug. ***

ayg wrote:

Bug 8221 has a considerably more detailed proposal that might or might not be the best way to do this.

I've got some interest in implementing this when I have time. Flags could be applied, for example, by the Abuse Filter, and Tor Block extensions.

We do have change tags in MW now

demon added a comment.Jul 14 2009, 7:56 PM
  • Bug 1596 has been marked as a duplicate of this bug. ***
demon added a comment.Jul 14 2009, 7:57 PM
  • Bug 4288 has been marked as a duplicate of this bug. ***
demon added a comment.Jul 16 2009, 5:33 PM
  • Bug 4288 has been marked as a duplicate of this bug. ***

mike.lifeguard+bugs wrote:

This request is about allowing humans to manually add a marker to a revision - not doing this automatically as AbuseFilter and TorBlock do.

Qgil added a comment.May 17 2014, 12:42 AM

It looks like starting with Bugzilla was/is the wrong path for this request. First the feature should have buy-in from the editors (pick a project, i.e. enwiki), and if it has consensus then we can discuss about implementing it.

As it is now, no developer will jump on it.

(In reply to Quim Gil from comment #18)

It looks like starting with Bugzilla was/is the wrong path for this request.
First the feature should have buy-in from the editors (pick a project, i.e.
enwiki), and if it has consensus then we can discuss about implementing it.

As it is now, no developer will jump on it.

This is nonsense. Adding arbitrary tags to revisions is inherently useful.

This Bugzilla installation and its various inputs are a clear demonstration of the utility of tags and keywords and a whiteboard. Of course Bugzilla attaches this metadata to bugs (vaguely equivalent to pages) rather than comments (vaguely equivalent to revisions), but between this ancient bug report and its duplicates, there's obvious interest in implementing this capability.

It also seems noteworthy that there's now a "Change tagging" component in Bugzilla. It'd be nice if users could, uh, tag changes.

Whether to put this feature in MediaWiki core or in a MediaWiki extension is up for debate, though.

werdna removed a subscriber: werdna.Dec 10 2014, 6:16 PM
He7d3r added a subscriber: He7d3r.Jan 3 2015, 2:28 PM
epriestley added a commit: Unknown Object (Diffusion Commit).Mar 4 2015, 8:21 AM
Qgil added a comment.Mar 4 2015, 8:40 AM

Accidental clash. Known issue. Sorry for the noise.

TTO added a subscriber: TTO.Apr 16 2015, 1:13 PM

How is this different from T20670? Can we close this now?

Add Comment