Hi Petr,
Nobody is language policing, this is about preventing abusive behavior and
creating an inviting environment where volunteers and staff don't have to
waste time with emotional processing of traumatic interactions.
I think we're after the same thing, that we want to keep our community
Am 14.08.2018 um 08:53 schrieb Adam Wight:
> What I was complaining about is that 2FA has to be used every time I log
> in. There doesn't seem to be an industry standard yet, for example gmail
> asks for 2FA only every 30 days if you've previously authenticated on the
> same machine, but GitHub
Apologies, "lack of session persistence" was a bad way to summarize what
I've been seeing. My session persistence is usually fine, and lasts a
while regardless of whether 2FA is enabled.
What I was complaining about is that 2FA has to be used every time I log
in. There doesn't seem to be an
Victoria,
Does the restriction on "Disclosure of a person's identity or other
private information without their consent" forbid the Foundation from
sharing the geolocation and IP addresses of editors with researchers
under NDA or law enforcement officials claiming to have, e.g., an
Interpol
Hey,
As a member of Code of conduct committee I just wanted to express how much
I appreciate your statement. The work we are doing is not fun, we are
dealing with frustrations, harassments, trolling, and all sorts of the dark
side of the Wikimedia movement but I genuinely believe that this type of
Sorry, I apparently replied to the wrong mailing list.
On 14/08/18 18:19, Isarra Yos wrote:
As a total random, I'd also like to second this - as much as I think
the CoC and the committee in particular have room to improve in how
things are handled, this will never happen without proper support
Hello everyone,
The executive leadership team, on behalf of the Foundation, would like to issue
a statement of unequivocal support for the Code of Conduct[1] and the
community-led Code of Conduct Committee. We believe that the development and
implementation of the Code are vital in ensuring
James, let's stay on topic, please. If you want to talk about other issues
then please start a new thread.
Victoria, I have mixed feelings about this statement.
I agree that we want to have civility in technical spaces, and a technical
code of conduct is one important way of working toward that
That's very valid but you don't see the CoCC bans anyone who makes an
unconstructive or angry comment. The problem here happens when it happens
too often from one person. When a pattern emerges. Do you agree that when
it's a norm for one person and warnings are not working out, the option is
to
Thanks Amir for clarifying this. This is the first I remember hearing this
was the reason for the sactions against mcbride, and differs significantly
from what I assumed was the reason.
However, MZMcbride has also claimed his comment was in exasperation after
facing the same breach of the CoC you
Amir, what you are suggesting at this point is basically that it doesn't
matter because that bug report was closed once and intended to remain
closed (despite being reopened) with reason that the WordPress website
isn't ready for public consumption yet was made public to replace the
previous. If
What I think has people talking past one another here is that the "final
straw" that led to the ban wasn't a per se ban-worthy offense, *and* there
is no clear standard or process for determining when past patterns of
behavior can be taken into account in determining whether a given action
crosses
Given that many of our users are from wikipedia, and as far as i understand
(I am not a wikipedian), on Wikipedia, using increasing length blocks as as
a punative punishment for rule infractions isn't allowed, I would guess
many of our community don't see it valid to block people temporarily just
I am OK if people who are attacking others are somehow informed that
this is not acceptable and taught how to properly behave, and if they
continue that, maybe some "preventive" actions could be taken, but is
that what really happened?
The comment by MZMcBride was censored, so almost nobody can
It's probably also worth noting that that is not the standard imposed by
the quoted CoC line.
On Tue, 14 Aug 2018, 20:49 Isarra Yos, wrote:
> Expecting every single comment to specifically move things forward
> seems... a bit excessive, frankly. Not everyone is going to have the
> vocabulary to
But this wasn't an unconstructive comment. And as a designer, angry
comments are particularly useful, to a point, as they help give us
insight into our users and thus better prioritise problems that require
immediate address. You cite my later response as an example of better
communication,
Brian, that's actually exactly how Wikipedia operates, as an admin in
Wikipedia serving for more than 9.5 years. The only difference is that it's
not punitive, and I don't think this ban was also punitive either. The ban
is made to prevent further damage.
Best
On Tue, Aug 14, 2018, 22:23 Brian
Hey Petr,
We have discussed this before in the thread and I and several other people
said it's a straw man.
The problem is not the WTF or "What the fuck" and as I said before the mere
use of profanity is not forbidden by the CoC. What's forbidden is "Harming
the discussion or community with
Expecting every single comment to specifically move things forward
seems... a bit excessive, frankly. Not everyone is going to have the
vocabulary to properly express themselves, let alone the skill to fully
explain exactly what the issues are, why they are, how to move forward,
or whatever.
How are these arguments against the Code of Conduct Commitee's actions not
arguments that the status quo for the technical community is fine and has
always been fine? Is it the opinion here that we a very welcoming
environment to new and estabilished contributors alike and that no one has
ever
So we are going to magically assume that somehow this block is going to
change mcbride's behaviour when it took a 100 message email thread before
he even found out the reason he was blocked (which differs from the implied
reason in the email which was sent to an email account he usually doesnt
Hi Brion.
I might be a bit late, but I just wonder why did you decide to go with
forking instead of Pthreads PHP extension?
AFAIK, Mediawiki should support not only *nix platforms, but Windows as
well, and `pcntl_fork()` does not work on Windows.
PS: Couldn't find related ticket. Can you post a
Am 14.08.2018 um 09:18 schrieb Adam Wight:
> Nobody is language policing, this is about preventing abusive behavior and
> creating an inviting environment where volunteers and staff don't have to
> waste time with emotional processing of traumatic interactions.
[Note: this is in the abstract,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/08/18 17:47, Petr Bena wrote:
> Right now there are only two options for two factor
> authentication:
>
> * Don't use two-factor authentication (insecure) * Use two factor
> authentication (annoying as hell)
Has any thought been given to
I keep seeing "abusers" and I still haven't seen the evidence of the
alleged long term abuse pattern.
Again, this isn't enwiki, but there would be a large mob gathering at the
administrators' doorstep on enwiki for a block without that context and
backstory. That's not exactly the standard here,
On Tue, Aug 14, 2018 at 8:34 AM Brion Vibber wrote:
> On Tue, Aug 14, 2018, 3:39 AM Aleksey Bekh-Ivanov <
> aleksey.bekh-iva...@wikimedia.de> wrote:
>
>> Hi Brion.
>>
>> I might be a bit late, but I just wonder why did you decide to go with
>> forking instead of Pthreads PHP extension?
>>
>
>
Hello,
This is the weekly update from the Search Platform team for the week
starting 2018-08-06.
As always, feedback and questions welcome.
== Discussions ==
=== Search ===
* Erik and David worked on setting up a new branch for elasticsearch
6.x (as a first step) [0], which is mostly done but
Yeah I wrote some code that got U2F support working through inside the
OATHAuth extension, though I don't think it ever got to Gerrit.
On Tue, 14 Aug 2018, 10:31 Simon Walker, wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 12/08/18 17:47, Petr Bena wrote:
> > Right now there
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, Bulgarian & Persian.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time
>
> Again, this isn't enwiki, but there would be a large mob gathering at the
> administrators' doorstep on enwiki for a block without that context and
> backstory.
>
That seems like really toxic behavior.
On Tue, Aug 14, 2018 at 6:27 AM George Herbert
wrote:
> I keep seeing "abusers" and I
On Tue, Aug 14, 2018, 3:39 AM Aleksey Bekh-Ivanov <
aleksey.bekh-iva...@wikimedia.de> wrote:
> Hi Brion.
>
> I might be a bit late, but I just wonder why did you decide to go with
> forking instead of Pthreads PHP extension?
>
ForkController and OrderedStreamingForkController were already
31 matches
Mail list logo
