<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
This is from Wikibooks: <a href="http://en.wikibooks.org/wiki/Help:Revision_review#Editors_and_reviewers"><font class="Apple-style-span" color="#000000">http://en.wikibooks.org/wiki/Help:Revision_review#Editors_and_reviewers</font></a></blockquote>
<blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><h3 style="color: black; background-image: none; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; font-weight: bold; margin-top: 0px; margin-right: 0px; margin-bottom: 0.3em; margin-left: 0px; padding-top: 0.5em; padding-bottom: 0.17em; border-bottom-width: initial; border-bottom-style: none; border-bottom-color: initial; font-size: 17px; font-family: sans-serif; line-height: 19px; ">
<span class="mw-headline" id="Automatic_editor_status_criteria">Automatic editor status criteria</span></h3></div><div><p style="margin-top: 0.4em; margin-right: 0px; margin-bottom: 0.5em; margin-left: 0px; line-height: 1.5em; font-family: sans-serif; font-size: 13px; ">
You should <i>automatically</i> get editor tools when/if you meet the following criteria:</p></div></blockquote><div><ul style="line-height: 1.5em; list-style-type: square; margin-top: 0.3em; margin-right: 0px; margin-bottom: 0px; margin-left: 1.5em; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; list-style-image: url(http://bits.wikimedia.org/skins-1.5/monobook/bullet.gif); font-family: sans-serif; font-size: 13px; ">
<ul><li style="margin-bottom: 0.1em; ">Have a registered account that is <i>at least</i> 30 days old, with an email set and confirmed in <a href="http://en.wikibooks.org/wiki/Special:Preferences" title="Special:Preferences" style="text-decoration: none; color: rgb(90, 54, 150); background-image: none; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; background-position: initial initial; background-repeat: initial initial; ">Special:Preferences</a>.</li>
<li style="margin-bottom: 0.1em; ">Have never been blocked, and have never had the editor or reviewer tools removed (you can <a href="http://en.wikibooks.org/wiki/Wikibooks:RFP" title="Wikibooks:RFP" class="mw-redirect" style="text-decoration: none; color: rgb(0, 43, 184); background-image: none; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; background-position: initial initial; background-repeat: initial initial; ">request the tools</a> in this case).</li>
<li style="margin-bottom: 0.1em; ">Have <i>at least</i> 100 edits since registration (excluding deleted edits), in which:</li></ul><li style="margin-bottom: 0.1em; "><ul style="line-height: 1.5em; list-style-type: square; margin-top: 0.3em; margin-right: 0px; margin-bottom: 0px; margin-left: 1.5em; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; list-style-image: url(http://bits.wikimedia.org/skins-1.5/monobook/bullet.gif); ">
<ul><li style="margin-bottom: 0.1em; ">50 or more edits are to pages other than discussion pages.</li><li style="margin-bottom: 0.1em; ">50 or more <a href="http://meta.wikimedia.org/wiki/edit_summaries" class="extiw" title="m:edit summaries" style="text-decoration: none; color: rgb(51, 102, 187); background-image: none; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; background-position: initial initial; background-repeat: initial initial; ">edit summaries</a> are used.</li>
<li style="margin-bottom: 0.1em; ">10 or more unique pages are edited <i>at least</i> once.</li><li style="margin-bottom: 0.1em; ">10 edits are spaced 2 or more days apart from each other (which takes <i>at least</i> 18 days, if you edit every 2 days).</li>
<li style="margin-bottom: 0.1em; ">10 or more edits are in <a href="http://en.wikibooks.org/wiki/Special:RecentChanges" title="Special:RecentChanges" style="text-decoration: none; color: rgb(0, 43, 184); background-image: none; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; background-position: initial initial; background-repeat: initial initial; ">recent changes</a> at the time automatic editor promotion is checked.</li>
</ul></ul></li></ul><div><br></div><div>I requested and got my editor privileges via the request page as I didn't have enough edits yet and was making a wikibook. It was nothing special or unusual, jus because I was a good contributor.</div>
<div><br></div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">I suspect though that this works best were there are a lot of reviewers / editors. On the codex there's a fairly small team of admins, and a few key contributors who may (or may not) desire to review other work.<br>
<br>Also the concept of something being reviewed could discourage small, quick edits.</span></blockquote><div><br></div><div>If you have editor or reviewer privileges, you can review your own edits, and I believe it marks your own edits as reviewed by default anyway. Besides, any contributors can easily get the privileges if they have a reason. So, in reality, it is less restrictive than it sounds. I do agree that if the team is too small, which I don't think it is, it could be a progress blocker.</div>
<div> </div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Sufficient would, I suspect, be to limit the number of edits a normal user can make in a specified period. Most spam attacks work because they blast a load of new pages out automatically in a short time. Normal users don't do this. So all you really need is a limit on this sort of thing. The admin team can easily handle small-scale spam.</blockquote>
<div><br></div><div>This might be a good idea, but I don't think it would work very well, as someone designing templates or something like that will run into drastic problems if they use subpages and parser functions.</div>
<div><br></div><div class="gmail_quote">On Tue, Jun 22, 2010 at 11:41 AM, Arlen Beiler <span dir="ltr"><<a href="mailto:arlenbee@gmail.com">arlenbee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Wikibooks has used reviewing with great success. If someone wants to review articles, they can request editor or reviewer status. Editor status can be given automatically or manually by an admin. Reviewer status is a higher privilege required only for giving pages featured book status and some other stuff. It is assumed that editors can be trusted as they have made many contributions. If someone is writing a wikibook, they can usually get editor status. I think some admins said once that it really cut down on drive-by spam and so forth. Something like this would give us the ability to control what visitors see when they visit. If a page is not reviewed the latest revision is shown. If a page is reviewed, the latest stable revision is shown.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Tue, Jun 22, 2010 at 6:03 PM, Gooitzen van der Ent <span dir="ltr"><<a href="mailto:contact@ecodelphinus.com" target="_blank">contact@ecodelphinus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#ffffff">
Hello Lorelle,<br>
<br>
Personally I favor the idea of approving accounts manually, and having
a select (international) doc team. Possibly covering the major
languages in any case. How to do this for lesser used languages?<br>
<br>
Another option could be to implement a WordPress article approval
system, where all changes/ additions to the codex for example in the
form of new articles must be approved for publishing by textmoderators.
<br>
<br>
Of course this raises the question whether or not the people approving
should (be able) to see if the information entered is valuable.<br>
<br>
Might help if some regular meetings (video conferences) are set-up
where codex writers sit down with code developers in order to write
things down.<br>
<br>
Just a few ideas. Open for other suggestions by all means. <br>
<br>
Hope it helps.<br>
<br>
Kind regards,<br><font color="#888888">
<br>
Gooitzen van der Ent</font><div><div></div><div><br>
<br>
<br>
On 06/22/2010 09:29 AM, Lorelle on WordPress wrote:
<blockquote type="cite">Matt says that now that logins are locked, new
registrations to the Codex are temporarily blocked. They are looking at
how to resolve this issue to permit "open" registration while
controlling the level of spam and the work volunteers need to do to
deal with it.
<div><br>
</div>
<div>In the interim, that puts the action in the hands of those
currently with access. I'm very unhappy with this status, as I'm sure
most of you are. If there are any MediaWiki experts in our crowd that
have some suggestions on how to help with this issue, would love your
input. Personally, I think Akismet should be the first to embrace spam
prevention on MediaWiki - would resolve a ton of issues for wiki fans,
including Wikipedia. :D I ask so much, don't I?</div>
<div><br>
</div>
<div>Ideas?</div>
<div><br>
</div>
<div>Lorelle<br>
<br>
<br>
<div class="gmail_quote">On Mon, Jun 21, 2010 at 10:53 AM, Jane Wells
<span dir="ltr"><<a href="mailto:jane@automattic.com" target="_blank">jane@automattic.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">On
6/21/10 1:38 PM, Lorelle on WordPress wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
Good questions. The logins, to the best of my understanding, were all
merged a long time ago. If you log into the <a href="http://wp.org" target="_blank">wp.org</a> <<a href="http://wp.org" target="_blank">http://wp.org</a>>,
the login takes you everywhere within the site. For spammers,
especially bots, they are focusing on mediawiki logins, not
WordPress.org, so this stops technical blocks them as they are bots.
For the human spammers, it's another hoop they have to jump through and
they might not know to jump. So we can only hope.
<div><br>
<br>
I just tested it and you're right. New registrants on WordPress.org
can't get access to the Codex. It's probably a permissions level issue.
I've let them know and we should have an answer shortly. Thanks for
pointing it out.<br>
<br>
Lorelle<br>
</div>
</blockquote>
I have different logins for the codex and for .org. I don't think the
codex users have been merged yet.
<div>
<div><br>
_______________________________________________<br>
wp-docs mailing list<br>
<a href="mailto:wp-docs@lists.automattic.com" target="_blank">wp-docs@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<pre><fieldset></fieldset>
_______________________________________________
wp-docs mailing list
<a href="mailto:wp-docs@lists.automattic.com" target="_blank">wp-docs@lists.automattic.com</a>
<a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
wp-docs mailing list<br>
<a href="mailto:wp-docs@lists.automattic.com" target="_blank">wp-docs@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
<br></blockquote></div><br>
</div></div></blockquote></div><br></div>