User:Seraphimblade/Draft petition to WMF: Difference between revisions

Content deleted Content added

Inline

Revision as of 02:37, 13 June 2019

Summary

On 10 June 2019, the Wikimedia Foundation desysopped and banned editor and administrator Fram from the English Wikipedia as an office action for a period of one year. Fram's statement ^[1] indicates that the ban was solely for on-wiki conduct; as of this writing, the Wikimedia Foundation has not contradicted this assertion. It is the sense of the English Wikipedia community that:

The desysopping and ban were ostensibly based on the rationale that the WMF must handle issues that the community cannot. Here, the issues were not presented to the community or the Arbitration Committee. Therefore, we reject the statement by the WMF as an explanation of the ban.
The desysopping and ban, being presumably based upon only on-wiki actions, usurp the authority of the English Wikipedia community to enforce its own rules in regards to behavior on the project.
The desysopping and ban are, therefore, invalid and must be reversed.
Regardless of the reasons for this ban, the WMF must refrain from intervention in future on-wiki matters, or off-wiki matters which could be handled by the project's Arbitration Committee, with the exception of matters traditionally handled by WMF such as child protection, threats of violence, threats of suicide, and legal matters.

Timeline of events

On 19 February 2019, the Wikimedia Foundation changed its Trust & Safety policy to allow itself to issue bans of less than indefinite duration and on specific wikis.^[2]^[3] This change was made without community consultation to determine if such a change was helpful or desired.
On 10 June 2019 at 17:41, WMFOffice blocked and desysopped editor and administrator Fram.^[4]
On 10 June 2019 at 17:56, a thread was started at the bureaucrats' noticeboard.^[5] The proposal was discussed by the community there and later moved to a separate page at Wikipedia:Community response to Wikimedia Foundation's ban of Fram due to the volume of discussion.
On 10 June 2019 at 20:58, the WMFOffice account, an official Wikimedia Foundation role account, posted a statement on behalf of the Trust & Safety Team to the bureaucrats' noticeboard discussion confirming the ban and desysopping but declining to provide further detail.^[6]
On 11 June 2019 at 08:03, Fram posted a statement to Wikimedia Commons with his understanding of the reasons behind the ban, and giving the WMF permission to post his email communication with them regarding the subject.^[1] As of this writing, the WMF has not disputed any portion of this statement.
On 11 June 2019 at 11:50, administrator Floquenbeam announced that they planned to unblock Fram in defiance of the office ban^[7] and at 12:23 decided to wait until 19:00, noon San Francisco time.^[8]
On 11 June 2019 at 13:28, administrator Bishonen announced that they plan to support Floquenbeam and unblock Fram if Floquembeam is desysopped.^[9]
On 11 June 2019 at 18:58, the WMF announced that it would release a second statement, and at 19:11, Floquenbeam wrote that they would wait to see the WMF's statement.^[10]
On 11 June 2019 at 19:27, the WMF posted a second statement to the community discussion.^[11]
On 11 June 2019 at 19:39, Floquenbeam unblocked Fram.^[12]
On 12 June 2019 at 00:32, the WMF desysopped Floquenbeam,^[13] allowing resysopping after 30 days in a third statement,^[14] and reblocked Fram.^[15] No community policy existed at that time to govern resysopping after temporary office desysoppings. At 00:33, the WMF posted a fourth statement.^[16]
On 12 June 2019 at 07:20, Bishonen unblocked Fram.^[17]
On 12 June 2019 at 07:31, Nick asked to be desysopped in protest of the Foundation's actions.^[18] At 10:54, Nick was desysopped^[19]
On 12 June 2019 at 10:23, Fram made a second statement,^[20] and at 19:59, they made a third statement,^[21] asking the WMF to send details to mutually trusted editors.
On 12 June 2019 at 13:33, in apparent defiance of their office desysopping, Floquenbeam requested a resysop at the bureaucrats' noticeboard.^[22]
On 12 June 2019 at 23:35, bureaucrat WJBScribe resysopped Floquenbeam^[23] and made a statement in response to Floquenbeam's request.^[24] At 00:03 on 13 June, they requested arbitration about their own action.^[25]

