EXACTLY Who is this community of which we speak so glibly?
Herein lies a large part of the problem. A few people claim to represent the
many, based on consensus derived from a tiny sample. There is no one
community, there are several, depending on who wants to make a point.
Clique may be a
Brad
On Mon, Aug 11, 2014 at 1:43 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
*Note these are entirely my own personal opinions as a community member and
in no way at all represent anything official.*
On Mon, Aug 11, 2014 at 3:12 AM, MZMcBride z...@mzmcbride.com wrote:
I'm
On Mon, Aug 11, 2014 at 3:12 AM, MZMcBride z...@mzmcbride.com wrote:
Hi.
I'm interested to read others' views about options and ways forward here.
I think the most helpful thing would be to not attempt to start wars, and
particularly not on behalf of anyone or against individuals. We
On Mon, 11 Aug 2014, at 08:42, Tomasz W. Kozłowski wrote:
Someone is definitely forgetting that Wikimedia wikis are not the
Foundation's personal playground.
It is becoming one for a long time now.
svetlana
___
Wikimedia-l mailing list, guidelines
One more option: wait for WMF to make wiki unbreakable and scriptable
*properly*, using something like Firefox's jetpack (which is fool proof)
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
I think the most helpful thing would be to not attempt to start wars, and
particularly not on behalf of anyone or against individuals. We are all on
the same side here: trying to make the projects (and the project
interfaces, as a part of that) better. That includes, for instance, trying
out
On 11 August 2014 03:19, Pine W wiki.p...@gmail.com wrote:
Lila,
I hope you are aware of the issues being described in this thread. Would
you please state your views on this situation?
Pine
+1 It would be great to hear from Lila on the current decisions being
taken by her employees.
The
Erik, I wonder, did you have discussion with other staff and moreso,
the technical staff before you went ahead and implemented this and
also something most of us are wondering, just because dewiki did not
accept your enforcement of MediaViewer, did you abuse your authority
and force the technical
phoebe ayers wrote:
I think the most helpful thing would be to not attempt to start wars, and
particularly not on behalf of anyone or against individuals. We are all on
the same side here: trying to make the projects (and the project
interfaces, as a part of that) better. That includes, for
On Aug 11, 2014 7:11 AM, Kim Bruning k...@bruning.xs4all.nl wrote:
Ha, you'd think so! ;-)
In reality so far, the only known application was to lock the common.js
at de.wikipedia, to prevent some crazy admin(s) from breaking the wiki.
Which incidentally shows that will not break the wiki
On Aug 11, 2014 1:57 AM, phoebe ayers phoebe.w...@gmail.com wrote:
On Mon, Aug 11, 2014 at 3:12 AM, MZMcBride z...@mzmcbride.com wrote:
Hi.
I'm interested to read others' views about options and ways forward
here.
I think the most helpful thing would be to not attempt to start
Guys,
This isn't a war, it's an argument on the internet. No-one is dying and
no-one is being shot at. No-one is even being arrested and I doubt anyone
has even been shouted at in person.
Can we please view this as what it is - a technical issue which can be
resolved - rather than throwing
Your responses here are coming across as very personally targeted and
focused.
Attempting to demonize Erik is a mistake and clouds the issue. Erik is
acting as an officer, not as an individual.
On Aug 11, 2014, at 1:40 PM, MZMcBride z...@mzmcbride.com wrote:
Erik has
Hi,
I have posted the upload issue in the same thread as the already fixed
issue.
It is still not possible to upload images. This is a major problem to us,
sine we use it alot for confidential documents, financials, etc.
Fine if someone more technical could do some guesswork on what might cause
Brandon,
Are you stating that Erik is not calling the shots here? If that's the
case, could someone please clarify who is in charge and asked for the new
right to be enabled?
On Aug 11, 2014 10:13 AM, Brandon Harris bhar...@wikimedia.org wrote:
Your responses here are coming across as
I'm stating that the tone here implies that Erik is some weird overlord
who orders everyone around and we cower in fear and do His Bidding.
It's not true. If you want to be angry, be angry at the Foundation.
Targeting Erik (or Jan) specifically is a mistake.
On Aug 11,
I thought a thread on Wikimedia-l might be useful for folks to share
feedback and their experiences, good or bad. I understand there is a
survey which we should remember to complete, and there has been a lot
of chat on Facebook, but I have a natural aversion to that space. :-)
My tuppence worth
Hi all!
Both the Wikimania flags are missing. The poles have come back, but not the
flag itself! We wanted to get one of these signed by everyone who helped
with Wikimania and display it in the UK office so we are a bit sad that
they're missing. They probably vanished in the final drunken packing
On Tue, Aug 12, 2014 at 12:18 AM, Brian Wolff bawo...@gmail.com wrote:
Now, having observed that not only user Eloquence (aka Erik Moeller)
himself engaged in the enforcement of superprotect right on de.wp
[1] but soon after a workaround was published a change was deployed
[2, 3] as counter
On Mon, Aug 11, 2014 at 9:12 AM, Brandon Harris bhar...@wikimedia.org
wrote:
Erik is acting as an officer, not as an individual.
Brandon, it is not as clear-cut as you suggest, and the lack of clarity
originates at the Wikimedia Foundation.
The most explicit statement I've seen on this topic
And what happens when said admin is overwhelmingly reelected by the
community?
This is not the way forward. WMF can't continue to treat its volunteers in
this manner.
On Aug 11, 2014 12:01 PM, John Mark Vandenberg jay...@gmail.com wrote:
On Tue, Aug 12, 2014 at 12:18 AM, Brian Wolff
On Mon, Aug 11, 2014 at 12:37 PM, Chris Keating chriskeatingw...@gmail.com
wrote:
A decision about how the public consumes Wikipedia content (e.g., Media
Viewer) is an editorial decision,
and it's one that the WMF has chosen to
make unilaterally. WMF has furthermore moved to give
brandon, erik is an intelligent person. and of course at the end persons
are acting, not organizations. if german elected community members,
trusted ones, think it is not good enough, why not just let it be? its easy
to get the reasons and act on it. wikipedia was and is community driven.
your
On Mon, Aug 11, 2014 at 2:01 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Before this, there was no expectation that a page could be protected
such that sysops could not alter the content of the superprotected
page.
This is false.
Now, the devs/ops have attempted to introduce that
On Tue, Aug 12, 2014 at 3:49 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Mon, Aug 11, 2014 at 2:01 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Before this, there was no expectation that a page could be protected
such that sysops could not alter the content of the
Chris Keating wrote:
In particular, I find it difficult to take people seriously when they're
suggesting solutions like disabling the German Wikipedia. I am more
than a little surprised this even needs to be said.
Magnus Manske wrote:
Strange. I seem to distinctly remember that, yesterday on
On 11/08/14 21:49, Brad Jorsch (Anomie) wrote:
On Mon, Aug 11, 2014 at 2:01 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Now, the devs/ops have attempted to introduce that capability, and the
new functionality is very likely riddled with holes, some of which
MZMcBride has suggested in the
Tim, I don't believe the issue was a failure to be clear. The problem is
the content of the change and its heavy handed enforcement.
Super protection either should not exist, or like suppression, it should be
used only by stewards and community approved functionaries.
On Aug 11, 2014 5:49 PM, Tim
On Aug 11, 2014, at 7:13 PM, Todd Allen toddmal...@gmail.com wrote:
like suppression, it should be
used only by stewards and community approved functionaries.
I'm confused. Are you suggesting that suppression is not used by staff?
Super protection can be used by staff, and was.
29 matches
Mail list logo
