Difference between revisions of "StrategyForKeepingUnpatrolledRecentChangesLow"

(Why we are doing this: alternative point of view)
(Strategy)
Line 21: Line 21:
  
 
==Strategy==
 
==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:
+
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 low are:
  
 
* Cleanup the recent changes before leaving on Friday evening
 
* 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
+
* 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 high
 
* Email alert to all staff members if RC goes above 3000
 
* Email alert to all staff members if RC goes above 3000
  
Line 31: Line 31:
 
:[[Umair]]|[[user talk:Umair Tamim|talk]]
 
:[[Umair]]|[[user talk:Umair Tamim|talk]]
  
 +
:: Let's not forget that staff doing RC is not sustainable.  When we're making our strategy, we need to take that into account.  In my opinion, what we need to do is find a way to get community members to do our patrolling.  Drew does some of this, for example.  Currently we need more than one person-day of effort on RC every day, right?  Call is 10 hours as a round number.  What would it take to have the community doing half of that?  Five person hours per day is 300 person minutes per day.  Do we have 15 community members that would do 20 minutes a day?  This will take time to develop and may require enhancements to [[UberPatrol]] so we can have a MetaPatrol.  As we increase active member patrolling, we have to correspondingly reduce staff patrolling, to make sure the active members always have something to do.  Of course sometimes we'll want to really "Push For Zero" to get active members more excited, but if we're near zero all the time, some of them will lose interest, as there's no vandalism to take care of. [[Ted Ernst]] | <small>[[User talk:TedErnst|talk]]</small> 06:14, 5 September 2007 (PDT)
  
 
==Discussion==
 
==Discussion==

Revision as of 13:14, 5 September 2007

OurWork (??) StrategyForKeepingUnpatrolledRecentChangesLow (Who?) OLDOLD

talk

We are done when

  • We have come up with a strategy for keeping unpatrolled recent changes low

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 low 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 high
  • Email alert to all staff members if RC goes above 3000
  • There should be an awareness session by the community team where one of us discusses the importance and strategy of RC with every individual staff member (i.e. something similar to the ConsensusPollingAwareness task).
  • There could always be at least two people on patrol every second. This will ensure that RCs are being taken care of constantly.
Umair|talk
Let's not forget that staff doing RC is not sustainable. When we're making our strategy, we need to take that into account. In my opinion, what we need to do is find a way to get community members to do our patrolling. Drew does some of this, for example. Currently we need more than one person-day of effort on RC every day, right? Call is 10 hours as a round number. What would it take to have the community doing half of that? Five person hours per day is 300 person minutes per day. Do we have 15 community members that would do 20 minutes a day? This will take time to develop and may require enhancements to UberPatrol so we can have a MetaPatrol. As we increase active member patrolling, we have to correspondingly reduce staff patrolling, to make sure the active members always have something to do. Of course sometimes we'll want to really "Push For Zero" to get active members more excited, but if we're near zero all the time, some of them will lose interest, as there's no vandalism to take care of. Ted Ernst | talk 06:14, 5 September 2007 (PDT)

Discussion



Retrieved from "http://aboutus.com/index.php?title=StrategyForKeepingUnpatrolledRecentChangesLow&oldid=9452303"