Notes

[fram_statement-1] Fram's statement on Wikimedia Commons

[en_rules-2] Wikipedia office policy extension

[meta_rules-3] Meta-wiki office policy extension

[fram_block_1-4] Log entry Fram's first block

[bnpost-5] Initial bureaucrats' noticeboard post

[wmf_statement_1-6] First statement by the Wikimedia Foundation

[floq_intent-7] Floquenbeam's "Statement of Intent"

[first_delay-8] Floquenbeam's delay until noon

[spartacus-9] Bishonen's statement

[noon_delay-10] Floquenbeam's last-minute delay

[wmf_statement_2-11] Second statement by the Wikimedia Foundation

[floq_unblock-12] Log entry for Floquenbeam's unblock

[floq_desysop-13] Floquenbeam's desysop log entry

[floq_desysop_statement-14] Third statement by the Wikimedia Foundation

[fram_block_2-15] Log entry for Fram's second block

[wmf_statement_4-16] Fourth statement by the Wikimedia Foundation

[<"bish_unblock"-17] Bishonen's unblock log entry

[nick_desysop_request-18] Nick's request on the bureaucrats' noticeboard

[nick_desysop-19] Log entry for Nick's desysop

[fram_statement_2-20] Fram's second statement

[fram_statement_3-21] Fram's third statement

[floq_resysop_request-22] Floquenbeam's resysop request

[floq_resysop-23] Floquenbeam's resysop log entry

[wjb_statement-24] WJBScribe's statement on the bureaucrats' noticeboard

[wjb_arb-25] WJBScribe's request for arbitration

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[24]

[25]

@@ Line 14: / Line 14: @@
 *On 11 June 2019 at 08:03, Fram posted a statement to Wikimedia Commons with his understanding of the reasons behind the ban, and giving the WMF permission to post his email communication with them regarding the subject.<ref name="fram_statement" /> As of this writing, the WMF has not disputed any portion of this statement.
 *On 11 June 2019 at 11:50, administrator {{noping|Floquenbeam}} announced that they planned to unblock Fram in defiance of the office ban<ref name="floq_intent">[https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Bureaucrats%27_noticeboard&diff=prev&oldid=901365774 Floquenbeam's "Statement of Intent"]</ref> and at 12:23 decided to wait until 19:00, noon San Francisco time.<ref name="first_delay">[https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Bureaucrats%27_noticeboard&diff=prev&oldid=901369223 Floquenbeam's delay until noon]</ref>
-*On 11 June 2019 at 13:28, administrator {{noping|Bishonen}} announced that they plan to support Floquenbeam and unblock Fram is Floquembeam is desysopped.<ref name="spartacus">[https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Community_response_to_the_Wikimedia_Foundation%27s_ban_of_Fram&diff=prev&oldid=901376353 Bishonen's statement]</ref>
+*On 11 June 2019 at 13:28, administrator {{noping|Bishonen}} announced that they plan to support Floquenbeam and unblock Fram if Floquembeam is desysopped.<ref name="spartacus">[https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Community_response_to_the_Wikimedia_Foundation%27s_ban_of_Fram&diff=prev&oldid=901376353 Bishonen's statement]</ref>
 *On 11 June 2019 at 18:58, the WMF announced that it would release a second statement, and at 19:11, Floquenbeam wrote that they would wait to see the WMF's statement.<ref name="noon_delay">[https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Community_response_to_Wikimedia_Foundation%27s_ban_of_Fram&diff=prev&oldid=901422165 Floquenbeam's last-minute delay]</ref>
 *On 11 June 2019 at 19:27, the WMF posted a second statement to the community discussion.<ref name="wmf_statement_2">[https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Community_response_to_Wikimedia_Foundation%27s_ban_of_Fram&diff=901424172&oldid=901424017 Second statement by the Wikimedia Foundation]</ref>