NextGenerationChanges
What (summary)
A new model of changes that focuses on sets of changes and spans all the different kinds of changes people make to the site.
Why this is important
As we develop many new ways to add and edit content that isn't traditional wikitext, we need to be able to patrol and peer-review those modifications.
DoneDone
- Every change is accessible from a single unified queue of changes
- Anything you can do to one change you can do to a set of changes
- History for any title shows all changes to the title, including changes to transcluded content
- All past changes to the wiki have been imported to the new format
A patroller/reviewer can
- select changes based on metadata about the changes
- IPs of changers
- Usernames of changers
- Titles changed
- Types of changes
- Level of detail of changes
- add/edit metadata about a set of changes
- include a reference link or citation for any content in the change
- create a change summary that groups a set of smaller, more detailed changes after they are created
- sign-off that a set of changes is constructive
- ask for help determining what to do about a set of changes, including their recommendation
- Undo the effects of a set of changes
- Action reporting pages are no-indexed (perhaps through robots.txt)
Views
- List view (a collection of actions/groups), one line per action
- Size of changes in bytes
- Summary view (a collection of actions/groups), some details per action
- Detailed view (one action/group), all the details you need
Steps to get to DoneDone
- Create Actions for all legacy changes (see below)
- Undo/Redo for normal edits
- Good looking details on summary view (side by side diff for pages)
- Link back to state (previous action) that the action refers to for diff purposes
- Display friendly selector error messages
- Prove timestamps are handled correctly, add ability to set timezone and display in local times
- Patrol Tool (see below)
Create Actions for all legacy changes
- Catalog all the kinds of changes that are currently saved in mediawiki
- R UserRegister (user)
- UserAuthenticateEmail (user)
- R UserBlock a user or ip (logging)
- R UserUnBlock a user or ip (logging)
- UserRename (logging, renameuser/renameuser)
- UserRightsAdjust change for a user (logging, rights/rights)
- R PageCreate (revision, recentchanges)
- R PageRevise (revision, recentchanges)
- PageDelete and archive page (logging)
- PageRestore and archive page (logging)
- PageMove page (logging)
- PageProtect page (logging)
- PageUnProtect page (logging)
- R ActionPatrol a revision (logging, recentchanges)
- R ActionUnPatrol a revision (logging, recentchanges)
- interwiki change (logging)
- newusers created (logging)
- ? upload image or file (logging)
Patrol Tool
- Mark Patrol 60%, Roll-To 10%, FixName 5%, Punt 1%, Tab out to interact 25%
- Asad Patrol 60% Roll to 15% Fix name 10 % Clear 3% Edit 20%
- Obed patrol: 40%, rollto: 18 %, fixname:12%
- Wishes
- Zero waiting
- Skip button
- Comment field for patrol, etc
- History of recently patrolled ... allows to edit, would be nice if tabbed to page
- Fixname in place
- Group by page, by user, by tag/category, by ip
- No empty edits
- Marking Adult Pages, ParkingLots, 404s etc, www.aboutus.org/AddSiteTools, www.AboutUs.org/AddSubdomain, NoWebsite, Undelete www.aboutus.org/Undelete (these are templates)
- Notice interesting edits
- Patrol all by this user
- Undo all by this user
- Group by user ... group by the type of edit, if they are doing the same edit over and over, they would all get grouped together
- make sure that there is a good crop of changes to patrol
- talking about placement, perhaps the Patrol button can be made bigger than the rest since that is what we use the most. Grouping the 'controls' in one area also would be nice from a UI stance (i think, so dont move the mouse too much)
- Add edit button to the interface, so we can directly go to the edit page.
- Actions by sysops, Activecommunity, bot should should be automatically marked as patrolled. (currently they show up on the unpatrolled page).
- randomize the start number for unpatrolled actions page in order to avoid duplication.
- rollback by a sysop, Activecommunity member should automatically patrol all the rolled back actions.
