StrategyForKeepingUnpatrolledRecentChangesLow

OurWork (??) StrategyForKeepingUnpatrolledRecentChangesLow (Asad, Obed, Ted, Kasey)

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)
Ted, I absolutely like the idea of involving community with RC. Should we make it a task for our next iteration? We need to have some clear guidelines of when a member should be given the Sysop status, so they can help? I also agree with Kasey that we should tell the new users how they can help. But all this as you said earlier, will take time to develop. So should we make a separate page for discussing how we can get community members to join us in patrolling while this page is reserved for coming up with a strategy for keeping unpatrolled RC with the help of resources available to us at this stage? Best, Asad
Maybe, we should use this page: RecentChanges:InvolvingOthers? Obed Suhail
Yes, that's the one. I don't have a clear sense of how long it will take us to be ready to invite folks to help. We already have some people looking for spam and such. The difference is that they're not sysops, so don't actually take away the red exclamation mark. In any event, let's move this discussion about involving others to the Involving Others page. TedErnst | talk 06:27, 11 September 2007 (PDT)
Agreed. Staff, especially under our new plan which has the CommunityTeam responsible for ensuring changes are patrolled ideally with community involvement. RC is not scalable and we need to draw our community into RC.
Part of the problem, beyond lacking in numbers, is our ineffective messaging to new users and the community.
Our RecentChanges_patrol page needs help! This page could be a tool; ways to share, ask questions, connect, or how to get started. Maybe some examples or more explicit instructions, or a link to PuntedPages or NeedsAttention (same page).
Maybe our Welcome message could contain a link to HowYouCanHelp, I believe Kristina does this already- so cool. Currently, the RecentChanges_patrol page is not all that helpful We can build the page to be more inviting to users and community members and then, actually link to it and use it. There is some disconnect too between what HowYouCanHelp says about RC (under Collaborate) and what you get on the RecentChanges_patrol page. I don't get any sense of how one would use her expertise and the drive to given the information on the page presently. Kasey 11:16, 5 September 2007 (PDT)
Kasey, I agree with you on inviting community to join hands on RC and also on incorporating the HowYouCanHelp link into the welcome message, but could you please say a bit more about how RecentChanges Patrol page can be improved to make it more useful? Best, Asad

Discussion

  • Not sure how this strategy is to evolve, or how effective this process is. Ideas? Kasey 09:17, 7 September 2007 (PDT)


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