On Fri, Nov 6, 2015 at 10:51 AM, Neil Harris wrote:
> That's fantastic, represents a huge vote of confidence for the Wiki Way,
> and is a big move towards improving the relationship between the WMF and
> the community.
>
Just to keep things in perspective: the removal of
On Sun, Nov 8, 2015 at 8:04 AM, pi zero wrote:
> In
> other words, it wasn't removed because it shouldn't have been imposed in
> the first place, but merely because it wasn't used. Is it good that it was
> removed? Sure, it's better to have had it removed than not. But
Hi pi zero,
On Sun, Nov 8, 2015 at 2:04 PM, pi zero wrote:
> it wasn't removed because it shouldn't have been imposed in
> the first place, but merely because it wasn't used.
I'm sorry if my wording could suggest this interpretation. I just wanted to
provide basic
On Nov 8, 2015 9:34 PM, "Quim Gil" wrote:
> the Q included more details:
>
>
https://www.mediawiki.org/wiki/WMF_product_development_process/2015-11-05#When_has_been_Superprotect_used.3F
>
> The main reason to act upon Superprotect now is the updated product
> development
Hi Andy,
On Mon, Nov 9, 2015 at 12:04 AM, Andy Mabbett
wrote:
> Referring to "misbehaviour" in this context is extremely offensive; the
> initial use of superprotect was not a response to "misbehaviour".
>
Changed for the more precise and descriptive term "irregular
Thanks for the explanations. I always thought of the Superprotect
function as a technical way to react in a social-legal space of
tension. A discussion about the technical function is much less
interesting than about the real issue, of how to improve the MediaWiki
software with regard to the
On 05/11/15 17:35, Quim Gil wrote:
Superprotect [1] was introduced by the Wikimedia Foundation to resolve a
product development disagreement. We have not used it for resolving a
dispute since. Consequently, today we are removing Superprotect from
Wikimedia servers.
Without Superprotect, a
Superprotect [1] was introduced by the Wikimedia Foundation to resolve a
product development disagreement. We have not used it for resolving a
dispute since. Consequently, today we are removing Superprotect from
Wikimedia servers.
Without Superprotect, a symbolic point of tension is resolved.
Thank you.
On Thu, Nov 5, 2015 at 12:35 PM, Quim Gil wrote:
> Superprotect [1] was introduced by the Wikimedia Foundation to resolve a
> product development disagreement. We have not used it for resolving a
> dispute since. Consequently, today we are removing Superprotect
That's an interesting update. Thanks for sharing.
--
Tito
On 5 November 2015 at 23:05, Quim Gil wrote:
> Superprotect [1] was introduced by the Wikimedia Foundation to resolve a
> product development disagreement. We have not used it for resolving a
> dispute since.
Il giorno gio, 05/11/2015 alle 18.35 +0100, Quim Gil ha scritto:
> Superprotect [1] was introduced by the Wikimedia Foundation to resolve
> a
> product development disagreement. We have not used it for resolving a
> dispute since. Consequently, today we are removing Superprotect from
> Wikimedia
Yay! Great news about Superprotect's scrapping, also really good to hear
the direction of travel on the development process.
Chris
On 5 Nov 2015 17:36, "Quim Gil" wrote:
> Superprotect [1] was introduced by the Wikimedia Foundation to resolve a
> product development
On 5 November 2015 at 10:14, Laurentius wrote:
> Just to understand, is it still present in MediaWiki but not active on
> Wikimedia sites or it not in the MediaWiki code anymore?
>
There was a patch merged which removed the protection level completely:
great news, indeed!
Thanks to everyone involved during the different stages of this process for
making this happen. :-)
Leila
On Thu, Nov 5, 2015 at 10:21 AM, Asaf Bartov wrote:
> \o/
>
>A.
>
> On Thu, Nov 5, 2015 at 10:20 AM, Dan Garry wrote:
At last it is gone. Great news. Looking forward.
Bodhisattwa
On 6 Nov 2015 00:40, "Pierre-Selim" wrote:
> It's a great news to hear that superprotect is gone and the willingness of
> a better collaboration.
> It's a long-awaited move.
>
> 2015-11-05 20:03 GMT+01:00
It's a great news to hear that superprotect is gone and the willingness of
a better collaboration.
It's a long-awaited move.
2015-11-05 20:03 GMT+01:00 Chris Keating :
> Yay! Great news about Superprotect's scrapping, also really good to hear
> the direction of travel
\o/
A.
On Thu, Nov 5, 2015 at 10:20 AM, Dan Garry wrote:
> On 5 November 2015 at 10:14, Laurentius wrote:
>
> > Just to understand, is it still present in MediaWiki but not active on
> > Wikimedia sites or it not in the MediaWiki code
Yes indeed, thank you.
On Nov 5, 2015 10:36 AM, "Quim Gil" wrote:
> Superprotect [1] was introduced by the Wikimedia Foundation to resolve a
> product development disagreement. We have not used it for resolving a
> dispute since. Consequently, today we are removing
On 2015-11-05 18:35, Quim Gil wrote:
Superprotect [1] was introduced by the Wikimedia Foundation to resolve
a
product development disagreement. We have not used it for resolving a
dispute since. Consequently, today we are removing Superprotect from
Wikimedia servers.
Great, thank you, it is
Brion Vibber wrote:
>In other words -- ignore the superprotect red herring! Please look at the
>documentation of the product process and give feedback on that, it's much,
>MUCH more important:
>
>https://www.mediawiki.org/wiki/WMF_Product_Development_Process
Great news to read that
Thank you for sharing the news, Quim.
Following Quim's announcement, there was also, for the first time since
nearly 1,000 Wikimedians requested the Foundation address this issue in
2014,[1] a formal statement about it from the organization's leadership.
Executive Director Lila Tretikov said
Good riddance to a bad mistake. Hopefully the underlying causes of the
MediaViewer conflict can be addressed before any other incidents of this
nature occur.
Cheers,
Craig
On 06/11/2015 3:36 AM, "Quim Gil" wrote:
> Superprotect [1] was introduced by the Wikimedia Foundation
Hi Quim,
you really made my day. :-)
Il 05/11/2015 18:35, Quim Gil ha scritto:
Superprotect [1] was introduced by the Wikimedia Foundation to resolve a
product development disagreement. We have not used it for resolving a
dispute since. Consequently, today we are removing Superprotect from
23 matches
Mail list logo