Difference between revisions of "StrategyForKeepingUnpatrolledRecentChangesLow"
| Line 1: | Line 1: | ||
| − | [[DistributedPlanningGame|< | + | <noinclude><big>[[DistributedPlanningGame]] < [[CommunityTeam]] < [[CommunityTeamPriorities|Priorities]] < |
| + | </noinclude>[[StrategyForKeepingUnpatrolledRecentChangesUnder3000]] ('''?''') ('''[[Asad]]''') <includeonly>{{JustTinyEditIcon|StrategyForKeepingUnpatrolledRecentChangesUnder3000}}</includeonly><noinclude></big> | ||
| − | |||
===What is this?=== | ===What is this?=== | ||
| Line 24: | Line 24: | ||
[[Category:CommunityTasks]] | [[Category:CommunityTasks]] | ||
| + | </noinclude> | ||
Revision as of 20:55, 24 August 2007
What is this?
- To come up with a strategy for making sure that the unpatrolled recent changes are kept under 3000.
Why we are doing this
- To invite views from community members for a common strategy to keep unpatrolled edits under 3000 so that:
- To make sure that the changes are being monitored all the time
- To ensure that all edits are constructive in nature, so that less vandalism is seen by readers.
We are done when
- We have come up with a strategy for keeping unpatrolled recent changes under 3000
Strategy
The most "critical" time for unpatrolled recent changes is Monday morning, because there is a gap of 39 hours between Friday evening (Portland time) and Monday morning (Lahore). So the two things that we need to do to keep unpatrolled recent changes under 3000 are:
- Cleanup the recent changes before leaving on Friday evening
- One or two people (on a rotation basis) volunteer to keep an eye on the recent changes over the weekend and patrol them if it gets higher than 3000
Discussion
