User talk:Dross

New Miraheze Meeting Announced!
Hello,

I am writing to let you know a new Miraheze Meeting has been confirmed as you requested updates.

Miramania

 * Date: 15/01/2020
 * Time: 21:00 UTC
 * Hosts: RhinosF1
 *  Available Meeting Operator: RhinosF1
 * Description: Discussion regarding the possibility of a face to face meetup event for Miraheze Users.
 * Attendees: Sign the attendance sheet by clicking here

Please come along to chat with us in #miraheze-meetings on chat.freenode.net during the alloted time.

Thanks, RhinosF1 15:18, 30 December 2019 (UTC)

Interested in continuing as a ?
Hi Dross,

Though we've never really interacted, I hope that you are doing well, and wish to thank you for your assisting your fellow Mirahezians over the years on community noticeboard. Since the closure of a recent Meta (local) RfC, the  and   user rights were split into two groups, and previous autopatrolled users lost the ability to patrol. After discussing with, we agreed that it makes sense to reach out to a few of the previous patrolling users who were either somewhat active or very active in roughly the past three months. You were one of those users. Would you be interested in continuing with that ability as a patroller? Please indicate your acceptance by way of a reply, with a ping to me so I am notified, and I'll switch you from  to , and update you on our initial patroller guidelines. :)

Thanks,

Dmehus (talk) 22:11, 2 September 2020 (UTC)


 * dross, I'm going to bump this old thread and re-ask you if you might be interested in this. Let me know. Dmehus (talk) 06:20, 9 January 2022 (UTC)
 * I would absolutely be willing at this point. I appreciate you coming back around and thinking of me! I think I look at RC enough to handle it. dross  (t • c • g) 06:42, 9 January 2022 (UTC)
 * Great. I'll post the generally accepted guidelines for patrollers, then grant the permission. Dmehus (talk) 06:43, 9 January 2022 (UTC)

Patroller granted - 2022-01-9
Hi, Dross. An administrator on Meta has granted you the  user group permission, which gives you the ability to   recent changes and new pages of other Miraheze users (both registered and anonymous) who are  not either autopatrolled or an administrator. In addition, this group also means that your edits are, so other patrollers or administrators don't have to patrol your edits. You should also be aware that the granting of this user group is at the discretion of Meta administrators, so different administrators will have slightly different criteria for granting. Likewise, just as it is a discretionary appointment, revocation is also at the discretion of Meta administrators and, again, each will have their own criteria for revocation.

In the medium-term, plans are in the works to develop a Meta Patrollers School, likely led by one or two active administrators, that will provide a comprehensive set of guidelines for patrollers and answers to commonly asked questions.

Nevertheless, the following are some of the main guidelines for patrolling. If you follow these guidelines completely, it is unlikely your patroller user group should ever be revoked. In technical terms, even when you find content that requires deletion by an administrator or otherwise requires remediation, undoing, reverting, or rolling back (if you are also a, of course), you should always first mark as patrolled any revisions regardless of whether that content is destined to remain extant to the page or even on Meta entirely.


 * 1) When patrolling talk pages, user talk pages, and noticeboards (in Main and Meta namespaces), you should first check to see whether the user properly signed their posts using four tildes . If they have not, you should add unsigned by substitution, where username is the user's username or IP address and the timestamp is the full timestamp from the diff page. As a best practice, you should also link to the diff in your edit summary, so other administrators and patrollers can easily tie your modification to the original edit being modified. To speed up this process, you can copy the   user script from line 5 of this page into either your (a) common.js or (b) global.js page (the latter applying globally on all Miraheze wikis);
 * 2) When patrolling the noticeboards, ask yourself whether this topic is on the correct noticeboard. If it is not, you should move it to the correct noticeboard, by either undoing the edit or manually removing the topic (if there have been intervening edits), again linking to the original noticeboard of the topic and the new noticeboard where it was moved in your edit summary. On the new noticeboard, you would simply paste in the topic (including the section header), linking to the diff page as in the first step. An example edit summary might be , where  ######  represents the numeric revision ID of the originally posted topic;
 * 3) Also when patrolling the noticeboards and talk pages (including user talk pages), as a best practice, take care to kindly fix any formatting mistakes (such as excess line breaks or incorrect wiki code), per WP:LISTGAP;
 * 4) If something requires deletion, you can add delete to the top of the page in question, taking care to follow the instructions on that template page;
 * 5) If you come across a user who repeatedly makes the same mistakes, send them a guidance note on their user talk page, informing of the steps need to edit and post constructively on Meta; and, finally,
 * 6) If in doubt whether something requires remediation or not, patrol it, and then ask any administrator via their user talk page or at Administrators' noticeboard if any further action needs to be taken.

If you have any questions, please don't hesitate to reach out. Thank you! --Dmehus (talk) 06:46, 9 January 2022 (UTC)