User talk:Reception123/Archive 2

__NOINDEX__

Dormancy Policy on my wiki
Hola, Quiero pedirte que mi wiki wiki1776.miraheze.org tenga una excepción para evitar su borrado. Será un almacén donde guardaré, recopilaré, desarrollaré y organizaré información relacionada a los proyectos donde estoy participando. --Wiki1776 (talk) 23:46, 26 January 2018 (UTC)
 * So should it be exempted because it is meant to be read, and you will not regularly add information to it? Reception123 (talk) ('C' ) 18:06, 3 February 2018 (UTC)
 * Había olvidado esto. Al principio sí pero al final decidí que no sería leído por cualquiera. Retiro la solicitud. --Wiki1776 (talk) 18:09, 3 February 2018 (UTC)
 * Reception. Hablando de esto, estoy queriendo reorganizar mi wiki UnionNorteamericana (con el mismo tema) para que el nombre de la página fuera más corta. Pero a la vez quiero hacerlo en "limpio" para también reorganizar el contenido. Por tanto crearía otra wiki, haría un Phab con las extensiones y configuraciones que quiero y borraría esta que uso actualmente. Pero tengo una pregunta. ¿Que pasaría con Política de Excepción que tiene mi wiki? se podría "trasladar" al nuevo url? o ¿Preferirías eliminarlo? Espero tu respuesta. Gracias de antemano. --Wiki1776 (talk) 21:16, 5 February 2018 (UTC)
 * Si, si su wiki "nueva" tiene el mismo proposito, la excepcion puede ser "trasladar". --Reception123 (talk) ('C' ) 06:20, 6 February 2018 (UTC)

Phabricator
Dear Reception123,

I have requested a feature on Phabricator. Please view it. --Vlad26t (talk) 15:34, 14 February 2018 (UTC)
 * I will look into it soon, if no one does. Reception123 (talk) ('C' ) 19:35, 14 February 2018 (UTC)
 * What means "Assigned To" ? --Vlad26t (talk) 08:34, 15 February 2018 (UTC)
 * I would like to give my two cents here. It is in my view that asking configurator's to look at your request is quite disruptive and can be an annoyance. We have countless feature requests to process and we process all of them as soon as we can. Asking them to be looked at will not get them looked at any sooner, well by me anyway. &#32; Miraheze Logo.svg CnocBride | Talk | Contribs  17:56, 15 February 2018 (UTC)
 * Maybe, I know there are a lot of tasks, but we should still aim at completing them as soon as we can, as to allow users to continue their projects with the required extensions, logo's, settings that they need. Reception123 (talk) ('C' ) 18:05, 15 February 2018 (UTC)
 * When will you do the task? --Vlad26t (talk) 09:29, 16 February 2018 (UTC)
 * You still haven't done this task. --Vlad26t (talk) 09:49, 18 February 2018 (UTC)
 * Please note that hurrying this will not make it go faster. Unfortunately, your task requires more work than others, since we don't have it set up yet. I am not the only volunteer, and I did not yet find time to take care of your task. It will be done soon. Reception123 (talk) ('C' ) 11:22, 18 February 2018 (UTC)
 * ✅ Reception123 (talk) ('C' ) 17:36, 18 February 2018 (UTC)
 * Oops, there is an error: Fatal exception of type MWException. --Vlad26t (talk) 13:43, 19 February 2018 (UTC)
 * If I want to log in, there will be error: Fatal exception of type MWException. --Vlad26t (talk) 15:59, 20 February 2018 (UTC)
 * You still haven't fixed "internal error". : Fatal exception of type MWException. --Vlad26t (talk) 09:28, 26 February 2018 (UTC)
 * I will look, but it's better to open a Phabricator task for tracking purposes. Reception123 (talk) ('C' ) 06:07, 28 February 2018 (UTC)

open wiki

 * Hi, you can open my this wiki?
 * 網路百科.
 * Thanks.--Msnhinet8 (talk) 05:47, 28 February 2018 (UTC)
 * If you need a new wiki please go to Special:RequestWiki. --Reception123 (talk) ('C' ) 06:37, 28 February 2018 (UTC)


 * ok,thanks.--Msnhinet8 (talk) 06:40, 28 February 2018 (UTC)

Request

 * Hi,you look my request?
 * 網路百科. --Msnhinet8 (talk) 09:09, 10 March 2018 (UTC)
 * you look my meassage?--Msnhinet8 (talk) 00:47, 13 March 2018 (UTC)
 * This. --Msnhinet8 (talk) 00:57, 13 March 2018 (UTC)
 * I will reply. Reception123 (talk) ('C' ) 06:28, 13 March 2018 (UTC)

logo

 * this new massage https://phabricator.miraheze.org/T2855, thanks.--Msnhinet8 (talk) 10:54, 18 March 2018 (UTC)

A barnstar

 * Thank you for the barnstar :) Reception123 (talk) ('C' ) 16:22, 19 March 2018 (UTC)


 * Hi, can you help me my logo?--Msnhinet8 (talk) 12:46, 20 March 2018 (UTC)
 * you look my request?--Msnhinet8 (talk) 06:01, 21 March 2018 (UTC)

User:Reception123/Sysadmin inactivity policy draft
I've read your draft. The one-month period for deciding Admin inactivity seems unobjectionable; likewise the discussion-and-voting to decide whether the Admin is inactive and whether promises to resume activity are credible. But it's not clear what the month is:
 * A lookback period during which the Admin must have been absent to be declared inactive?
 * A clock that begins to run following a claim of inactivity?

Related: Was there a complaint? Does one charge an Admin with inactivity? or declare that the Admin has been inactive for the past month?

Separately, you list four criteria (it is the plural of criterion, so you have grammar errors) to judge inactivity. A criterion is like an algorithm. There could be "criteria" for deciding inactivity, but your list of "criteria" is instead a list of forums, such as IRC. (The plural of this is "fora" but nobody knows it.) A given Admin might be active on some of the forums but neglect others. Do you intend to require that every Admin be active at all possible points of contact? (Has Discord become a fifth?)

I am not an Admin and have no disagreements with any Admin; I just wanted to give you more ideas to think about. 00:34 26-Apr-2018
 * Thank you for taking the time to read and comment on the draft. The "month" is a period when an Ops member thinks it would be appropriate to review activity, I don't think it's necessary to impose specific dates, it can be something that's done every 3 months or so. It's not really about "complaints", as I explained above, inactivity can be a security risk, and either way what is the point of having server access if you do not use it? And yes, based on this a user can be deemed "inactive".


 * As for the "criteria", what you mention about someone being active on some but not on others is why there are multiple ones. Server access and GitHub commits are important, as that is what you gain with access mainly. Phabricator and IRC are also important, though, because (at least I think so) it is very difficult to work on things without communicating with people and staff, and even if you don't necessarily do stuff, advising other people on IRC and Phabricator can still be very helpful. As for Discord, no decision has been made yet whether it is official or not, but either way, it will probably still be the same criterion "Discord and/or IRC". Reception123  (talk) ('C' ) 05:51, 26 April 2018 (UTC)


 * Very good; perhaps clarify that, for instance, absence from IRC is not proof of anything if the Admin is continuing to participate. The criterion should be absence from everything.  I don't think "it's necessary to impose specific dates" either, just be clearer about how absence becomes an issue in the first place.  Cheers!   13:59 27-Apr-2018