The appointment process is now concluded, and the appointment motion has been published below.
Wikipedia Arbitration |
---|
|
Track related changes |
The Arbitration Committee is seeking to appoint at least three non-arbitrator members to the Audit Subcommittee.
The Audit Subcommittee (AUSC) was established by the Arbitration Committee to investigate complaints concerning the use of CheckUser and Oversight privileges on the English Wikipedia, and to provide better monitoring and oversight of the CheckUser and Oversight positions, and use of the applicable tools.
Matters brought before the subcommittee may be time-sensitive and subcommittee members should be prepared and available to discuss cases promptly so they may be resolved in a timely manner. Sitting subcommittee members are expected to actively participate in AUSC proceedings and may be replaced should they become inactive. All subcommittee members are subject to the relevant local and global policies and guidelines concerning CheckUser and Oversight.
The subcommittee is made up of three arbitrators (who typically serve six-month terms) and three at-large members appointed for one-year terms. Applicants must be at least eighteen years old and willing to identify to the Wikimedia Foundation. Active subcommittee members are given the CheckUser and Oversight permissions, and have access to the Arbcom-audit-en, Functionaries-en, Checkuser-l, and Oversight-l mailing lists as well as the oversight-en-wp OTRS queue.
Details on the appointment process may be found below.
Candidates self-nominate by email to arbcom-en-blists.wikimedia.org. Each candidate will receive an application questionnaire to be completed and returned to the arbcom-en-b mailing list. The completed application should include a nomination statement, to a maximum of 250 words, for inclusion on the candidate's nomination sub-page(s).
During this period, the Arbitration Committee will review applications, notify the candidates going forward for community consultation, and create candidate sub-pages as necessary. The pages will be transcluded to the Candidates section below prior to the community consultation period.
The nomination statements are published and the candidates invited to answer standard questions and any additional questions the community may pose. Simultaneously, the community is invited to comment on the suitability or unsuitability of each candidate. These comments may either be posted publicly on the candidates' pages or submitted privately by email to arbcom-en-blists.wikimedia.org. Editors are encouraged to include a detailed rationale, supported by relevant links where appropriate.
The committee shall review all the comments submitted and other relevant factors before finalizing an internal resolution, at which point the appointments will be published. The successful candidates will be required to identify to the Wikimedia Foundation prior to receiving the permissions.
Effective 1 March 2012, Avraham ( talk · contribs), Ponyo ( talk · contribs), and Salvio giuliano ( talk · contribs) are appointed as community representatives to the Audit Subcommittee. The period of appointment will be 1 March 2012 to 28 February 2013. MBisanz ( talk · contribs) is designated as an alternate member of the subcommittee and will become a full member should one of the appointees resign their role during the term. The Arbitration Committee thanks all of the candidates, as well as the many members of the community who participated in the appointment process for these roles.
The Arbitration Committee also extends its thanks to Keegan ( talk · contribs) who is expected to remain in office until 31 March 2012.
For the Arbitration Committee, – xeno talk 17:55, 1 March 2012 (UTC)
Avraham ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
With the current lack of non-arbitrator members of the AUSC, I would like to support the continued smooth running of the English Wikipedia project by volunteering for AUSC. I am an experienced checkuser and oversighter on the English Wikipedia project, with three and two years of experience respectively using those tools. Having been subject to the regulations governing OS and CU for years, and to the AUSC for as long as it has been in existence, I am comfortable with both the tools and the situations in which they should be used.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 22:57, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:07, 10 February 2012 (UTC)
6. While I have no issue with editors wearing multiple hats across the project and across Wikimedia, because of the number of positions you hold, and the advanced levels of access you have, I'm curious to hear if you think that there might be a conflict between any of them. For example, if appointed, do you think you could devote sufficient time to both your steward work and your AUSC work? Or do you think that you could continue to be an active functionary and maintain sufficient detachment that you could impartially evaluate your fellow functionaries, or that your own actions were unlikely to come before the AUSC? HJ Mitchell | Penny for your thoughts? 09:10, 13 February 2012 (UTC)
Avi's response to my question allays any concerns I might have had. The number and type of positions he holds across various projects is an indication that he is held in high esteem and can be trusted to make good use of tools for their intended purpose. He assures us that he has time to fulfil this role in addition to the others, and that none of the others will conflict with his AUSC role. I think somebody who has made prolific use of functionary tools (especially across multiple wikis) on AUSC will bring a useful set of skills and perspectives, and since at least one of the appointees (assuming ArbCom appoints three from these seven) will be somebody who has never used functionary tools, there will be a nice balance on the subcommittee. HJ Mitchell | Penny for your thoughts? 17:30, 16 February 2012 (UTC)
DeltaQuad ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Hello everyone, I am DeltaQuad, and I've been an administrator for several months now, and have been an SPI clerk for about a year and a half now. I've seen many forms of anything from vandals to meatpuppets to right out sockpuppets themselves and how they disrupt the community. This trust to investigate potential sockpuppets in a neutral view is similar, but multiplies significantly when we talk about the Audit Subcommittee. The trust of Functionaries group is only something that is earned from a community and this subcommittee is what helps maintain that trust. With leaving close to no trace behind, these tools need to be used carefully and why it has guidelines for usage. The community in general should already trust the Functionaries team, but it does not remove the necessity that some sort of oversight or auditing to occur since a user's privacy is at stake when these tools are used. I'm not saying I don't trust the functionaries team, I do trust them, but trust has to be maintained, as anyone would know with friendship. If you are willing to have me, I would like to assist in maintaining this trust between the community and the Functionaries team. -- DQ (ʞlɐʇ)
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 22:57, 9 February 2012 (UTC)
Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS.
3. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs?
4. Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member?
5. Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:07, 10 February 2012 (UTC)
MBisanz ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Hi, my name is Matt and I have been editing Wikipedia for several years now. In that time I have consistently pushed for greater accountability and participated in a wide range of activities in both content creation and policy debate. Further, I am mindful of the responsibility that comes with access to private data, being a former AUSC member and having access to OTRS and Oversight. One principle I think that is paramount in AUSC members is that they avoid using CU/OV access in order to avoid the appearance of impropriety. If selected, I pledge to avoid using the tools in non-emergency situations in general and in emergency situations when another user or steward can be found who can perform the task. I am open to any questions individuals may have with regard to my editing and maintain a rather open policy as to my own personal information in the interest of informing others as to any factors they may find important to know with regard to my editing.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 22:58, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:08, 10 February 2012 (UTC)
6. You are currently running as a candidate in the 2012 steward elections. Being a steward is a time demanding job as there is an almost endless number of requests for blocks, permission changes etc. Whilst it is true that there are a number of stewards, if you were elected as a steward and an AUSC member, do you believe that you would be able to adequately manage the work load such that you are an active and fully engaged member of both roles within the Wikimedia community? The Helpful One 07:13, 15 February 2012 (UTC)
7 You have been around Wikipedia for a very long time and hold many advanced level permissions. It can be said that you are among a minority of Wikipedians in that you are very involved in the internal workings. Your work up to date has generally been solid and strong. Do you think, however, that it might be time to let new blood flow into this internal mechanism of the English Wikipedia? 140.247.141.165 ( talk) 23:41, 20 February 2012 (UTC)
Ponyo ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
I have decided to submit my application for AUSC candidacy as I believe that I have the necessary mix of technical and temperamental qualifications suited to the role. Regarding my Wikipedia background, I have been a member of the Wikipedia community since March 2007 and have found it to be an incredibly rewarding experience. I am approaching my first anniversary as an admin (February 2, 2012) and I am also active on OTRS where I work mainly with BLP subjects via the quality queue.
The technical skills I believe I would bring to the AUSC role include a real life background in data interpretation and forensics; in addition I have a natural disposition for thoroughness and attention to detail. If I were to be appointed to the 2012 AUSC I would ensure that complaints were reviewed with the utmost respect for all individuals involved – my work with OTRS requires the utmost discretion and will certainly extend to this role as well. Trust is an immutable requirement for AUSC members; I hope that my nearly five years of interactions with the Wikipedia community show that I am indeed trustworthy and able to respond with discretion, promptness, and clarity to any complaints raised during my potential tenure on the committee.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 23:02, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:07, 10 February 2012 (UTC)
Salvio giuliano ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
I would like to put my name forward to serve as a member of the Audit Subcommittee. I am Salvio giuliano, an editor, an administrator and an ArbCom clerk. I have been active for a while and I believe I am in good standing with the community.
There is very little I can add about myself: I consider myself to be an experienced and dedicated metapedian and I deem it my responsibility as a sysop to always try to assist as much as I can in making things run smoothly on Wikipedia for those who create content. And in this spirit I would approach my role as a member of AUSC, if I were chosen. I consider the Subcommittee to be one of the most important bodies in Wikipedia's current structure, as checkuser and oversight actions share common elements which distinguish them from any other on-wiki activity: first of all, they can seriously impinge on the privacy of all users and, furthermore, their logs can only be consulted by a very limited number of Wikipedians. This makes abuse insidious and hard to detect, thus limiting these users' accountability, which is why diligent supervision is crucial.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 23:02, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:08, 10 February 2012 (UTC)
The appointment process is now concluded, and the appointment motion has been published below.
Wikipedia Arbitration |
---|
|
Track related changes |
The Arbitration Committee is seeking to appoint at least three non-arbitrator members to the Audit Subcommittee.
The Audit Subcommittee (AUSC) was established by the Arbitration Committee to investigate complaints concerning the use of CheckUser and Oversight privileges on the English Wikipedia, and to provide better monitoring and oversight of the CheckUser and Oversight positions, and use of the applicable tools.
Matters brought before the subcommittee may be time-sensitive and subcommittee members should be prepared and available to discuss cases promptly so they may be resolved in a timely manner. Sitting subcommittee members are expected to actively participate in AUSC proceedings and may be replaced should they become inactive. All subcommittee members are subject to the relevant local and global policies and guidelines concerning CheckUser and Oversight.
The subcommittee is made up of three arbitrators (who typically serve six-month terms) and three at-large members appointed for one-year terms. Applicants must be at least eighteen years old and willing to identify to the Wikimedia Foundation. Active subcommittee members are given the CheckUser and Oversight permissions, and have access to the Arbcom-audit-en, Functionaries-en, Checkuser-l, and Oversight-l mailing lists as well as the oversight-en-wp OTRS queue.
Details on the appointment process may be found below.
Candidates self-nominate by email to arbcom-en-blists.wikimedia.org. Each candidate will receive an application questionnaire to be completed and returned to the arbcom-en-b mailing list. The completed application should include a nomination statement, to a maximum of 250 words, for inclusion on the candidate's nomination sub-page(s).
During this period, the Arbitration Committee will review applications, notify the candidates going forward for community consultation, and create candidate sub-pages as necessary. The pages will be transcluded to the Candidates section below prior to the community consultation period.
The nomination statements are published and the candidates invited to answer standard questions and any additional questions the community may pose. Simultaneously, the community is invited to comment on the suitability or unsuitability of each candidate. These comments may either be posted publicly on the candidates' pages or submitted privately by email to arbcom-en-blists.wikimedia.org. Editors are encouraged to include a detailed rationale, supported by relevant links where appropriate.
The committee shall review all the comments submitted and other relevant factors before finalizing an internal resolution, at which point the appointments will be published. The successful candidates will be required to identify to the Wikimedia Foundation prior to receiving the permissions.
Effective 1 March 2012, Avraham ( talk · contribs), Ponyo ( talk · contribs), and Salvio giuliano ( talk · contribs) are appointed as community representatives to the Audit Subcommittee. The period of appointment will be 1 March 2012 to 28 February 2013. MBisanz ( talk · contribs) is designated as an alternate member of the subcommittee and will become a full member should one of the appointees resign their role during the term. The Arbitration Committee thanks all of the candidates, as well as the many members of the community who participated in the appointment process for these roles.
The Arbitration Committee also extends its thanks to Keegan ( talk · contribs) who is expected to remain in office until 31 March 2012.
For the Arbitration Committee, – xeno talk 17:55, 1 March 2012 (UTC)
Avraham ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
With the current lack of non-arbitrator members of the AUSC, I would like to support the continued smooth running of the English Wikipedia project by volunteering for AUSC. I am an experienced checkuser and oversighter on the English Wikipedia project, with three and two years of experience respectively using those tools. Having been subject to the regulations governing OS and CU for years, and to the AUSC for as long as it has been in existence, I am comfortable with both the tools and the situations in which they should be used.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 22:57, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:07, 10 February 2012 (UTC)
6. While I have no issue with editors wearing multiple hats across the project and across Wikimedia, because of the number of positions you hold, and the advanced levels of access you have, I'm curious to hear if you think that there might be a conflict between any of them. For example, if appointed, do you think you could devote sufficient time to both your steward work and your AUSC work? Or do you think that you could continue to be an active functionary and maintain sufficient detachment that you could impartially evaluate your fellow functionaries, or that your own actions were unlikely to come before the AUSC? HJ Mitchell | Penny for your thoughts? 09:10, 13 February 2012 (UTC)
Avi's response to my question allays any concerns I might have had. The number and type of positions he holds across various projects is an indication that he is held in high esteem and can be trusted to make good use of tools for their intended purpose. He assures us that he has time to fulfil this role in addition to the others, and that none of the others will conflict with his AUSC role. I think somebody who has made prolific use of functionary tools (especially across multiple wikis) on AUSC will bring a useful set of skills and perspectives, and since at least one of the appointees (assuming ArbCom appoints three from these seven) will be somebody who has never used functionary tools, there will be a nice balance on the subcommittee. HJ Mitchell | Penny for your thoughts? 17:30, 16 February 2012 (UTC)
DeltaQuad ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Hello everyone, I am DeltaQuad, and I've been an administrator for several months now, and have been an SPI clerk for about a year and a half now. I've seen many forms of anything from vandals to meatpuppets to right out sockpuppets themselves and how they disrupt the community. This trust to investigate potential sockpuppets in a neutral view is similar, but multiplies significantly when we talk about the Audit Subcommittee. The trust of Functionaries group is only something that is earned from a community and this subcommittee is what helps maintain that trust. With leaving close to no trace behind, these tools need to be used carefully and why it has guidelines for usage. The community in general should already trust the Functionaries team, but it does not remove the necessity that some sort of oversight or auditing to occur since a user's privacy is at stake when these tools are used. I'm not saying I don't trust the functionaries team, I do trust them, but trust has to be maintained, as anyone would know with friendship. If you are willing to have me, I would like to assist in maintaining this trust between the community and the Functionaries team. -- DQ (ʞlɐʇ)
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 22:57, 9 February 2012 (UTC)
Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS.
3. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs?
4. Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member?
5. Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:07, 10 February 2012 (UTC)
MBisanz ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Hi, my name is Matt and I have been editing Wikipedia for several years now. In that time I have consistently pushed for greater accountability and participated in a wide range of activities in both content creation and policy debate. Further, I am mindful of the responsibility that comes with access to private data, being a former AUSC member and having access to OTRS and Oversight. One principle I think that is paramount in AUSC members is that they avoid using CU/OV access in order to avoid the appearance of impropriety. If selected, I pledge to avoid using the tools in non-emergency situations in general and in emergency situations when another user or steward can be found who can perform the task. I am open to any questions individuals may have with regard to my editing and maintain a rather open policy as to my own personal information in the interest of informing others as to any factors they may find important to know with regard to my editing.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 22:58, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:08, 10 February 2012 (UTC)
6. You are currently running as a candidate in the 2012 steward elections. Being a steward is a time demanding job as there is an almost endless number of requests for blocks, permission changes etc. Whilst it is true that there are a number of stewards, if you were elected as a steward and an AUSC member, do you believe that you would be able to adequately manage the work load such that you are an active and fully engaged member of both roles within the Wikimedia community? The Helpful One 07:13, 15 February 2012 (UTC)
7 You have been around Wikipedia for a very long time and hold many advanced level permissions. It can be said that you are among a minority of Wikipedians in that you are very involved in the internal workings. Your work up to date has generally been solid and strong. Do you think, however, that it might be time to let new blood flow into this internal mechanism of the English Wikipedia? 140.247.141.165 ( talk) 23:41, 20 February 2012 (UTC)
Ponyo ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
I have decided to submit my application for AUSC candidacy as I believe that I have the necessary mix of technical and temperamental qualifications suited to the role. Regarding my Wikipedia background, I have been a member of the Wikipedia community since March 2007 and have found it to be an incredibly rewarding experience. I am approaching my first anniversary as an admin (February 2, 2012) and I am also active on OTRS where I work mainly with BLP subjects via the quality queue.
The technical skills I believe I would bring to the AUSC role include a real life background in data interpretation and forensics; in addition I have a natural disposition for thoroughness and attention to detail. If I were to be appointed to the 2012 AUSC I would ensure that complaints were reviewed with the utmost respect for all individuals involved – my work with OTRS requires the utmost discretion and will certainly extend to this role as well. Trust is an immutable requirement for AUSC members; I hope that my nearly five years of interactions with the Wikipedia community show that I am indeed trustworthy and able to respond with discretion, promptness, and clarity to any complaints raised during my potential tenure on the committee.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 23:02, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:07, 10 February 2012 (UTC)
Salvio giuliano ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
I would like to put my name forward to serve as a member of the Audit Subcommittee. I am Salvio giuliano, an editor, an administrator and an ArbCom clerk. I have been active for a while and I believe I am in good standing with the community.
There is very little I can add about myself: I consider myself to be an experienced and dedicated metapedian and I deem it my responsibility as a sysop to always try to assist as much as I can in making things run smoothly on Wikipedia for those who create content. And in this spirit I would approach my role as a member of AUSC, if I were chosen. I consider the Subcommittee to be one of the most important bodies in Wikipedia's current structure, as checkuser and oversight actions share common elements which distinguish them from any other on-wiki activity: first of all, they can seriously impinge on the privacy of all users and, furthermore, their logs can only be consulted by a very limited number of Wikipedians. This makes abuse insidious and hard to detect, thus limiting these users' accountability, which is why diligent supervision is crucial.
Please describe any relevant on-Wiki experience you have for this role.
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
1. Do you think AUSC members should actively use the CheckUser or Oversight tool? Amalthea 08:47, 9 February 2012 (UTC)
2. Why do you think it is important to keep AUSC investigations private? Whenaxis talk · contribs 23:02, 9 February 2012 (UTC)
3, 4, and 5. Part of the rationale for having non-Arb members on this committee, at least as I see it, is to give more voice to the 'common editor'. People who have had advanced permissions for long periods of time might view the use of those permissions differently from those that didn't have access to those rights before joining the committee. With this in mind, I note that several candidates have advanced permissions, including not only CU and OS but also permissions are more powerful and more exclusive that CU and OS. Firstly, do you consider my 'common editor' rationale to be accurate? If not, what is the reason that the committee contains non-Arbs? Secondly, do you believe that having advanced and ultra-advanced permissions for significant periods of time would alter how a user (not any specific user) would approach the position of AUSC member? Finally, do you believe that this 'overqualified' concern might reasonably apply to you, and if so, how would you go about handling such a concern and mitigating its impact? Sven Manguard Wha? 16:08, 10 February 2012 (UTC)