[Wikimedia-l] Re: Google not indexing Wikisource for last few years now.

2024-01-20 Thread Peter Southwood
Why would Google want to start being honest and straightforward? 
Cheers, Peter

-Original Message-
From: Michael Snow [mailto:wikipe...@frontier.com] 
Sent: 19 January 2024 17:45
To: wikimedia-l@lists.wikimedia.org
Subject: [Wikimedia-l] Re: Google not indexing Wikisource for last few years
now.

I realize SEO has its own jargon, but to those not immersed in the field 
it is completely tautological to say a page is not indexed because "the 
indexing process determines that the page is unlikely to be requested in 
search." In an open-ended search, you aren't necessarily requesting a 
specific page, you're only asking the search engine to point you to 
pages that will hopefully be relevant to your query. It would be more 
honest and straightforward for Google to say that "based on our 
knowledge of what people search for, your page would appear so rarely 
among the highest-ranked results that we're not going to bother 
including it in our index."

--Michael Snow

On 1/19/2024 4:55 AM, npe...@wikimedia.org wrote:
> Hi everyone,
>
> I am Nicholas Perry, Senior Manager of Strategic Partnerships at WMF.
Following up on Jorge's previous email to add a summary of Google's recent
response to this issue, which was originally shared by Suman on this
Phabricator ticket: https://phabricator.wikimedia.org/T325607.
>
> 
> The web is really large and the search index can simply not include every
single page. A page that otherwise has no problems may not be indexed for a
myriad of complex reasons, for instance if the indexing process determines
that the page is unlikely to be requested in search. This is in line with
the Search Central documentation that states: "Google doesn't guarantee that
it will crawl, index, or serve your page, even if your page follows the
Google Search Essentials."
> 
>
> Google also shared a document containing resource links, which can be
found in the Phabricator ticket. They also encouraged people to submit any
questions and attend their SEO Office Hours
(https://developers.google.com/search/help/office-hours), with the caveat
that Google might not be able to answer all questions in a given instance.
>
> Best,
>
> Nicholas
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/N2DTL2NU377YCEGAQAVRF7EPCGB76OAB/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/E2ZX7E5ABTFXKLUWS2MNVWTBMXJPBKYO/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Arabic Wikipedia day of action

2023-12-24 Thread Peter Southwood
Never again is always. Cheers, Peter

-Original Message-
From: Ziko van Dijk [mailto:zvand...@gmail.com] 
Sent: 23 December 2023 19:54
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Arabic Wikipedia day of action

Hello,

I am most sure that 99,9% of German Wikipedians are aware what was
necessary to end World War II: destroying the National Socialist
German Workers' Party.
With Hitler or another party member being in rule, peace was impossible.
(I say this with my mother''s family having been refugees, and my
father's family having suffered from the Allied bombings.)
Eventually, the civil society of Germany understood how the war and
all its consequences came into existence: "Because we gave in 1933
power to the wrong people." The inofficial state motto became "Never
again!", and in this spirit following the horrors of the Holocaust,
German Wikipedians edit Wikipedia.
Never again! is now.

Kind regards,
Ziko
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/ZRFZVGVZK6GXPLDXS5PECSGD6CBHIMUU/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/YYH25ADQJZSOD5FQV6O2LQFLQHBBWLFZ/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Fwd: We went big in 2023. Here's some of what didn't work:

2023-12-19 Thread Peter Southwood
I guess that would depend on the mistakes. Some are inherently more tolerable 
than others. Some should not be tolerated (depending on what one classifies as 
‘mistakes’). Cheers, Peter

 

From: Natacha Rault via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 18 December 2023 18:38
To: wikimedia-l@lists.wikimedia.org
Cc: Natacha Rault
Subject: [Wikimedia-l] Re: Fwd: We went big in 2023. Here's some of what didn't 
work:

 

I love it too  But will lovers of this message tolerate other people's 
mistakes ? That's the question :)

So for new year let's make a committment to be more tolerant towards what we 
usually do not tolerate !

We may well learn something useful along the way ...

Nattes

 

Le 18.12.23 à 12:43, Florence Devouard a écrit :

Excellent. Love it. Thanks for sharing Z. 

Flo

PS: and it works. I opened my wallet a bit ;)
Second time of the year actually... toss a coin guys

 

Le 18/12/2023 à 00:36, Željko Blaće a écrit :

Very interesting direction in communication to wider audience by acknowledging 
mistakes and failures. 

 

I hope for others in the field will follow and extend towards more authentic 
communication and we see less PR tricks.

-- Forwarded message --
From: Mozilla 
Date: Friday, December 15, 2023
Subject: We went big in 2023. Here's some of what didn't work:
To: "zbl...@mi2.hr" 



Where we failed in 2023‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ 
͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ 
͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌  ͏‌ ͏‌ 
͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ 
͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ 
͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌  ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ 
͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ 
͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ ͏‌ 
͏‌ ͏‌ ͏



 

 




  Mozilla

  ?? Mozilla 
??

  Donate 

 




 


Hello Z., 


Guess what? We make mistakes. We’re human!

This year we at Mozilla set out to take on more new initiatives, reach for 
deeper impact, and go bigger than ever before. A lot of it went well – but 
we've also had our fair share of fails, goofs, oopsies, and dadgummits in 2023. 
And so we thought, why not share with our supporters about times where we tried 
things that didn't work out, or that went differently than expected, or where 
we simply screwed up? 

We thought you might appreciate transparency and honesty about our work, even 
when it's not all sunshine and roses. And yes, at the end of this email, we're 
going to ask if you can  
 add a 
donation to Mozilla's end of year fundraising drive – while we won't promise 
perfection, we will promise transparency. 

So, here’s a highlight of our lowlights and what we learned in 2023:


Mistake #1: Facebook Ads and Privacy Don't Mix


 Facebook in a mixing bowl 

 


 


We wanted to get more people to sign one of our petitions as part of a campaign 
to get TikTok to be more transparent about how it shares user data. Our 
marketing team decided to try their hand at running ads on Facebook to reach 
people who might not be in the Mozilla universe yet.

  

What went wrong: Mozilla's commitment to user privacy is incompatible with the 
data sacrifices required by Meta. Turns out, if you don’t use Meta’s 
privacy-intrusive conversion pixel on your website – and you also refuse to 
give Meta any of your data – there's little chance of driving actions with 
their advertising.

Lesson learned: It is impossible to build a movement to hold tech companies 
accountable while relying on the tools they want you to use. We'll stick to 
places that better represent our values – because that's also where we'll find 
people who are most committed to our movement.


Mistake #2: Storms Bring Us Together, But Make Your Backup Plans


 People watching a storm 

 


 


Mozilla Festival – better known as MozFest – is our global gathering of 
artists, activists, researchers, policymakers, and technologists. This year's 
MozFest event in Nairobi, Kenya focused on issues around a healthy internet and 
trustworthy AI in Eastern and Southern Africa.

  

What went wrong: MozFest got hammered by some truly terrible weather – a hail 
storm so bad and so loud it shut down a featured panel conversation; winds too 
high to walk between buildings; and a tent even blew over! People 

[Wikimedia-l] Re: Launch of Justapedia

2023-09-16 Thread Peter Southwood
Complaints about politics are business as usual. When we stop getting 
complaints about politics is the time to worry, because we will have become 
irrelevant.
Cheers,
Peter

-Original Message-
From: Lauren Worden [mailto:laurenworde...@gmail.com] 
Sent: 12 September 2023 00:43
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Launch of Justapedia

The only specific and non-contradictory complaints about Wikipedia
bias I can find on
https://justapedia.org/wiki/Justapedia:Justapedia_Foundation are
climate change and COVID-19, which are areas in which I think
Wikipedia excels. The complaints about politics go in both directions.

Perhaps Atsme can clarify?

-LW

On Mon, Sep 11, 2023 at 3:18 PM Andy Mabbett  wrote:
>
>
>
>
> On Sun, 10 Sept 2023, 14:31 Rey Bueno via Wikimedia-l, 
>  wrote:
>
>> Justapedia
>
>
> It's laughable, as the logo [1] that (inadvertently,?) shows "disinformation" 
> and "lies" being given equal weight with "information" in determining "truth" 
> suggests.
>
> But this [2] hints at the darker underbelly:
>
> "The Editorial Review Board (ERB) [...] will make binding decisions regarding 
> the retention and rejection of article content, as well as serve to resolve 
> content disputes, and notability issues... ERB members are required to have a 
> high level, native understanding of written English"
>
>> Besides, there are alarming rumors I saw in Y Combinator [...]
>
>
> Oh, please. Do better than that.
>
>
> [1] https://justapedia.org/wiki/File:Hands-circ-sifts-sources-Sm.png
>
> [2] https://justapedia.org/wiki/Justapedia:Editorial_Review_Board
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at 
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/7W7MOK6DIXWW2EDSGEZLBW7EMO3VTJB3/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/ZPURICMWJV5FKR4EKQEMTD2J3DSJUFOA/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MX6K3JLBHIP2JFTGMFD6S5YHGE436FDN/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Launch of Justapedia

2023-09-16 Thread Peter Southwood
Maybe it is not intended to be a Venn diagram, but just looks like one.

Cheers, Peter

 

From: Vi to [mailto:vituzzu.w...@gmail.com] 
Sent: 12 September 2023 09:51
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Launch of Justapedia

 

Indeed Venn diagrams are a left-wing-woke-cancel-culture propaganda.

 

Vito

 

Il giorno mar 12 set 2023 alle ore 08:15 Galder Gonzalez Larrañaga 
 ha scritto:

The logo is quite funny. According to that Information + Disinformation = 
Facts. It might be that they don't know what a Venn diagram is, or simply that 
they actually think that.

 

Don't worry, this is just one more project that will fall into oblivion.

 

Galder

  _  

From: Lauren Worden 
Sent: Tuesday, September 12, 2023 12:42 AM
To: Wikimedia Mailing List 
Subject: [Wikimedia-l] Re: Launch of Justapedia 

 

The only specific and non-contradictory complaints about Wikipedia
bias I can find on
https://justapedia.org/wiki/Justapedia:Justapedia_Foundation are
climate change and COVID-19, which are areas in which I think
Wikipedia excels. The complaints about politics go in both directions.

Perhaps Atsme can clarify?

-LW

On Mon, Sep 11, 2023 at 3:18 PM Andy Mabbett  wrote:
>
>
>
>
> On Sun, 10 Sept 2023, 14:31 Rey Bueno via Wikimedia-l, 
>  wrote:
>
>> Justapedia
>
>
> It's laughable, as the logo [1] that (inadvertently,?) shows "disinformation" 
> and "lies" being given equal weight with "information" in determining "truth" 
> suggests.
>
> But this [2] hints at the darker underbelly:
>
> "The Editorial Review Board (ERB) [...] will make binding decisions regarding 
> the retention and rejection of article content, as well as serve to resolve 
> content disputes, and notability issues... ERB members are required to have a 
> high level, native understanding of written English"
>
>> Besides, there are alarming rumors I saw in Y Combinator [...]
>
>
> Oh, please. Do better than that.
>
>
> [1] https://justapedia.org/wiki/File:Hands-circ-sifts-sources-Sm.png
>
> [2] https://justapedia.org/wiki/Justapedia:Editorial_Review_Board
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at 
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/7W7MOK6DIXWW2EDSGEZLBW7EMO3VTJB3/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/ZPURICMWJV5FKR4EKQEMTD2J3DSJUFOA/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/U6EHCOOQX2SSQJTVDIASE747GQDVHLET/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

 


 

 

Virus-free. 

 www.avg.com

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/555NK3JME6JTUQGM7TXS52J4F6UP7WEU/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Sharing an update on the Wikimedia Foundation Knowledge Equity Fund’s grantees

2023-08-20 Thread Peter Southwood
This would be more convincing if our house was in order. It is not. Cheers, 
Peter

 

From: Nathan [mailto:nawr...@gmail.com] 
Sent: 18 August 2023 12:24
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Sharing an update on the Wikimedia Foundation 
Knowledge Equity Fund’s grantees

 

Steven,

 

I've been thinking about your points here and I wonder if it's worth zooming 
out a little bit on what Wikimedia is trying to achieve. The classic slogan of 
making the sum of all human knowledge accessible to all is an incredibly broad 
and ambitious goal. Since the WMF was founded, the primary implementation of 
that goal has been the various projects (anchored by Wikipedia's, the initial 
innovation). But how convinced are we that this is and will always remain the 
best way to achieve WMF's actual mission? 

 

If we're completely sure that any distraction away from the WMF projects, and 
the model of collecting and distributing knowledge that they represent, would 
be harmful to that goal... then I would agree that the approach taken by 
funding these grants is taking us down the wrong road.

 

If we admit to ourselves instead that Wikimedia's projects represent a great 
model now, and hopefully for many years to come, but that more or better ways 
of achieving the mission may surface... Then perhaps its worthwhile to invest 
persistently in supporting other approaches, to create opportunities for the 
same innovation and discovery behind Wikipedia to uncover what model may best 
meet future moments in delivering knowledge to all. 


~Nate

 

On Wed, Aug 16, 2023 at 1:08 PM Steven Walling  wrote:

 

On Wed, Aug 16, 2023 at 12:34 AM Christophe Henner 
 wrote:

Hi Steven,

 

If I may, I have a different reading on the topic. Knowledge Equity is a topic 
because for centuries knowledges have been destroyed, banned, etc? as such, and 
with our current rules with written sources, funding any organisation 
empowering marginalised communities is critical.

 

If we were funding only direct integration of marginalised knowledges into the 
project we would actually be missing so much.

 

I actually appreciate the Movement funding initiatives outside the Movement.

 

As Nadee said in her email, and I get a feeling it also is partly your point, 
what would be critical here would be to ensure the grantees are supported and 
encouraged in working with local or thematic Wikimedia Organisations. 

@Nadee out of curiosity, is there any staff in the Knowledge Equity Fund 
project in charge of working with grantees to increase their relationships with 
us?

 

Thanks a lot :)

 

Christophe

 

Christophe, 

 

Thanks for your thoughts. I think the problem with "I actually appreciate the 
Movement funding initiatives outside the Movement." is where does the boundary 
of acceptable initiatives end? 

For instance, should we feel comfortable creating a grants program to fight 
climate change? Extreme weather events obviously threaten the stability of the 
projects, and might disrupt editors from volunteering their time. Solving world 
hunger and global health issues would increase the pool of potential 
volunteers. We could also fund a non-profit alternative to Starlink, to 
increase global Internet access to make it possible for more people to edit the 
projects. 

 

The problem is that none of these things are what donors believe they are 
funding when they give us $5 from a banner on Wikipedia asking them to support 
the projects. 

 





On Aug 16, 2023, at 8:36 AM, Steven Walling  wrote:

?

This is really really disappointing to see. The lessons noted in the blog post 
totally miss the point as to why the Wikimedia community has objected to 
Knowledge Equity Fund. The issue is not community oversight via committees or 
visibility into the work. It?s that the work had no demonstrable impact on 
Wikimedia projects whatsoever. We all should want the projects to be more 
equitable when it comes to representing knowledge?it's perfectly aligned with 
the Wikimedia mission. This program is doing absolutely nothing to accomplish 
that.

 

If we want to impact knowledge equity, why not say, let people working on 
underserved languages and topics apply for expense reimbursement when they've 
bought access to sources or equipment to create media for Commons? Or fund a 
huge series of edit-a-thons on BIPOC topics? 

 

If we want free knowledge created by and for people with less systemic 
privilege in the world, direct grants (given to actual Wikimedians) is 
something that the Foundation is uniquely placed to do, as opposed to generic 
lump sum grants for addressing the root causes of social injustice and 
inequity. While those are laudable problems to solve, they are not in fact our 
organization?s mission and what donors think they are funding when they give us 
money. 

 

A second Knowledge Equity round that fails to specifically address how each 
grantee and their work is going to help Wikimedia projects 

[Wikimedia-l] Re: Sharing an update on the Wikimedia Foundation Knowledge Equity Fund’s grantees

2023-08-20 Thread Peter Southwood
This is fair comment, but the lack of transparency makes it impossible to make 
a fair judgement. These things are not sufficiently obvious to just do them 
without adequate explanation. Cheers, Peter

 

From: effe iets anders [mailto:effeietsand...@gmail.com] 
Sent: 17 August 2023 05:44
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Sharing an update on the Wikimedia Foundation 
Knowledge Equity Fund’s grantees

 

I'm very interested to see this develop further, and can understand some of the 
tensions that Steven has articulated. It's tricky to experience that we can't 
fund everything we want to do that has direct impact on our own work, and yet 
fund projects that don't feel like they directly support other activities our 
movement is deploying. 

 

There is one analogy that comes to mind, and I'm not sure how accurate it is, 
but I wanted to share it as a thought experiment. In the 20th century, there 
was a range of technology companies that depended on scientific progress. Some 
of these companies, like IBM and Philips, then started to support also more 
fundamental research that did not necessarily always have a direct feed into 
their product pipeline. In a way, this kind of program has the same vibe to me: 
we're supporting a broader knowledge ecosystem to develop areas that we know 
are underserved (which may well be an understatement), without always having a 
direct connection to how that will feed into our projects, into our activities 
or communities. There is little doubt in my mind though, that in the long run 
the ecosystem will benefit from it, and we depend on that ecosystem for our 
work in turn. 

 

So honestly, I don't see this program much in the context of 'we need to help 
society' but rather an indirect selfish attempt to help improve the ecosystem 
that we're operating in. The conversation 'what are donors donating for' is 
equally a tricky one: I like to believe that they donate to us to help achieve 
the mission and trust us to make the choices that best serve this big picture. 

 

We can have long discussions whether we're the organization or funder best 
situated to fund these activities - but given the large backlog that we're 
dealing with in knowledge equity, I'm not very afraid that we'll have to worry 
about overcrowding in this space for a while. I personally think we may be 
reasonably well located for this - maybe not to be the most important funder, 
but we will have the chance to make a difference. I am however convinced that 
where it comes to climate change there are many other organizations that are 
much better positioned. Of course, this is likely very subjective :)

 

Warmly,

Lodewijk

 

On Thu, Aug 17, 2023 at 6:39 AM Christophe Henner  
wrote:

That would be a great discussion indeed to set the line.

 

But it?s the different from what you started the discussion with where you were 
saying ?we all should want?.

 

I want us to make things that move the needle regarding knowledge equity and 
that probably require outside of the projects programs.

 

As to where we draw the line, that would be a terrific strategic discussion but 
I don?t find where we had it.

Sent from my iPhone





On Aug 16, 2023, at 7:07 PM, Steven Walling  wrote:

?

 

On Wed, Aug 16, 2023 at 12:34?AM Christophe Henner 
 wrote:

Hi Steven,

 

If I may, I have a different reading on the topic. Knowledge Equity is a topic 
because for centuries knowledges have been destroyed, banned, etc? as such, and 
with our current rules with written sources, funding any organisation 
empowering marginalised communities is critical.

 

If we were funding only direct integration of marginalised knowledges into the 
project we would actually be missing so much.

 

I actually appreciate the Movement funding initiatives outside the Movement.

 

As Nadee said in her email, and I get a feeling it also is partly your point, 
what would be critical here would be to ensure the grantees are supported and 
encouraged in working with local or thematic Wikimedia Organisations. 

@Nadee out of curiosity, is there any staff in the Knowledge Equity Fund 
project in charge of working with grantees to increase their relationships with 
us?

 

Thanks a lot :)

 

Christophe

 

Christophe, 

 

Thanks for your thoughts. I think the problem with "I actually appreciate the 
Movement funding initiatives outside the Movement." is where does the boundary 
of acceptable initiatives end? 

For instance, should we feel comfortable creating a grants program to fight 
climate change? Extreme weather events obviously threaten the stability of the 
projects, and might disrupt editors from volunteering their time. Solving world 
hunger and global health issues would increase the pool of potential 
volunteers. We could also fund a non-profit alternative to Starlink, to 
increase global Internet access to make it possible for more people to edit the 
projects. 

 

The problem is that none of these things are 

[Wikimedia-l] Re: Who is the editor with the longest editing streak? Find out!

2023-08-01 Thread Peter Southwood
This is a bit like edit counts, in that it indicates nothing about the value of 
the edits. In a way it is impressive that someone is so dedicated, but all the 
guy at the top of the list needs to do to crash and burn is a couple of days of 
inability to edit for reasons out of their control, so some luck is involved. 

Cheers,

Peter

 

From: Yaroslav Blanter [mailto:ymb...@gmail.com] 
Sent: 28 July 2023 18:56
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Who is the editor with the longest editing streak? 
Find out!

 

Thanks, interesting, I am apparently a human #19 in the list.

 

Best

Yaroslav

 

On Fri, Jul 28, 2023 at 6:43 PM F. Xavier Dengra i Grau via Wikimedia-l 
 wrote:

Bon dia / Hi,

 

Is there any available tool to precisely count how many days in a row a 
Wikimedian from a specifif project has been editing? The source that is linked 
in the Diffs page 
(https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Longest_active_user_editing_streaks)is
 only within the English Wikipedia…

 

Has anyone checked that there is no other user in the rest of the other 
projects (hundreds of them) with a similar or better streak, so that the 
sentence “the Wikimedian with the longest editing streak” is fully accurate 
regarding both language and Wikimedia project?

 

Gràcies! / Thank you!

 

Xavier Dengra 

 

El dv, 28 jul., 2023 a 17:15, Natalia Szafran-Kozakowska 
 va escriure:

Read in عربي, bahasa Indonesia, français, Deutsch, español, Kiswahili, and 
Polish on Diff 

 . 

 

Johnny Au   has been editing 
every single day since November 11, 2007, which makes him the Wikimedian with 
the longest editing streak. That's more than 15 years or - more precisely - 
5733 days of continuous editing! 


Each day Johnny checks his extensive watchlist, which includes articles related 
to his beloved hometown Toronto. From local sports teams and art galleries, to 
Toronto transit system – Johnny is passionate about all things Toronto-related, 
and carefully watches over Wikipedia articles about it. He specializes in 
minor, maintenance edits: correcting spelling and language, reverting 
vandalisms, adding images and correcting mistakes.

 

The daily habit of editing and the pure love for Wikipedia, and passion for 
free knowledge, is what keeps him going. When asked about advice to share with 
other editors, he says: Never give up. Fight the good fight. We must fight 
against misinformation and disinformation.

 

Learn more about Johnny, his work (and this one time when his editing streak 
almost broke!) on Diff  

 or on Meta 
 , as 
we WikiCelebrate  
 his incredible 
dedication to free knowledge. You can also leave some kind words for Johnny on 
the meta page 
  and 
congratulate him on his amazing achievement!

 

Johnny is one of the great people that have contributed so much to bringing us 
to where we are today, and continue to do so. Each month we WikiCelebrate a 
different Wikimedian, acknowledging the amazing community, the pillars of our 
movement. We warmly invite you to write about the people celebrated each month. 
If you know them, share some wiki love. If there’s an outstanding Wikimedian 
that you think should be celebrated, recommend them 
 .

 

Happy celebrating!

Natalia and Mehrdad

 

-- 


  

 

Natalia Szafran-Kozakowska (she/her)
Senior Global Movement Communications Specialist (European Region)
  Wikimedia Foundation

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/TI7ADTGXKCDZIROI7HAD6B36TVJYTZET/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

 


 

 

Virus-free. 

 www.avg.com

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 

[Wikimedia-l] Re: ChatGPT as a reliable source

2023-05-18 Thread Peter Southwood
It depends on how much you know about the topic, Both methods have their 
advantages.

Cheers,

Peter

 

From: Todd Allen [mailto:toddmal...@gmail.com] 
Sent: 17 May 2023 20:10
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: ChatGPT as a reliable source

 

Though, this does run the risk of encouraging people to take the "backwards" 
approach to writing an article--writing some stuff, and then (hopefully at 
least) trying to come up with sources for it.

 

The much superior approach is to locate the available sources first, and then 
to develop the article based upon what those sources say.

 

Todd

 

On Wed, May 17, 2023 at 12:06 PM Samuel Klein  wrote:

 

First: Wikipedia style for dense inline citations is one of the most granular 
and articulate around, so we're pushing the boundaries in some cases of 
research norms for clarity in sourcing.  That's great; also means sometimes we 
are considering nuances that may be new.

 

Second: We're approaching a topic close to my heart, which is distinguishing 
reference-sources from process-sources.  Right now we often capture process 
sources (for an edit) in the edit summary, and this is not visible anywhere on 
the resulting article.  Translations via a translate tool; updates by a script 
that does a particular class of work (like spelling or grammer checking); 
applying a detailed diff that was workshopped on some other page.  An even 
better interface might allow for that detail to be visible to readers of the 
article [w/o traversing the edit history], and linked to the 
sections/paragraphs/sentences affected.

 

I think any generative tools used to rewrite a section or article, or to 
produce a sibling version for a different reading-level, or to generate a 
timeline or other visualization that is then embedded in the article, should 
all be cited somehow.  To Jimbo's point, that doesn't belong in a References 
section as we currently have them.  But I'd like to see us develop a way to 
capture these process notes in a more legible way, so readers can discover them 
without browsing the revision history.  

 

People using generative tools to draft new material should find reliable 
sources for every claim in that material, much more densely than you would when 
summarizing a series of sources yourself.   

However, as we approach models that can discover sources and check facts, a 
combination of those with current generative tools could produce things closer 
to what we'd consider acceptable drafts, and at scale could generate reference 
works in languages that lack them.  I suggest a separate project for those as 
the best way to explore the implications of being able to do this at scale, and 
should capture the full model/tuning/prompt details of how each edit was 
generated.  Such an automatically-updated resource would not be a good reliable 
source, just as we avoid citing any tertiary sources, but could be a research 
tool for WP editors and modelers alike. 

 

SJ

 

On Wed, May 17, 2023 at 9:27 AM Jimmy Wales  wrote:

One way I think we can approach this is to think of it as being the latest in 
this progression:

spellchecker -> grammar checker -> text generation support

We wouldn't have any sort of footnote or indication of any kind that a 
spellchecker or grammar checker was
used by an editor, it's just built-in to many writing tools.  Similarly, if 
writing a short prompt to generate a longer
text is used, then we have no reason to cite that.

What we do have, though, is a responsibility to check the output.  
Spellcheckers can be wrong (suggesting the correct
spelling of the wrong word for example).  Grammar checkers can be wrong (trying 
to correct the grammar of a direct quote
for example).  Generative AI models can be wrong - often simply making things 
up out of thin air that sound plausible.

If someone uses a generative AI to help them write some text, that's not a big 
deal.  If they upload text without checking
the facts and citing a real source, that's very bad.

 

On 2023-05-17 11:51, The Cunctator wrote:

Again at no point should even an improved version be considered a source; at 
best it would be a research or editing tool.

 

On Wed, May 17, 2023, 4:40 AM Lane Chance  wrote:

Keep in mind how fast these tools change. ChatGPT, Bard and
competitors understand well the issues with lack of sources, and Bard
does sometimes put a suitable source in a footnote, even if it
(somewhat disappointingly) just links to wikipedia. There's likely to
be a variation soon that does a decent job of providing references,
and at that point the role of these tools moves beyond being an
amusement to a far more credible research tool.

So, these long discussions about impact on open knowledge are quite
likely to have to run again in 2024...

On Wed, 17 May 2023 at 09:24, Kiril Simeonovski
 wrote:
>
> Thank you everyone for your input.
>
> Your considerations are very similar to mine, and they give a clear direction 
> towards what 

[Wikimedia-l] Re: ChatGPT as a reliable source

2023-05-18 Thread Peter Southwood
Agreed. The editor is responsible for their edits, if they fail to provide 
suitable sourcing, misrepresent the cited source, plagiarise or infringe on 
copyright  that is on them. Do it too often and they get banned. We don’t need 
to know how they composed the content, so we shouldn’t care. Competence is 
required. Using a different tool just needs a slightly different competence. 
Like a chainsaw instead of an axe

Cheers, Peter.

 

From: Denny Vrandečić [mailto:vrande...@gmail.com] 
Sent: 18 May 2023 01:35
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: ChatGPT as a reliable source

 

I think Jimmy's proposal is spot on.

 

A generative AI is a tool, and whoever makes the edit is fully responsible for 
the edit, no matter whether the text was written by the person or with the help 
of a generative tool. This has the potential to open us for people who are not 
good at formulating, or who are not confident about their writing. As long as 
they completely take responsibility for the written text, all is fine.

 

This is similar to the approach the ACM has taken for AI generated text. They 
decided that a generative model cannot be a co-author as it lacks the ability 
to be morally responsible for the text. Second, anything that you publish under 
your name is your responsibility.

 

 

On Wed, May 17, 2023 at 11:11 AM Todd Allen  wrote:

Though, this does run the risk of encouraging people to take the "backwards" 
approach to writing an article--writing some stuff, and then (hopefully at 
least) trying to come up with sources for it.

 

The much superior approach is to locate the available sources first, and then 
to develop the article based upon what those sources say.

 

Todd

 

On Wed, May 17, 2023 at 12:06 PM Samuel Klein  wrote:

 

First: Wikipedia style for dense inline citations is one of the most granular 
and articulate around, so we're pushing the boundaries in some cases of 
research norms for clarity in sourcing.  That's great; also means sometimes we 
are considering nuances that may be new.

 

Second: We're approaching a topic close to my heart, which is distinguishing 
reference-sources from process-sources.  Right now we often capture process 
sources (for an edit) in the edit summary, and this is not visible anywhere on 
the resulting article.  Translations via a translate tool; updates by a script 
that does a particular class of work (like spelling or grammer checking); 
applying a detailed diff that was workshopped on some other page.  An even 
better interface might allow for that detail to be visible to readers of the 
article [w/o traversing the edit history], and linked to the 
sections/paragraphs/sentences affected.

 

I think any generative tools used to rewrite a section or article, or to 
produce a sibling version for a different reading-level, or to generate a 
timeline or other visualization that is then embedded in the article, should 
all be cited somehow.  To Jimbo's point, that doesn't belong in a References 
section as we currently have them.  But I'd like to see us develop a way to 
capture these process notes in a more legible way, so readers can discover them 
without browsing the revision history.  

 

People using generative tools to draft new material should find reliable 
sources for every claim in that material, much more densely than you would when 
summarizing a series of sources yourself.   

However, as we approach models that can discover sources and check facts, a 
combination of those with current generative tools could produce things closer 
to what we'd consider acceptable drafts, and at scale could generate reference 
works in languages that lack them.  I suggest a separate project for those as 
the best way to explore the implications of being able to do this at scale, and 
should capture the full model/tuning/prompt details of how each edit was 
generated.  Such an automatically-updated resource would not be a good reliable 
source, just as we avoid citing any tertiary sources, but could be a research 
tool for WP editors and modelers alike. 

 

SJ

 

On Wed, May 17, 2023 at 9:27 AM Jimmy Wales  wrote:

One way I think we can approach this is to think of it as being the latest in 
this progression:

spellchecker -> grammar checker -> text generation support

We wouldn't have any sort of footnote or indication of any kind that a 
spellchecker or grammar checker was
used by an editor, it's just built-in to many writing tools.  Similarly, if 
writing a short prompt to generate a longer
text is used, then we have no reason to cite that.

What we do have, though, is a responsibility to check the output.  
Spellcheckers can be wrong (suggesting the correct
spelling of the wrong word for example).  Grammar checkers can be wrong (trying 
to correct the grammar of a direct quote
for example).  Generative AI models can be wrong - often simply making things 
up out of thin air that sound plausible.

If someone uses a generative AI to help 

[Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening tour

2023-04-20 Thread Peter Southwood
And an international organisation hiring more people in a city where employment 
conditions are so expensive you can’t do the job properly is not? 

Also no-one was recommending firing the current incumbents, or not that I 
noticed anyway. Cheers, P

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 20 April 2023 10:18
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening tour

 

No, what I said was that firing people in one country then hiring some else in 
another country with the same skills to do the same job just because employment 
conditions are cheaper is morally bankrupt.  With that just hiring from certain 
countries because its cheapest with the least amount of conditions, is also 
morally bankrupt.

  

 

On Thu, 20 Apr 2023 at 16:02, Peter Southwood  
wrote:

So leave them to rot because their standard of living is low and their 
government is crap? Right. 

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 18 April 2023 13:49
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening tour

 

Hiring people because they are in such countries as the basis for saving money 
is morally bankrupt,  yet we'll happily draw from the pool of donations that 
primarily come from those more expensive countries.  Much like we talk about 
equity but decide that some places arent worth engaging in because its too far 
to travel leaving others to shoulder the burden of travel.

 

On Tue, 18 Apr 2023 at 19:35, Felipe Schenone  wrote:

Yet in some countries, like mine, paying for food, renting a place, buying a 
house, etc. is far cheaper than in the US, so paying a lower salary (in USD) 
wouldn't amount to a lower standard of living at all, and doesn't feel immoral, 
at least to me.

 

On Tue, Apr 18, 2023 at 8:00 AM Gnangarra  wrote:

 Either we make software development cheaper somehow (move the WMF to Romania 
or something)

 

Hiring in countries with the worst labour laws and cheapest minimum wages is 
totally immoral. Especially in a community where equity is part of our culture 
we must endeavour to ensure that employees/contractors regardless of where they 
live paid fairly and equally subject to skills and responsibilities of the 
role.  WMF already has many employees that are based in countries where such 
immoral employment conditions dominate. 

 

On Tue, 18 Apr 2023 at 05:49, Dan Garry (Deskana)  wrote:

I agree with much of what Amir has said here, except one little bit...

 

On Mon, 17 Apr 2023 at 20:52, Amir Sarabadani  wrote:

And even if a software would have an owner, it used to be that the team was 
under so much pressure to produce new things instead of maintenance that the 
software would practically be without a maintainer (or worse, as even 
volunteers couldn't unofficially take the role). I can example a few.

 

I think pressure on a team to deliver new things is one reason why this 
situation has come about, but it's far from being the only one. Here's a few 
others off the top of my head:

*   Owning so many things that even if there was zero pressure to deliver 
new features, the team still couldn't maintain everything that they own.
*   Incredibly powerful and incredibly complex features that teams are 
afraid of touching lest they break them and make community members angry.
*   Conservatism and fear of community outrage causing reluctance to 
deprecate functionality.
*   Lack of understanding of the impact of the feature.
*   Lack of a clear roadmap (a list of bug reports and feature requests is 
not a roadmap).

There's more but those are some that come to the top of my head. And, not 
everyone one of those always applies to every situation, e.g. I definitely 
don't think all of the items in your list should be deprecated!

 

This causes the path of least resistance to be, for everyone involved, to leave 
things in limbo and hope for the best.

 

Dan

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/Y4YKOLNJKWAUQFNOVMZSKDSZRORSWFNB/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org




 

-- 

Boodarwun
Gnangarra

'ngany dabakarn koorliny arn boodjera dardoon ngalang Nyungar koortaboodjar'

  

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/P2JSB3JJ6ZOLPMBYV3EPYDP5RALWN7O6/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening tour

2023-04-20 Thread Peter Southwood
So leave them to rot because their standard of living is low and their 
government is crap? Right. 

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 18 April 2023 13:49
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening tour

 

Hiring people because they are in such countries as the basis for saving money 
is morally bankrupt,  yet we'll happily draw from the pool of donations that 
primarily come from those more expensive countries.  Much like we talk about 
equity but decide that some places arent worth engaging in because its too far 
to travel leaving others to shoulder the burden of travel.

 

On Tue, 18 Apr 2023 at 19:35, Felipe Schenone  wrote:

Yet in some countries, like mine, paying for food, renting a place, buying a 
house, etc. is far cheaper than in the US, so paying a lower salary (in USD) 
wouldn't amount to a lower standard of living at all, and doesn't feel immoral, 
at least to me.

 

On Tue, Apr 18, 2023 at 8:00 AM Gnangarra  wrote:

 Either we make software development cheaper somehow (move the WMF to Romania 
or something)

 

Hiring in countries with the worst labour laws and cheapest minimum wages is 
totally immoral. Especially in a community where equity is part of our culture 
we must endeavour to ensure that employees/contractors regardless of where they 
live paid fairly and equally subject to skills and responsibilities of the 
role.  WMF already has many employees that are based in countries where such 
immoral employment conditions dominate. 

 

On Tue, 18 Apr 2023 at 05:49, Dan Garry (Deskana)  wrote:

I agree with much of what Amir has said here, except one little bit...

 

On Mon, 17 Apr 2023 at 20:52, Amir Sarabadani  wrote:

And even if a software would have an owner, it used to be that the team was 
under so much pressure to produce new things instead of maintenance that the 
software would practically be without a maintainer (or worse, as even 
volunteers couldn't unofficially take the role). I can example a few.

 

I think pressure on a team to deliver new things is one reason why this 
situation has come about, but it's far from being the only one. Here's a few 
others off the top of my head:

*   Owning so many things that even if there was zero pressure to deliver 
new features, the team still couldn't maintain everything that they own.
*   Incredibly powerful and incredibly complex features that teams are 
afraid of touching lest they break them and make community members angry.
*   Conservatism and fear of community outrage causing reluctance to 
deprecate functionality.
*   Lack of understanding of the impact of the feature.
*   Lack of a clear roadmap (a list of bug reports and feature requests is 
not a roadmap).

There's more but those are some that come to the top of my head. And, not 
everyone one of those always applies to every situation, e.g. I definitely 
don't think all of the items in your list should be deprecated!

 

This causes the path of least resistance to be, for everyone involved, to leave 
things in limbo and hope for the best.

 

Dan

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/Y4YKOLNJKWAUQFNOVMZSKDSZRORSWFNB/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org




 

-- 

Boodarwun
Gnangarra

'ngany dabakarn koorliny arn boodjera dardoon ngalang Nyungar koortaboodjar'

  

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/P2JSB3JJ6ZOLPMBYV3EPYDP5RALWN7O6/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/OSWIMESHLJQ57TRBXAIEYTW7YLSDKX7V/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org




 

-- 

Boodarwun
Gnangarra

'ngany dabakarn koorliny arn boodjera dardoon ngalang Nyungar koortaboodjar'

  

 


 

 

Virus-free. 

 www.avg.com

 

___
Wikimedia-l 

[Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening tour

2023-04-20 Thread Peter Southwood
There is nothing stopping an organisation from paying a decent salary and using 
fair hiring practices even when not legally required to do so,  and still 
getting more bang for their bucks. In what way would that be immoral? Cheers, P

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 18 April 2023 13:00
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening tour

 

 Either we make software development cheaper somehow (move the WMF to Romania 
or something)

 

Hiring in countries with the worst labour laws and cheapest minimum wages is 
totally immoral. Especially in a community where equity is part of our culture 
we must endeavour to ensure that employees/contractors regardless of where they 
live paid fairly and equally subject to skills and responsibilities of the 
role.  WMF already has many employees that are based in countries where such 
immoral employment conditions dominate. 

 

On Tue, 18 Apr 2023 at 05:49, Dan Garry (Deskana)  wrote:

I agree with much of what Amir has said here, except one little bit...

 

On Mon, 17 Apr 2023 at 20:52, Amir Sarabadani  wrote:

And even if a software would have an owner, it used to be that the team was 
under so much pressure to produce new things instead of maintenance that the 
software would practically be without a maintainer (or worse, as even 
volunteers couldn't unofficially take the role). I can example a few.

 

I think pressure on a team to deliver new things is one reason why this 
situation has come about, but it's far from being the only one. Here's a few 
others off the top of my head:

*   Owning so many things that even if there was zero pressure to deliver 
new features, the team still couldn't maintain everything that they own.
*   Incredibly powerful and incredibly complex features that teams are 
afraid of touching lest they break them and make community members angry.
*   Conservatism and fear of community outrage causing reluctance to 
deprecate functionality.
*   Lack of understanding of the impact of the feature.
*   Lack of a clear roadmap (a list of bug reports and feature requests is 
not a roadmap).

There's more but those are some that come to the top of my head. And, not 
everyone one of those always applies to every situation, e.g. I definitely 
don't think all of the items in your list should be deprecated!

 

This causes the path of least resistance to be, for everyone involved, to leave 
things in limbo and hope for the best.

 

Dan

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/Y4YKOLNJKWAUQFNOVMZSKDSZRORSWFNB/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org




 

-- 

Boodarwun
Gnangarra

'ngany dabakarn koorliny arn boodjera dardoon ngalang Nyungar koortaboodjar'

  

 


 

 

Virus-free. 

 www.avg.com

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/BQHII3EZIHG53IGAVNPP3Z7VKLTMFDVW/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: reflecting on my Wiki tour

2023-04-17 Thread Peter Southwood
Got to agree there. P

 

From: WereSpielChequers [mailto:werespielchequ...@gmail.com] 
Sent: 17 April 2023 14:50
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: reflecting on my Wiki tour

 

Far from a pipe dream, a strategy of keeping useful functionality maintained 
and working through known problems, sounds like a much better use of IT 
resource than one of neglecting deployed software to prioritise the latest fads.

 

WSC

On Mon, 17 Apr 2023, 1:04 pm ,  


   1. Re: [Wikitech-l] Re: Reflecting on my listening tour (Gergő Tisza)


--

Message: 1
Date: Sun, 16 Apr 2023 17:50:57 -0700
From: Gergő Tisza 
Subject: [Wikimedia-l] Re: [Wikitech-l] Re: Reflecting on my listening
tour
To: Wikimedia Mailing List 
Message-ID:

Content-Type: multipart/alternative;
boundary="6a8f6905f97d969b"

On Sat, Apr 15, 2023 at 7:49 AM AntiCompositeNumber <
anticompositenum...@gmail.com> wrote:

> Agreed. It has long been the case that infrastructure critical to the
> operation of the various wikis has been left without a clear
> maintainer, or has been maintained only in the volunteer time of a
> single staffer already fulfilling a full-time role. Teams would be
> dissolved or reassigned to completely different projects after
> completion, without the ability and/or willingness to even review
> patches. That assumes that the team doing the work wasn't made up of
> contractors who departed the Foundation when the project was
> "completed", taking their knowledge of it with them.
>
> This was a major factor in causing the technical debt problem, and
> must be addressed to have any chance of solving it.
>

At some point we will have to admit that we have created a feature set many
times larger than we have the capacity to actively maintain and improve.
Either we make software development cheaper somehow (move the WMF to
Romania or something), or we cut some of the non-software spending (but we
already spend 50%+ of movement funds on software, and we'd have to increase
capacity way more than by a factor of two to maintain all our code), or we
undeploy most current features, or we'll have to put up with most things
being unmaintained, which is the status quo. That's not to say we can't be
smarter about it (e.g. microservices are a great way to have maintenance
overhead spin even more out of control) or that maintenance efforts
couldn't be better prioritized (e.g. the lack of maintainership of our
authentication stack is somewhat wild), but fundamentally changing the
current mode of operation (where most things are deployed and
then abandoned to work on the next thing) is a pipe dream IMO.
-- next part --
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 2167 bytes
Desc: not available

--

Subject: Digest Footer

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


--

End of Wikimedia-l Digest, Vol 788, Issue 1
***

 


 

 

Virus-free. 

 www.avg.com

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/5PDNAPWLYXTX3UUEVR6EMBKOTDNHOMEZ/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Bing-ChatGPT

2023-03-18 Thread Peter Southwood
“Cowen has sufficient credentials to be treated as a reliable expert”

Maybe not for much longer.

Cheers, P.

 

From: The Cunctator [mailto:cuncta...@gmail.com] 
Sent: 17 March 2023 17:49
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Bing-ChatGPT

 

This is an important development for editors to be aware of - we're going to 
have to be increasingly on the lookout for sources using ML-generated bullshit. 
Here are two instances I'm aware of this week:

 

https://www.thenation.com/article/culture/internet-archive-publishers-lawsuit-chatbot/
In late February, Tyler Cowen, a libertarian economics professor at George 
Mason University, published a blog post  

 titled, “Who was the most important critic of the printing press in the 17th 
century?” Cowen’s post contended that the polymath and statesman Francis Bacon 
was an “important” critic of the printing press; unfortunately, the post 
contains long, fake quotes attributed to Bacon’s The Advancement of Learning 
(1605), complete with false chapter and section numbers.
Tech writer Mathew Ingram drew attention to the fabrications  

 a few days later, noting that Cowen has been  

 writing approvingly about the AI chatbot ChatGPT for some time now; several 
commenters on Cowen’s post assumed the fake quotes must be the handiwork of 
ChatGPT. (Cowen did not reply to e-mailed questions regarding the post by press 
time, and later removed the post entirely, with no explanation whatsoever. 
However, a copy remains at the Internet Archive’s Wayback Machine).

 

 

 
https://www.vice.com/en/article/3akz8y/ai-injected-misinformation-into-article-claiming-misinformation-in-navalny-doc
An article claiming to identify misinformation in an Oscar-winning documentary 
about imprisoned Russian dissident Alexei Navalny is itself full of 
misinformation, thanks to the author using AI. 
Investigative news outlet The Grayzone recently  
 
published an article that included AI-generated text as a source for its 
information. The  

 piece, “Oscar-winning ‘Navalny’ documentary is packed with misinformation” by 
Lucy Komisar, included hyperlinks to  

 PDFs uploaded to the author’s personal website that appear to be screenshots 
of conversations she had with ChatSonic, a free generative AI chatbot that 
advertises itself as a ChatGPT alternative that can “write factual trending 
content” using Google search results.

That said, I don't think this is anything to be too stressed about; the 
Grayzone is already a deprecated source and blogs like Marginal Revolution are 
treated with caution, though Cowen has sufficient credentials to be treated as 
a reliable expert.

 

On Fri, Mar 17, 2023 at 11:23 AM Kimmo Virtanen  
wrote:

Hi,

 

The development of open-source large language models is going forward. The 
GPT-4 was released and it seems that it passed the Bar exam and tried to hire 
humans to solve catchpas which were too complex. However, the development in 
the open source and hacking side has been pretty fast and it seems that there 
are all the pieces for running LLM models in personal hardware (and in web 
browsers). Biggest missing piece is fine tuning of open source models such as 
Neox for the English language. For multilingual and multimodal (for example 
images+text) the model is also needed.

 

So this is kind of a link dump for relevant things for creation of open source 
LLM model and service and also recap where the hacker community is now.

 

1.) Creation of an initial unaligned model. 

· Possible models

·   20b Neo(X) by EleutherAI 
(Apache 2.0)

·   Fairseq Dense by 
Facebook (MIT-licence)

·   
LLaMa by Facebook (custom license, leaked research use only)

·   Bloom by Bigscience ( 
 custom license. open, 
non-commercial)

 

2.) Fine-tuning or align

·

[Wikimedia-l] Re: Chat GPT

2023-02-06 Thread Peter Southwood
It would depend on whether it uses the text or the information/data. My guess 
is that the more it uses its own words, the more drift in meaning there will 
be, and the less reliable the result, but I have no way to test this 
hypothesis. 

 Cheers, Peter

 

From: Ilario Valdelli [mailto:valde...@gmail.com] 
Sent: 06 February 2023 09:38
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Chat GPT

 

And this is a problem.

 

If ChatGPT uses open content, there is an infringement of license.

 

Specifically the CC-by-sa if it uses Wikipedia. In this case the attribution 
must be present.

 

Kind regards

 

On Sun, 5 Feb 2023, 08:12 Peter Southwood,  wrote:

“Not citing sources is probably a conscious design choice, as citing sources 
would mean sharing the sources used to train the language models” This may be a 
choice that comes back to bite them. Without citing their sources, they are 
unreliable as a source for anything one does not know already. Someone will 
have a bad consequence from relying on the information and will sue the 
publisher. It will be interesting to see how they plan to weasel their way out 
of legal responsibility while retaining any credibility. My guess is there will 
be a requirement to state that the information is AI generated and of entirely 
unknown and untested reliability. How soon to the first class action, I wonder. 
Lots of money for the lawyers. Cheers, Peter.

 

From: Subhashish [mailto:psubhash...@gmail.com] 
Sent: 05 February 2023 06:37
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Chat GPT

 

Just to clarify, my point was not about Getty to begin with. Whether Getty 
would win and whether a big corporation should own such a large amount of 
visual content are questions outside this particular thread. It would certainly 
be interesting to see how things roll.

 

But AI/ML is way more than just looking. Training with large models is a very 
sophisticated and technical process. Data annotation among many other forms of 
labour are done by real people. the article I had linked earlier tells a lot 
about the real world consequences of AI. I'm certain AI/ML, especially when 
we're talking about language models like ChatGPT, are far from innocent 
looking/reading. For starters, derivative of works, except Public Domain ones, 
must attribute the authors. Any provision for attribution is deliberately 
removed from systems like ChatGPT and that only gives corporations like OpenAI 
a free ride sans accountability.

 

Subhashish 

 

 

On Sat, Feb 4, 2023, 4:41 PM Todd Allen  wrote:

I'm not so sure Getty's got a case, though. If the images are on the Web, is 
using them to train an AI something copyright would cover? That to me seems 
more equivalent to just looking at the images, and there's no copyright problem 
in going to Getty's site and just looking at a bunch of their pictures.

 

But it will be interesting to see how that one shakes out.

 

Todd

 

On Sat, Feb 4, 2023 at 11:47 AM Subhashish  wrote:

Not citing sources is probably a conscious design choice, as citing sources 
would mean sharing the sources used to train the language models. Getty has 
just sued Stability AI, alleging the use of 12 million photographs without 
permission or compensation. Imagine if Stability had to purchase from Getty 
through a legal process. For starters, Getty might not have agreed in the first 
place. Bulk-scaping publicly visible text in text-based AIs like ChatGPT would 
mean scraping text with copyright. But even reusing CC BY-SA content would 
require attribution. None of the AI platforms attributes their sources because 
they did not acquire content in legal and ethical ways [1]. Large language 
models won't be large and releases won't happen fast if they actually start 
acquiring content gradually from trustworthy sources. It took so many years for 
hundreds and thousands of Wikimedians to take Wikipedias in different languages 
to where they are for a reason.

 

1. https://time.com/6247678/openai-chatgpt-kenya-workers/




Subhashish

 

 

On Sat, Feb 4, 2023 at 1:06 PM Peter Southwood  
wrote:

>From what I have seen the AIs are not great on citing sources. If they start 
>citing reliable sources, their contributions can be verified, or not. If they 
>produce verifiable, adequately sourced, well written information, are they a 
>problem or a solution?

Cheers,

Peter

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 04 February 2023 17:04
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Chat GPT

 

I see our biggest challenge is going to be detecting these AI tools adding 
content whether it's media or articles, along with identifying when they are in 
use by sources.  The failing of all new AI is not in its ability but in the 
lack of transparency with that being able to be identified by the readers. We 
have seen people impersonating musicians and writing songs in their style. We 
have also seen pictures that have 

[Wikimedia-l] Re: Chat GPT

2023-02-04 Thread Peter Southwood
“Not citing sources is probably a conscious design choice, as citing sources 
would mean sharing the sources used to train the language models” This may be a 
choice that comes back to bite them. Without citing their sources, they are 
unreliable as a source for anything one does not know already. Someone will 
have a bad consequence from relying on the information and will sue the 
publisher. It will be interesting to see how they plan to weasel their way out 
of legal responsibility while retaining any credibility. My guess is there will 
be a requirement to state that the information is AI generated and of entirely 
unknown and untested reliability. How soon to the first class action, I wonder. 
Lots of money for the lawyers. Cheers, Peter.

 

From: Subhashish [mailto:psubhash...@gmail.com] 
Sent: 05 February 2023 06:37
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Chat GPT

 

Just to clarify, my point was not about Getty to begin with. Whether Getty 
would win and whether a big corporation should own such a large amount of 
visual content are questions outside this particular thread. It would certainly 
be interesting to see how things roll.

 

But AI/ML is way more than just looking. Training with large models is a very 
sophisticated and technical process. Data annotation among many other forms of 
labour are done by real people. the article I had linked earlier tells a lot 
about the real world consequences of AI. I'm certain AI/ML, especially when 
we're talking about language models like ChatGPT, are far from innocent 
looking/reading. For starters, derivative of works, except Public Domain ones, 
must attribute the authors. Any provision for attribution is deliberately 
removed from systems like ChatGPT and that only gives corporations like OpenAI 
a free ride sans accountability.

 

Subhashish 

 

 

On Sat, Feb 4, 2023, 4:41 PM Todd Allen  wrote:

I'm not so sure Getty's got a case, though. If the images are on the Web, is 
using them to train an AI something copyright would cover? That to me seems 
more equivalent to just looking at the images, and there's no copyright problem 
in going to Getty's site and just looking at a bunch of their pictures.

 

But it will be interesting to see how that one shakes out.

 

Todd

 

On Sat, Feb 4, 2023 at 11:47 AM Subhashish  wrote:

Not citing sources is probably a conscious design choice, as citing sources 
would mean sharing the sources used to train the language models. Getty has 
just sued Stability AI, alleging the use of 12 million photographs without 
permission or compensation. Imagine if Stability had to purchase from Getty 
through a legal process. For starters, Getty might not have agreed in the first 
place. Bulk-scaping publicly visible text in text-based AIs like ChatGPT would 
mean scraping text with copyright. But even reusing CC BY-SA content would 
require attribution. None of the AI platforms attributes their sources because 
they did not acquire content in legal and ethical ways [1]. Large language 
models won't be large and releases won't happen fast if they actually start 
acquiring content gradually from trustworthy sources. It took so many years for 
hundreds and thousands of Wikimedians to take Wikipedias in different languages 
to where they are for a reason.

 

1. https://time.com/6247678/openai-chatgpt-kenya-workers/




Subhashish

 

 

On Sat, Feb 4, 2023 at 1:06 PM Peter Southwood  
wrote:

>From what I have seen the AIs are not great on citing sources. If they start 
>citing reliable sources, their contributions can be verified, or not. If they 
>produce verifiable, adequately sourced, well written information, are they a 
>problem or a solution?

Cheers,

Peter

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 04 February 2023 17:04
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Chat GPT

 

I see our biggest challenge is going to be detecting these AI tools adding 
content whether it's media or articles, along with identifying when they are in 
use by sources.  The failing of all new AI is not in its ability but in the 
lack of transparency with that being able to be identified by the readers. We 
have seen people impersonating musicians and writing songs in their style. We 
have also seen pictures that have been created by copying someone else's work 
yet not acknowledging it as being derivative of any kind.

 

Our big problems will be in ensuring that copyright is respected in legally, 
and not hosting anything that is even remotely dubious 

 

On Sat, 4 Feb 2023 at 22:24, Adam Sobieski  wrote:

Brainstorming on how to drive traffic to Wikimedia content from conversational 
media, UI/UX designers could provide menu items or buttons on chatbots' 
applications or webpage components (e.g., to read more about the content, to 
navigate to cited resources, to edit the content, to discuss the content, to 
upvote/downvote the content, to share the content or the recent dialo

[Wikimedia-l] Re: Chat GPT

2023-02-04 Thread Peter Southwood
>From what I have seen the AIs are not great on citing sources. If they start 
>citing reliable sources, their contributions can be verified, or not. If they 
>produce verifiable, adequately sourced, well written information, are they a 
>problem or a solution?

Cheers,

Peter

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 04 February 2023 17:04
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Chat GPT

 

I see our biggest challenge is going to be detecting these AI tools adding 
content whether it's media or articles, along with identifying when they are in 
use by sources.  The failing of all new AI is not in its ability but in the 
lack of transparency with that being able to be identified by the readers. We 
have seen people impersonating musicians and writing songs in their style. We 
have also seen pictures that have been created by copying someone else's work 
yet not acknowledging it as being derivative of any kind.

 

Our big problems will be in ensuring that copyright is respected in legally, 
and not hosting anything that is even remotely dubious 

 

On Sat, 4 Feb 2023 at 22:24, Adam Sobieski  wrote:

Brainstorming on how to drive traffic to Wikimedia content from conversational 
media, UI/UX designers could provide menu items or buttons on chatbots' 
applications or webpage components (e.g., to read more about the content, to 
navigate to cited resources, to edit the content, to discuss the content, to 
upvote/downvote the content, to share the content or the recent dialogue 
history on social media, to request review/moderation/curation for the content, 
etc.). Many of these envisioned menu items or buttons would operate 
contextually during dialogues, upon the most recent (or otherwise selected) 
responses provided by the chatbot or upon the recent transcripts. Some of these 
features could also be made available to end-users via spoken-language commands.

At any point during hypertext-based dialogues, end-users would be able to 
navigate to Wikimedia content. These navigations could utilize either URL query 
string arguments or HTTP POST. In either case, bulk usage data, e.g., those 
dialogue contexts navigated from, could be useful. 

The capability to perform A/B testing across chatbots’ dialogues, over large 
populations of end-users, could also be useful. In this way, Wikimedia would be 
better able to: (1) measure end-user engagement and satisfaction, (2) measure 
the quality of provided content, (3) perform personalization, (4) retain 
readers and editors. A/B testing could be performed by providing end-users with 
various feedback buttons (as described above). A/B testing data could also be 
obtained through data mining, analyzing end-users’ behaviors, response times, 
responses, and dialogue moves. These data could be provided for the community 
at special pages and could be made available per article, possibly by enhancing 
the “Page information” system. One can also envision these kinds of analytics 
data existing at the granularity of portions of, or selections of, articles. 

 

 

Best regards,

Adam

 

  _  

From: Victoria Coleman 
Sent: Saturday, February 4, 2023 8:10 AM
To: Wikimedia Mailing List 
Subject: [Wikimedia-l] Re: Chat GPT 

 

Hi Christophe, 

 

I had not thought about the threat to Wikipedia traffic from Chat GPT but you 
have a good point. The success of the projects is always one step away from the 
next big disruption. So the WMF as the tech provider for the mission (because 
first and foremost in my view that?s what the WMF is - as well as the financial 
engine of the movement of course) needs to pay attention and experiment to 
maintain the long term viability of the mission. In fact I think the cluster of 
our projects offers compelling options. For example to your point below on data 
sets, we have the amazing Wikidata as well the excellent work on abstract 
Wikipedia. We have Wikipedia Enterprise which has built some avenues of 
collaboration with big tech. A bold vision is needed to bring all of it 
together and build an MVP for the community to experiment with.

Best regards, 

 

Victoria Coleman





On Feb 4, 2023, at 4:14 AM, Christophe Henner  
wrote:

?Hi, 

 

On the product side, NLP based AI biggest concern to me is that it would 
drastically decrease traffic to our websites/apps. Which means less new editors 
ans less donations. 

 

So first from a strictly positioning perspective, we have here a major change 
that needs to be managed.

 

And to be honest, it will come faster than we think. We are perfectionists, I 
can assure you, most companies would be happy to launch a search product with a 
80% confidence in answers quality.

 

>From a financial perspective, large industrial investment like this are 
>usually a pool of money you can draw from in x years. You can expect they did 
>not draw all of it yet.

 

Second, GPT 3 and ChatGPT are far from being the most expensive products they 
have. On top of people you 

[Wikimedia-l] Re: The Endowment, again

2023-01-27 Thread Peter Southwood
Yes, but sometimes a yes/no answer does not reasonably represent reality. 

Cheers, Peter

 

From: The Cunctator [mailto:cuncta...@gmail.com] 
Sent: 25 January 2023 17:26
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: The Endowment, again

 

It looks like what Wikimedia is saying is they gave a (typically) confusing 
response to the Italian journalists which they (in good faith) misreported.

 

Wikimedia communications would benefit from a willingness to answer yes/no 
questions with a yes or no, imho.

 

On Wed, Jan 25, 2023, 7:24 AM Andreas Kolbe  wrote:

Lodewijk,

 

The question at the top of that talk page section on Meta[1] is: 

 

"Is the money still with Tides?"

 

The answer seems to be "Yes". 

 

If so, then the next question is: 

 

If the money is still with Tides, then why did the WMF tell the Italian 
journalists that their information was incorrect and the Endowment had already 
been moved to the 501(c)(3)?

 

It seems like another case of paltering.[2] The bigger issue is that this sort 
of thing undermines community trust in everything the WMF says, especially 
about money.[3] Why didn't the WMF simply tell the journalists, as you just put 
it, Lodewijk, "No, not yet. But we are going towards that new situation"? 

 

We had two high-profile community RfCs on the English Wikipedia's Vilage Pump 
last year that came to the conclusion that the WMF puts out misleading or 
deceptive communications.[4] Half the shortlisted board candidates in last 
year's board election endorsed that view during their campaigns.[5]

 

We have a longstanding and, I believe, popular (his talk page has 670 watchers) 
English Wikipedia administrator, a former member of the Arbitration Committee, 
saying things like the following on his talk page[6] (last year, in a different 
context): 

 

"I don't doubt that the WMF is lying here—when it comes to where the money 
comes from, where it goes, and who is taking a cut along the way, it would be 
more unusual to find them being honest". 

 

"What's particularly irritating is that there's no need for the WMF to 
equivocate here and they're just doing it out of habit."

 

I believe those are fairly mainstream views in the community, based on close 
observation of the WMF's conduct. It's not healthy, and I believe the WMF 
should look at its paltering habit.

 

Andreas

 

[1] 
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Endowment#Is_the_money_still_with_Tides?

[2] https://en.wikipedia.org/wiki/Paltering

[3] See also ongoing discussions here: 
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Enterprise#Additional_members_of_the_LLC_besides_the_Wikimedia_Foundation

[4] 
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Archive_193#Review_of_English_Wikimedia_fundraising_emails
 and 
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Archive_197#RfC_on_the_banners_for_the_December_2022_fundraising_campaign

[5] 
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Community_Voting/Election_Compass/Answers

[6] https://en.wikipedia.org/w/index.php?title=User_talk:Iridescent 

 =1124517409

 

 

On Tue, Jan 24, 2023 at 9:18 PM effe iets anders  
wrote:

Hi Lane,

 

maybe I'm just reading this differently, but doesn't "we are in the process" 
typically mean "no, not yet. But we are going towards that new situation"? If 
you don't feel this answers your question, it might be beneficial to spell out 
the question a bit more explicitly. Re-reading the statement of Andreas, I 
mostly see a statement that he is confused and his question is "could someone 
please clarify this please". In Julia's response, I read a good faith effort 
(but apparently insufficient for you) to achieve just that: clarification. 

 

Best,

Lodewijk

 

On Tue, Jan 24, 2023 at 2:40 AM Lane Chance  wrote:

Fascinating, the WMF are saying they have answered the question on
Meta, yet a simple fact check, by reading the page, shows they have
not answered the obvious simple yes/no needed.

A vague reply of "We are in the process" must set off red flags for
any logical reader. The huge amount of money under scrutiny is either
controlled by Tides or it isn't. The fact that the WMF has evaded the
yes/no question several times indicates there is a problem here that
they are not prepared to confirm in public, such as using interim
"holders" or incurring significant fees. Though the fast reader might
think the answer was "yes", it does not actually say "yes", nor does
it give any fixed dates that anyone could be held accountable to, like
for example "the funds are controlled by Tides until the end of
February 2023" which would be specific, accountable and verifiable.

Happy to be confirmed wrong, with *facts* rather than more opinions
and defensive non-answers.

For some unknown reason, the WMF official reply was not included in
the email, here it is for anyone to fact 

[Wikimedia-l] Re: In memory of Holger Ellgaard

2023-01-25 Thread Peter Southwood
A real loss, but his work will remain.

Peter

 

From: Johan Jönsson [mailto:brevlis...@gmail.com] 
Sent: 25 January 2023 09:38
To: Wikimedia Mailing List
Subject: [Wikimedia-l] In memory of Holger Ellgaard

 

Holger Ellgaard – User:Holger.Ellgaard – has died.

Holger was one of the most prolific article writers on Swedish Wikipedia, 
having written thousands of articles, with a couple of hundred thousand edits 
on Swedish Wikipedia and another hundred thousand edits on Commons, where he 
had uploaded more than fifty thousand photographs since coming to the Wikimedia 
movement in the spring of 2007.

As we know, an edit count says very little in itself – myself, I have a large 
number of minor fixes and few excellent articles. Holger, on the other hand, 
wrote a large number of featured and good articles, the kind of texts the 
community wanted to highlight as its best and put on the main page for everyone 
to see.

Having spent his professional life as an architect and with a passion for 
photography, he wrote about buildings and city planning, architecture and 
infrastructure. His articles were long, well sourced and full of illustrations, 
usually his own photos. He liked to visit a place before writing about it, 
photographing it and making sure he had the pictures he wanted.

Many of his best articles were more ambitious in scope. He wrote about Swedish 
kitchen standard and the redevelopment of central Stockholm from the 1950s to 
the 1970s. He wrote about any conceivable aspect of Stockholm as a city: public 
toilets in Stockholm, traffic signals in Stockholm, emergency housing in 
Stockholm, illuminated signs in Stockholm, railroad tunnels in Stockholm and 
about so many other things.

When Wikimedia Sweden started giving out an annual award to someone who had 
contributed to free knowledge, Holger was the inaugural recipient. He felt like 
an obvious choice. Not only because of the amount of work he had put into 
writing his articles, but also his willingness to help anyone writing within 
his area of expertise.

He was a great public educator. And now he isn’t, and we’re less for his 
absence.

 

//Johan Jönsson

--

 


 

 

Virus-free. 

 www.avg.com

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MZY2RFP7DGRWQNMECGKOGA4QSCDKKPJ2/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: @Wikipedia losing opportunities in Twitter

2023-01-18 Thread Peter Southwood
A Wikipedia account should be under the control of Wikipedians, following the 
editorial policy for Wikipedia, but they could let WMF do the technical work if 
such exists.  WMF can and should run Wikimedia accounts. WMF running a 
Wikipedia account could be misrepresentation. 

Cheers,

Peter

 

From: Andreas Kolbe [mailto:jayen...@gmail.com] 
Sent: 19 January 2023 02:46
To: Wikimedia Mailing List
Cc: F. Xavier Dengra i Grau
Subject: [Wikimedia-l] Re: @Wikipedia losing opportunities in Twitter

 

Dear all,

 

The obvious question surely is: Why not let volunteers (co-)run the Wikipedia 
Twitter account? 

 

A number of Wikipedia language versions (French, Catalan, Portuguese, Basque, 
Waray, etc.) seem to have volunteer-managed Twitter accounts that are doing 
fine. If volunteers are good enough to write the encyclopedia and curate the 
main page of each language version, aren't they good enough to write (or 
suggest) the occasional tweet?

 

Andreas

 

On Wed, Jan 18, 2023 at 11:20 PM F. Xavier Dengra i Grau via Wikimedia-l 
 wrote:

Hi/Bona nit,

 

This last tweet from @Wikipedia is a good example of what some of us have been 
mentioning in this list during the past days:

 

https://twitter.com/wikipedia/status/1615756186640334848?s=46 

 =7wB7VI4gwISyFjo-X2jZvQ

 

Despite the fact that many Wikipedias have already had this new skin deployed 
since months ago as voluntary testers, not a single mention on their huge 
contribution was explained on Twitter (neither back then nor today…). We need 
to go to the 8th tweet of today's publication to read something like "The new 
features, which start rolling out on English Wikipedia today, were built in 
collaboration with Wikipedia volunteers worldwide." 

 

If this is the situation in which the main account is monopolized only to the 
English version and its news/articles, why not specifying it as "English 
Wikipedia" in the profile and in the main link?

 

Days pass by and we keep sharing to this list proofs, data and justified 
arguments (even collagues offering themselves and willing to trace a joint 
planning!), but still not a word or single thought from the Comms department. 
Disappointing, I am sad to say.

 

Kind regards/Salutacions

 

Xavier Dengra

 

El ds, 14 gen., 2023 a 09:52, Galder Gonzalez Larrañaga  
va escriure:

Egun on Boodarwun/Gnangarra,

You are righth in one thing: it is very difficult to prove a point only from 
one puntual statistic. That's why I have been tracking statistics for a long 
time, because patterns are here the most important thing. Neverthless, there is 
only one way to know if the point me and some other users in this thread are 
rising is valid: experimenting. @Wikipedia should try something: tweeting 6-7 
times a day, with varied topics, "on this day" like tweets, varying timezones 
and even curiosities about how Wikipedia works 
(https://twitter.com/depthsofwiki/status/1614045362985082881 2 million 
impressions in 9 hours). Then, after -let's say- one month, if the results 
(engagement, followers, retention) are better, it would be quite obvious that 
there's a point changing the social media strategy. If not, if engagement is 
the same, no obvious uprise in followers or RTs is visible, the current 
strategy could be validated.

 

Me, personally, I'm ready to help the Communications Team with this task, 
proposing intercultural items that could be tweeted and promoted. If they want 
help, they know where to go for it. Again, I think that following the same 
pattern is a bad communication strategy (as we can see by our own eyes) and 
trying something new could be better. Is up to the communications team to 
aknowledge this and give a try.

 

Sincerely,

Galder

 

  _  

From: Gnangarra 
Sent: Saturday, January 14, 2023 6:00 AM
To: Wikimedia Mailing List 
Subject: [Wikimedia-l] Re: @Wikipedia losing opportunities in Twitter 

 

Kaya Galder

 

The assumption that despite there being a wider audience the interests of those 
audience members is exactly the same, if that was true why have multiple 
channels.  What I am saying is that in different communities that doesnt and 
will never hold true.  Using statistics to compare the two is the issue and 
then complaining about different audience responses to the same event being 
caused by those posting to the channel. Its not the channel operators, it's the 
underlying expectation that all audiences are the same and react exactly the 
same way every time even as the audience is increasing by many orders of 
magnitude.

 

Boodarwun

 

On Sat, 14 Jan 2023 at 02:06, Galder Gonzalez Larrañaga  
wrote:

@Gnangarra: I would doubt on the idea that Pelé is not relevant to the English 
audience, as it was the most visited article by far that day 
(https://pageviews.wmcloud.org/topviews/?project=en.wikipedia.org 

[Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines for the Universal Code of Conduct

2023-01-06 Thread Peter Southwood
Thanks, Nataliia. That seems a reasonable approach. As one of the people who 
gave feedback on some areas of concern but find the document generally 
acceptable, I am pleased to know that it is being improved, and used as a 
working document.

Regards, Peter

 

From: Nataliia Tymkiv [mailto:ntym...@wikimedia.org] 
Sent: 05 January 2023 19:36
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines 
for the Universal Code of Conduct

 

Dear Chico, and Peter, dear all.

Speaking as the chair of the Wikimedia Foundation Board of Trustees, I have a 
few thoughts. First, the UCoC is being enforced now. Not only does it help 
guide the Wikimedia Foundation in its current actions (and has since it was 
adopted by resolution [1]), but multiple communities have referred to it in 
their own actions. The policy is in place already, and its enforcement by 
communities is encouraged, there is no expectation that it be delayed until the 
guidelines for globally approaching the enforcement of the policy are agreed 
upon.

You do raise a valid question about the success of the last round of votes. At 
that point in time, as at this time, staff had recommended that we, the Board, 
review any version that passed a simple majority, but such a situation was 
never a guarantee of ratification. We respected the results of the vote – if 
communities at large could not support the outcome, we would not have evaluated 
it at all – but we were interested not only in support numbers but in causes of 
concern. What we noticed last time was that concerns coalesced around a few 
specific areas, so we felt the guidelines would benefit from deeper discussion 
and exploration of those specific areas. We wanted to make sure the enforcement 
guidelines were as widely understood and supported at their launch as they 
could be and greatly appreciate the work the communities have done together 
with the volunteer-led revisions drafting committee to explore those areas.

With this next round of voting, we hope to find that the further conversations 
have led to alignment in these few challenging areas. Ideally, the guidelines 
will meet with even more support than last time. If not, if the changes have 
actually reduced support, then it might be worth considering whether those 
revisions were actually beneficial to the broader community. If this version of 
the enforcement guidelines do not exceed the level of support of the last, we 
may instead need to consider ratifying the last or some hybrid of the two or 
even further reviewing with the community certain aspects for different 
development.

No matter what happens with the enforcement guidelines vote, the UCoC is 
important to our community health. While global alignment on how to approach 
issues is being sought, we trust local communities are continuing to uphold 
this policy and other requirements of the Terms of Use to the best of their 
abilities.

 

[1] 
https://foundation.wikimedia.org/wiki/Resolution:Approval_of_a_Universal_Code_of_Conduct

 

Best regards,
antanana / Nataliia Tymkiv

Chair, Wikimedia Foundation Board of Trustees

 

NOTICE: You may have received this message outside of your normal working 
hours/days, as I usually can work more as a volunteer during weekend. You 
should not feel obligated to answer it during your days off. Thank you in 
advance!

 

 

 

On Thu, Jan 5, 2023 at 5:23 PM Peter Southwood  
wrote:

An interesting standoff. I don’t suppose anyone has analysed the potential 
losses and gains associated with each option. If that is even possible, 
considering the number of unknowns. I agree that it is taking an amazingly long 
time, and it is not obvious why.

Cheers,

Peter

 

From: Chico Venancio [mailto:chicocvenan...@gmail.com] 
Sent: 05 January 2023 16:56
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines 
for the Universal Code of Conduct

 

The heart of the matter is why are we voting? What is the threshold that will 
enact the UCoC?

> Who it would be respected by.

 

WMF and the board. We've had 3 and a half years of discussion on the UCoC and a 
majority vote to approve enforcement guidelines, and yet no functioning UCoC.

>As volunteers, if a significant part of the community sufficiently dislikes 
>the proposed UCOC, we simply lose them, and some may become vociferous 
>opponents because reasonably fixable issues were ignored. Taking longer and 
>getting it closer to right is to me a better plan. You may not care about some 
>of the issues that needed to be fixed, but some of us do.

As volunteers, if a significant part of the community sufficiently dislikes the 
status quo we simple lose them, and some may become vociferous opponents 
because reasonably fixable issues were ignored. Taking over 3 years to 
implement an Universal Code of Conduct is to me a bad plan. You may not care 
about some of the issues that 

[Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines for the Universal Code of Conduct

2023-01-05 Thread Peter Southwood
An interesting standoff. I don’t suppose anyone has analysed the potential 
losses and gains associated with each option. If that is even possible, 
considering the number of unknowns. I agree that it is taking an amazingly long 
time, and it is not obvious why.

Cheers,

Peter

 

From: Chico Venancio [mailto:chicocvenan...@gmail.com] 
Sent: 05 January 2023 16:56
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines 
for the Universal Code of Conduct

 

The heart of the matter is why are we voting? What is the threshold that will 
enact the UCoC?

> Who it would be respected by.

 

WMF and the board. We've had 3 and a half years of discussion on the UCoC and a 
majority vote to approve enforcement guidelines, and yet no functioning UCoC.

>As volunteers, if a significant part of the community sufficiently dislikes 
>the proposed UCOC, we simply lose them, and some may become vociferous 
>opponents because reasonably fixable issues were ignored. Taking longer and 
>getting it closer to right is to me a better plan. You may not care about some 
>of the issues that needed to be fixed, but some of us do.

As volunteers, if a significant part of the community sufficiently dislikes the 
status quo we simple lose them, and some may become vociferous opponents 
because reasonably fixable issues were ignored. Taking over 3 years to 
implement an Universal Code of Conduct is to me a bad plan. You may not care 
about some of the issues that needed to be fixed, but some of us do.

 

Cheers,


Chico Venancio

 

Em qui., 5 de jan. de 2023 às 11:22, Peter Southwood 
 escreveu:

It seems that sorting out problems that are pointed out during an approval 
process is not an unreasonable thing to do, as leaving them unchanged would be 
irresponsible and extremely likely to cause other problems later. Asking 
whether a vote result will be respected misses the issue of who it would be 
respected by. Can you clarify that? As volunteers, if a significant part of the 
community sufficiently dislikes the proposed UCOC, we simply lose them, and 
some may become vociferous opponents because reasonably fixable issues were 
ignored. Taking longer and getting it closer to right is to me a better plan. 
You may not care about some of the issues that needed to be fixed, but some of 
us do.

Cheers, Peter

 

From: Chico Venancio [mailto:chicocvenan...@gmail.com] 
Sent: 04 January 2023 20:48
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines 
for the Universal Code of Conduct

 

Hi Patrick,
Five months ago I wrote in the Movement Strategy forum:[1]

Could we have clear criteria for approval of the guidelines? I find it pretty 
frustrating that a vote was taken and the majority is being ignored to review a 
few points that are not even central to the functioning of the UCoC. Can we 
suspend these sections for further review and enforce the UCoC now?

The first reference I find to UCoC is in june of 2019, and I fear any 
participation in this now 3 year long process of creating a universal code of 
conduct is pointless, as goalposts can always be shifted later.

 

Could we have an answer? What is the goalpost here? Will this vote result be 
respected?

 

Kind regards,

 

[1] 
https://forum.movement-strategy.org/t/revisions-to-the-universal-code-of-conduct-ucoc-enforcement-guidelines/377/15?u=chicocvenancio



Chico Venancio 

 

Em qua., 4 de jan. de 2023 às 15:41, Patrick Earley  
escreveu:

 
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Universal_Code_of_Conduct/Revised_enforcement_guidelines/Announcement/Voting_1>
 You can find this message translated into additional languages on Meta-wiki.

Hello all,

In mid-January 2023, the  
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Universal_Code_of_Conduct/Revised_enforcement_guidelines>
 Enforcement Guidelines for the  
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Universal_Code_of_Conduct> 
Universal Code of Conduct will undergo a second community-wide ratification 
vote. [1][2] This follows  
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Universal_Code_of_Conduct/Enforcement_guidelines/Voting/Results>
 the March 2022 vote, which resulted in a majority of voters supporting the 
Enforcement Guidelines. [3] During the vote, participants helped highlight 
important community concerns. The Board’s  
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_Community_Affairs_Committee>
 Community Affairs Committee requested that these areas of concern be reviewed. 
[4]

The volunteer-led  
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Universal_Code_of_Conduct/Drafting_committee#Revisions_Committee_members>
 Revisions Committee worked hard reviewing community input and making changes. 
[5] They updated areas of concern, such as training and affirmation 
requirements, pr

[Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines for the Universal Code of Conduct

2023-01-05 Thread Peter Southwood
It seems that sorting out problems that are pointed out during an approval 
process is not an unreasonable thing to do, as leaving them unchanged would be 
irresponsible and extremely likely to cause other problems later. Asking 
whether a vote result will be respected misses the issue of who it would be 
respected by. Can you clarify that? As volunteers, if a significant part of the 
community sufficiently dislikes the proposed UCOC, we simply lose them, and 
some may become vociferous opponents because reasonably fixable issues were 
ignored. Taking longer and getting it closer to right is to me a better plan. 
You may not care about some of the issues that needed to be fixed, but some of 
us do.

Cheers, Peter

 

From: Chico Venancio [mailto:chicocvenan...@gmail.com] 
Sent: 04 January 2023 20:48
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Upcoming vote on the revised Enforcement Guidelines 
for the Universal Code of Conduct

 

Hi Patrick,
Five months ago I wrote in the Movement Strategy forum:[1]

Could we have clear criteria for approval of the guidelines? I find it pretty 
frustrating that a vote was taken and the majority is being ignored to review a 
few points that are not even central to the functioning of the UCoC. Can we 
suspend these sections for further review and enforce the UCoC now?

The first reference I find to UCoC is in june of 2019, and I fear any 
participation in this now 3 year long process of creating a universal code of 
conduct is pointless, as goalposts can always be shifted later.

 

Could we have an answer? What is the goalpost here? Will this vote result be 
respected?

 

Kind regards,

 

[1] 
https://forum.movement-strategy.org/t/revisions-to-the-universal-code-of-conduct-ucoc-enforcement-guidelines/377/15?u=chicocvenancio



Chico Venancio 

 

Em qua., 4 de jan. de 2023 às 15:41, Patrick Earley  
escreveu:

 

 You can find this message translated into additional languages on Meta-wiki.

Hello all,

In mid-January 2023, the  

 Enforcement Guidelines for the  
 
Universal Code of Conduct will undergo a second community-wide ratification 
vote. [1][2] This follows  

 the March 2022 vote, which resulted in a majority of voters supporting the 
Enforcement Guidelines. [3] During the vote, participants helped highlight 
important community concerns. The Board’s  

 Community Affairs Committee requested that these areas of concern be reviewed. 
[4]

The volunteer-led  

 Revisions Committee worked hard reviewing community input and making changes. 
[5] They updated areas of concern, such as training and affirmation 
requirements, privacy and transparency in the process, and readability and 
translatability of the document itself.

The revised Enforcement Guidelines can be viewed  

 here, and a comparison of changes can be found  

 here. [6][7]

How to vote?

Beginning January 17, 2023, voting will be open.  

 This page on Meta-wiki outlines information on how to vote using SecurePoll.

Who can vote?

The  

 eligibility requirements for this vote are the same as for the Wikimedia Board 
of Trustees elections. See the voter information page for more details about 
voter eligibility. If you are an eligible voter, you can use your Wikimedia 
account to access the voting server.

What happens after the vote?

Votes will be scrutinized by an independent group of volunteers, and the 
results will be published on Wikimedia-l, the Movement Strategy Forum, Diff and 
on Meta-wiki. Voters will again be able to vote and share concerns they have 
about the guidelines. The Board of Trustees will look at the levels of support 
and concerns raised as they look at how the Enforcement Guidelines should be 
ratified or developed further.

On behalf of the UCoC Project Team,

Patrick

-

[1], [6] Revised Enforcement Guidelines: 

[Wikimedia-l] Re: Obnoxious fundraisers again: Undismissable notice

2022-12-18 Thread Peter Southwood
You speak for yourself.
P

-Original Message-
From: Rey Bueno via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 17 December 2022 21:05
To: wikimedia-l@lists.wikimedia.org
Cc: Rey Bueno
Subject: [Wikimedia-l] Re: Obnoxious fundraisers again: Undismissable notice

Here's a proposition for the WMF. 

You can keep the banners as big and as long as you want, but in return you
must sponsor the next Arch Missions to back contents from top 10 Wikipedias
(English, Japanese, Russian, French, German, Spanish, Italian, Chinese,
Arabic, Portuguese) to Moon & beyond. Editors do not get paid from spending
so much time on Wikipedia, but at least they'll all derive some reward from
it.

Context of Arch Mission:
https://www.space.com/40598-lunar-library-wikipedia-astrobotic-moon-mission.
html
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/Z63PMAW7ICAPH7XWHMWOUA5JDPKGPTY3/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/GI3SUWMT7ICJCMZSHOPSSSRMXTNXU5ON/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Decision of WLM in Ukraine organizers not to submit photos for the international round

2022-12-14 Thread Peter Southwood
Sometimes there are no good options.

Cheers,

Peter

 

From: Коля Красный via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: Thursday, December 15, 2022 00:12
To: Wikimedia Mailing List
Cc: Коля Красный
Subject: [Wikimedia-l] Re: Decision of WLM in Ukraine organizers not to submit 
photos for the international round

 

Olga, thank you for your message, I think it's very important to know the 
insight of this decision.

And at the time when I agree with your decision to not to take responsibility 
for the risks that are (sadly still) exist for the photographers, I can not 
agree with your assumption that Wikimedians of Russia "are living normal life".

Yes, bombs are not falling onto our homes but we are having risks of other 
nature that can have same, or even worse consequences. And I'm not talking 
about mobilization that have already took few of my acquaintances, involuntary. 
I'm taking about a condition of a society when any person photographing 
anything in public can be understood by police or even by bystanders as a treat 
with a very bad result. I, personally, had a very rough conversations with 
random people on streets during my personal or even our user group photowalks. 
After the beginning of mobilization I even asked our affiliate members to 
terminate all of the photographing activities and offline events.

I'm talking about an enormous emotional pressure when authorities claim 
Wikimedia Movement as their enemy and Wikimedians as traitors and a treat to 
the "only truth". And, adding to that, some of our fellow Wikimedians are 
trying to treat us bad just because of our citizenship.

We can't get any support or appreciation from both our compatriots and people 
who share our views. We can be claimed as a treat and jailed or even killed in 
our country in any day and at the same time there are some people in the 
movement who wants us out.

Yes, what happens in Ukraine is a mess (there should be another word for that, 
but my English is not perfect, so I know only obscene synonyms) and should not 
happen anywhere and anytime. If I could do more that I've done already to stop 
that — I'd do it. But don't think that you are the only one struggling. That 
would be a bit selfish even in these damn conditions.

Cultural heritage topic was always aside of world politics and I hoped this 
time it would stay the same. Keeping in mind number of losses of Ukrainian 
heritage monuments I think that work made by Wikimedia community on 
photodocumenting them and maintenancing the database is one of the coolest 
thing humanity made so far. And all we've done in WLM along the years was 
dedicated to that. I hope that this horrible actions of a part of a Russian 
society will not intervene our productive work on that field.

--
Sorry if I've offended someone.
Nikolai Bulykin (User:Красный)
North-West Russia Wiki-Historians User Group

четверг, 15 декабря 2022г., 02:44 +06:00 от Olga Milianovych 
olga.milianov...@wikimedia.org.ua:




Hi all,

 

On behalf of the organizing team for Wiki Loves Monuments in Ukraine I’m 
writing to inform you of our decision not to submit photos for the 
international round. 

 

Traditionally, Wiki Loves Monuments in Ukraine has been one of the biggest WLM 
local contests in the world, as well as among the biggest projects supported by 
Wikimedia Ukraine.

 

This year, Ukraine and subsequently the contest has suffered from Russia’s 
full-scale invasion. Particularly, for security reasons the organizers had to 
limit submissions only to photos taken before February 24th, 2022, which is the 
date when Russia openly invaded Ukraine.

 

Despite the limitations, we managed to organize the contest in 2022 and attract 
almost 14,000 photos of Ukrainian cultural heritage from almost 300 
participants. They illustrate over 5,300 monuments, including 351 monuments 
depicted for the first time.

 

However, the local organizers will not be submitting Ukrainian photos for the 
international round because of the international organizers’ decisions to 
accept photos from Russia on the international stage. To be clear, we do not 
support this decision and had asked the international team not to accept 
Russian photos in the international round. 

 

While we fully support the spread of free knowledge in various forms, we 
believe that it is not appropriate to promote on the international level photos 
from the country that wages a brutal war against Ukraine, kills thousands of 
Ukrainians – and systematically destroys and steals Ukrainian cultural, 
architectural and archaeological monuments. 

 

Besides, Russia’s war has deprived Ukrainian photos of equal conditions in the 
competition. While daily life in Russia continues largely as normal, Ukrainian 
photographers have had to operate in extremely difficult conditions and under 
many limitations – both the formal ones imposed for security reasons and the 
overall situation in Ukraine (power blackouts, problems with 

[Wikimedia-l] Re: Long Reddit post laying out inner workings of English Wikipedia

2022-12-14 Thread Peter Southwood
Last I heard, Wikipedia is not for sale, so not much point in persuading
someone to try to buy it. Also some real competition could be good for
Wikipedia, and for that matter, good for the Wikimedia Foundation. It would
also be very interesting to see how a real challenge to English Wikipedia
would be organized. All the previous attempts have failed, often quite
dismally. If it were to work better, many of us would probably join it, if
it turns out to be a thing one could join. 
Many of us are loyal to the concept of free knowledge, not so much to the
platform it is presented on.
Cheers,
Peter

-Original Message-
From: Rey Bueno via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: Monday, December 12, 2022 19:01
To: wikimedia-l@lists.wikimedia.org
Cc: reybue...@proton.me
Subject: [Wikimedia-l] Re: Long Reddit post laying out inner workings of
English Wikipedia

The last part of the great wall of text appears to persuade him to invest in
alternatives instead of buying Wikipedia. For him Wiki is like a sole
McDonald's in a food dessert, and that the solution is to open new
"restaurants".
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/6LNO3HAMIVCEXO7PBMZGRAOG2JGGI4IW/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/VL2H4QTOIIEPIARBE34Q7Y7CLAMMTIG7/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Long Reddit post laying out inner workings of English Wikipedia

2022-12-14 Thread Peter Southwood
Bit of jumping to conclusions there. ("a lot" does not imply "all",  and
labelling things that are "fairly obvious" as an "open secret" is also a
distortion of reality )
Cheers,
Peter

-Original Message-
From: Rey Bueno via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: Monday, December 12, 2022 10:27
To: wikimedia-l@lists.wikimedia.org
Cc: reybue...@proton.me
Subject: [Wikimedia-l] Re: Long Reddit post laying out inner workings of
English Wikipedia

"A lot of it is fairly obvious"

So all the problems he described are already an open secret here, right? If
so then that's disheartening.
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/S4U5HAWKEV2PQP6DYPM72J6GO7E45T6T/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/52IUOWETXGZO3FBQR5NEHXECWKCLNYVQ/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Long Reddit post laying out inner workings of English Wikipedia

2022-12-12 Thread Peter Southwood
"Citations needed."
Not saying it is all wrong, a lot of it is fairly obvious, but some of it
is, or appears to be, somewhat biased. Could use a bit of copyediting in
places. Also, does not seem to say anything new. 
Cheers, Peter

-Original Message-
From: reybueno1--- via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 11 December 2022 19:05
To: wikimedia-l@lists.wikimedia.org
Cc: reybue...@proton.me
Subject: [Wikimedia-l] Long Reddit post laying out inner workings of English
Wikipedia

This just up in /r/trueunpopularopinion and YCombinator:

https://www.reddit.com/r/TrueUnpopularOpinion/comments/zieyyf/wikipedia_is_n
ot_so_great_and_is_overrated/


Quoted below because it was explicitly released under public domain:

You all have heard by now that Elon Musk said that Wikipedia has a "left
wing bias" when the article about Twitter Files had been suggested for
deletion. This has been received with mixed responses from liberals and
conservatives alike; the former dismissing it as "an attack on free
knowledge" and the latter cheering the move as "against censorship" and
vindication of their beliefs that Big Tech is biased against them.

True, Wikipedia is supposedly editable by anyone around the world and I had
been an on and off editor there for years mostly doing small-ish edits like
fixing typos and reverting obvious vandalism. This is done while on IP as
opposed to using accounts because I would rather that some edits (i.e.
sensitive topics like religious and political areas) not tied to my name and
identity. However, reality is far from the preferred sugar-coated
description of Wikipedia, particularly its editing community.

The editing community in overall is best described as a slightly
hierarchical and militaristic "do everything right" structure, traditionally
associated with Dell and recently Foxconn and now-defunct Theranos.
Exceptions apply in quieter and outlier areas such as local geography and
space, usually the top entry points for new users wanting to try their first
hand. There are higher tolerance of good-faith mistakes such as
point-of-view problems and using unreliable resources, which are usually
explained in detail on how to correct by them rather than a mere warning
template or even an abrupt block.

Ultimately those sub-communities which can be said as populated by
exopedians, have relatively little to no power over the wider and core
communities, mostly dominated by metapedians. A third group called
mesopedians often alternates between these inner and outer workings.
Communities can have shared topical interest which are grouped by
WikiProject, an example being WikiProject Science

I spend a lot of time casually browsing through edit wars (can be so lame at
times) like a fly on the wall, along with meta venues of Wikipedia such as
Articles for Deletion, Centralized discussion Neutral Point of View
Noticeboard, Biographical of Living Persons Noticeboard, Conflict of
Interest Noticeboard, Administrator's Noticeboard Incidents, Sockpuppet
investigations, Arbitration Committee noticeboard which is the "supreme
court" in Wikipedia community for serious behavioral and conduct disputes.
Therefore I can sum up how the editing community really functions, although
not really as extensive as you might expect because I am not a
"Wikipedioholic" with respect to inner workings.

Deletionism and inclusionism
This has been very perennial and core reasons for just about any disputes on
Wikipedia ever D Deletionists treat Wikipedia as another "regular
encyclopedia" where information has to be limited once it become very much
to be covered; like cutting out junk, while inclusionists treats Wikipedia
as a comprehensive encyclopedia not bound by papers and thus can afford to
cover as much information as it can take; one man's junk could be another
man's treasure. Personally I support the latter and often the conflict
between two editing ideologies leads to factionalism, where attempts to
understand mutual feelings and perspectives are inadequate or even none at
all.

There are no absolute standards of what defines "encyclopedic knowledge" and
"notability". Inclusionism posits that almost everything could become
valuable and encyclopedic in the future, even if they're aren't today. An
example I can think of is events, figures and stories from World War II.
Deletionism has been closely related to "academic standard kicks" and rely
on the premise that Wikipedia has to be of high standard and concise. There
are people who deem an addition of something as useful, and there are those
who think it's "trivia" or "crufty" something that is nominally discouraged
if not prohibited by Wikipedia's documentation (see this in particular,
although sometimes exceptions are applied through the spirit of "Ignoring
all rules for sake of improvement", which are frequent at entertainment and
gaming topics).

On pages, notability debates around a person subject and otherwise are
frequently the main point 

[Wikimedia-l] Re: The new Signpost is out!

2022-10-04 Thread Peter Southwood
+1

There will always be mails that some people will not be interested in. Often 
most of them. This does not mean that they are not relevant to the list. We can 
delete them without reading them if they are not relevant to us.

Cheers,

Peter

 

From: Nathan [mailto:nawr...@gmail.com] 
Sent: 03 October 2022 21:27
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: The new Signpost is out!

 

Gerard, 

 

It's a widely shared mailing list. Its members have a wide range of interests. 
As some have expressed, that includes an interest in the Signpost. Many posts 
on many topics posted to this list may not be relevant for you or other 
subscribers. That's the nature of a shared, public resource. Simply skip over 
the Signpost messages in your inbox. 

 

~Nate

 

On Mon, Oct 3, 2022 at 3:09 PM Gerard Meijssen  
wrote:

Hoi,

Be realistic. A newsletter across the Wikimedia Movement would promote existing 
newsletter that mostly in a language people do not understand. 

 

It does not change my point that I do not want to read promotions for a product 
that is not representative while it assumes that it does reflect a relevant 
opinion. An opinion that is mostly negative in its aspirations.

Thanks,

   GerardM

 

 


 

  width=

Virus-free. 

 www.avg.com

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/KW26U2TW5BLANFDRH5JQIV65F6ZBJ65I/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: The new Signpost is out!

2022-10-04 Thread Peter Southwood
Not sure how that would work.

P

 

From: Gregory Varnum [mailto:gregory.var...@gmail.com] 
Sent: 03 October 2022 22:30
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: The new Signpost is out!

 

The Meta-Wiki based tech newsletter is available in a fair number of languages. 
Perhaps a Meta based truly cross-project newsletter could utilize Meta-Wiki?s 
translation setup to avoid an English-only usage?

-greg

 

___

Sent from my iPhone - a more detailed response may be sent later.





On Oct 3, 2022, at 9:09 PM, Gerard Meijssen  wrote:

?

Hoi,

Be realistic. A newsletter across the Wikimedia Movement would promote existing 
newsletter that mostly in a language people do not understand. 

 

It does not change my point that I do not want to read promotions for a product 
that is not representative while it assumes that it does reflect a relevant 
opinion. An opinion that is mostly negative in its aspirations.

Thanks,

   GerardM

 

On Mon, 3 Oct 2022 at 20:28, Rexogamer  wrote:

It might be worth creating a unified "Newsletters across the Wikimedia 
movement" email, consisting of the Signpost and any other 
newsletters/publications produced/released by community members that month - 
are there any other "newspapers"/publications created by Wikimedia communities 
and released on a regular basis?

 

- Sophie (User:Remagoxer)

 

On Mon, 3 Oct 2022 at 19:2 3, Risker  wrote:

Hi Gerard (and everyone else) - 

 

I join with others in saying that links to other newsletters published on our 
various projects, and in various languages, would be a really valuable addition 
to this list.  Many of us would really like to learn about what different 
projects consider to be important. I'd really like to encourage that other 
newsletter links be posted on this list.  

 

Risker/Anne  

 

On Mon, 3 Oct 2022 at 07:31, Gerard Meijssen  wrote:

Hoi,

The problem with the arguments made in the Signpost is that they represent 
English Wikipedia and adhere to what some consider what the pov of Wikipedia 
should be. As a pov it is fine but I do consider it not a publication that is 
representative. As such I do not need the advertisements for its publication.

Thanks,

  

 

On Mon, 3 Oct 2022 at 06:50, WereSpielChequers  
wrote:

While the Signpost is hosted on the English Wikipedia and started as very much 
an EN Wiki venture, it aspires to be of more general interest. Looking at that 
specific issue, yes there is much that is mainly English Wikipedia focused, 
including a small contribution of mine. But some of the content, such as about 
the WMF elections is of general community interest, and at least one story is 
about Wikimedia Commons rather than Wikipedia.

 

WSC 

 




Message: 2
Date: Sat, 1 Oct 2022 16:35:35 +0200
From: Gerard Meijssen 
Subject: [Wikimedia-l] Re: The new Signpost is out!
To: Wikimedia Mailing List 
Message-ID:

Content-Type: multipart/alternative;
boundary="c55e2e05e9fa0636"

Hoi,
De Signpost is een publicatie van de Engelse Wikipedia. Waarom wordt de
Wikimedia mailing list daarmee lastig gevallen?
Vriendelijke groet,
   GerardM

On Sat, 1 Oct 2022 at 14:26, Andreas Kolbe  wrote:

 

Name: not available


End of Wikimedia-l Digest, Vol 613, Issue 1
***

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/EW26JDC3PO2J4TO4K7VODOJ7R4CI75JR/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/WGGKF3VFLEDRBQHLNHXZOA4L6ZLNJ6JK/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/OEAR5Y24T2FMU6Y4BUUHVSDPHGIFMTVP/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 

[Wikimedia-l] Re: Leadership Development Working Group is ready for community feedback!

2022-09-17 Thread Peter Southwood
I, too, would appreciate such enlightenment, Cheers, Peter

 

From: Andreas Kolbe [mailto:jayen...@gmail.com] 
Sent: 16 September 2022 20:48
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Leadership Development Working Group is ready for 
community feedback!

 

Dear Ivan,

 

I am very sorry, but I honestly don't understand what any of this is for, and 
why the WMF is spending money on defining leadership – money collected under 
the pretence that money is urgently needed to keep Wikipedia online – given 
that community feedback to this initiative to date seems to be largely negative.

 

https://meta.wikimedia.org/wiki/Talk:Leadership_Development_Working_Group

 

It is not like the world lacks definitions of leadership. Aren't we spending 
donors' money to reinvent the wheel here?

 

Could I refer back to an interesting thread Samuel Klein started a while back, 
titled "Simplifying governance processes"? 

 

https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/thread/7UVDBQTEWTR3ZNYLEP5TWAOVHF372OEL/#YRALVPPHAWMMATDUSUTZVBHG2CXOKAU6

 

To me, at least, what Samuel and others said in that thread seemed to be 
pertinent to initiatives like this one. Samuel started by saying, 

 

"Dear Board (and all), The growing complexity of governance efforts is 
defeating us. Process creep is an existential threat for projects like ours – 
it is self-perpetuating if not actively curtailed, as it filters out people who 
dislike excess process. There's a reason 'bureaucrats' and 'stewards' have 
unglamorous titles. Global governance in particular seems to be suffering from 
this now. Let's try to scale it back!"

 

He received no reply from the WMF, at least not here on this list where he 
posted. 

 

It seems to me we are spending a great deal of money to produce words – but not 
words in Wikipedia, Wiktionary, Wikisource etc., that the public enjoys and 
finds valuable, but words on Meta talking about ourselves in the best 
navel-gazing tradition.

 

Now, maybe I have this all back to front and am simply clueless ... so if 
someone feels like enlightening me, please do!

 

Best,

Andreas 

 

On Fri, Sep 16, 2022 at 4:33 PM Ivan Martínez  wrote:

TL;DR: The draft leadership definition[1] prepared by the Leadership 
Development Working Group is ready for community feedback! Please share your 
feedback on Meta[2], the feedback form[3] or the Movement Strategy Forum[4]. 
You can also directly mail us at  leadershipworkinggr...@wikimedia.org. The 
feedback will be collected till October 6, 2022.  

 

Hello everyone!

 

I hope you are aware that the Leadership Development Working Group[5] has been 
working over the past few months to formulate and find ways to nurture the 
leadership of our movement. The Leadership Development Working Group (LDWG) is 
a group of Wikimedia volunteers representing different communities, languages, 
roles, and experiences. We are pleased to inform the community that our draft 
definition of leadership is now available for community feedback. This first 
draft definition of leadership was written after months of discussion, 
learning, and sharing from our community perspective. The Wikimedia Movement, 
which is by nature diverse and distinctive in its own way, is expressly 
addressed by this definition.

 

Please consider going through the definition and letting us know what you think 
by October 6, 2022. The draft definition includes a general definition of 
leadership and subcategories that elaborate on the actions, qualities, and 
outcomes of good leadership. 

 

There are many places where you can express your ideas, suggestions, and 
comments, such as the meta talk page[2], the feedback form[3], and Movement 
Strategy Forum Post[4]. You can also directly mail us at  
 
leadershipworkinggr...@wikimedia.org. 

 

You can check if the general definition, and the subcategories align with your 
idea of leadership in the movement. You can also try finding the gaps, maybe 
some qualities of a leader or anything else are missing in the draft definition 
or you can check if the definition applies to all cultural, linguistic, 
community or other contexts of the movement and share your thoughts with us.

 

Together, let's celebrate the movement's diverse and distinctive leadership! 

 

Cheers!

 

[1]  
 
Link to the draft definition on meta 

[2]  
 
Link to meta talk page 

[3]   Link to the feedback form

[4] 

  Link to the Movement Strategy Forum post 

[5]   
Link to the meta page of LDWG


 

-- 

Iván Martínez
Voluntario - Wikimedia México A.C.
User:ProtoplasmaKid 


[Wikimedia-l] Re: Is GoogleTV violating Wikipedia's license?

2022-08-31 Thread Peter Southwood
Agree that they could shake the tree a bit. I hope you will encourage them
to do that if you make it to the board. Cheers, Peter

-Original Message-
From: Andy Mabbett [mailto:a...@pigsonthewing.org.uk] 
Sent: 30 August 2022 14:39
To: Wikimedia Mailing List
Cc: F. Xavier Dengra i Grau
Subject: [Wikimedia-l] Re: Is GoogleTV violating Wikipedia's license?

On Tue, 30 Aug 2022 at 10:18, Peter Southwood
 wrote:

> If I understand the CC-by-sa licence correctly, Wikipedia and WMF
themselves do not
> own the copyright, it is owned by the contributors who created the text.
They can take
> this up with Google,

All of the above is true.

> the WMF cannot

That is not true. The WMF cannot sue Google as a copyright holder.
However, there is nothing stopping WM from raising the issue with
Google, and gently reminding them of their obligations. Indeed, that
would probably be more effective than individual editors doing so.

-- 
Andy Mabbett
@pigsonthewing
https://pigsonthewing.org.uk
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/LZVQOHEGOFOAVKGLI52HYJ5245YVQXBY/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/FZDQVUGHATAFYYQB5H3LP4QBYAYOWHKL/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Is GoogleTV violating Wikipedia's license?

2022-08-30 Thread Peter Southwood
If I understand the CC-by-sa licence correctly, Wikipedia and WMF themselves do 
not own the copyright, it is owned by the contributors who created the text. 
They can take this up with Google, the WMF cannot. If you are one of those 
contributors you can approach Google as misusing your copyright.

Cheers,  Peter

 

From: F. Xavier Dengra i Grau via Wikimedia-l 
[mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 29 August 2022 19:00
To: Wikimedia Mailing List; le...@wikimedia.org
Cc: F. Xavier Dengra i Grau
Subject: [Wikimedia-l] Is GoogleTV violating Wikipedia's license?

 

Hi all,

 

I want to bring a legal concern here on Google's misuse of our content. It came 
up today 

  on Twitter that the GoogleTV app had linked a movie description text in 
Catalan language (which in principle it should be good news regarding language 
normalization). However, shortly after a wikipedian colleague realised that the 
text was fully taken by the Catalan Wikipedia. Once I downloaded the app by 
myself, I double-checked that Google does not specify anywhere (or at least 
that I could find minimally visible) that those lines belong to Wikipedia: 
neither the origin, the license, nor a link to the full article or to the CC 
license.

 

I'd like to recall the licensing footpage on Wikipedia (Text is available under 
the Creative Commons Attribution-ShareAlike License 3.0 

 ) and its conditions, as well as to ask others to check whether there's more 
situations like this one. It's worth noting how wrong this is to minoritised 
language Wikipedias: not only the legal issue itself, but also the lack of 
legitimate clicks and views that we end up losing, the confusion and 
misunderstandings from the readers that think this is a win by Google (the 
example I shared, with both screenshots enclosed), and even a subsequent 
chicken-and-egg situation that can lead to deleted articles by some users 
thinking that the content was stolen from Google and not actually the opposite.

 

I remember that there was a previous thread here, not so long ago, about the 
problems of Google taking over our data and therefore diminishing clicks to the 
Wikimedia projects. Considering that I am fully against the GAFAM-drift that 
the WMF is increasingly adopting by benefiting from Google in our human, 
economical and digital structures, I prefer to share it here as well -and not 
only to the legal team of the WMF (cced). 

 

Kind regards,

 

Xavier Dengra

 

 

 


 

  width=

Virus-free. 

 www.avg.com

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/PB7W2FI5L6AAWYDI37VTWD6UGUNYTFWN/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Small joy of the day: Txikipedia

2022-06-24 Thread Peter Southwood
I took a look at Vikidia, thought I could do something for them, signed up with 
an account, read what I could find of the guidance, and created an article on 
Underwater diving, following the rules as I understood them, using properly 
attributed CC-by-sa content from Simple English Wikipedia as a basic framework, 
and was busy expanding it when it was deleted without discussion by user 
Ajeje_Brazorf with the edit summary (Please don't copy from simple wikipedia}, 
and no explanation why not. If I had done that on English Wikipedia I would 
risk losing my admin bit. If that is how new users are routinely treated there 
that encyclopedia is doomed. I will not be back to waste my time there. Cheers, 
Peter

 

From: Mathias Damour [mailto:mathias.dam...@gmx.fr] 
Sent: 24 June 2022 00:00
To: wikimedia-l@lists.wikimedia.org
Subject: [Wikimedia-l] Re: Small joy of the day: Txikipedia

 

Ok, I did read your message too fast... I nevertheless know Simple English 
Wikipedia.

 

I think that SEWP was created like it is, partly by fear of creating a project 
openly directed to children, and I'm afraid it precisely make it not so 
compelling for them.

 

> The thing is, as the main English Wikipedia more specialist, and therefore 
> more complicated, we have a Simple English Wikipedia that we shouldn’t let 
> languish in the hopes of creating a children's encyclopedia out of whole 
> cloth.

 

Actually, Vikidia in english does exist, with 4,035 articles !

https://en.vikidia.org

Unfortunately, the developpment of the wikis for children is very uneven, and 
it seems hard to overcome the delay when they were launched later one than 
another or missed their launch. For exemple I know about two or three unlucky 
attempts in german before Klexikon* (and I beleive German had or has a very 
good potential for such a project - demography and cultural ground favourable 
to children participation and their freedom of information). Yet it was in 
Dutch that Wikikids was launched early and is now quite big and active.

 

They may be a way to promote a existing (or to be launched) wiki encyclopedia 
for children, to "use the momentum of Wikipedia to make it easier to discover" 
as just said Galder Gonzalez Larrañaga, but somewhat different from the way 
they chooses on the Basque Wikipedia : That would be to let appear the kid 
equivalent article in the "In other projects" section.

 

Or maybe a very active work both in promotion and gathering a substantial set 
of core articles (picking the best/most usefull, most viewed articles from 
several kids wikis and Simple English Wikipedia, translating...)

 

**

*- the original "Wikikids" proposal as a Wikimedia project was made by german 
speaking wikipedians in early 2005 : 
https://lists.wikimedia.org/pipermail/foundation-l/2005-January/015108.html 
https://meta.wikimedia.org/w/index.php?title=Wikikids=89757 but was 
chilled down by the reactions on this list...

- Grundschulwiki was launched in december 2005, it still exists but is 
restricted to works done in primary classroom and therefore is not much 
developped : 
https://grundschulwiki.zum.de/index.php?title=Hauptseite=prev=history

- a 2010 project ended as they were told to request a Simple German Wikipedia 
and then denied to open it: 
https://de.wikipedia.org/wiki/Wikipedia:Redaktion_Medizin/Projekt_Kinderleicht 
https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Simple_German_3

Meanwhile Wikikids.nl was launched in March 2006 and Vikidia in French in 
November 2006.

 

  

Envoyé: jeudi 23 juin 2022 à 21:15
De: "Neurodivergent Netizen" 
À: "Wikimedia Mailing List" 
Objet: [Wikimedia-l] Re: Small joy of the day: Txikipedia

The English Wikipedia has a “plain language” wikipedia, the Simple English 
Wikipedia. It’s targeted not only towards children, but also towards people who 
aren’t fluent in English and/or have learning disabilities. A few “internet 
hack” memes say “If you can’t understand the Wikipedia article, change en to 
simple!” Basically, the English Wikipedia community has two very 
general-to-slightly-specialist encyclopedias.

 

Unfortunately, I’ve witnessed in years past that the Simple English Wikipedias’ 
activity level was, shall we say, wanting. I hope that’s changed; I suspect 
kids would enjoy learning to research for the purpose of writing on Simple 
before moving on to the so-called “real” English Wikipedia, but that might 
require some assistance that might not always exist offline. I think Simple 
would certainly be a good place to start making Wikipedia more accessible to 
8-10 year olds.

  

From,

I dream of horses

She/her

 


 

  

On Jun 23, 2022, at 11:40 AM, Mathias Damour  wrote:

  

Hi,
  

 De: "WereSpielChequers" 

A childrens' encyclopaedia written for nine year olds would surely be very 
different than one written for thirteen year olds. And content that parents of 
fourteen year olds thought was age inappropriate in Alabama might be 

[Wikimedia-l] Re: Small joy of the day: Txikipedia

2022-06-24 Thread Peter Southwood
Yes, I find it more difficult to write for Simple English, because it
(Simple English) is not my first language and I do not think in it, and the
words I would normally use for the topics I prefer are not invented there
and have to be worked around, so it is translation a lot of the time. There
is no major obstacle other than money and contributors to creating a simple
version encyclopaedia in any other language  in a non WMF environment. 

Cheers,

Peter

 

From: Galder Gonzalez Larrañaga [mailto:galder...@hotmail.com] 
Sent: 24 June 2022 09:59
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Small joy of the day: Txikipedia

 

Just a reminder that Simple English Wikipedia exists, but there are no
Simple _ Wikipedia versions and there won't be. So that may be a
solution for English (it is not, as writing in Simple Wikipedia is way more
complex than doing at the regular one, because you must change the language)
but not for the other languages. There's where especial places for children
may work.

 

Have a good day,

Galder

  _  

From: Neurodivergent Netizen 
Sent: Friday, June 24, 2022 6:13 AM
To: Wikimedia Mailing List 
Subject: [Wikimedia-l] Re: Small joy of the day: Txikipedia 

 

I don't disagree with trying to make language more understandable in
general, though.

 

Right, but like I’m saying, we have the Simple Wikipedia already. 

 

From,

I dream of horses

She/her

 

 

 





On Jun 23, 2022, at 8:57 PM, Clover Moss 
wrote:

 

I don't disagree with trying to make language more understandable in
general, though. If there was a children's version, it might be useful for
things like math articles. I remember looking up stuff like the quadratic
formula when I was in high school, seeing way more advanced mathematics than
I was used to and just giving up that Wikipedia could be a useful resource
for that. Obviously Wikipedia isn't the end-all be-all for everything and it
shouldn't be (obviously it wasn't meant to help me with homework either),
but I do agree with the general principle expressed that WereSpielChequers
that Wikipedia should be written for a general audience and that's what
considered inappropriate is variable depending on your life circumstances. 

 

On Thu, Jun 23, 2022 at 9:57 AM WereSpielChequers
 wrote:

Hi,

 

I'm curious as to what level of reading skill you are writing this for and
also what level of understanding/adulthood. 

 

I see these as two different issues and both are likely to vary sharply
especially between different countries with very different education
systems. 

 

A childrens' encyclopaedia written for nine year olds would surely be very
different than one written for thirteen year olds. And content that parents
of fourteen year olds thought was age inappropriate in Alabama might be
thought appropriate or even bowdlerised by parents of ten year olds in
London.

 

In other words, are you sure that one single childrens' encyclopaedia is the
answer to either the problem of reading age or age appropriate content?

 

Where I think that Wikipedia could and should change re this is in our use
of jargon. To my mind a "general interest" english language encyclopaedia
should be written in plain English. I suspect other language versions have
similar issues.  Perhaps if we focussed more on this we would make it easier
for those who wish to create childrens' versions.

 

Regards

 

WSC

 

On Thu, 23 Jun 2022 at 13:03, 
wrote:

Send Wikimedia-l mailing list submissions to
wikimedia-l@lists.wikimedia.org

To subscribe or unsubscribe, please visit
 
https://lists.wikimedia.org/postorius/lists/wikimedia-l.lists.wikimedia.org/

You can reach the person managing the list at
wikimedia-l-ow...@lists.wikimedia.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wikimedia-l digest..."

Today's Topics:

   1. Re: Small joyy: Txikipedia  of the da(Neurodivergent Netizen)



--

Message: 1
Date: Wed, 22 Jun 2022 17:13:33 -0700
From: Neurodivergent Netizen 
Subject: [Wikimedia-l] Re: Small joy of the day: Txikipedia
To: Wikimedia Mailing List 
Message-ID: <8c62ada1-09ee-46ff-b27d-389b6bb3e...@gmail.com>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_9EEB7F4B-E2E5-42FB-AED5-C7C07107CEF2"

>> That wouldn't be a wise choice that WMF host such a wiki if it brings the
risk of being legaly attacked on that ground, even for bad reasons and
unsuccessfully, whereas it never happened to Vikidia in 15 years (and very
few kind of bad buzz like "look what they teach to the children").

And of course, any WMF-affiliated wiki would be more at-risk simply because
of the association with the more well-known Wikipedia.

> The document is not really public yet. :-)

I think I can wait until it’s public and proofread. :-)

From,
I dream of horses
She/her





> On Jun 22, 2022, at 1:45 PM, Ziko van Dijk  wrote:
> 
> Hello,
> At 

[Wikimedia-l] Re: Wikimedia Research Showcase June 15

2022-06-09 Thread Peter Southwood
Hi Yaroslav, 

That is what I would guess too, I was wondering if anyone had gone to the 
trouble of analysing the situation more rigorously. It seems that it might be 
less easy to get useful and reliable data on what sources are available, and 
particularly those not available, by language, which would be quite a strong 
constraint on coverage. For example, one on the biggest historical constraints 
on coverage of women in science is lack of sources, so no matter how much we 
might want to improve coverage it is just more difficult to do it, this problem 
even applies to men in some lower profile fields. and we have not yet plucked 
all the low hanging fruit, even on English Wikipedia. Sometimes it looks like 
the research also mainly goes for the low hanging fruit. After all, why 
wouldn’t they?

There is also the matter of free access vs paywalled and paper only which can 
be quite difficult if you are nowhere near a suitable library, which also puts 
Europe and North America ahead in the game. What numbers of Wikipedians would 
have access to any given source, by language and geographical distribution, 
would also be an interesting topic for analysis. All these things ae barriers 
to contribution in some fields.

Cheers, 

Peter

 

From: Yaroslav Blanter [mailto:ymb...@gmail.com] 
Sent: 09 June 2022 09:05
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Wikimedia Research Showcase June 15

 

Hi Peter,

 

from my (admittedly from more than ten years ago) experience with the Russian 
Wikipedia, articles are often translated from other language Wikipedias, with 
references just taken over and not being independently checked (perhaps it is 
checked that an online reference is still available, but not its content). I 
also see my articles on the English Wikipedia being translated to other 
languages, even when they have Dutch or Russian references which I do not 
expect the translators to be able to read. This is an anecdotal evidence though.

 

In addition, there are very few projects where the main population is 
monolingual, in almost all cases the bulk of the editors speak also a major 
language which is used like lingua franca (like Russian for the Chuvash 
Wikipedia, or perhaps Spanish for the Quechua Wikipedia). This makes the 
problem less acute.

 

Best

Yaroslav

 

On Wed, Jun 8, 2022 at 8:44 PM Peter Southwood  
wrote:

Interesting research. Maybe I just missed it, but I didn’t notice any 
discussion of relation of availability of reliable sources to coverage in 
different languages. In English Wikipedia we are not allowed to write about 
topics which are not covered by suitable sources, but there may also be more 
and a wider range of sources available in English, and English Wikipedia is 
also written by people with a wider range of languages, making more non-English 
sources available. Is there any research on comparing  this tendency in other 
languages? If there is no-one editing a Wikipedia who can read a source, no-one 
can write about its content. It can be very difficult to find sources for some 
topics, and it would be unsurprising if geographical topics in an area where a 
given language is not spoken are not covered in that language.

Cheers,

Peter

 

From: Emily Lescak [mailto:eles...@wikimedia.org] 
Sent: 08 June 2022 15:13
To: wikimedia-l@lists.wikimedia.org; analyt...@lists.wikimedia.org; 
wiki-researc...@lists.wikimedia.org
Subject: [Wikimedia-l] Wikimedia Research Showcase June 15

 

Hi all,

The next Research Showcase, Wikipedia's Languages, will be live-streamed 
Wednesday, June 15, at 4:00 AM PST/11:00 AM UTC. View your local time here 
<https://zonestamp.toolforge.org/1655290800> . 

YouTube stream: https://www.youtube.com/watch?v=AZQM1dtn3g0

You are welcome to ask questions via YouTube chat or on IRC at 
#wikimedia-research. 

This month's presentations: 

Quantifying knowledge synchronisation in the 21st century

By Jisung Yoon (Pohang University of Science and Technology)

Humans acquire and accumulate knowledge through language usage and eagerly 
exchange their knowledge for advancement. Although geographical barriers had 
previously limited communication, the emergence of information technology has 
opened new avenues for knowledge exchange. However, it is unclear which 
communication pathway is dominant in the 21st century. Here, we explore the 
dominant path of knowledge diffusion in the 21st century using Wikipedia, the 
largest communal dataset. We evaluate the similarity of shared knowledge 
between population groups, distinguished based on their language usage. When 
population groups are more engaged with each other, their knowledge structure 
is more similar, where engagement is indicated by socio-economic connections, 
such as cultural, linguistic, and historical features. Moreover, geographical 
proximity is no longer a critical requirement for knowledge dissemination. 
Furthermore, we integrate our data into a mechanistic model to 

[Wikimedia-l] Re: Wikimedia Research Showcase June 15

2022-06-08 Thread Peter Southwood
Interesting research. Maybe I just missed it, but I didn’t notice any 
discussion of relation of availability of reliable sources to coverage in 
different languages. In English Wikipedia we are not allowed to write about 
topics which are not covered by suitable sources, but there may also be more 
and a wider range of sources available in English, and English Wikipedia is 
also written by people with a wider range of languages, making more non-English 
sources available. Is there any research on comparing  this tendency in other 
languages? If there is no-one editing a Wikipedia who can read a source, no-one 
can write about its content. It can be very difficult to find sources for some 
topics, and it would be unsurprising if geographical topics in an area where a 
given language is not spoken are not covered in that language.

Cheers,

Peter

 

From: Emily Lescak [mailto:eles...@wikimedia.org] 
Sent: 08 June 2022 15:13
To: wikimedia-l@lists.wikimedia.org; analyt...@lists.wikimedia.org; 
wiki-researc...@lists.wikimedia.org
Subject: [Wikimedia-l] Wikimedia Research Showcase June 15

 

Hi all,

The next Research Showcase, Wikipedia's Languages, will be live-streamed 
Wednesday, June 15, at 4:00 AM PST/11:00 AM UTC. View your local time here 
 . 

YouTube stream: https://www.youtube.com/watch?v=AZQM1dtn3g0

You are welcome to ask questions via YouTube chat or on IRC at 
#wikimedia-research. 

This month's presentations: 

Quantifying knowledge synchronisation in the 21st century

By Jisung Yoon (Pohang University of Science and Technology)

Humans acquire and accumulate knowledge through language usage and eagerly 
exchange their knowledge for advancement. Although geographical barriers had 
previously limited communication, the emergence of information technology has 
opened new avenues for knowledge exchange. However, it is unclear which 
communication pathway is dominant in the 21st century. Here, we explore the 
dominant path of knowledge diffusion in the 21st century using Wikipedia, the 
largest communal dataset. We evaluate the similarity of shared knowledge 
between population groups, distinguished based on their language usage. When 
population groups are more engaged with each other, their knowledge structure 
is more similar, where engagement is indicated by socio-economic connections, 
such as cultural, linguistic, and historical features. Moreover, geographical 
proximity is no longer a critical requirement for knowledge dissemination. 
Furthermore, we integrate our data into a mechanistic model to better 
understand the underlying mechanism and suggest that the knowledge "Silk Road" 
of the 21st century is based online.




The Language Geography of Wikipedia

By Martin Dittus

Every language is a system of being, doing, knowing, and imagining. With over 
7,000 active languages in the world, how many languages are fully represented 
online? To answer this question, digital non-profit Whose Knowledge? initiated 
the first ever report on the State of the Internet's Languages. As part of this 
report, Martin Dittus and Mark Graham have investigated the languages of 
Wikipedia. Wikipedia began with a single English-language edition more than two 
decades ago, and now offers more than 300 language editions, which places it at 
the forefront of digital language support. However, this does not mean that 
speakers of these languages get access to the same content: Wikipedia’s 
language editions vary widely in scale. We further find that this inequality is 
also reflected in Wikipedia’s geographic coverage: not all places are captured 
in every language. Wikipedia's coverage often follows the global distribution 
of speakers of the respective language. Yet even when we account for the 
distribution of language populations, certain language communities are much 
more strongly represented on Wikipedia than others. As a consequence, we find 
that for many countries in Africa, Central and South America, and South Asia, 
most of the content about those countries is in a foreign language, often a 
European-colonial language. In other words, in many of these places, people may 
need to be able to speak a second (possibly foreign) language in order to 
access Wikipedia information about their own places. Why do we see these 
differences? And what can be done to improve things?

You can also watch our past research showcases here: 
https://www.mediawiki.org/wiki/Wikimedia_Research/ 
 Showcase

 

Emily, on behalf of the Research team

 

--

Emily Lescak (she / her)

Senior Research Community Officer

The Wikimedia Foundation

 


 

 

Virus-free.  

 www.avg.com 

 


[Wikimedia-l] Re: Fact-checking Raju Narisetti in the Indian Express

2022-06-04 Thread Peter Southwood
org/wikipedia/foundation/e/e4/Wikimedia_Foundation_2020_Form_990.pdf#page=34

[3] 
https://upload.wikimedia.org/wikipedia/foundation/1/1e/Wikimedia_Foundation_FY2020-2021_Audit_Report.pdf#page=5

[4] 
https://upload.wikimedia.org/wikipedia/foundation/e/e4/Wikimedia_Foundation_2020_Form_990.pdf#page=29

[5] 
https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2022-05-29/Opinion

[6] 
https://foundation.wikimedia.org/wiki/Resolution:Remit_of_Planned_Gifts_to_the_Wikimedia_Endowment

 

On Thu, Jun 2, 2022 at 11:39 PM Megan Hernandez  
wrote:

Hi Andreas, 

 

We have followed up to your questions on the fundraising meta talk page 
<https://meta.wikimedia.org/wiki/Talk:Fundraising#Raju_Narisetti_interview:_most_of_the_money_is_flowing_into_the_Global_South>
 . 

 

Thank you, 

 

Megan 

 

 

On Thu, Jun 2, 2022 at 6:52 PM Peter Southwood  
wrote:

This seems a reasonable request.

Cheers,

Peter

 

From: Andreas Kolbe [mailto:jayen...@gmail.com] 
Sent: 02 June 2022 15:13
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Fact-checking Raju Narisetti in the Indian Express

 

Dear all,

 

Last weekend, an interview with Raju Narisetti, titled "Wikipedia is building 
trust with transparency", was published in the Indian Express, one of the major 
daily newspapers in India.

 

For your convenience, here is an archive link for the article: 
https://archive.ph/RaCwX

 

The Indian Express link is: 
https://indianexpress.com/article/technology/tech-news-technology/raju-narisetti-interview-wikipedia-trust-transparency-7940621/

 

The article quotes Raju as saying (my emphases),

 



 

“More than 75% of the money we raise globally goes to two things. One is to 
give money back to the volunteer community so they can launch a new language. 
Two is about half of it goes to the infrastructure. You need to have databases 
and put it on the cloud and make sure it’s reliable,” he said. Although a lot 
of the money is raised in the more developed Western markets, most of it is 
actually flowing into the global south, where the growth will come in languages 
and users.

 



 

This diverged sharply from my understanding of WMF finances. So I looked at the 
records to try to fact-check these statements.

 

I found the Foundation raised $163 million in the 2020/2021 financial year.[1] 
But it actually only spent $112 million of it (69%).[1] If the WMF kept 31% of 
its revenue to itself, it obviously can't have spent "more than 75%" (i.e. over 
$120M) of the money it raised on anything. 

 

This is a trivial point. But I was even more astonished by the other statement 
in the article, that most of the money raised "is actually flowing into the 
global south". 

 

Raju was talking to an Indian audience. This article was timed to coincide with 
the start of the Indian fundraiser – Indians are currently faced with 
fundraising banners on Wikipedia as well as emails soliciting repeat 
donations.[2] So I appreciate it is a good soundbite that might motivate Indian 
citizens to reach for their purses and wallets. After all, few people in India 
feel it is their job to send financial aid to the US, right? 

 

But is this soundbite really true? 

 

To fact-check that claim, I looked at the official figures in the latest (2020) 
WMF Form 990 tax return detailing WMF spending outside the US. According to the 
Form 990 section "General Information on Activities Outside the United States", 
spending on activities outside the US amounted to a total of $20,076,181 in 
2020.[3] This means well over 80% of WMF expenditure was in the US.

 

The Form 990 also provides a breakdown by global regions, detailing the precise 
amounts the WMF spent in each region. Again, I found this paints a very 
different picture to what the Indian public has been told in the Indian Express.

 

First I added up all the amounts (Program Services, p. 29, and Grantmaking, pp. 
30–31) that were spent in Europe and North America (excluding the US). I 
arrived at a total of $14.8M – which means that 73.5% of the total spending on 
non-US activities was in these regions of the affluent north. 

 

This left only $5.3M, or about 3% of total WMF revenue in 2020/2021, for the 
entire rest of the world, which also includes countries like Saudi Arabia, 
Russia, Japan, Korea and Taiwan, which are not usually included in the Global 
South. The actual money flowing into the Global South is thus even less than 3% 
– hardly "most" of the money raised.

 

Raju mentioned the volunteers. I thought, let's leave Program Services expenses 
(which presumably would include servers and caching centres abroad) out of the 
equation and look at Grantmaking alone (pages 30 and 31 of the Form 990). 

 

The Grantmaking total for activities outside the US given in the Form 990 is 
$3,475,062.

 

Almost exactly $1.2M (35%) of that went to Europe and North America (excluding 
the US). 

 

So total grantmaking in th

[Wikimedia-l] Re: Fact-checking Raju Narisetti in the Indian Express

2022-06-02 Thread Peter Southwood
This seems a reasonable request.

Cheers,

Peter

 

From: Andreas Kolbe [mailto:jayen...@gmail.com] 
Sent: 02 June 2022 15:13
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Fact-checking Raju Narisetti in the Indian Express

 

Dear all,

 

Last weekend, an interview with Raju Narisetti, titled "Wikipedia is building 
trust with transparency", was published in the Indian Express, one of the major 
daily newspapers in India.

 

For your convenience, here is an archive link for the article: 
https://archive.ph/RaCwX

 

The Indian Express link is: 
https://indianexpress.com/article/technology/tech-news-technology/raju-narisetti-interview-wikipedia-trust-transparency-7940621/

 

The article quotes Raju as saying (my emphases),

 



 

“More than 75% of the money we raise globally goes to two things. One is to 
give money back to the volunteer community so they can launch a new language. 
Two is about half of it goes to the infrastructure. You need to have databases 
and put it on the cloud and make sure it’s reliable,” he said. Although a lot 
of the money is raised in the more developed Western markets, most of it is 
actually flowing into the global south, where the growth will come in languages 
and users.

 



 

This diverged sharply from my understanding of WMF finances. So I looked at the 
records to try to fact-check these statements.

 

I found the Foundation raised $163 million in the 2020/2021 financial year.[1] 
But it actually only spent $112 million of it (69%).[1] If the WMF kept 31% of 
its revenue to itself, it obviously can't have spent "more than 75%" (i.e. over 
$120M) of the money it raised on anything. 

 

This is a trivial point. But I was even more astonished by the other statement 
in the article, that most of the money raised "is actually flowing into the 
global south". 

 

Raju was talking to an Indian audience. This article was timed to coincide with 
the start of the Indian fundraiser – Indians are currently faced with 
fundraising banners on Wikipedia as well as emails soliciting repeat 
donations.[2] So I appreciate it is a good soundbite that might motivate Indian 
citizens to reach for their purses and wallets. After all, few people in India 
feel it is their job to send financial aid to the US, right? 

 

But is this soundbite really true? 

 

To fact-check that claim, I looked at the official figures in the latest (2020) 
WMF Form 990 tax return detailing WMF spending outside the US. According to the 
Form 990 section "General Information on Activities Outside the United States", 
spending on activities outside the US amounted to a total of $20,076,181 in 
2020.[3] This means well over 80% of WMF expenditure was in the US.

 

The Form 990 also provides a breakdown by global regions, detailing the precise 
amounts the WMF spent in each region. Again, I found this paints a very 
different picture to what the Indian public has been told in the Indian Express.

 

First I added up all the amounts (Program Services, p. 29, and Grantmaking, pp. 
30–31) that were spent in Europe and North America (excluding the US). I 
arrived at a total of $14.8M – which means that 73.5% of the total spending on 
non-US activities was in these regions of the affluent north. 

 

This left only $5.3M, or about 3% of total WMF revenue in 2020/2021, for the 
entire rest of the world, which also includes countries like Saudi Arabia, 
Russia, Japan, Korea and Taiwan, which are not usually included in the Global 
South. The actual money flowing into the Global South is thus even less than 3% 
– hardly "most" of the money raised.

 

Raju mentioned the volunteers. I thought, let's leave Program Services expenses 
(which presumably would include servers and caching centres abroad) out of the 
equation and look at Grantmaking alone (pages 30 and 31 of the Form 990). 

 

The Grantmaking total for activities outside the US given in the Form 990 is 
$3,475,062.

 

Almost exactly $1.2M (35%) of that went to Europe and North America (excluding 
the US). 

 

So total grantmaking in the entire rest of the world outside Europe and North 
America was $2.3M, or 1.4% of the money the WMF raised in 2020/2021. 

 

Again 1.4% is not "most of the money raised", by any stretch of the 
imagination. And the Global South only accounts for a part of that 1.4%.

 

Lastly, as Raju was speaking to the Indian public, I wanted to find out how 
much money the WMF actually spent on grantmaking in India. The Form 990 only 
gives grantmaking totals for "South Asia" – which along with India includes 
other major countries like Bangladesh and Pakistan. 

 

These totals are $75,198 (grants and other assistance to 22 individuals, 
certainly not rank-and-file Wikipedians, given the average amount) and $3,339 
(grants to organisations). This yields a total of $78,537 for all of South Asia.

 

I make that 0.048% of the WMF's 2020/2021 revenue. Only a part of that may have 
been spent in India. 

 

Please 

[Wikimedia-l] Re: To make apodictic articles

2022-05-19 Thread Peter Southwood
Which may never happen. Cheers, Peter

-Original Message-
From: suvratjai...@gmail.com [mailto:suvratjai...@gmail.com] 
Sent: 18 May 2022 06:30
To: wikimedia-l@lists.wikimedia.org
Subject: [Wikimedia-l] To make apodictic articles

We have to complete all stub articles in wikipedia.
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/7QT3WJ25LAYGQHTIYJIJBIVT4SZ5PWFA/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG.
https://www.avg.com

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/PEBD6LB3GEF6M5G4LGLZCHK47SLCRMIG/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Simplifying governance processes

2022-05-19 Thread Peter Southwood
+1

P

 

From: Samuel Klein [mailto:meta...@gmail.com] 
Sent: 18 May 2022 22:44
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Simplifying governance processes

 

Dear Board (and all),

 

The growing complexity of governance efforts is defeating us. Process creep 
  is an 
existential threat for projects like ours – it is self-perpetuating if not 
actively curtailed, as it filters out people who dislike excess process. 
There's a reason 'bureaucrats' and 'stewards' have unglamorous titles.

 

Global governance in particular seems to be suffering from this now. Let's try 
to scale it back!  Recent developments, all at least somewhat confusing:

 

Global Council: A three-stage vote for the drafting committee.  After 6 months 
of work in private, we know the charter will cover governance, resourcing,  
 & community.  A 
ratifiable charter by 2023 should include Council scope, then another group may 
draft an election process. Council elections would start mid-2024.

 

Conduct: Two years from first draft to realization. Custom review & revision 
process for policy, set to change ~once a year. Enforcement by another group 
(U4C), not yet defined, with an idea about annual elections for it [starting in 
2023?].

 

WMF Board: A four-stage election, with a new complex nomination template. 
Nominees evaluated by another elected 9-person Analysis Committee, followed by 
a two-stage vote.
Months of process, 16 staff facilitators.  

 

Something has to give. We don't have time for all of these to be different, 
complex affairs. 
And this complexity feels self-imposed, like trying to push spaghetti through a 
straw. 

 

~ ~ ~

Four short proposals for your consideration:

 

1. Focus discussions on the decisions we need to resolve, not on process.
We need a foundation Board & global Council for specific practical reasons. 
What challenges do they need to resolve this year?  What major issues + nuances 
are at play?

2. Make elections simple, flexible, consistent. 
Build tools and frameworks that conserve rather than soak up community time.  
Make longer processes capture proportionately detailed results. Empower a 
standing election committee.

 

3. Highlight ways people can engage with governance + prioritization, 
regionally + globally, beyond winning elections to procedural bodies. Support 
organizers + facilitators rather than hiring them out of their communities to 
facilitate on behalf of a central org.

 

4. Delegate more.  Delegate to community.  Delegate design and implementation.

Our communities excel at self-organization, and rebel against arbitrary 
mandates. Avoid language or policies that remove agency or exaggerate 
staff-community division.

 

풲♡,  SJ

 

-- 

Samuel Klein  @metasj   w:user:sj  +1 617 529 4266

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/TRFX5636NPWQ2Z4PVREVG7SNOAPPVUMW/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Are you considering running for the 2022 Wikimedia Foundation board elections?

2022-05-07 Thread Peter Southwood
Linking to a subscription article does not answer my question. Some might
consider it offensive.  Cheers, Peter

-Original Message-
From: H4CUSEG via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: Friday, May 6, 2022 15:15
To: Wikimedia Mailing List
Cc: H4CUSEG
Subject: [Wikimedia-l] Re: Are you considering running for the 2022
Wikimedia Foundation board elections?

"I hate that word so, so much." Ava DuVernay in The New York Times, January
25, 2016.
https://www.nytimes.com/2016/01/26/movies/ava-duvernay-on-hollywoods-inclusi
on-problem.html?partner=IFTTT&_r=0

Sent with ProtonMail secure email.
--- Original Message ---
On Friday, May 6th, 2022 at 7:25 AM, Peter Southwood
 wrote:


> In what way is "diverse people" offensive, and to whom? Cheers, Peter.
>
> -Original Message-
> From: H4CUSEG via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org]
> Sent: 04 May 2022 16:37
> To: Wikimedia Mailing List
> Cc: H4CUSEG
> Subject: [Wikimedia-l] Re: Are you considering running for the 2022
> Wikimedia Foundation board elections?
>
> Can we stop referring to "diverse people" please? It's offensive.
>
> Sent with ProtonMail secure email.
> --- Original Message ---
> On Wednesday, May 4th, 2022 at 3:30 AM, Lorenzo Losa ll...@wikimedia.org
>
> wrote:
>
> > Are you considering running for the Wikimedia Foundation board
> > elections? Are you unsure about that it entails, or whether it's the
> > right choice?
> > You can have a talk with a trustee (or a former trustee):
>
>
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Peer_sup
> port_for_potential_candidates
>
> > Remember that you can submit you candidacy until May 9:
>
>
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Apply_to
> _be_a_Candidate
>
> > We are looking forward a new round of skilled and diverse people to
> > join the board!
> >
> > Lorenzo
> >
> > P.S.: current and recent trustees are welcomed to add their name to the
> > list
> > ___
> > Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
>
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
>
> > Public archives at
>
>
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
> message/LW6TCCMOQGPIIVCU6DWLK4BSUZQHEQKO/
>
> > To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
>
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
> message/PNITIQUN3ULR7HNCX74N3CYMIEBEPPM3/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/IHSK76K26Q32KXG4UR5XXDGVU3ZLD2NC/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/ASGM3QX4UKYOAKZZNKM6TBWMOYCV2SH2/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/YVAOILRT2G44NGM7AZ4PBVJLUTQBS2W6/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Are you considering running for the 2022 Wikimedia Foundation board elections?

2022-05-07 Thread Peter Southwood
How do you propose that relevant  competencies be recognized, defined, or
assessed? Cheers, Peter

-Original Message-
From: H4CUSEG via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: Friday, May 6, 2022 15:52
To: Wikimedia Mailing List
Cc: H4CUSEG
Subject: [Wikimedia-l] Re: Are you considering running for the 2022
Wikimedia Foundation board elections?

Yes. We shouldn't define people by what they're not (white, cis-gendered,
male, etc.). But we should also adopt an expanded conceptualization of
"competency" that is more inclusive. What we think of as competency has been
defined by people who found their own specific skills particularly important
(and their own race better than other people's). To be inclusive means to
understand and value the competencies that people bring, in stead of
requiring that people of colour can join as long as they also have all the
"white" competencies.


Sent with ProtonMail secure email.
--- Original Message ---
On Friday, May 6th, 2022 at 2:59 AM, Lorenzo Losa 
wrote:


> On mer, 2022-05-04 at 14:36 +, H4CUSEG via Wikimedia-l wrote:
>
> > Can we stop referring to "diverse people" please? It's offensive.
>
>
> I'm sorry for that.
>
> If I understand it right - and correct me if I'm wrong - you are saying
> that calling someone a "diverse person" is labeling that person in a
> bad way. This is a fair point. Diversity relates to a multitude, not to
> an individual.
> To rephrase my sentence: we need trustees who are individually skilled
> and experienced, forming a board that is collectively diverse - that is
> able to express and create space for different perspectives and ideas.
>
> Lorenzo
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/IJHKZYD7YDC7KQNAHJRJRSLIUCYANO2Q/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/2AF725BB7LMS7EFMNHB6ITYFDXBBSW2W/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/NYWU7OLMF3M5O3JQACO4TMR4XEEDN4JS/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Are you considering running for the 2022 Wikimedia Foundation board elections?

2022-05-06 Thread Peter Southwood
In what way is "diverse people" offensive, and to whom? Cheers, Peter.

-Original Message-
From: H4CUSEG via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 04 May 2022 16:37
To: Wikimedia Mailing List
Cc: H4CUSEG
Subject: [Wikimedia-l] Re: Are you considering running for the 2022
Wikimedia Foundation board elections?

Can we stop referring to "diverse people" please? It's offensive.

Sent with ProtonMail secure email.
--- Original Message ---
On Wednesday, May 4th, 2022 at 3:30 AM, Lorenzo Losa 
wrote:


> Are you considering running for the Wikimedia Foundation board
> elections? Are you unsure about that it entails, or whether it's the
> right choice?
> You can have a talk with a trustee (or a former trustee):
>
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Peer_sup
port_for_potential_candidates
>
> Remember that you can submit you candidacy until May 9:
>
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Apply_to
_be_a_Candidate
>
> We are looking forward a new round of skilled and diverse people to
> join the board!
>
> Lorenzo
>
> P.S.: current and recent trustees are welcomed to add their name to the
> list
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/LW6TCCMOQGPIIVCU6DWLK4BSUZQHEQKO/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/PNITIQUN3ULR7HNCX74N3CYMIEBEPPM3/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG.
https://www.avg.com

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/IHSK76K26Q32KXG4UR5XXDGVU3ZLD2NC/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: Open proxies and IP blocking

2022-05-03 Thread Peter Southwood
And who will do all this tedious work? Cheers, Peter

 

From: g...@tiscali.it [mailto:g...@tiscali.it] 
Sent: 01 May 2022 20:01
To: wikimedia-l@lists.wikimedia.org
Subject: [Wikimedia-l] Open proxies and IP blocking

 

Another somewhat obvious solution: instead, or before, of blocking, make the 
edits coming from one of the (too) dangerous IPs go through a reviewal process 
before getting published; hopefully a very quick one. 
In theory this would be against the original Wikipedia ideas, but I saw that 
it's something already practiced in some cases, and anyway blocking seems 
enormously worse than requiring a review before publication. 

By the way, I now realized that the current Wikipedia is already very different 
than what I believed, and it works just because it does *not* really allow 
anyone to make edits. 
Before deciding where to go from here I'd suggest you to reflect on what's 
worse: to forbid anonymity or require reviews; I believe most normal people are 
more interested in privacy than immediate publication of edits. 

Kind regards, 
Gabriele 

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/RZ6KIYQKTYQSMFSJV6XVHSAF224Y22DC/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: [African Wikimedians] Re: Africa Knowledge Initiative (AKI) Community Engagements

2022-04-29 Thread Peter Southwood
I am encouraged that it is as many as 27000, How was this number calculated? 
Cheers, Peter (one of the 27000)

 

From: Felix Nartey [mailto:fnar...@wikimedia.org] 
Sent: 29 April 2022 15:05
To: Mailing list for African Wikimedians
Cc: Wikimedia Mailing List; Shupai Mchuchu; hlezi.mo...@wikimedia.org.za; 
tshepiso.ngal...@wikimedia.org.za
Subject: [Wikimedia-l] Re: [African Wikimedians] Re: Africa Knowledge 
Initiative (AKI) Community Engagements

 

Thanks Bobby and Douglas for your interest. Sorry, I missed the time in my 
earlier email, the details for the office hour are as follows:

 

Event: AKI Office Hour

Date: 4th May 2022

Time: 3:00pm to 4:00pm GMT+00

Link: https://wikimedia.zoom.us/j/87653338679

 

Looking forward to seeing you all soon!

 

Warmest regards,

 

On Fri, Apr 29, 2022 at 12:04 PM Douglas Scott  
wrote:

Thanks Felix. I would love to attend. What time on 4 May 2022 will the open 
office hour take place? I seem to have missed that bit.

 

Regards,


Douglas.

 

On Fri, 29 Apr 2022 at 12:42, Bobby Shabangu  wrote:

Thanks for sharing this Felix, 

 

Our chapter is definitely getting involved and we shall see you at the 4 May 
meeting. 

 

Best, 

Bobby Shabangu

 

On Fri, 29 Apr 2022 at 11:57, Felix Nartey  wrote:

More than 1 billion people live on the continent of Africa but just about 27 
thousand Africans contribute to the African story on Wikipedia. 

 

Are you ready to help put back the African narrative in the hands of its people?

 

The partnership & community programs team at the WMF is forming a partnership 
with the African Union to encourage content creation from the continent. The 
project seeks to empower Wikimedia communities on the continent by creating 
access to the network and the resources of the AU.

 

You can read more about the project in our recently published diff post 

 .[1] Please do not hesitate to contact us via campai...@wikimedia.org if you 
have further questions or join us at the AKI office hour on 4 May 2022 

  to meet partner institutions, engage and contribute to making this 
storytelling project a success! [2]

 

Best,

[1] - 
https://diff.wikimedia.org/2022/04/21/setting-our-sights-on-knowledge-equity-with-the-african-union/

[2] - https://wikimedia.zoom.us/j/87653338679

-- 

 


  

 

Felix Nartey

Senior Program Officer, Campaigns 

  Wikimedia Foundation 

 

 

___
African-Wikimedians mailing list -- african-wikimedi...@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

___
African-Wikimedians mailing list -- african-wikimedi...@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org




 

-- 

Douglas Ian Scott
司道格
Skype:  douglas0scott
South African mobile number: +27 (0)79 515 8727

___
African-Wikimedians mailing list -- african-wikimedi...@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org




 

-- 

 


  

 

Felix Nartey

Senior Program Officer, Campaigns 

  Wikimedia Foundation 

 

 

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/YCBMDD7OUDL4R37IMKYTX5E6TLLLZYWE/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Next steps: Universal Code of Conduct (UCoC) and UCoC Enforcement Guidelines

2022-04-26 Thread Peter Southwood
When someone is blocked for NOTHERE, it is judged on what they have done, we 
generally don’t care what they claim to have intended, as there is no way to 
prove or disprove such claims. Cheers, Peter

 

From: Stella Ng [mailto:s...@wikimedia.org] 
Sent: 25 April 2022 17:38
To: Wikimedia Mailing List
Cc: H4CUSEG
Subject: [Wikimedia-l] Re: Next steps: Universal Code of Conduct (UCoC) and 
UCoC Enforcement Guidelines

 

Hello Everyone,

 

I appreciate the questions and concerns regarding intent - I’m going to 
reference Jan Eissfeldt here, the Global Head of Trust and Safety, and how he 
interpreted this concern during the last CAC conversation hour on April 21st 
(https://youtu.be/3cd2FxovdXE)

 

As mentioned previously, the UCoC was created to establish a minimum set of 
guidelines for expected and unacceptable behavior. The policy was written to 
take into account two main points: intent and context. It trusts people to 
exercise the reasonable person standard - which indicates that based on a 
reasonable person’s judgment of the scenario, the personalities behind it, and 
the context of the individuals involved in, as well as any extrapolating 
information, could make a call on an enforcement action.

 

This is not a new way of working for many of our communities. For instance, 
guidelines against “Gaming the system” exist in 26 projects, most if not all of 
which refer to deliberate intention or bad faith.

 

We do not believe that the crafters of the UCoC were looking for people to 
engage in any form of law interpretation or anything complex, but instead, to 
exercise their experience using the parameters of what a reasonable person 
would be expected to tolerate in a global, intercultural environment. 

 

Regards,

Stella

 

 

On Mon, Apr 25, 2022 at 2:14 AM Peter Southwood  
wrote:

This question has been asked before, and so far no workable answer has been 
suggested. Cheers, Peter.

 

From: H4CUSEG via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 20 April 2022 19:44
To: Wikimedia Mailing List
Cc: H4CUSEG
Subject: [Wikimedia-l] Re: Next steps: Universal Code of Conduct (UCoC) and 
UCoC Enforcement Guidelines

 

Stella, how are the community members who review situations supposed to 
establish the mens rea of the accused? Intent is one of the hardest things to 
prove in criminal cases, and we're going to rely on volunteers to get it right? 
We should not look at intent at all, consider only the actual harm that 
occurred and focus on remediation, harm reduction and rehabilitation in stead 
of punishing people. 

 

Vexations

 

Sent with ProtonMail <https://protonmail.com/>  secure email. 

 

--- Original Message ---
On Tuesday, April 19th, 2022 at 2:24 PM, Stella Ng  wrote:



Hello Andreas and Todd, 

 

I am not Rosie, but I believe I can field this. 

 

First, as a reminder to all, the UCoC was created to establish a minimum set of 
guidelines for expected and unacceptable behavior. However, it does not make 
existing community policies irrelevant. Currently, communities in our global 
movement may have different policies around the disclosure of private 
information (“doxxing”), specifically taking into context what is going on on a 
day-to-day basis, as well as relationship and political dynamics (such as the 
position of power or influence) that the individuals involved could have. 
Depending on the specific context of your examples, interpretation and action 
could differ widely under those doxxing policies. 

 

What would be contextually consistent across the communities, however, is the 
UCoC. If we look specifically at section 3.1, which is what doxxing is nested 
under, what is important to note is context - specifically that if the 
information is provided or the behavior is “intended primarily to intimidate, 
outrage or upset a person, or any behaviour where this would reasonably be 
considered the most likely main outcome” (emphasis added). The next sentence 
expands further that “Behaviour can be considered harassment if it is beyond 
what a reasonable person would be expected to tolerate in a global, 
intercultural environment.” (emphasis added) The policy as written is pretty 
clear that both intent and what is often called in law the “reasonable person 
<https://en.wiktionary.org/wiki/reasonable_person#:~:text=Noun=(law)%20A%20fictional%20person%20used,due%20care%20in%20like%20circumstances.%22>
 ” test applies. This is one of the reasons that the Enforcement Guidelines are 
built around human review since application of policy will always require 
judgment. The community members who review situations will hopefully read the 
text in context within the policy and will also have experience in 
understanding the parties involved, their unique dynamics within their 
respective communities, and their own project policies on doxxing as COI, as 
they will have the experience of dealing with the day to day. 

 

However, it is likely t

[Wikimedia-l] Re: Next steps: Universal Code of Conduct (UCoC) and UCoC Enforcement Guidelines

2022-04-25 Thread Peter Southwood
This question has been asked before, and so far no workable answer has been 
suggested. Cheers, Peter.

 

From: H4CUSEG via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 20 April 2022 19:44
To: Wikimedia Mailing List
Cc: H4CUSEG
Subject: [Wikimedia-l] Re: Next steps: Universal Code of Conduct (UCoC) and 
UCoC Enforcement Guidelines

 

Stella, how are the community members who review situations supposed to 
establish the mens rea of the accused? Intent is one of the hardest things to 
prove in criminal cases, and we're going to rely on volunteers to get it right? 
We should not look at intent at all, consider only the actual harm that 
occurred and focus on remediation, harm reduction and rehabilitation in stead 
of punishing people. 

 

Vexations

 

Sent with ProtonMail   secure email. 

 

--- Original Message ---
On Tuesday, April 19th, 2022 at 2:24 PM, Stella Ng  wrote:




Hello Andreas and Todd, 

 

I am not Rosie, but I believe I can field this. 

 

First, as a reminder to all, the UCoC was created to establish a minimum set of 
guidelines for expected and unacceptable behavior. However, it does not make 
existing community policies irrelevant. Currently, communities in our global 
movement may have different policies around the disclosure of private 
information (“doxxing”), specifically taking into context what is going on on a 
day-to-day basis, as well as relationship and political dynamics (such as the 
position of power or influence) that the individuals involved could have. 
Depending on the specific context of your examples, interpretation and action 
could differ widely under those doxxing policies. 

 

What would be contextually consistent across the communities, however, is the 
UCoC. If we look specifically at section 3.1, which is what doxxing is nested 
under, what is important to note is context - specifically that if the 
information is provided or the behavior is “intended primarily to intimidate, 
outrage or upset a person, or any behaviour where this would reasonably be 
considered the most likely main outcome” (emphasis added). The next sentence 
expands further that “Behaviour can be considered harassment if it is beyond 
what a reasonable person would be expected to tolerate in a global, 
intercultural environment.” (emphasis added) The policy as written is pretty 
clear that both intent and what is often called in law the “reasonable person 

 ” test applies. This is one of the reasons that the Enforcement Guidelines are 
built around human review since application of policy will always require 
judgment. The community members who review situations will hopefully read the 
text in context within the policy and will also have experience in 
understanding the parties involved, their unique dynamics within their 
respective communities, and their own project policies on doxxing as COI, as 
they will have the experience of dealing with the day to day. 

 

However, it is likely the standards could be clarified further in the round of 
Policy review that will be conducted a year after the completion of Phase 2.

 

Regards,

Stella

 

 

On Fri, Apr 15, 2022 at 11:02 PM Todd Allen  wrote:

Actually, you're technically even breaching it saying it here, since the 
mailing list is "outside the Wikimedia projects".

 

I would agree that this needs substantial clarification, especially regarding 
both spammers and already-public information.

 

Regards,

 

Todd Allen

 

On Fri, Apr 15, 2022 at 12:02 PM Andreas Kolbe  wrote:

Dear Rosie,

 

Could you kindly also look at and clarify the following passage in the 
Universal Code of Conduct:

 

· Disclosure of personal data (Doxing): sharing other contributors' private 
information, such as name, place of employment, physical or email address 
without their explicit consent either on the Wikimedia projects or elsewhere, 
or sharing information concerning their Wikimedia activity outside the projects.

 

As written, the first part of this says that contributors must no longer state 
– on Wikipedia or elsewhere – that a particular editor appears to be working 
for a PR firm, is a congressional staffer,[1] etc.

 

The second part forbids any and all discussion of contributors' Wikimedia 
activity outside the projects. (For example, if I were to say on Twitter that 
User:Koavf has made over 2 million edits to Wikipedia, I would already be in 
breach of the code as written.)

 

Thanks,

Andreas

 

[1] https://en.wikipedia.org/wiki/Wikipedia:Congressional_staffer_edits

 

On Fri, Apr 15, 2022 at 5:09 PM Rosie Stephenson-Goodknight 
 wrote:

Hello,

 

The Community Affairs Committee of the Wikimedia Foundation Board of Trustees 
would like to thank everyone who participated in the recently concluded 
community vote on the 

[Wikimedia-l] Re: Open proxies and IP blocking

2022-04-25 Thread Peter Southwood
“the block message only shows up when I try to save the page”

That is just inexcusable. Symbolic of complete indifference to other people’s 
time wasted. Why would a new editor treated like this ever bother to try again? 
 Block message with explanation and alternatives (with links) should come up 
when the person tries to open to edit, and page should not open to edit.

 

Wikipedia, the encyclopedia that “anyone” can edit if:

*very long list of conditions that apply…

*list of hoops that you must jump through to get access…

 

Cheers, Peter

 

From: Bence Damokos [mailto:bdamo...@gmail.com] 
Sent: 20 April 2022 21:59
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Open proxies and IP blocking

 

Beyond the mentioned countries, this is also affecting those who have opted in 
to Apple’s Private Relay, which I expect will be somewhat popular/default once 
out of beta status. I myself am unable to edit for example - and half the time 
I am not bothered to workaround the issue and just give up the edit. 

 

Also, annoyingly, the block message only shows up when I try to save the page 
(at least on mobile), not when I start the edit, again, leading to unnecessary 
frustration.

 

Best regards,

Bence

On Wed, 20 Apr 2022 at 20:42, Alessandro Marchetti via Wikimedia-l 
 wrote:

Yes, it's getting frequent and not only from people in Africa. 

 

I ended up to trouble-shoot these problems by mails or direct messaging on 
Facebook more and and more frequently, maybe with simple users who just know me 
or have my contact. Sometimes it looks like sharing the duties of a sysop or a 
steward with no power. 

 

It's getting less and less clear how pros and cons are calculated exactly, but 
you just get the feeling that some users really care a lot about this policy 
and you just have to deal with the consequences, no matter how time-consuming 
it's getting.

 

A.M.

 

Il mercoledì 20 aprile 2022, 20:34:36 CEST, Amir E. Aharoni 
 ha scritto: 

 

 

I don't have a solution, but I just wanted to confirm that I agree fully with 
the description of the problem. I hear that this happens to people from 
Nigeria, Ghana, Kenya and some other countries almost every day.

 

The first time I heard about it was actually around 2018 or so, but during the 
last year it has become unbearably frequent.

 

A smarter solution is needed. I tried talking to stewards about this several 
times, and they always say something like "we know that this affects certain 
countries badly, and we know that the technology has changed since the 
mid-2000s, but we absolutely cannot allow open proxies because it would 
immediately unleash horrible vandalism on all the wikis". I'm sure they mean 
well, but this is not sustainable.


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore

 

 

‫בתאריך יום ד׳, 20 באפר׳ 2022 ב-21:21 מאת ‪Florence Devouard‏ <‪ 
 fdevou...@gmail.com‏>:

Hello friends

Short version : We need to find solutions to avoid so many africans being 
globally IP blocked due to our No Open Proxies policy.
https://meta.wikimedia.org/wiki/No_open_proxies/Unfair_blocking

 

Long version : 

I'd like to raise attention on an issue, which has been getting worse in the 
past couple of weeks/months. 

Increasing number of editors getting blocked due to the No Open Proxies policy 
[1]
In particular africans.

In February 2004, the decision was made to block open proxies on Meta and all 
other Wikimedia projects. 

According to the no open proxies policy : Publicly available proxies (including 
paid proxies) may be blocked for any period at any time. While this may affect 
legitimate users, they are not the intended targets and may freely use proxies 
until those are blocked [...]

Non-static IP addresses or hosts that are otherwise not permanent proxies 
should typically be blocked for a shorter period of time, as it is likely the 
IP address will eventually be transferred or dynamically reassigned, or the 
open proxy closed. Once closed, the IP address should be unblocked.

According to the policy page, « the Editors can be permitted to edit by way of 
an open proxy with the IP block exempt flag. This is granted on local projects 
by administrators and globally by stewards. »

 

I repeat -> ... legitimate users... may freely use proxies until those are 
blocked. the Editors can be permitted to edit by way of an open proxy with the 
IP block exempt flag <-- it is not illegal to edit using an open proxy


Most editors though... have no idea whatsoever what an open proxy is. They do 
not understand well what to do when they are blocked.

In the past few weeks, the number of African editors reporting being blocked 
due to open proxy has been VERY significantly increasing. 
New editors just as old timers.
Unexperienced editors but also staff members, president of usergroups, 
organizers of edit-a-thons 

[Wikimedia-l] Re: Next steps: Universal Code of Conduct (UCoC) and UCoC Enforcement Guidelines

2022-04-25 Thread Peter Southwood
This question has been asked before, and I have never seen a reasonably 
practicable proposal for managing the problem. Cheers, Peter

 

From: H4CUSEG via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 20 April 2022 19:44
To: Wikimedia Mailing List
Cc: H4CUSEG
Subject: [Wikimedia-l] Re: Next steps: Universal Code of Conduct (UCoC) and 
UCoC Enforcement Guidelines

 

Stella, how are the community members who review situations supposed to 
establish the mens rea of the accused? Intent is one of the hardest things to 
prove in criminal cases, and we're going to rely on volunteers to get it right? 
We should not look at intent at all, consider only the actual harm that 
occurred and focus on remediation, harm reduction and rehabilitation in stead 
of punishing people. 

 

Vexations

 

Sent with ProtonMail   secure email. 

 

--- Original Message ---
On Tuesday, April 19th, 2022 at 2:24 PM, Stella Ng  wrote:




Hello Andreas and Todd, 

 

I am not Rosie, but I believe I can field this. 

 

First, as a reminder to all, the UCoC was created to establish a minimum set of 
guidelines for expected and unacceptable behavior. However, it does not make 
existing community policies irrelevant. Currently, communities in our global 
movement may have different policies around the disclosure of private 
information (“doxxing”), specifically taking into context what is going on on a 
day-to-day basis, as well as relationship and political dynamics (such as the 
position of power or influence) that the individuals involved could have. 
Depending on the specific context of your examples, interpretation and action 
could differ widely under those doxxing policies. 

 

What would be contextually consistent across the communities, however, is the 
UCoC. If we look specifically at section 3.1, which is what doxxing is nested 
under, what is important to note is context - specifically that if the 
information is provided or the behavior is “intended primarily to intimidate, 
outrage or upset a person, or any behaviour where this would reasonably be 
considered the most likely main outcome” (emphasis added). The next sentence 
expands further that “Behaviour can be considered harassment if it is beyond 
what a reasonable person would be expected to tolerate in a global, 
intercultural environment.” (emphasis added) The policy as written is pretty 
clear that both intent and what is often called in law the “reasonable person 

 ” test applies. This is one of the reasons that the Enforcement Guidelines are 
built around human review since application of policy will always require 
judgment. The community members who review situations will hopefully read the 
text in context within the policy and will also have experience in 
understanding the parties involved, their unique dynamics within their 
respective communities, and their own project policies on doxxing as COI, as 
they will have the experience of dealing with the day to day. 

 

However, it is likely the standards could be clarified further in the round of 
Policy review that will be conducted a year after the completion of Phase 2.

 

Regards,

Stella

 

 

On Fri, Apr 15, 2022 at 11:02 PM Todd Allen  wrote:

Actually, you're technically even breaching it saying it here, since the 
mailing list is "outside the Wikimedia projects".

 

I would agree that this needs substantial clarification, especially regarding 
both spammers and already-public information.

 

Regards,

 

Todd Allen

 

On Fri, Apr 15, 2022 at 12:02 PM Andreas Kolbe  wrote:

Dear Rosie,

 

Could you kindly also look at and clarify the following passage in the 
Universal Code of Conduct:

 

· Disclosure of personal data (Doxing): sharing other contributors' private 
information, such as name, place of employment, physical or email address 
without their explicit consent either on the Wikimedia projects or elsewhere, 
or sharing information concerning their Wikimedia activity outside the projects.

 

As written, the first part of this says that contributors must no longer state 
– on Wikipedia or elsewhere – that a particular editor appears to be working 
for a PR firm, is a congressional staffer,[1] etc.

 

The second part forbids any and all discussion of contributors' Wikimedia 
activity outside the projects. (For example, if I were to say on Twitter that 
User:Koavf has made over 2 million edits to Wikipedia, I would already be in 
breach of the code as written.)

 

Thanks,

Andreas

 

[1] https://en.wikipedia.org/wiki/Wikipedia:Congressional_staffer_edits

 

On Fri, Apr 15, 2022 at 5:09 PM Rosie Stephenson-Goodknight 
 wrote:

Hello,

 

The Community Affairs Committee of the Wikimedia Foundation Board of Trustees 
would like to thank everyone who participated in the recently concluded 

[Wikimedia-l] Re: Collection / Special:Book usage

2022-04-19 Thread Peter Southwood
I used to use it, but then it broke so I stopped using it. Just one of the 
things that died out because no-one could be bothered to maintain it.  Cheers, 
Peter

 

From: Galder Gonzalez Larrañaga [mailto:galder...@hotmail.com] 
Sent: 17 April 2022 17:47
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Collection / Special:Book usage

 

No one or very few use it, because you can't save a book. I had some teachers 
in our university courses who used it to download what their students did, but 
since the WMF decided to break it, evidently they are not using it anymore. I 
repeat: it worked and it was broken in purpose. So now we have an option to 
create a book but no actual book can be created, besides printing it with 
PediaPress.

 

2022(e)ko api. 17(a) 09:59 erabiltzaileak hau idatzi du ("Amir E. Aharoni" 
):

> On Sun, Apr 17, 2022, 09:29 Strainu  wrote:
> >
> > The correct question is: does it still do anything of value?
> ‫בתאריך יום א׳, 17 באפר׳ 2022 ב-10:42 מאת ‪Jan Ainali‏ 
> <‪ainali@gmail.com‏>:
>
> Even with all output options broken it is still a decent user interface for 
> creating and organizing collections of articles.

This may well be true, but I'm wondering how much is it *actually* used. I know 
I never use it, but it's possible that thousand of other people do. If it's 
true, then everything is fine. I can't find a log of its usage, or a statistics 
page that shows how often do people use this feature.

 

It currently appears in at least two prominent places:

1. "Create a book" link in the desktop sidebar (in some wikis; I don't see it 
in the English Wikipedia, but I do see it in Swedish and Basque).

2. "Extensions used by Wikimedia - Main" group in translatewiki.net, which 
means that volunteer localizers are asked to translate it with (relatively) 
high priority.

 

If only, say, five people use it in the whole Wikimedia universe, then perhaps 
someone should consider downgrading its prominence or maybe removing it 
entirely.

 

On translatewiki, I can move it from "Extensions used by Wikimedia - Main" to 
"Extensions used by Wikimedia - Advanced" or even to "Extensions used by 
Wikimedia - Legacy", but again, before I do this, I'd like to make sure that 
it's not actually used by a lot of people.


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore

 

 

  _  


  AVG logo

This email has been checked for viruses by AVG antivirus software. 
www.avg.com   





___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/URQCEBEG5QSKLOAMOTSPKIX6ZINGFTG7/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Register for Contribuling – Conference on minority languages and free participative software

2022-04-13 Thread Peter Southwood

Thanks Remy, Natacha, That abstract was useful. Do you know of any articles on 
any Wikipedia covering the topic?  closest I can find on en: is Cultural 
hegemony


Cheers, Peter

 

From: GERBET Remy via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 13 April 2022 11:15
To: Wikimedia Mailing List
Cc: GERBET Remy
Subject: [Wikimedia-l] Re: Register for Contribuling – Conference on minority 
languages and free participative software

 

Hi Peter, :) 

Thank you Natacha for your answer. You're right. Non-hegemonic languages are 
the ones that are not associated with a country or people that imposes itself 
on other cultures or claims any kind of control over the rest of the world. So 
that would be most existing languages. I used the word non-hegemonic to imply 
that those who are interested in language diversity online would probably find 
useful people and information at this conference.

Best, 

--

Rémy Gerbet

Directeur exécutif

Executive director

  +33 1 42 36 26 24

  +33 7 84 37 91 04

-

WIKIMEDIA FRANCE
Association pour le libre partage de la connaissance
 <http://www.wikimedia.fr/> www.wikimedia.fr

 <https://www.openstreetmap.org/node/1234174880> 28 rue de Londres, 75009 PARIS

Le 2022-04-13 10:55, Natacha Rault via Wikimedia-l a écrit :

Hi, maybe this can explain a little 
https://journals.sagepub.com/doi/10.1177/1056492612444316 

 

I think basically Chinese, Russian, Arabic, Spanish, French and English can be 
categorized as hegemonic. 

 

Kind regards,

 

Nattes

 

 

 

 

Le 13 avr. 2022 à 10:24, Peter Southwood  a écrit 
:

Hi Remy,

It might help if you defined what you mean by a non-hegemonic language. I would 
not think it a term familiar to most readers, and it is poorly covered by a 
google search.

Cheers,

Peter

 

From: GERBET Remy via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 12 April 2022 13:27
To: Wikimedia Mailing List
Cc: GERBET Remy
Subject: [Wikimedia-l] Register for Contribuling – Conference on minority 
languages and free participative software

 

Dear all,

If you speak a non-hegemonic language or are interested in minority languages 
in general, please come join us on April 22 at  
<https://meta.wikimedia.org/wiki/ContribuLing_2022> ContribuLing!

Wikimedia France 
<https://www.wikimedia.fr/les-inscriptions-pour-contribuling-sont-ouvertes/>  
and Wikimedia Morocco <https://meta.wikimedia.org/wiki/Wikimedia_MA_User_Group> 
 teamed up with the INALCO <http://www.inalco.fr/en/welcome-inalco-website> , 
BULAC <https://bulac.hypotheses.org> , NTeAlan <https://ntealan.org/>  and 
Idemi Africa <https://idemi.africa/>  to put together this second yearly 
edition of the conference. The focus is on free participative software that 
help document minority languages.

We will have some projects around Wikipedia, Wikidata and Lingua Libre, of 
course, but some conferences and workshops will also introduce participants to 
tools outside the Wikimedia movement, as complementary solutions.

We will cover a vast array of languages, from Japanese, Teochew (China), 
Atikamekw (Canada), Marseillais (France) to Fong (Benin) and Tshiluba (DRC). 
Other sessions will showcase multilingual platforms that can be used for a 
family of languages or for all languages.

The event will be translated live into English for participants joining us on 
zoom.

If you are interested, please feel free to register here: 
https://framaforms.org/contribuling-2022-registration-form-1648203716 
<https://framaforms.org/contribuling-2022-registration-form-1648203716> 

 The program and further details are available on meta: 
https://meta.wikimedia.org/wiki/ContribuLing_2022/Program 
<https://meta.wikimedia.org/wiki/ContribuLing_2022/Program> 

 For any further information, please contact contribul...@framalistes.org.

Best,

--

Rémy Gerbet

Directeur exécutif

Executive director

  +33 1 42 36 26 24

  +33 7 84 37 91 04

-

WIKIMEDIA FRANCE
Association pour le libre partage de la connaissance
 <http://www.wikimedia.fr/> www.wikimedia.fr

 <https://www.openstreetmap.org/node/1234174880> 28 rue de Londres, 75009 PARIS

 


 
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
 

Virus-free.  
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/7THQTTBCDTUM5

[Wikimedia-l] Re: Register for Contribuling – Conference on minority languages and free participative software

2022-04-13 Thread Peter Southwood
Hi Remy,

It might help if you defined what you mean by a non-hegemonic language. I would 
not think it a term familiar to most readers, and it is poorly covered by a 
google search.

Cheers,

Peter

 

From: GERBET Remy via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 12 April 2022 13:27
To: Wikimedia Mailing List
Cc: GERBET Remy
Subject: [Wikimedia-l] Register for Contribuling – Conference on minority 
languages and free participative software

 

Dear all,

If you speak a non-hegemonic language or are interested in minority languages 
in general, please come join us on April 22 at  
 ContribuLing!

Wikimedia France 
  
and Wikimedia Morocco  
 teamed up with the INALCO  , 
BULAC  , NTeAlan   and 
Idemi Africa   to put together this second yearly 
edition of the conference. The focus is on free participative software that 
help document minority languages.

We will have some projects around Wikipedia, Wikidata and Lingua Libre, of 
course, but some conferences and workshops will also introduce participants to 
tools outside the Wikimedia movement, as complementary solutions.

We will cover a vast array of languages, from Japanese, Teochew (China), 
Atikamekw (Canada), Marseillais (France) to Fong (Benin) and Tshiluba (DRC). 
Other sessions will showcase multilingual platforms that can be used for a 
family of languages or for all languages.

The event will be translated live into English for participants joining us on 
zoom.

If you are interested, please feel free to register here: 
https://framaforms.org/contribuling-2022-registration-form-1648203716 
 

 The program and further details are available on meta: 
https://meta.wikimedia.org/wiki/ContribuLing_2022/Program 
 

 For any further information, please contact contribul...@framalistes.org.

Best,

--

Rémy Gerbet

Directeur exécutif

Executive director

  +33 1 42 36 26 24

  +33 7 84 37 91 04

-

WIKIMEDIA FRANCE
Association pour le libre partage de la connaissance
  www.wikimedia.fr

  28 rue de Londres, 75009 PARIS

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/7THQTTBCDTUM5NZB6XK4EJI3AFVBS4KT/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: An Open Letter to Maryana Iskander

2022-04-12 Thread Peter Southwood
I sympathise with a lot of what you say, but do you have a workable alternative 
to reliable sources as currently defined? Peter

 

From: Frederick Noronha [mailto:fredericknoro...@gmail.com] 
Sent: 11 April 2022 21:19
To: Wikimedia Mailing List
Subject: [Wikimedia-l] An Open Letter to Maryana Iskander

 

  

 

https://www.opensourceforu.com/2022/01/an-open-letter-to-maryana-iskander/


 

-- 


 April 2022  | Frederick Noronha. 784 Saligao 403511 Goa
Su Mo Tu We Th Fr Sa | M (after 2pm) +91 9822122436 Twitter @fn
  1  2 | 
 3  4  5  6  7  8  9  |   
fredericknoron...@gmail.com
10 11 12 13 14 15 16  | Books. Words. Photos. Wikipedia. Networks
17 18 19 20 21 22 23  | PHOTOS:   
https://flickr.com/photos/fn-goa/
24 25 26 27 28 29 30  | VIDEOS:   http://t.ly/58ji 


 


 

 Mailtrack

Sender notified by 
 

 Mailtrack 

12/04/22, 12:45:14 am



  

 

  

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/L2MR7GFRAQW53QSCD2RB5FYFB753MKNB/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Open letter on negating race and ethnicity as "meaningful distinctions" in the UCoC

2022-04-12 Thread Peter Southwood
Race and ethnicity have already proven to be controversial in this context, and 
will probably continue to be controversial, but maybe less so if appropriately 
defined. Anyway, those who make the decisions carry the ethical responsibility, 
even if they can avoid legal responsibility. Cheers, Peter

 

From: Benjamin Lees [mailto:emufarm...@gmail.com] 
Sent: 12 April 2022 10:36
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Open letter on negating race and ethnicity as 
"meaningful distinctions" in the UCoC

 

On Mon, Apr 11, 2022 at 1:06 AM Peter Southwood  
wrote:

Definitions of terminology makes sense in any document that is intended as an 
enforceable guide to behavior. Without them, whose definition applies? Cheers, 
Peter

 

No document defines all its terms.  It's particularly unnecessary to define 
race and ethnicity in the context of how they're used in the UCoC because the 
terms are only used in conjunction with other terms that fill in whatever gaps 
might exist even under narrow definitions.  Discussions about [[Who is a Jew?]] 
are a red herring here.

 


 
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
 

Virus-free.  
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/DFYGI5SEL6AX76YNY7F5FNKWV2IBJVOA/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Open letter on negating race and ethnicity as "meaningful distinctions" in the UCoC

2022-04-10 Thread Peter Southwood
Definitions of terminology makes sense in any document that is intended as an 
enforceable guide to behavior. Without them, whose definition applies? Cheers, 
Peter

-Original Message-
From: Lane Chance [mailto:zinkl...@gmail.com] 
Sent: Saturday, April 9, 2022 11:17
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Open letter on negating race and ethnicity as 
"meaningful distinctions" in the UCoC

It would make the UCoC easier to understand if there was a glossary on
the same page. A chosen definition of "race" or "ethnicity" being used
in the context of this policy document may not be the same as exists
in the reader's head, how they describe their own identity, or as
might be used on their local language Wikipedia. This could then be
the place to distinguish the relevance to the policy of race versus
racism.

In this thread we see stated as a fact that Jews are an ethnicity but
not a race, which could cause a big argument in its own right. See the
"Whoopi Goldberg" incident.

Lane

On Sat, 9 Apr 2022 at 01:19, Zachary T.  wrote:
>
> Hi everyone,
>
> I think there's a misinterpretation here. Saying that race and ethnicity 
> aren't meaningful distinctions among people doesn't mean that racism doesn't 
> exist. That's a lot of negatives, but the way I see it, it's just recognizing 
> that race is in fact a social construct, and thus because of that it isn't 
> truly meaningful. I would suggest using inherently meaningful to clear up the 
> confusion here, because I think that more clearly expresses the sentiment.
>
> On Fri, Apr 8, 2022 at 4:23 PM Maggie Dennis  wrote:
>>
>> Hello, Anasuya and Whose Knowledge.
>>
>>
>> (Context for those who don’t know me: I am the Vice President of Community 
>> Resilience & Sustainability, and among others I oversee the team shepherding 
>> the UCoC process.)
>>
>>
>> Thank you very much for raising this issue. Foundation staff have been 
>> discussing this as well with the same points that you have raised, and it is 
>> something we’ve been thinking about how to address.
>>
>>
>> As probably many of you know, the plan all along had been to get the UCoC 
>> policy, to get the enforcement approach, and then to see how they work 
>> together in operation. Our plan has been to review the policy and 
>> enforcement approach together a year after the ratification of Phase 2. 
>> However, we decided to prioritize a slower approach to Phase 2 to make sure 
>> it was functional out the gate especially for the functionaries and 
>> volunteers who enforce it, as a result of which the timeline we had imagined 
>> for Policy review has been considerably pushed back. If we had made our 
>> preliminary time plan, we would have started testing these out months ago. 
>> The Policy and Enforcement Guidelines would have been ripe for review 
>> sometime around November 2022.
>>
>>
>> As you all know, the vote has just concluded on the UCoC Phase 2. In the 
>> vote, community members were asked if they supported it as written or not, 
>> with the ability to provide feedback either way - with the notion that the 
>> feedback would help us focus on major blockers to the enforcement approach. 
>> I have already spoken to several members of the Board about some of the 
>> concerns that have been raised about the enforcement guidelines; we’ve 
>> spoken about this passage in the Policy, too. I know from my conversations 
>> with the Board that they want to get this done right, not just get it done - 
>> and they are very open to understanding these major blockers.
>>
>>
>> The project team is compiling a report for the Board on the challenging 
>> points surfaced during the vote. We think the enforcement guidelines are a 
>> very good first draft for the enforcement pathways, but–based on the 
>> comments we’ve seen–we are very aware there may be more work ahead before we 
>> reach a Board ratified version of those guidelines. As this passage in 
>> policy is not necessary to achieve the goal of the UCoC - which is to forbid 
>> harassment and attacks based on personal factors including race and 
>> ethnicity - our intention has been to recommend to the Board that the 
>> passage in question be reviewed simultaneously with any further Phase 2 
>> enforcement workshopping, instead of waiting for the “year in operation” 
>> review intended.
>>
>>
>> I still think it makes sense to review how the enforcement guideline and 
>> policy work together to see how they are functioning once they have a trial 
>> period. But I ALSO don’t think it makes any sense to hold off on reviewing a 
>> passage from policy that community members (including some community members 
>> who are Foundation staff) strongly agree may be actively harmful just 
>> because Phase 2 is taking longer than anticipated.
>>
>>
>> I also want to say that I have spoken to some of the individuals who were 
>> involved in writing the UCoC and understand fully that the intent of the 
>> composers was to avoid any 

[Wikimedia-l] Re: Sanctions against the Russian Federation; support for Ukrainian Wikimedians

2022-03-03 Thread Peter Southwood
Yes, that is what we are supposed to do and supposed to be good at. Cheers, 
Peter

 

From: Ilario Valdelli [mailto:valde...@gmail.com] 
Sent: 02 March 2022 10:31
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Sanctions against the Russian Federation; support 
for Ukrainian Wikimedians

 

I agree and I think that the best support is to offer a neutral and complete 
information against any kind of propaganda.

 

This is what Wikimedia can do better.

 

Kind regards

 

On Tue, 1 Mar 2022, 23:21 Valentin Nefedov,  wrote:

Thanks for your support! The best "sanctions" WMF can implement is raising 
awareness about the whole situation. For example, the promotion of Ukraine's 
Cultural Diplomacy Month 2022 
 . 
About Russian Wikipedia: unfortunately, most likely it will get banned in the 
Federation. More than 70 Russian Wikipedians wrote open letter to us on our 
village pump 

  where they condemned the invasion, so WMF might support people who signed 
this letter legally because of possible threats.

 

Best regards,

Renvoy

 

вт, 1 бер. 2022 р. о 22:57 James Heilman  пише:

I wonder if a banner raising awareness regarding the existence of offline apps 
specifically Kiwix for when communication goes down would be useful?

 

https://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile 

 =en_CA=US

 

We also have Internet in a Box, with instruction on how to build your own here

 

https://mdwiki.org/wiki/WikiProjectMed:Internet-in-a-Box

 

James

 

On Tue, Mar 1, 2022 at 2:37 PM GorillaWarfare 
 wrote:

+1 on the "what can we all do to help?" question. On the VPN topic, I suspect 
the functionary teams will be pretty open to granting IPBE for folks editing 
from that region. 
https://en.wikipedia.org/wiki/Wikipedia:IP_block_exemption#Used_for_anonymous_proxy_editing
 has details if anyone needs it.




– Molly White (GorillaWarfare)

https://en.wikipedia.org/wiki/User:GorillaWarfare

she/her

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/ZYJG2NIRGKQESE4ZRQJRZODURYDGZ55F/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org




 

-- 

James Heilman
MD, CCFP-EM, Wikipedian

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/OJBWUCGPUDA6BROQPCHVYMQQIGC2V73G/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/2VGRC3NI5GWCUMUMBBG463RZS7JREZIB/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/7SOMY3VMIF4D4H2COBAASOQ5WMPPCJBE/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Seeking community recommendations for Equity Fund grantees

2022-01-25 Thread Peter Southwood
Good points, these. I hope someone will answer them.
Cheers,
Peter

-Original Message-
From: Inductiveload [mailto:inductivel...@gmail.com] 
Sent: 26 January 2022 02:36
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Seeking community recommendations for Equity Fund
grantees



On 25 January 2022 17:11:59 GMT, Nadee Gunasena 
wrote:
> I've shared more
>information about how we'll be sharing the recommendations and making
>decisions about the grantees on Meta in response to your comment there:
>https://meta.wikimedia.org/wiki/Talk:Knowledge_Equity_Fund#Concerns.

Besides how the grants are allocated in the first place, something I do not
see on that page is the clear description of how the success of the grants
are measured and reported, auditing of expenditures and when the results are
due. 

>From the Meta page:

> The Equity Fund is focused on supporting groups outside of the movement
whose work will impact and improve knowledge equity on the Wikimedia
projects over the long term. 

Thus I imagine a good part of the results will be able to be tied to long
term changes that will be measurable as some kind of wiki engagement? If the
results are not expected to manifest "on-wiki", where and when are they
expected to manifest? Obviously, "long term" implies no final results
"soon", but responsible management means that the outcomes of interest are,
of course, known already along with a plan for follow-up analysis. 

No self-respecting organisation would spend over $7 million without even a
way to tell if the money is being spent as promised, or no way to tell if
the project is working or has lasting effects. 

For context, it's enough money to keep the servers on for years, or, as
about 50 person-years of payroll and overhead expenditure, keep a modest dev
team trucking for a decade or so. The story of what knowledge-societal good
has been done with this amount of money will be absolutely fascinating to
anyone with an interest in knowledge equity, and critical to justifying
support for similar initiatives in future. The analysis and accurate
reporting of the outcomes of these grants is at least as valuable to future
similar efforts as the grants themselves. Imagine the utterly disastrous
effect it would have if it were impossible to showcase the success: it could
undermine the whole idea of knowledge equity in general as a worthwhile
financial cause, and within the wiki movement, it would badly injure the
concept that funds donated in good faith are spent carefully.

I look forward to reading in detail about what outcomes have been selected
to be tracked, how and why that selection was made, how each grant is
expected and hoped to affect them, and when and how we may be expected to
find out how it went, both "on the ground" for the grantees and in terms of
the already-set outcomes. These are all things that must already have been
carefully documented. 

Down the road, a thorough breakdown of how it actually did go and how it can
be done better, if possible, for future rounds will be a cornerstone of
best-practice for knowledge equity initiatives for years to come.

Cheers,

--IL
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/TGZK3JNX4FLBZIIQB6GUBXL7IMPE4CV2/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG.
https://www.avg.com

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/4LDLMPMZAXEIDDBZH5P3ZUUK66YRGZQ3/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: "content was" when deleting pages - is it useful?

2022-01-17 Thread Peter Southwood
If the reason for deletion was to suppress undesirable content, why would one 
want part of it to remain viewable? Cheers, Peter

 

From: Vi to [mailto:vituzzu.w...@gmail.com] 
Sent: 17 January 2022 23:45
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: "content was" when deleting pages - is it useful?

 

On it.wiki we removed both this and "the only editor was..." which proved to be 
misleading for newcomers, e.g. "I don't think that being the sole editor is a 
valid reason for this deletion".

 

Vito

 

Il giorno lun 17 gen 2022 alle ore 15:19 Amir E. Aharoni 
 ha scritto:

Hallo!

 

There's an old MediaWiki feature: When an administrator deletes a page, a bit 
of its content is automatically added to an edit summary. This is later 
viewable in deletion logs.

 

If you edit in the English, German, or Italian Wikipedia, then you haven't 
actually seen this feature in years, because administrators in these wikis 
essentially removed it by locally blanking the system messages that make it 
work.

 

In many other wikis, however, this feature is still working.

 

Is it actually useful? Or should it perhaps be removed?

 

Here's a Phabricator task about it:

https://phabricator.wikimedia.org/T299351

 

If you have an opinion, weigh in there or here.

 

Thanks!


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/4ZONY3L5LEPO45POJ2SWTPHKFFIJ63UR/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/VSGPRXX2MQKPG7PBYZAQHSONNLQAUNWE/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: [Wikitech-l] Re: Uplifting the multimedia stack (was: Community Wishlist Survery)

2022-01-01 Thread Peter Southwood
“until a couple months ago, we didn't have backups for the media files”

How is that even possible?

Cheers, Peter

 

From: Amir Sarabadani [mailto:ladsgr...@gmail.com] 
Sent: 01 January 2022 08:42
To: Wikitech-l
Cc: Wikimedia Mailing List; Wikimedia Commons Discussion List
Subject: [Wikimedia-l] Re: [Wikitech-l] Re: Uplifting the multimedia stack 
(was: Community Wishlist Survery)

 

 

 

On Fri, Dec 31, 2021 at 12:42 AM Strainu  wrote:

> So where is the best current place to discuss scaling Commons, and all that 
> entails? 

My impression is that we don't have one. All we hear is "it needs to be 
planned", but there is no transparency on what that planning involves or when 
it actually happens.

> I'd be surprised if the bottleneck were people or budget 

The main problem I see is that we end up in this kind of situation. Scaling and 
bug fixing critical features should be part of the annual budget. Each line of 
code deployed to production wikis should have an owner and associated 
maintenance budget each year. Without this, the team will not even commit 
reviews - see the thread on wikitech a few months back where a volunteer 
programmer willing to work on Upload Wizard was basically told "We will not 
review your code. Go fork." 

 

There is "code stewardship program" and its goal is to find owners for 
components that don't have an owner (or undeploy them). Sometimes it's 
successful, sometimes it's not. I have been asking for a maintainer for 
FlaggedRevs for four years now, beta cluster is suffering from a similar 
situation, etc. etc. It takes time to find an owner for everything, to fill the 
gaps in places we don't have a team to handle those (e.g. Multimedia, you can't 
just hand over that to team responsible for security for example). More info at 
https://www.mediawiki.org/wiki/Code_stewardship_reviews


> Some examples from recent discussions  

Also improvements to the Upload Wizard. There are quite a few open items in 
Phab on this. 

+1 


I really hope you will have better luck than others with bringing this issue up 
in the priority list for next year - multimedia support is growing more 
outdated by the minute. 

Honestly, the situation is more dire than you think. For example, until a 
couple months ago, we didn't have backups for the media files. There was a live 
copy in the secondary datacenter but for example if due to a software issue, we 
lost some files, they were gone. I would like to thank Jaime Crespo for pushing 
for it and implementing the backups.

 

But I beat my drum again, it's not something you can fix overnight. I'm sure 
people are monitoring this mailing list and are aware of the problem.

 

Best


Strainu 

Pe joi, 30 decembrie 2021, Samuel Klein  a scris:
> Separate thread.  I'm not sure which list is appropriate. 
> ... but not all the way to sentience.
>
> The annual community wishlist survey (implemented by a small team, possibly 
> in isolation?) may not be the mechanism for prioritizing large changes, but 
> the latter also deserves a community-curated priority queue.  To complement 
> the staff-maintained priorities in phab ~
> For core challenges (like Commons stability and capacity), I'd be surprised 
> if the bottleneck were people or budget.  We do need a shared understanding 
> of what issues are most important and most urgent, and how to solve them. For 
> instance, a way to turn Amir's recent email about the problem (and related 
> phab tickets) into a family of persistent, implementable specs and proposals 
> and their articulated obstacles.
> An issue tracker like phab is good for tracking the progress and dependencies 
> of agreed-upon tasks, but weak for discussing what is important, what we know 
> about it, how to address it. And weak for discussing ecosystem-design issues 
> that are important and need persistent updating but don't have a simple 
> checklist of steps.
> So where is the best current place to discuss scaling Commons, and all that 
> entails?  Some examples from recent discussions (most from the wm-l thread 
> below):
> - Uploads: Support for large file uploads / Keeping bulk upload tools online
> - Video: Debugging + rolling out the videojs player
> - Formats: Adding support for CML and dozens of other common high-demand file 
> formats
> - Thumbs: Updating thumbor and librsvg
> - Search: WCQS still down, noauth option wanted for tools
> - General: Finish implementing redesign of the image table
>
> SJ
> On Wed, Dec 29, 2021 at 6:26 AM Amir Sarabadani  wrote:
>>
>> I'm not debating your note. It is very valid that we lack proper support for 
>> multimedia stack. I myself wrote a detailed rant on how broken it is [1] but 
>> three notes:
>>  - Fixing something like this takes time, you need to assign the budget for 
>> it (which means it has to be done during the annual planning) and if gets 
>> approved, you need to start it with the fiscal year (meaning July 2022) and 
>> then hire (meaning, write JD, do recruitment, 

[Wikimedia-l] Re: Community Wishlist Survey 2022 is coming. Help us and prepare

2021-12-30 Thread Peter Southwood
Is the community wishlist not for for projects run by volunteers? Volunteers do 
what they choose, employees do what they are paid for. Keeping the Wikis 
functional should be the work of employees and the WMF. 

Cheers,

Peter

 

From: Gnangarra [mailto:gnanga...@gmail.com] 
Sent: 29 December 2021 07:37
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Community Wishlist Survey 2022 is coming. Help us 
and prepare

 

Kaya


Instead of putting resources into making more tools, how about putting more 
resources into sustainability. For a large part of the last 12 months Commons 
has been unable to upload large files, bulk upload tools falling over have been 
hampering efforts to engage with GLAMs.   Every other aspect of the WMF work 
has been put on hold while reviews into the systems take place. I think it's 
time to put new development on hold or at least limit priority and capacity 
then focus efforts on updating and upgrading existing tools. If those tools 
cant be fixed, rewrite them from scratch

 

Gnangarra

 

On Wed, 29 Dec 2021 at 12:08, Szymon Grabarczuk  
wrote:

The Community Wishlist Survey 2022 
  starts in 
less than two weeks (Monday 10 January 2022, 18:00 UTC 
 ). 
We, the team organizing the Survey, need your help.

*   Translate important messages 

  and/or
*   Promote the Survey 
  among 
anyone and everyone you know who has an account on wiki. Promote the Survey on 
social media, via instant messaging apps, in other groups and chats, in your 
WikiProject, Wikimedia affiliate - wherever contributors with registered 
accounts may be.
*   You may also start thinking about ideas for technical improvements or 
even writing them down in the CWS sandbox 
 .

Why are we asking? 

*   We have improved the documentation 
 . It's 
friendlier and easier to use. This will mean little if it's only in English.
*   Thousands of volunteers haven't participated in the Survey yet. We'd 
like to improve that, too. Three years ago, 1387 people participated. Last 
year, there were 1773 of them. We hope that in the upcoming edition, there will 
be even more - if you help us with translations. Also, you are better than us 
in contacting Wikimedians outside of wikis. We have prepared some images to 
share. More to come.

What is the Community Wishlist Survey? 

 

It's an annual survey that allows contributors to the Wikimedia projects to 
propose and vote for tools and platform improvements. Long years of experience 
in editing or technical skills are not required. 

 

Thank you for your time and attention. To those who have participated in the 
Survey - many thanks for your dedication.

 

See you in January!

 


  

 

Szymon Grabarczuk (he/him)

Community Relations Specialist

Wikimedia Foundation 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/XL37Y7D6N65ZXU7W43XP5KO5HFTK2CD7/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org




 

-- 

GN.

 2021

Celebrating 20 years of Wikipedia

 

 

Wikimania: Error! Filename not specified.Error! Filename not specified.Error! 
Filename not specified.Error! Filename not specified.Error! Filename not 
specified.  
https://wikimania.wikimedia.org/wiki/User:Gnangarra

Noongarpedia: Error! Filename not specified.Error! Filename not 
specified.Error! Filename not specified.Error! Filename not specified.Error! 
Filename not specified.Error! Filename not specified. 
 
https://incubator.wikimedia.org/wiki/Wp/nys/Main_Page
My print shop: Error! Filename not specified.Error! Filename not 
specified.Error! Filename not specified.Error! Filename not specified.Error! 
Filename not specified.  
https://www.redbubble.com/people/Gnangarra/shop?asc=u

 

 


 

 

Virus-free.  

[Wikimedia-l] Re: Community Wishlist Survey 2022 is coming. Help us and prepare

2021-12-29 Thread Peter Southwood
Fair comment. If you want to keep editors, make sure they have functioning 
tools. Is this not one of the reasons WMF was originally formed?

Cheers,

Peter

 

From: DerHexer via Wikimedia-l [mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 29 December 2021 12:11
To: Wikimedia Mailing List
Cc: DerHexer
Subject: [Wikimedia-l] Re: Community Wishlist Survey 2022 is coming. Help us 
and prepare

 

I have to agree with Gnangarra: Why should keeping one of our major projects 
running require a global popularity vote? The way how the various problems on 
Commons are (not!) handled by WMF and others is not acceptable anymore. We 
don't need a poll to detect that! It's not a wish we have, it's a demand we 
make: Get Commons fixed now, as soon as possible! And I don't care who does: 
WMF, WMDE, anybody else.

 

It's nice to have additional ressources for popular community wishes but clean 
up your own backyard first!

 

Best,

DerHexer (Top 10 contributor on Commons, Commons administrator, Steward)

 

 

Am Mittwoch, 29. Dezember 2021, 10:32:22 MEZ hat Amir Sarabadani 
 Folgendes geschrieben: 

 

 

The wishlist survey is defined as:

> The Community Wishlist Survey is an annual survey that allows contributors to 
> the Wikimedia projects to propose and vote for tools and platform improvements

 

That doesn't necessarily translate into just "new tools". The community can 
wish for better support of multimedia stack and improvements on the multimedia 
platform and If it gets enough votes, I'm hopeful it'll be picked up.

 

On Wed, Dec 29, 2021 at 8:02 AM Željko Blaće  wrote:

Nice. This looks much better than before. Previously it felt so many people had 
high hopes for projects that are outside of capacities that are committed to 
this project. I feel this needs to be a super clear fact from the start and not 
ask for the global community to commit XYZ number of hours in the actions of 
promoting, translating, proposing and decision making processes when developers 
can commit far less back to the same community. Otherwise it feels like 
unbalanced work from a more holistic perspective, but this is also 
non-exceptional...no? 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/W2DTMUUD76RCBVPOJ3VGSJKPYL7V6EZF/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org



-- 

Amir (he/him)

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines  
 and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/ZSZM4BRNWV3NIQ6RH66QBFFINLKMOIKG/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/X7GPV3LXCL647SEO6PE7EOBUHG53QB3U/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: [Marketing Mail] Re: [Marketing Mail] Re: Auction at Christie's

2021-12-06 Thread Peter Southwood
Cue extended rant by somebody that the board, Foundation comms and/or legal 
staff have no authority and/or are not competent to advise on this in 1, 2, 3 
...
Cheers,
P

-Original Message-
From: Andy Mabbett [mailto:a...@pigsonthewing.org.uk] 
Sent: 06 December 2021 15:35
To: Wikimedia Mailing List
Subject: [Marketing Mail] [Wikimedia-l] Re: [Marketing Mail] Re: Auction at 
Christie's

On Mon, 6 Dec 2021 at 07:36, Peter Southwood
 wrote:
>
> Damned if you do, damned if you don’t.

Quite. As Jimmy notes in the WP:AN discussion which has already been linked to:

   I was instructed to inform the community by the Board of the WMF
and advised by
   the Foundation comms and legal staff that a post to wikimedia-l and
to my talk
   page would be the right way to do it... I can equally imagine that
if I had defied the
   board and refused to communicate with the community about it, someone would
   be getting inflamed over that.

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/RFWB4IYYPDXNSU7HHSXAILXWG325IGST/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG.
https://www.avg.com
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/JZZMIRA3LKZ2ZLS7MRIOZI2AELVVHPC3/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: [Marketing Mail] Re: Auction at Christie's

2021-12-05 Thread Peter Southwood
Damned if you do, damned if you don’t.

Cheers,

P

 

From: Adam Wight [mailto:adam.m.wi...@gmail.com] 
Sent: 03 December 2021 17:32
To: Wikimedia Mailing List
Subject: [Marketing Mail] [Wikimedia-l] Re: Auction at Christie's

 

This is a good opportunity for us to take a look at the new conflict of 
interest policies [1], in light of preventing this sort of email in the future. 
 In my opinion, the WMF Board had the right idea—this is a personal project, 
and broadcasting to a movement list gives a strong sense of capitalizing on 
fame and networks, at the expense of nudging us towards venal boosterism.

 

I'm sure this was an innocent idea and something good will be done with the 
money, but that's beside the point, we're not a forum for major donor press 
releases.  Thank you for sharing some of the thought process behind your post.

 

[1] https://meta.wikimedia.org/wiki/Conflict_of_interest_policy/2021_updates

 

On Fri, Dec 3, 2021 at 3:10 PM Jimmy Wales  wrote:

Hi all,

I am writing to let you know that I am doing an auction with Christie’s auction 
house, commencing today and closing on December 15th. 

We’re auctioning two things - the original Strawberry iMac that I used during 
the founding time period of Wikipedia, and an NFT artwork that I created to 
commemorate the earliest moment of Wikipedia.

A bit of Q

**What is an NFT?**

NFT stands for ‘non fungible token’, there is a fairly thorough article about 
it on English Wikipedia   
.

**What is this NFT exactly?**

I saw earlier in the year that Tim Berners-Lee did an NFT of “the original 
source code of the web”.   In his own words: “"I’m selling a picture that I 
made, with a Python program that I wrote myself, of what the source code would 
look like if it was stuck on the wall and signed by me.”

I thought I should try to push forward from that and so instead of just doing a 
picture (screenshot) of what Wikipedia looked like when I first installed the 
Usemod software and typed “Hello, World!” I would prefer to do something 
interactive.

The artistic concept is not just to see what Wikipedia looked like to me in 
that moment, but to relive the experience: here is this incredible vulnerable 
thing, a wiki, and you dream of it becoming an encyclopedia for the whole 
world, but will it?  Will it be taken over by vandals and trolls instantly?  
What policies will you need?  What kind of community can you attract? 

**Will any portion of the proceeds go to the WMF?**

The Wikimedia Foundation board has explicitly asked that I not pledge any funds 
to Wikimedia.  (They aren’t asking me not to donate, just not to pledge to do 
so up front.)  I am pledging to donate to “help support a variety of charities 
working in the free culture world.”  I’ll decide after we see how it goes in 
terms of what exactly I’ll do!  (Advice welcome!  I’d be interested in a 
community process to help choose.)

I’ve worked with the WMF per the board’s instructions on getting approval on 
all the marketing materials to make sure that it’s clear that this is a 
personal project of mine and not a WMF thing at all.  I believe the WMF will 
also post about that.

**What about the environmental costs of creating an NFT?**

Ethereum is moving from 'Proof of Work' to 'Proof of Stake', which requires a 
lot less energy per NFT - I’m happy to see that and hope it happens soon.

In the meantime, I’ve looked for the highest estimate of the amount of 
electricity consumed to mint an NFT.  I’ve found an estimate that the average 
NFT minting consumes 340kWh.  For scale, my friend has a Tesla Model X, and 
340kWh would charge it about 3 ½ times.  This is roughly 81.6 kg of CO2.  For 
further comparison an economy-class ticket to NYC from London generates about 
1800 kilograms of CO2. (Citation needed, and very happy for anyone with 
expertise to help me improve these calculations.)

While I generally think it is better not to generate emissions than to generate 
and offset, I also think that generating withOUT offsetting is much worse.  So 
I’ll be finding the most pessimistic estimate of the CO2 that I’ve generated 
and offset it by 5x.

** What is the estimate for the auction? **

Christie’s was unable to offer any public estimate for either the computer or 
the NFT.  I can sincerely say that I have absolutely no idea what to expect.  
Given the current state of the NFT market, I’m very hopeful that some crypto 
whale will find this irresistible, who knows though?

I’ll be around for the next 8 hours or so to answer any questions but to keep 
it all centralized, let’s keep it on my English wikipedia talk page, 
https://en.wikipedia.org/wiki/User:Jimbo_Wales  
 


Article at Christie’s website here:


[Wikimedia-l] Re: [Marketing Mail] Re: Closing the comment period for the Universal Code of Conduct Enforcement Draft Guidelines and next step

2021-11-27 Thread Peter Southwood
Fair comment. 
P

-Original Message-
From: nosebagb...@gmail.com [mailto:nosebagb...@gmail.com] 
Sent: 27 November 2021 13:04
To: wikimedia-l@lists.wikimedia.org
Subject: [Marketing Mail] [Wikimedia-l] Re: Closing the comment period for
the Universal Code of Conduct Enforcement Draft Guidelines and next step

Hello,

I would make a couple of notes here:

One is that when you say "comment period will end", that can't be of the
process. 

There are numerous open questions that we have yet to see any draft policy
text on - they can't go into the final document without chance for open
review and further revision. 

While I've heard bits about how they will be discussed, we've seen nothing
formal and nothing in writing. 

Please let me know BEFORE the 29th how that will be handled to the
community's expectations. As the inherently most controversial bits (that's
why they were open questions!) the actual next needs MORE time to review
than the aspects already there, not less. 

Yours,

Nosebagbear
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/
message/GD5CSLNTF7XBCQVCEZT7CGD7XHQ2PRIQ/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

-- 
This email has been checked for viruses by AVG.
https://www.avg.com

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/SXTXR5H2SIO7YTK74GSJX66CWC2PMWFN/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org


[Wikimedia-l] Re: [Marketing Mail] Re: License for Wikifunctions and Abstract Wikipedia

2021-11-25 Thread Peter Southwood
This is a strong argument for CC-by-sa whenever possible to push for 
verifiability and traceability. The credit is secondary, almost irrelevant 
compared to being able to track down the origins.

Cheers,

Peter

 

From: Andreas Kolbe [mailto:jayen...@gmail.com] 
Sent: 25 November 2021 14:52
To: Wikimedia Mailing List
Subject: [Marketing Mail] [Wikimedia-l] Re: License for Wikifunctions and 
Abstract Wikipedia

 

Thanks. The key question to my mind is whether abstract content and the 
resulting foreign-language text output should be CC0 (like Wikidata) or CC 
BY-SA (like Wikipedia). 

 

The difference is that with CC0, re-users do not have to credit Wikimedia or 
Wikipedia for the material they use. Voice assistants like Amazon Alexa, Apple 
Siri and Google's Assistant along with search engines like Google and Bing 
would no longer have to say that they got the material from a Wikimedia 
project. They would also be free to copyright any derivative works.

 

I think both of these results are undesirable, for reasons aptly described by 
Heather Ford in her Wikipedia@20 chapter, "The Rise of the Underdog".[1] 

 

Here is one part of the chapter that speaks to this:

 

---o0o---

 

"... Wikipedia’s facts are now increasingly extracted without credit by 
artificial intelligence processes that consume its knowledge and present it as 
objective fact.

 

"As one of most popular websites in the world, it is tempting in 2020 to see 
Wikipedia as a top dog in the world of facts, but the consumption of 
Wikipedia’s knowledge without credit introduces Wikipedia’s greatest 
existential threat to date. This is not just because of the ways in which 
third-party actors appropriate Wikipedia content and remove the links that 
might sustain the community in terms of contributions of donations and 
volunteer time. More important is that unsourced Wikipedia content threatens 
the principle of verifiability, one of the fundamental principles on which 
Wikipedia was built.

 

"Verifiability sets up a series of rights and obligations by readers and 
editors of Wikipedia to knowledge whose political and social status is 
transparent. By removing direct links to the Wikipedia article where statements 
originate from, search engines and digital assistants are removing the clues 
that readers could use to (a) evaluate the veracity of claims and (b) take 
active steps to change that information through consensus if they feel that it 
is false. Without the source of factual statements being attributed to 
Wikipedia, users will see those facts as solid, incontrovertible truth, when in 
reality they may have been extracted during a process of consensus building or 
at the moment in which the article was vandalized.

 

"Until now, platform companies have been asked to contribute to the Wikimedia 
Foundation’s annual fund-raising campaign to “give back” to what they are 
taking out of the commons.[23] 
  But 
contributions of cash will not solve what amounts to Wikipedia’s greatest 
existential threat to date. What is needed is a public campaign to reinstate 
the principle of verifiability in the content that is extracted from Wikipedia 
by platform companies. Users need to be able to understand (a) exactly where 
facts originate, (b) how stable or unstable those statements are, (c) how they 
might become involved in improving the quality of that information, and (d) the 
rules under which decisions about representation will be made.

 

"Wikipedia was once recognized as the underdog not only because it was 
underresourced but also, more importantly, because it represented the just 
fight against more powerful media who sought to limit the possibilities of 
people around the world to build knowledge products together. Today, the fight 
is a new one, and Wikipedia must adapt in order to survive.

 

"Sitting back and allowing platform companies to ingest Wikipedia’s knowledge 
and represent it as the incontrovertible truth rather than the messy and 
variable truths it actually depicts is an injustice. It is an injustice not 
only for Wikipedians but also for people around the world who use the resource 
— either directly on Wikimedia servers or indirectly via other platforms like 
search."

 

---o0o---

 

There is a lot at stake in this discussion.

 

Andreas

 

 

[1] https://hfordsa.medium.com/rise-of-the-underdog-92565503e4af

 

 

 

On Mon, Nov 22, 2021 at 9:25 PM Denny Vrandečić  
wrote:

Hello all,

Here is a conversation and decision we need to have before launch of 
Wikifunctions:

How should the contents of Abstract Wikipedia and Wikifunctions be licensed?

Since the discussion is expected to be potentially complicated, let us keep a 
single place of record for discussing this question:

https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Licensing_discussion

We would like the discussion to go on for four weeks and that we have some form 
of 

[Wikimedia-l] Re: [Marketing Mail] Re: Small gratitude to our fellow wikimedians

2021-11-09 Thread Peter Southwood
Seems a reasonable idea. Cheers, Peter

 

From: Alessandro Marchetti via Wikimedia-l 
[mailto:wikimedia-l@lists.wikimedia.org] 
Sent: 09 November 2021 14:16
To: 'Wikimedia Mailing List'
Cc: Alessandro Marchetti
Subject: [Marketing Mail] [Wikimedia-l] Re: Small gratitude to our fellow 
wikimedians

 

 

Yes, a user status/right “deceased" is IMHO important. It was also the reason 
why I expected a SUL policy to be created soon or later. I tried two or three 
time to raise the issue since 2016.

 

Now some projects block accounts, but it's not a standard process. It has to be 
fixed soon or later. At the moment, a relative can reuse an old account in 
theory on another platform, if they wish to do so. For example I find archive 
of images of my deceased partner and despite the user being blocked on a local 
wikipedia, I start to upload them on Commons in their name. Everybody has their 
way to cope with grief. Do we accept this or not?

 

Alessandro

Il martedì 9 novembre 2021, 10:17:51 CET, Geert Van Pamel  
ha scritto: 

 

 

I do find this an excellent proposal.

 

Wouldn’t it be good to also implement a user status/right “deceased” to 
identify those accounts?

 

This information could be shown to their user rights page e.g. 
https://en.wikipedia.org/wiki/Special:UserRights/Geertivp?

 

One could get a list of volunteers that are no longer amongst us via 
https://en.wikipedia.org/wiki/Special:ListUsers.

 

Geert Van Pamel

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines  
 and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/VVK2TIYRJ56RL7JB2SDBZ2VPLZLSC7L3/


To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/SB672P4RHNHF3F3E7TIDXBT56ZKQMUJ4/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: [Marketing Mail] Re: About raising money

2021-09-28 Thread Peter Southwood
I think perhaps you attribute to malice that which can be adequately explained 
by incompetence. 

Cheers,

Peter

 

From: Todd Allen [mailto:toddmal...@gmail.com] 
Sent: 28 September 2021 10:01
To: Wikimedia Mailing List
Subject: [Marketing Mail] [Wikimedia-l] Re: About raising money

 

It's not only that.

 

When the WMF uses its funds to actively act against its volunteer community 
(ACTRIAL, MEDIAVIEWER, FRAMBAN, and more lately UCOC), that raises issues 
beyond disgust. The projects we spent our time building are now actively being 
used to do things we don't want to do. It is not just that WMF is using its 
money on frivolous or useless projects (though that would be a problem), it is 
that WMF is using its funds from what we built to actively punch us in the face 
and act against us.

 

If WMF were using its funds to take trips out to Barbados for no reason, 
well--we'd probably still be irritated about that. But use our funds to 
actively stomp on our volunteer community, and ignore what they say?

 

Well that's not just disgust. That's anger, and that's what you're seeing.

 

Regards,

 

Todd Allen

 

On Sat, Sep 25, 2021 at 2:51 PM Guillaume Paumier  
wrote:

Hi,

 

(Sending this as a personal opinion, albeit one informed by my work on revenue 
strategy in the past few years.)

 

Discussions about fundraising in the Wikimedia movement often involve the same 
arguments over time. My theory, after observing and participating in those 
discussions for 15 years, is the following.

 

Objections to Wikimedia fundraising (and, more broadly, revenue generation) 
tend to stem from three main sources:

* the moral superiority of financial disinterest

* outlandish budgets and fundraising goals

* improper means used to raise money.

 

The first one is relatively simple. A significant number of us find any 
relationship between money and free knowledge viscerally disgusting. We've been 
editing as volunteers for years, devoting our free time to the advancement of 
humankind through knowledge. We have done so through countless acts of 
selflessness. Our financial disinterest is inextricably woven into our identity 
as Wikimedians. The Foundation should only raise the minimum funds required to 
"keep the lights on." Anything more is an attempt to profit from our free 
labor, and that's revolting. 

 

This is not unlike discussions of business models in the libre software 
community; we can also see those arguments surface in discussions around paid 
editing. I will leave the moral argument aside, because little can be done to 
change individual identities and moral judgments of money. But let's name them 
explicitly, in hopes that we can separate them from more fact-based arguments, 
if we are willing and able.

 

The second point of contention is how much we raise. To those of us who 
remember the early years ("May we ask y'all to chip in a few dollars so we can 
buy our second server?!"), raising $150+ million a year these days seems 
extravagant, and probably always will. The much smaller budgets from our past 
act as cognitive anchors, [1] and in comparison recent budgets appear greedily 
outsized. Instead of being outraged by the growth of the budget, we should 
instead ask ourselves how much money we really need.

 

[1] https://en.wikipedia.org/wiki/Anchoring_(cognitive_bias)

 

And the fact is that, as a movement, we need as much money as we can get to 
advance our mission. Our vision is so ambitious and expansive that it is also 
bound to be inevitably expensive. This is something that the Board understood: 
shortly after endorsing the Strategic Direction in 2017, they directed the 
Foundation to prepare to raise more funds than usual, to be able to move 
towards our collective vision for 2030. [2] My fellow members of the working 
group on Revenue Streams for movement strategy also understood the scope of the 
movement's ambitions: the first guiding question for our work was how to 
"maximize revenue for the movement". [3]

 

[2] 
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Board_noticeboard/November_2017_-_Statement_endorsing_future_resourcing_and_direction_of_the_organization

[3] 
https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Working_Groups/Revenue_Streams#Guiding_Questions

 

People who attended the meeting of strategy working groups in Berlin in early 
2018 might remember a thought exercise led by the Revenue Streams group. In it, 
we estimated that coming closer to our vision would probably require an annual 
budget for the movement in the vicinity of a billion dollars. There is nothing 
intrinsically outrageous about that amount, as long as the money advances the 
mission efficiently and equitably. The International Committee of the Red Cross 
had a global budget of $1.6 billion in 2016.


And that's the heart of the argument about fundraising goals; it's less about 
how much we raise, and more about what we spend it on. Moral argument aside, 

[Wikimedia-l] Re: Wikipedia issues in UNDARK.org #Opinion article to check...

2021-08-30 Thread Peter Southwood
Are these “facts of the matter” available for evidence focused rational 
consideration?

Cheers,

Peter

 

From: Mike Godwin [mailto:mnemo...@gmail.com] 
Sent: 30 August 2021 02:30
To: Andreas Kolbe
Cc: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Wikipedia issues in UNDARK.org #Opinion article to 
check...

 

Andreas writes

 

On Mon, Aug 23, 2021 at 11:12 AM Andreas Kolbe  wrote:

But unless I am totally misreading you, your attitude sounds a lot like "Why 
should anyone care (or have cared) about Croatian and all these other languages 
spoken in some countries at the other end of the world?" If that does reflect 
your sentiment, then your mindset seems very much out of tune with WMF thought 
today.

 

The most generous assessment of this gloss is that you are, in fact, totally 
misreading me. The less generous assessments I leave to the rhetorically 
inclined reader.  

 

I am not sure you are actually interested in an answer here, but what I did do, 
for what it's worth, was to make sure that the WP Signpost and WP Kurier 
covered the story when it first broke, mention it repeatedly over the years in 
my writing on WO and in the Signpost, as well as in correspondence with 
journalists and academics, and submit the aforementioned idea to the WMF – to 
have experts review human rights topics' coverage in Wikipedia language 
versions that may be subject to undue political influence, and publicly report 
the results. I think that's about all you could have reasonably expected me to 
have done here.

 

I also think it is reasonable to expect you not to default to presuming things 
about the motives of WMF personnel in the absence of evidence. But that's 
me--I'm evidence-focused. 

 

The fact of the matter is that for about a decade, one of Wikipedia's top-50 
language versions promoted extremist content, with the WMF's full knowledge. 
That is Not A Good Thing, whether you work for the WMF or not, and you have 
given no discernible reason why what was done this year could not have been 
done years ago, when the WMF was first made aware of the situation.

 

Your characterization of "the fact of the matter" is morally confused. To wit, 
you want to imply that if some people at WMF knew something about what was 
happening in the Croatian Wikipedia, it follows that WMF institutionally 
decided, as a matter of policy, not to do what you wish they might have done. 
You do not have "the facts of the matter" that demonstrate such an 
institutional decision took place.

 

Once again, you default to moral condemnation, and it seems self-evident that 
you're doing so because it's cheaper and easier than understanding what might 
actually have happened.

 

Mike Godwin

 

 

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/WJV5JTVLXWRJR47IM37FSPBZLA5AT6S7/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Wikipedia issues in UNDARK.org #Opinion article to check...

2021-08-18 Thread Peter Southwood
Gerard,

With whom do you beg to differ?

P

 

From: Gerard Meijssen [mailto:gerard.meijs...@gmail.com] 
Sent: 17 August 2021 09:32
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Wikipedia issues in UNDARK.org #Opinion article to 
check...

 

Hoi,

I beg to differ. If anything the WMF needs to focus us more on the imbalance 
that exists between the fundamental bias toward English versus all other 
languages. For me the easiest picking is to share in the sum of the knowledge 
that is available to us. To get there simple goals like "a nine year old is 
able to find pictures in Commons" are fundamental. As it is, this is not even 
considered. 

Thanks,

   GerardM

 

On Tue, 17 Aug 2021 at 08:46, Peter Southwood  
wrote:

And it is based on a fundamental misconception of the legally mandated role of 
the WMF. Everything based on this false premise, fails.

Cheers,

Peter

 

From: Željko Blaće [mailto:zbl...@mi2.hr] 
Sent: 17 August 2021 06:18
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Wikipedia issues in UNDARK.org #Opinion article to 
check...

 

...considering recent discussions on Wikimania and here, this is maybe a useful 
opinion piece from  https:// 
UNDARK.org/2021/08/12/wikipedia-has-a-language-problem-heres-how-to-fix-it/ 


It is packed with good insights and while I do not agree with all this, the 
final sentence feels kind of brilliant: ... to achieve its stated mission to 
“help everyone share in the sum of all knowledge,” they might first need to 
create the sum of all Wikipedias.

 

Best Z. Blace

 

 


 
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
 

Virus-free.  
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/KYVKAVWN4EEFQ7OLAZYEPUXZA2PJLB7M/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/UGJ4SMD76OOHM45VDGN7YP3H5T5DNDSD/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Wikipedia issues in UNDARK.org #Opinion article to check...

2021-08-17 Thread Peter Southwood
And it is based on a fundamental misconception of the legally mandated role of 
the WMF. Everything based on this false premise, fails.

Cheers,

Peter

 

From: Željko Blaće [mailto:zbl...@mi2.hr] 
Sent: 17 August 2021 06:18
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Wikipedia issues in UNDARK.org #Opinion article to 
check...

 

...considering recent discussions on Wikimania and here, this is maybe a useful 
opinion piece from  https:// 
UNDARK.org/2021/08/12/wikipedia-has-a-language-problem-heres-how-to-fix-it/ 


It is packed with good insights and while I do not agree with all this, the 
final sentence feels kind of brilliant: ... to achieve its stated mission to 
“help everyone share in the sum of all knowledge,” they might first need to 
create the sum of all Wikipedias.

 

Best Z. Blace

 

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/KYVKAVWN4EEFQ7OLAZYEPUXZA2PJLB7M/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Blocking users for Palestinian flag

2021-07-02 Thread Peter Southwood
The problem is which political opinions would be acceptable on a user page, and 
who gets to decide this. We are expected to edit neutrally, so expressing a 
political opinion on a user page could be  considered a declaration of 
partisanship which could extend to editing behaviour.  

Cheers,

Peter

 

From: Frederick Noronha [mailto:fredericknoro...@gmail.com] 
Sent: 30 June 2021 00:57
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Blocking users for Palestinian flag

 

Just seeking clarity:

Is there anything wrong with expressing a political opinion on a userpage? 

A lot of our badges, flags, icons might have some or the other political 
history behind them, just that these are seen as more "normal" by today's 
standards. At one time, slavery too was considered quite legal.

Can't this be discussed in the public domain?

FN

 

On Wed, 30 Jun 2021 at 03:34, Gereon Kalkuhl  wrote:

Dear 4nn1|2,

Thank you for informing us about the incident. But to be clear: You write that 
it's about a Palestinian flag. Yet actually it's about a flag with a statement: 
free Palestine. There's a difference. And a member of the Persian Wikipedia 
removed the deletion request on Commons and kept the file on the same day. I'm 
not judging anything here, but please be more precise in your accusations.

Thank you,
Gereon

Am 29.06.2021 um 20:34 schrieb Amir Sarabadani:

If anyone is interested to know about this incident. Send me a private message 
and I can explain better.

 

Best

 

On Tue, Jun 29, 2021 at 8:17 PM 4nn1l2 <4nn1l2.w...@gmail.com> wrote:

Dear Wikimedians, 

 

Persian Wikipedia has reached a new level in their arbitrary and nonesense 
adminship. They have blocked me for placing a Palestinian flag on my userpage 
(of course they have already removed it from my userpage and you need to see a 
previous revision of my userpage).

 

https://fa.m.wikipedia.org/w/index.php?title=%DA%A9%D8%A7%D8%B1%D8%A8%D8%B1:4nn1l2
 

 =32191672

 

Another user has nominated the file for deletion on Commons!

 

I am admin on Commons myself and I'm fed up with how fawiki is managed. They 
block users for the most friviolous reasons.

 

What does this mean?

 

Yours faithfully,

User:4nn1l2

 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/QKGG6JWW5S4SI4Q5XN5ZUXG5FPE5JOKE/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org



-- 

Amir (he/him)

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/TCKQO6QDYJJGGJUYG623C7KRQHQPIUVQ/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/UAHL5ZUAFLXOFFWLSIUXHIK5UHWRIB2N/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org




 

-- 

 

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

_/  FN * फ्रेड्रिक नोरोन्या * فريدريك نورونيا‎ +91-9822122436 

_/  See a different Goa here, via 

_/  https://youtube.com/c/frederickfnnoronha

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

 

 


 

 

Virus-free.  

 www.avg.com 

 

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/WDBOEJIAM4T72JYZQ2VFBHEP4FGAGEAY/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Affiliations Committee Call for Candidates - June 2021

2021-05-17 Thread Peter Southwood
Is all this stuff somewhere on Meta?

 

From: Isaac Olatunde [mailto:reachout2is...@gmail.com] 
Sent: 17 May 2021 01:07
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Re: Affiliations Committee Call for Candidates - June 
2021

 

To add to Risker's question, which subcommittee is responsible for appointing 
new members of the affiliation committee? Or are new members selected or 
appointed by the WMF board?

 

Regards

 

Isaac

 

On Sun, 16 May 2021, 22:11 Risker,  wrote:

Thanks, Jeffrey; it's a start.  Perhaps asking specific questions will be more 
helpful.

 

Which subcommittee is responsible for:

*establishing standards for new affiliates (differentiated by type) and 
existing affiliates?  Are they the same group, or is this responsibility split?
*   collecting  and reviewing information to verify that the affiliates are 
meeting their standards?
*   supporting and encouraging existing affiliates to meet those standards?
*   assisting in the ongoing development of affiliates
*   determining whether an affiliate has fallen so far below standard that 
it can no longer continue?
*   revoking the approval of an affiliate (or recommending revocation - in 
which case, to whom does it make the recommendation?)
*   advocating within the movement on the value of the affiliate system

Does the Affiliates Committee continue to be a committee of the WMF Board of 
Trustees?  

 

Is it expected to have any role in recommendations about funding (or 
denying/withdrawing funding) to new and existing affiliates, now that the FDC 
has essentially been eliminated, either as a group or through one or the other 
of its subcommittees?

 

What range of conflict resolution tools will be available to the conflict 
subcommittee?  

 

 These were the first questions that came to me when I first saw your email.  I 
would not be surprised if others have more questions. 

 

Risker/Anne

 

On Sun, 16 May 2021 at 15:03, Jeffrey Keefer  wrote:

Risker-

 

Thank you for question on this. 

 

The descriptions are being revised, but let me try to briefly summarize them so 
there is something to work with for now. 

 

The Recognitions Subcommittee is involved with helping new Affiliates (User 
Groups, Chapters, and Thematic Organizations) to form and be recognized groups 
within the Movement. This involves clarifying their scope and ensuring there is 
no confusion in overlap of intentions. 

 

The Conflicts Subcommittee helps Affiliates when conflicts arise within or 
between Affiliates, including attempts to resolve these issues or ideally 
prevent them if possible. 

 

I hope this is helpful, even in this shortened form. 

 

Thank you. 


-

Jeffrey
User:FULBERT

 





On May 16, 2021, at 12:09 AM, Risker  wrote:

 

Jeffrey, could you please link to a description of the roles and 
responsibilities of members of the two subcommittees?  You've mentioned the 
expected skillset for each, but have not explained what they are actually 
expected to be responsible for. 

 

Thanks,

 

Risker/Anne

 

On Sat, 15 May 2021 at 14:41, Jeffrey Keefer  wrote:

The Affiliations Committee 
  – 
the committee responsible for guiding volunteers in establishing Wikimedia 
chapters, thematic organizations, and user groups – is looking for new members!

The main role of the AffCom is to guide groups of volunteers that are 
interested in forming Wikimedia affiliates. We review applications from new 
groups, answer questions and provide advice about the different Wikimedia 
affiliation models and processes, review affiliate bylaws for compliance with 
requirements and best practices, and update the Wikimedia Foundation Board of 
Trustees as well as advise them on issues connected to chapters, thematic 
organizations and Wikimedia user groups.

The committee consists of five to fifteen members, selected at least once every 
year, to serve two-year terms. 

Being a part of the AffCom requires communication with volunteers all over the 
world, negotiating skills, cultural sensitivity, and the ability to understand 
legal texts. We look for a mix of different skill sets in our members. 

Responsibilities

*   Availability of up to 5-8 hours per month

*   Participate in monthly one and two-hour voice/video meetings

*   Commitment to carry out assigned tasks in a given time.

*   Facilitate and support communications

*   Affiliate Support and growth

Required and Recommended Abilities, Skills, Knowledge for Affiliations 
Committee Members

Strong interpersonal relationship among members of the committee and also with 
the Wikimedia community members. Across all committee members, there are 
additional relevant skills as well as requirements which help to support the 
committee and its sustainability which include both required and relevant 
general skills

Required

*   Fluency in English
*   

Re: [Wikimedia-l] Board Ratification of Universal Code of Conduct

2021-02-20 Thread Peter Southwood
In what way would this clarify anything? Common sense is not so common, and 
sometimes is not even rational. Reasonable person at least provides some 
conditions for testing, though is also clearly not very useful in a 
multicultural environment.

Cheers,

Peter

 

From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Arthur Cheung
Sent: 20 February 2021 20:33
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Board Ratification of Universal Code of Conduct

 

Dear all,

 

Please allow me to add a solution to issue 1 as a brilliant colleague reminded 
my mistake for not putting any solution for that problem.

 

My ideal solution is to replace the word "reasonable person" with some 
equivalent words like "common sense" though that is not accurate as "reasonable 
man". The criteria will not be removed along with the replacement of the word 
"reasonable person". The 7 examples in current version are definitely not 
problematic and I would encourage to make such a list.

 

The reason is that for users from out of common law world, they might need a 
little bit training to get the sense of judgment. That is a waste of manpower 
and time and, makes the Code not universal enough. I would like to see more 
documents, even with examples, to explain and form the mind of "commons sense". 
That great fellow said we may make some FQA, and I think that is a great 
solution.

 

I apology for any inconvenience caused by that. If there is any other issue, 
you may find me on Telegram or by email.

 

Best Regards,

Arthur Cheung 
User:だ*ぜ (Dasze)

Board Member of Wikimedia Community User Group Hong Kong (WMHKG)

Telegram: @Dasze





Arthur Cheung  於 2021年2月20日 P.M.11:50 寫道:

 

Dear all,

 

I would like to share some ideas regarding UCoC and experience while I was 
acting as an administrator of Chinese Wikipedia chatting groups. Please first 
allow me to introduce myself: I used to be a former drafter of Chinese 
Wikipedia IRC protocol (Zhwiki’s IRCPOL) but abandoned to continue the work for 
the reason of massive problems existing in Chinese Wikipedia members that makes 
me feel unable and powerless to change through improving local protocols.

 

Within my knowledge and experience, and apart from political disputes, I have 
found several problems that might not or seldom occurred in the anglophone 
communities:

 

1. Non-Universal Usage:

The rules as to harassment stated that "Behaviour can be considered harassment 
if it is beyond what a reasonable person would be expected to tolerate in a 
global, intercultural environment". That requires the administrators for the 
knowledge of "reasonable man test". Such a test is widely and commonly used, 
and regarded as the objective test in the common law world. However, it is 
unfriendly for people from countries adopting legal systems other than the 
common law system. Those people shall be familiar with the test which is 
relatively depending on a subjective judgment of an admin on a certain issue. 
The uncertainty of the test is confirmed in various appeal cases in which the 
House of Lords held that the Court of Appeal made mistakes in adopting this 
test. Without a declaration of the certain standards or necessary training, I 
think it is inappropriate to use the term "reasonable man" since the test, 
which was already being adopted in Zhwiki’s IRCPOL before the UCoC was 
well-drafted and completed, has been proved its unfriendliness to those who 
come from China and Taiwan where both jurisdictions are of the Continental Law.

 

2. Connective Penalties in Instant Messaging (IM) and on Wikimedia Projects 

The user’s behaviours in IM may affect people’s view of that user. However, it 
is unclear whether the restriction on Wikimedia Projects can be given directly 
to a user breached the UCoC or, breached policies and guidelines in IM (such as 
canvassing). Without Safe and Trustee team or Stewards or Ombudsman Commission, 
can the administrators (admins) use the messages in IM as evidence to punish 
the wrongdoers in Wikipedia or other projects? I wish the Community and the 
Board may clarify that in UCoC.

 

3. Refusal of User Rights:

Some admins disagree with the point that users have the right of freedom of 
speech but adopted the rules of "Wikipedia:User access level" which the right 
for using instant messaging is a user access level and can be withdrawn. That 
causes admins to prefer to use the restriction and penalty which is beyond the 
reasonable proportionality for groups' order and peacefulness. That may cause 
the problem of admins’ preference on rules to be adopted for punishment purpose 
rather than for educational purpose in certain events. For example, I have seen 
that several Chinese Wikipedian involved in oral conflicts which the admin 
somehow prefer to warn and mute both sides for the reason of civility, instead 
of dispute resolving. User rights might be a blocker for admins and bureaucrats 
to think of a 

Re: [Wikimedia-l] Moving the technical infrastructure out of the US

2020-10-01 Thread Peter Southwood
If things are as bad as that then there should be and might already be an 
offshore backup, possibly more than one, as it is a no-brainer, and I don’t 
think WMF tech management  and the board are stupid, and nor are those who 
would wish to prevent it from happening. But plausible deniability. Cheers, 
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Christophe Henner
Sent: 30 September 2020 23:07
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Moving the technical infrastructure out of the US

Hi everyone,

Options to mitigate any risks are numerous, especially when it comes to
content distribution (private/semi-private/public/delegated/federated/a mix
of everything) but given the current context I would restrain from having
this as a public / community discussion.

We, community members, would most probably have great inputs but when one
is dealing with this kind of topic, designing contingencies plan, one has
to be ful of what information can be public. I have no idea whether staff
is working on such a topic, and it is better that way.

But we, as community members and awesome human beings, must be mindful of
some things:

   - The people in charge of that topic are mostly US Citizens. The current
   political and social climate is most probably draining their energy.
   Imagine having to manage it both from a personal and professional
   standpoint. Top that doing it for something as important as our projects.
   We cannot fathom their anxiety levels and should not add any to it.
   - Sending email about this topic, they have to read it. They most
   probably have to discuss, debate and balance whether they should answer or
   not. Imagine adding that to the first point.
   - They know for a fact, remember a lot of community members are staff,
   that community could be helping. But they can't ask for it.
   - Top all of that with them knowing that whatever course of action they
   might pick, it comes with a toll. Whether it is to talk about it here, and
   perhaps hinder their efforts, or not talk about it here and be perceived as
   ignoring the community.
   - Top all of that with the stress of trying to do their job in a global
   pandemic situation that might have them with loved ones at risk. Or with
   the need to care daily for young / elderly people.
   - Top that with the fact that they most probably all have relatives that
   at best are in financial struggle, or health struggles or are managing with
   the loss of loved ones.

Take a pause. Try to step in that space. Imagine how you would feel.
Multiply that by a hundred.

I would recommend we (community members) restrain from talking about it.
Perhaps what could be helpful, I am saying could, is for the people that do
actually have knowledge on those topics to just say they are available to
help if needs be with your area of expertise.

If no one at the Foundation acknowledges this thread or your emails, it is
ok. It doesn't mean you are not valued, it means that you are being spared
from that weight. We can provide support, but we should be mindful not to
increase their current level of stress.

Please all take care of yourselves, loved ones and each other

PS: I said staff, but read it as "anyone with an official Wikimedia
Foundation capacity". I know for a fact how those situations can be hard to
manage when you are a volunteer board member in the shadow too.


--
Christophe


On Wed, 30 Sep 2020 at 21:32, Steven Walling 
wrote:

> On Wed, Sep 30, 2020 at 12:22 PM Nathan  wrote:
>
> > Well, to Steven's point that you might need a jurisdiction where
> corporate
> > officers and employees aren't subject to extradition... I believe Germany
> > does in fact have an extradition treaty with the United States.
> >
>
> The chapters do seem like the obvious potentially viable easy
> solution here, if WMF set up that contingency plan.
>
> For instance, if WMDE did take over in an emergency, then the critical
> difference is that Germany doesn't extradite its own citizens to the US. So
> there'd just have to be a complete handoff of primary hosting to outside
> the US and some kind of agreement for WMDE (or pick your chapter) to take
> over operational control. There's probably a lot that real lawyers, of
> which I am not one, would know better here.
>
>
> > So far the criteria I'm hearing from the comments here:
> >
> > 1) Politically stable
> > 2) Liberal political environment
> > 3) Strong protections against government interference in relevant
> > operations
> > 4) Section 230-like protection against liability for user content
> > 5) No natural disasters like fires, floods, hurricanes, volcanoes, etc.
> > 6) Strong technological sophistication - preferably a robust technology
> > industry that can supply local talent for WMF needs
> > 7) Protections in the law for data privacy
> > 8) Availability of renewable energy sources and other resources that
> allow
> > for 

Re: [Wikimedia-l] [feedback requested] Taxonomy of knowledge gaps

2020-09-26 Thread Peter Southwood
Good points. 
Are these maybe covered in a future stage of the project?
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Samuel Klein
Sent: 26 September 2020 19:26
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] [feedback requested] Taxonomy of knowledge gaps

Thank you Leila -- I appreciate the reflection and the update here.  The
paper is thorough and methodical in its approach, which makes it easier for
me to see a problem (for my own ideas):

I don't see a focus on the primary tremendous *gaps *-- which for content
is depth + breadth + freshness, and for contributors is reach, and for
readers is reach in much of the world.
I do see an excellent discussion of systemic *bias*, but mostly treated as
*static* bias of what is there, and less *dynamic* bias of what we exclude
or disallow or discourage.

I left detailed feedback on meta
.
I would welcome any help in aligning the way I think about this w/  your
work (if that's desired).
Perhaps best to address there, since it is all about refactoring and may
benefit from that.  But I am posting the heart of it below for completeness:

===
Here are the first things I think of around coverage gaps.  Only the 0th
item seems to directly fit the current taxonomy...

0) exclusion via lack of awareness, interest, or expertise
1) exclusion via deletionism
2) exclusion via topic notability norms (including pop culture + current
events)
3) exclusion via source notability + limiting source formats
4) exclusion via license pessimism
5) exclusion via file format (!) and codec pessimism
6) exclusion of dense specialist knowledge via review bottlenecks
7) exclusion via knowledge type [model, dataset, map layer]
8) exclusion / rejection via behavior on the projects
9) exclusion / rejection under 1-4 via differential application of policy

Some of these, like file-format and review-bottleneck exclusion, are
primarily technical restrictions.
Some of these, like the first ~4 above, are social+regulatory+technical
restrictions that could be alleviated with simple tools (including
extensions, alternatives, and sandboxes) -- just as nupedia's social
restrictions were alleviated w/ the technical solution of a wiki for the
drafting stage.
And the last two are purely social restrictions, projecting systemic bias
in the community of practice onto who joins and what contributions are
welcomed. I'd like to see that subset of gaps addressed directly, and not
split up across other parts of a taxonomy.

===
Wiki♥, Sam.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Moderation notice

2020-09-13 Thread Peter Southwood
Unfortunately I think all these points are valid. These behavious do not 
improve communication for many of us. There seems to be a choice between 
freedom of expression and effective communication in a multicultural group. 
There is theoretically the option of asking for clarification, but it is often 
ignored. Sometimes bluntly refused, and sometimes claimed not to be necessary.
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Eduardo Testart
Sent: 12 September 2020 22:45
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Moderation notice

Hi All,

I just wanted to give my opinion on how to make things more civil and
gentle in general, and also to add clarity to the threads. As a non-English
native speaker, there are many things I consider do not help at all in
written discussions in general in any given list, most of the time when
these things are done, then everything turns challenging, complicated, or
sadly blatantly uncivil:

1) Irony
2) Jokes
3) Long and numerous paragraphs (extensive writing)
4) Acronyms

I believe these things are very important to pay attention too and should
be avoided, no matter what we are feeling or thinking about any specific
subject. Not doing so regularly leads to conflictive states, and paying
attention to the latter and restraining from doing so normally contributes
to open discussions.

I believe also that helps a lot to reduce:
5) Sayings and expressions

Maybe all this resonates with someone, and if not, it's also ok :]


Cheers!

On Fri, Sep 11, 2020 at 1:00 PM Asaf Bartov  wrote:

> On Fri, Sep 11, 2020 at 6:50 PM Dan Szymborski 
> wrote:
>
> > As long as people are going to continue to talk about me and imply that
> I'm
> > actually *harassing* people, then I feel I have a right to defend myself.
> >
>
> Nobody ever denied you that right.
>
> I brought up that the UCoC standard is a reasonable person standard, not a
> > "most offended person" standard and this was never addressed. Instead, I
> > was demeaned by being placed on a special moderation protocol. Asaf
> Bartov
> > threatened me that if I continued to defend myself -- even as people
> > continued to discuss me -- that *I'm* hijacking the thread.
>
>
> What I actually wrote to you, and I quote, was:
>
> "I also must insist that you not hijack this thread, which is for
> discussing the draft UCoC.  If you see value in bringing up your concerns
> on those other matters on this list, please do so on separate threads.
> Since you have expressed the opinion that this UCoC draft is illegitimate,
> I suggest there is really no reason for you to post further on this thread,
> leaving it for those who *would* like to discuss it."
>
> I then did indeed threaten that *if you continue to disrupt the UCoC
> thread*, your messages won't be let through. As you can see, your latest
> letter, since it was no longer disrupting the UCoC thread, *was* let
> through.
>
> I asked Asaf if Koerner was given a similar warning for a very long, smug,
> > patronizing screed about me as on-topic. Bartov reiterated that nobody
> else
> > was given any warning about off-topic communication. Only *I* am not
> > allowed to talk about *my* apparent offense.
> >
>
> Since now you quote a question you asked privately, I will quote the answer
> I gave you:
>
> 
> "No, I did not warn Ms. Koerner about thread hijacking, because the very
> problem with thread hijacking is that once the change of topic is made,
> people legitimately want to respond. I have not observed Ms. Koerner
> *initiating* a thread hijack.
>
> I do encourage you to continue contributing on the list, including in
> criticizing whatever flaws you find in the Foundation's actions.  I
> certainly find such flaws myself.
>
> But again, as a professional, perhaps you can be less ornery and more
> measured in expressing the *substance* of your concerns. It would at the
> very least be no less effective, and perhaps more so."
> 
>
>A.
> --
> Asaf Bartov 
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>


-- 
Eduardo Testart
(56)(98) 293 5278 Móvil
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



-- 
This email has been checked for viruses by AVG.
https://www.avg.com



Re: [Wikimedia-l] Foundation and affiliates disclosing salaries on job ads & the effect of this on workplace equity

2020-09-12 Thread Peter Southwood
This is the point I was working on. I also have no confident answer to this 
problem, but have a gut feel it is somewhere in between the extremes. There is 
also the point that most people have some choice in where they live, though I 
do not have any useful suggestion of how that should be factored into the 
calculation. San Francisco does seem to be a rather expensively arbitrary 
choice of address, which may be influencing the way the foundation operates. 
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Dan Garry (Deskana)
Sent: 12 September 2020 18:38
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Foundation and affiliates disclosing salaries on job 
ads & the effect of this on workplace equity

On Fri, 11 Sep 2020 at 12:39, Nathan  wrote:

> Shouldn't two candidates for the same position for the same company get
> roughly the same salary, regardless of where they live?
>

I don't know. Maybe.

Within the US, there are markets where decent, experienced software
engineers earn half of what a software engineer in San Francisco would
earn, and they would also probably have a comparable quality of life.
Outside the US, there are markets out there where the going rate
for decent, experienced software engineers is 15 times less than the going
rate for a software engineer in San Francisco. Due to the relative decrease
in purchasing power, the salary that's 15 times lower gives these people a
good quality of life comparable to (or possibly even better than) life in
San Francisco. Is it exploiting them to pay them 15 times less given that
their quality of life is the same, or even higher, than people in San
Francisco? Would it be fair to people in San Francisco, or other locations,
to do this? Should the Wikimedia Foundation pay people in this market 15
times more than they would earn at another company? As Gergő said, would
that be a responsible use of donor funds?

I don't have the answer to these questions. They are very hard questions
where there is no obviously correct answer.

Dan
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Foundation and affiliates disclosing salaries on job ads & the effect of this on workplace equity

2020-09-11 Thread Peter Southwood
On one side it would be nice to pay equal rate for equal work, on the other
would be equal personal benefit for equal work. Then there is the economics
of getting value for money, and the politics of diversity. It is a tricky
issue.
Cheers,
P

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Nathan
Sent: 11 September 2020 14:10
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Foundation and affiliates disclosing salaries on
job ads & the effect of this on workplace equity

I'm sure it will vary considerably. Does that matter? When measuring
internal equity, do we measure based on how expensive of a  lifestyle each
employee leads?

On Fri, Sep 11, 2020, 7:46 AM Peter Southwood 
wrote:

> Should they? Their cost of living expenses may vary considerably.
> Cheers,
> Peter
>
> -Original Message-
> From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> Behalf
> Of Nathan
> Sent: 11 September 2020 13:39
> To: Wikimedia Mailing List
> Subject: Re: [Wikimedia-l] Foundation and affiliates disclosing salaries
on
> job ads & the effect of this on workplace equity
>
> Dan,
>
> Shouldn't two candidates for the same position for the same company get
> roughly the same salary, regardless of where they live?
>
> On Fri, Sep 11, 2020, 7:00 AM Dan Garry (Deskana) 
> wrote:
>
> > Asking candidates for their current salary is prohibited in San
Francisco
> > as of July 2018 [1] which means that, as a San Francisco based
> > organisation, the Foundation will undoubtedly not be doing this. To my
> > knowledge, this wasn't done by the Foundation before either, but we can
> > confidently state that it won't be done now.
> >
> > There are some complexities in disclosing salary ranges for the
> Foundation.
> > One practice that can be used for encouraging diversity in candidate
> > applications is to specify that a position is open to candidates with a
> > wide range of experience and in all locations in the world, in which
case
> > the salary range posted will be so large that it will basically be
> > meaningless. On the other hand, another good practice for encouraging
> > diversity is to source internally for senior positions, which opens up
> more
> > junior roles that can be sourced externally, in which case a salary
range
> > can be more meaningful and helpful. It's hard to figure out what the
> right
> > balance is.
> >
> > Regardless, more public transparency in salary banding would be good to
> > see.
> >
> > Dan
> >
> > [1]:
> >
> >
>
>
https://www.shrm.org/resourcesandtools/legal-and-compliance/state-and-local-
> updates/pages/san-francisco-bans-salary-history-questions.aspx
>
<https://www.shrm.org/resourcesandtools/legal-and-compliance/state-and-local
-updates/pages/san-francisco-bans-salary-history-questions.aspx>
> >
> > On Fri, 11 Sep 2020 at 10:44, Chris Keating 
> > wrote:
> >
> > > Good morning everyone!
> > >
> > > There's a campaign(1) for nonprofits to disclose the salaries, or at
> > least
> > > salary ranges, on job ads.
> > >
> > > An increasing body of evidence(2) shows that practices like not
> > disclosing
> > > expected pay, and requiring applicants to disclose their current
> salary,
> > is
> > > harmful to equity in the workplace.
> > >
> > > Not disclosing salaries affects pay levels within the organisation -
> > > because white men are usually relatively confident in negotiating
their
> > > salaries upwards, so tend to end up with a better deal.
> > >
> > > It can also affect the diversity of candidates who apply. Candidates
> who
> > > have stronger networks within the industry they're moving into (again,
> > more
> > > commonly white men with privileged social and educational backgrounds)
> > also
> > > have clear expectations because they are 'in the know' about industry
> > > norms, while people who don't, find the lack of salary information a
> > > barrier to application. (After all, why take the time and effort to
> apply
> > > for a job when you have no idea how the likely pay compares to your
> > current
> > > employment?)
> > >
> > > I know practices vary within the movement - I believe the WMF never
> > > mentions salaries on ads, and I don't know whether the range is
> disclosed
> > > to applicants or not - some chapters I know do advertise a salary.
> > However,
> > > I'd urge all entities within the movement that hire staff to disclose
> the
>

Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-11 Thread Peter Southwood
There was no clear statement of "this is the problematic text and this is why 
it is considered unacceptable", which is a thing that I consider a reasonable 
expectation, as it is possible to learn from it, understand it, pass 
constructive criticism or agreement, and use as it a precedent for future 
expectations.
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Adam Wight
Sent: 11 September 2020 11:56
To: wikimedia-l@lists.wikimedia.org
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review

> Is there somewhere we can refer to the list of offensive and unacceptable
> expressions, and how they are determined?

There were been several explanations already.  It's possible to use mild 
words in a cruel way, for example a father telling their child "You've 
always had beans for brains."  Editors are aware of this simple truth 
and any feigned outrage must be disingenuous.

It's interesting that I've voiced some extremely harsh criticism of the 
WMF, even suggesting that the editors form a union and sue for control 
of the Board, yet I've never once been moderated.  Had my job threatened 
perhaps, but never blocked.

The point here is that petty hostility only achieves the goal of 
creating an unpleasant and unwelcoming environment.  If you (speaking to 
the people here who are critical of the UCoC) want to make real change, 
please organize yourselves somewhere else, come up with a coherent 
argument, and present it here.  The constant attrition of "why can't I 
say 'fart'?" is tiresome and dilutes any conversation of substance.

Kind regards,
U:Adamw


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Foundation and affiliates disclosing salaries on job ads & the effect of this on workplace equity

2020-09-11 Thread Peter Southwood
Should they? Their cost of living expenses may vary considerably. 
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Nathan
Sent: 11 September 2020 13:39
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Foundation and affiliates disclosing salaries on
job ads & the effect of this on workplace equity

Dan,

Shouldn't two candidates for the same position for the same company get
roughly the same salary, regardless of where they live?

On Fri, Sep 11, 2020, 7:00 AM Dan Garry (Deskana)  wrote:

> Asking candidates for their current salary is prohibited in San Francisco
> as of July 2018 [1] which means that, as a San Francisco based
> organisation, the Foundation will undoubtedly not be doing this. To my
> knowledge, this wasn't done by the Foundation before either, but we can
> confidently state that it won't be done now.
>
> There are some complexities in disclosing salary ranges for the
Foundation.
> One practice that can be used for encouraging diversity in candidate
> applications is to specify that a position is open to candidates with a
> wide range of experience and in all locations in the world, in which case
> the salary range posted will be so large that it will basically be
> meaningless. On the other hand, another good practice for encouraging
> diversity is to source internally for senior positions, which opens up
more
> junior roles that can be sourced externally, in which case a salary range
> can be more meaningful and helpful. It's hard to figure out what the right
> balance is.
>
> Regardless, more public transparency in salary banding would be good to
> see.
>
> Dan
>
> [1]:
>
>
https://www.shrm.org/resourcesandtools/legal-and-compliance/state-and-local-
updates/pages/san-francisco-bans-salary-history-questions.aspx
>
> On Fri, 11 Sep 2020 at 10:44, Chris Keating 
> wrote:
>
> > Good morning everyone!
> >
> > There's a campaign(1) for nonprofits to disclose the salaries, or at
> least
> > salary ranges, on job ads.
> >
> > An increasing body of evidence(2) shows that practices like not
> disclosing
> > expected pay, and requiring applicants to disclose their current salary,
> is
> > harmful to equity in the workplace.
> >
> > Not disclosing salaries affects pay levels within the organisation -
> > because white men are usually relatively confident in negotiating their
> > salaries upwards, so tend to end up with a better deal.
> >
> > It can also affect the diversity of candidates who apply. Candidates who
> > have stronger networks within the industry they're moving into (again,
> more
> > commonly white men with privileged social and educational backgrounds)
> also
> > have clear expectations because they are 'in the know' about industry
> > norms, while people who don't, find the lack of salary information a
> > barrier to application. (After all, why take the time and effort to
apply
> > for a job when you have no idea how the likely pay compares to your
> current
> > employment?)
> >
> > I know practices vary within the movement - I believe the WMF never
> > mentions salaries on ads, and I don't know whether the range is
disclosed
> > to applicants or not - some chapters I know do advertise a salary.
> However,
> > I'd urge all entities within the movement that hire staff to disclose
the
> > expected salary ranges for posts they are advertising, as part of their
> > commitment to equality, diversity and inclusion.
> >
> > Thanks for reading,
> >
> > Chris
> >
> >
> >
> > (1): https://showthesalary.com/
> > (2): e.g. at https://showthesalary.com/resources/
> > ___
> > Wikimedia-l mailing list, guidelines at:
> > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > https://meta.wikimedia.org/wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
> >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


-- 
This email has been checked for viruses by AVG.
https://www.avg.com



___
Wikimedia-l mailing list, guidelines at: 

Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-11 Thread Peter Southwood
I would call this fair comment, and parallels can be drawn between how the UCoC 
may be used and the current discussion. Without clear statement on why a 
decision is made it cannot be properly understood, accepted or improved, and we 
end up in the usual spiral of speculation, accusation and bad feelings by all.
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Benjamin Ikuta
Sent: 11 September 2020 13:16
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review



Thanks for the reply. 

I took a look at it and found it terribly vague. 

Depending on subjective interpretation, I can imagine it being used to justify 
whatever judgement is to be made. 

I am no more enlightened. 



> On Sep 11, 2020, at 4:05 AM, Alphos OGame  wrote:
> 
> Hello everyone,
> 
> What I want to read : comments on the UCoC.
> What I don't want to read : a barrage of *insert adjective, whether laudative 
> or criticizing* reply after reply after reply after reply on the comments of 
> one or more of the subscribers of this list.
> 
> I understand the initial comments shocked some of you, and some may want to 
> defend freedom of expression and  others yet criticize actions past or 
> current by the Foundation, but still, I'd rather we'd compartmentalize and, 
> instead of bickering about something the list mods have already given what 
> seems to be a rather decent decision, talk about the Universal Code of 
> Conduct, as I still haven't wrapped my head around it.
> 
> Please, no more back and forth, no more inanity, no more four mails an hour.
> Thank you…
> 
> Roger / Alphos
> 
> 
>> Le 11 sept. 2020 à 12:22, Quim Gil  a écrit :
>> 
>> On Fri, Sep 11, 2020 at 9:31 AM Benjamin Ikuta 
>> wrote:
>> 
>>> Please, enlighten me.
>> 
>> Here is an alternative suggestion. Check the UCoC draft and see whether you
>> see room for improvement or disagree with anything specific in it. This is
>> a productive way to compare your personal understanding of civility against
>> the understanding of civility the UCoC offers for the entire movement. If
>> you have ideas to improve the draft, share them, if possible on the Meta
>> page where the main discussion is happening.
>> 
>> https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Draft_review
>> 
>> 
 On Sep 10, 2020, at 11:39 PM, Ziko van Dijk  wrote:
 Am Fr., 11. Sept. 2020 um 08:07 Uhr schrieb Benjamin Ikuta
 :
> Is there some context that makes this much worse than it seems, or do I
>>> have a deeply flawed understanding of civility?
 Well, are you open to consider the possibility that the latter might
 theoretically be the case, at least partially?
 Kind regards
 Ziko
>> 
>> 
>> -- 
>> Quim Gil (he/him)
>> Senior Manager of Community Relations @ Wikimedia Foundation
>> https://meta.wikimedia.org/wiki/User:Qgil-WMF
>> ___
>> Wikimedia-l mailing list, guidelines at: 
>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
>> https://meta.wikimedia.org/wiki/Wikimedia-l
>> New messages to: Wikimedia-l@lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
>> 
> 
> ___
> Wikimedia-l mailing list, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
> 


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-11 Thread Peter Southwood
In that case, can we please have an explanation of exactly how the relevant
text was found to be inappropriate, as this is patently unclear, and
apparently the reason for all this debate. I have my own speculation, but as
it is speculation, it would be inappropriate to publicise unless there is no
official explanation.
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Asaf Bartov
Sent: 11 September 2020 11:46
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review

No, it is not "forbidden words" that are the problem, and we have no
intention of maintaining a list.

We expect list subscribers to maintain civil discourse, which does include
avoiding vulgarity, and expressing oneself with respect to both one's
interlocutors (or addressees of criticism) and the broader audience.

Happily, this is something more than 99 percent of subscribers manage to do
without effort.

As I have repeatedly clarified, respectful discourse absolutely does not
preclude criticism. Indeed, it is liable to make the criticism more likely
to be heard.

   A.

On Fri, 11 Sep 2020, 12:26 Peter Southwood 
wrote:

> Is there somewhere we can refer to the list of offensive and unacceptable
> expressions, and how they are determined?
> Cheers,
> Peter
>
> -Original Message-
> From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> Behalf
> Of Anders Wennersten
> Sent: 11 September 2020 10:33
> To: wikimedia-l@lists.wikimedia.org
> Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review
>
> There are many of us on this list who have given the feedback we find
> that expression offensive and unacceptable.
>
> Do not forget the readers of this list comes from may different cultures
> and if you and the people close to you find it "acceptable" it is not a
> valid judgment for all, and why do you want us to leave this list just
> so you can use a language like that. (I certainly would if that was
> accepted as a norm)
>
> The language on this list is English, it means we non-native have to
> adjust our entries to a unfamiliar language. It mean we have to limit
> our means of expression (we will not be experts on nuances).  You who
> are native English speaker have all the advantages, would it then be too
> hard for you to adjust you language to what is acceptable to us others?
>
> Anders
>
>
> Den 2020-09-11 kl. 09:31, skrev Benjamin Ikuta:
> >
> > Please, enlighten me.
> >
> >
> >
> > On Sep 10, 2020, at 11:39 PM, Ziko van Dijk  wrote:
> >
> >> Am Fr., 11. Sept. 2020 um 08:07 Uhr schrieb Benjamin Ikuta
> >> :
> >>> Is there some context that makes this much worse than it seems, or do
I
> have a deeply flawed understanding of civility?
> >> Well, are you open to consider the possibility that the latter might
> >> theoretically be the case, at least partially?
> >> Kind regards
> >> Ziko
> >>
> >>
> >>
> >>> a.org?subject=unsubscribe>
> >> ___
> >> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> >> New messages to: Wikimedia-l@lists.wikimedia.org
> >> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > ___
> > Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
>
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubsc

Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-11 Thread Peter Southwood
Is there somewhere we can refer to the list of offensive and unacceptable
expressions, and how they are determined?
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Anders Wennersten
Sent: 11 September 2020 10:33
To: wikimedia-l@lists.wikimedia.org
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review

There are many of us on this list who have given the feedback we find 
that expression offensive and unacceptable.

Do not forget the readers of this list comes from may different cultures 
and if you and the people close to you find it "acceptable" it is not a 
valid judgment for all, and why do you want us to leave this list just 
so you can use a language like that. (I certainly would if that was 
accepted as a norm)

The language on this list is English, it means we non-native have to 
adjust our entries to a unfamiliar language. It mean we have to limit 
our means of expression (we will not be experts on nuances).  You who 
are native English speaker have all the advantages, would it then be too 
hard for you to adjust you language to what is acceptable to us others?

Anders


Den 2020-09-11 kl. 09:31, skrev Benjamin Ikuta:
>
> Please, enlighten me.
>
>
>
> On Sep 10, 2020, at 11:39 PM, Ziko van Dijk  wrote:
>
>> Am Fr., 11. Sept. 2020 um 08:07 Uhr schrieb Benjamin Ikuta
>> :
>>> Is there some context that makes this much worse than it seems, or do I
have a deeply flawed understanding of civility?
>> Well, are you open to consider the possibility that the latter might
>> theoretically be the case, at least partially?
>> Kind regards
>> Ziko
>>
>>
>>
>>> a.org?subject=unsubscribe>
>> ___
>> Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
>> New messages to: Wikimedia-l@lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,

> ___
> Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


-- 
This email has been checked for viruses by AVG.
https://www.avg.com



___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-11 Thread Peter Southwood
It is not yet clear that the use of the words "fart" or "flatulence" are the 
actual issue. Context matters, but we do not know the full context yet, as the 
reasons have not been explained, leaving us with little option but to 
speculate. We are experiencing a failure of communication as much, or more, 
than a failure of civility.
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Todd Allen
Sent: 11 September 2020 09:14
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review

Except, apparently, if someone says "fart". For godsakes, that's about the
mildest of language you could ask for. I could use far stronger about this
whole farce.

If the "UCoC" means that people can't say "fart" because someone might get
their feewings hurted, then I've very well been right to strongly oppose it.

Todd

On Thu, Sep 10, 2020 at 3:45 AM Asaf Bartov  wrote:

> As you can see, Dan, your choice of imagery, appreciated and encouraged in
> less buttoned-up journalism, is offensive to some subscribers here.  Your
> strong criticism of the Foundation, on the other hand, is perfectly
> acceptable.
>
> As a professional wordsmith, I am confident you can continue to voice this
> criticism while employing milder imagery, or indeed dispensing with
> figurative language entirely.
>
> A.
>
> On Thu, Sep 10, 2020 at 12:31 PM Dan Szymborski 
> wrote:
>
> > I am absolutely flabbergasted that a generic reference of an organization
> > to flatulence, something we see in rated-G television isn't considered
> > "collegial" enough yet the actions that the WMF has taken over the last
> 18
> > months, many of which were pushed by people on this list *are* considered
> > collegial.
> >
> > If a joke that would be appropriate for a four-year-old leads to special
> > moderation, what action ought be taken for someone on the list pushing
> the
> > failure of a collaborative process that WMF is foisting upon the
> community?
> > One of the people "doth protesting too much" about the reference is also
> > someone banned from English Wikipedia for a whole litany of *actual*
> things
> > that took up countless hours of community time, including making legal
> > threats based on finding offense in normal Wikipedia actions.
> >
> > I am a longtime, accredited journalist, possibly even slightly respected
> in
> > the field -- though there's always that risk of Dunning-Kruger -- who has
> > written for a ton of outlets and there's not an editor in the world that
> > I've worked with who would've asked me to change the *very* gentle
> wording.
> > If anything, I was too mild. *I'm* grossly offended by the WMF's actions
> > over the last 18 months. *I'm* grossly offended by the perversion of a
> free
> > information movement being converted into a third-tier social media app.
> > *I'm* grossly offended by board policies that empower the vested, the
> > connected, the politically adept to judge the weak and the voiceless.
> *I'm*
> > grossly offended by the people here who cheerfully announce the board
> > arbitrarily changing board terms or that the community has no actual say
> in
> > what the *community* (not the board) built. The Wiki movement is far
> bigger
> > than the WMF; which is a good thing because I can't imagine it being
> > smaller than the board's self-dealing petty bourgeoisie affair.
> >
> > No, I didn't mean petit.
> >
> > Yet I don't call for anyone to be silenced because, well, disagreeing
> > vigorously is what adults are able to do.
> >
> > It matters not if this message is censored by the list overlords. One of
> > the few benefits of being a journalist is that combination of
> > self-righteousness and having myriad ways to prevent an opinion from
> being
> > suppressed on dubious grounds.
> >
> > Cheers,
> >
> > Dan
> >
> > On Thu, Sep 10, 2020 at 2:55 AM Natacha Rault via Wikimedia-l <
> > wikimedia-l@lists.wikimedia.org> wrote:
> >
> > > Hello,
> > >
> > > A code of conduct id something many of us have asked the WMF to write
> for
> > > many years. We are asking the WMF to take an active part in stopping
> > > abusive behaviors in our community.
> > >
> > > On fr wiki, many admins say they are tired of conflicts and that they
> did
> > > not enroll to deal with them. A code of conduct could help then take
> > action
> > > because it offers a frame.
> > >
> > > This is COMPLETELY different with the branding process.
> > >
> > > We are one of the few projects in the open source world without a code
> of
> > > conduct.
> > >
> > > So thank you for this draft, thank you for opening up for discussions,
> > and
> > > I hope the language will remain respectful.
> > >
> > > I believe moderators should ban from this list the person who spoke
> about
> > > « wmf flatulence ».
> > >
> > >
> > >  I dont want to read that type of language among people who are
> > supposedly
> > > asked to write neutral enccyclopedias.
> > >

Re: [Wikimedia-l] New board of Wikimedia Chile / Nuevo directorio de Wikimedia Chile

2020-09-11 Thread Peter Southwood
Good luck to all of you
P

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Rocío Consales
Sent: 10 September 2020 20:39
To: wikimedia-l@lists.wikimedia.org
Subject: [Wikimedia-l] New board of Wikimedia Chile / Nuevo directorio de 
Wikimedia Chile

[*Spanish below*]

Comrades:


I hope everyone is in good health. I write to inform you of the update of
the Wikimedia Chile board. I have submitted my resignation to the
presidency, since I obtained a scholarship to study in Spain. The new
president of WMCL is Carlos Figueroa, whom the whole team has great esteem
and confidence in to continue with the multiple projects that the chapter
has ahead. Luis Cristóbal Carrasco, a very enthusiastic member, who we know
will be a great contribution to this administration, joins the board.


The new board consists of:
President: Carlos Figueroa
Vicepresident: Marco Correa
Secretary: Claudio Loader
Treasurer: Osmar Valdebenito
Board member: Dennis Tobar
Board member: Luis Cristóbal Carrasco


The team is fully aware of the lack of gender diversity in the board, but
it has been done and will continue to work with the commitment to solve
this problem in the near future. The work related to reducing the gender
gap has been transversal in all our activities and in the administrations
of our chapter, and we sincerely hope as a team that the steps that have
been taken in that direction will soon bear fruit.


It only remains for me to thank the trust placed in me by the partners and
the entire team, and wish the best of success to the new structure of the
board of directors.


Sincerely,

Rocío Consales

___


Camaradas:


Espero que todos se encuentren bien de salud. Escribo para informar la
actualización del directorio de Wikimedia Chile. He presentado mi renuncia
a la presidencia, ya que obtuve una beca para estudiar en España. El nuevo
presidente de WMCL es Carlos Figueroa, a quien todo el equipo le tiene una
gran estima y confianza para seguir adelante con los múltiples proyectos
que el capítulo tiene por delante. Ingresa al directorio Luis Cristóbal
Carrasco, socio muy entusiasta que sabemos será un gran aporte a esta
administración.


El nuevo directorio se compone por:
Presidente: Carlos Figueroa

Vicepresidente: Marco Correa

Secretario: Claudio Loader

Tesorero: Osmar Valdebenito

Director: Dennis Tobar

Director Luis Cristóbal Carrasco


El equipo está completamente consciente de la falta de diversidad de género
en el directorio, pero se ha hecho y seguirá trabajando con el compromiso
de solventar este problema en el futuro próximo. El trabajo relacionado a
disminuir la brecha de género ha sido transversal en todas nuestras
actividades y en las administraciones de nuestro capítulo, y esperamos
sinceramente como equipo que los pasos que se han dado en esa dirección
pronto rindan frutos.


Solo me queda agradecer la confianza depositada en mí por los socios y todo
el equipo, y desear el mayor de los éxitos a la nueva estructura de la
junta directiva.



Un abrazo,

Rocío Consales
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Moderation notice

2020-09-11 Thread Peter Southwood
Lukas, If you could explain exactly what your objection was, it lets all of us 
understand better where the line was drawn. That allows discussion to be 
focused on reality rather than speculation, which could get us closer to an 
acceptable code of conduct, instead of fuelling paranoia.
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Lukas Mezger
Sent: 10 September 2020 20:30
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Moderation notice

Hello,

As one of the list subscribers who contacted the list moderators about the
messages in question, please let me second the sentiment that this list
should welcome discourse that is honest and frank while remaining
constructive and civil. Being subscribed to this list can be stressful for
some of us at times, so please keep that in mind when contributing.
Thank you, and kind regards,

Lukas


--

Dr. Lukas Mezger
Vorsitzender des Präsidiums / chair of the Supervisory Board

Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 260 – (0151) 268 63 931
http://wikimedia.de

Bleiben Sie auf dem neuesten Stand! Aktuelle Nachrichten und spannende
Geschichten rund um Wikimedia, Wikipedia und Freies Wissen im Newsletter: Zur
Anmeldung <https://www.wikimedia.de/newsletter/>.

Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207

Am Do., 10. Sept. 2020 um 18:19 Uhr schrieb Peter Southwood <
peter.southw...@telkomsa.net>:

> Is the objection to the words he used or to the way he used them?
> Cheers,
> Peter
>
> -Original Message-
> From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> Behalf
> Of Asaf Bartov
> Sent: 09 September 2020 21:57
> To: Wikimedia Mailing List
> Subject: [Wikimedia-l] Moderation notice
>
> Dear Wikimedians,
>
> List subscriber Dan Szymborski has been placed under moderation, due to
> posts with unacceptable language.
>
> I remind everyone that criticism is appropriate and welcome on this list,
> so long as it remains civil and respectful of the people involved.
>
>Asaf (volunteer capacity)
>on behalf of Wikimedia-l list moderators
> --
> Asaf Bartov 
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
>
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>


-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>


Re: [Wikimedia-l] Moderation notice

2020-09-10 Thread Peter Southwood
Is the objection to the words he used or to the way he used them?
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Asaf Bartov
Sent: 09 September 2020 21:57
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Moderation notice

Dear Wikimedians,

List subscriber Dan Szymborski has been placed under moderation, due to
posts with unacceptable language.

I remind everyone that criticism is appropriate and welcome on this list,
so long as it remains civil and respectful of the people involved.

   Asaf (volunteer capacity)
   on behalf of Wikimedia-l list moderators
-- 
Asaf Bartov 
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


-- 
This email has been checked for viruses by AVG.
https://www.avg.com



___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-10 Thread Peter Southwood
For a UVoC to be helpful, it would have to be sufficiently clear  about what is 
unacceptable, and why it is unacceptable, and would itself have to be 
sufficiently clear and acceptable to be seen as fair by the communities who 
would be bound by it. This is not easy to do, and the talk page already 
illustrates how far the draft is from an acceptable state of clarity. I am not 
saying it cannot get there, but it will take more work. Possibly a lot more 
work, and it does not appear to be getting there fast.

What Anders says about the use of a simplified subset of English has value. 
Words should be used that are easily translatable, even when this may require 
more words to be used to make a point.

Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Jackie
Sent: 10 September 2020 16:16
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review

Dan,

I am so glad you have given us a real-world example as to how a Universal
Code of Conduct would be super helpful. It would provide you with a clear
understanding of how your comments impacted others. It wasn't just your use
of the word "flatulence" (which, funny enough, I had to reference spelling
from your email because I have *never* written this word in any
correspondence). As a parent, I certainly understand the place of such
words in juvenile humor, but your use here was to implicate an organization
of professionals is simply operating in bad faith. That sort of comment is
hostile and denigrates people who *actually* work very hard to empower
people in the free knowledge movement.

This language serves to alienate people from participation and sews
discord. These mailing lists are already missing a lot of the people who
*should* be at the table in these discussions. The mailing lists are rather
homogeneous in participation because of responses like this call for
discussion. I hope the future means we move to something more inclusive and
covered by a Code of Conduct.

In a situation like this where someone has said something offensive, a CoC
would provide a process for everyone to follow and understand. The people
reporting the concern would have avenues on which to do so without facing
public backlash and the steps for reviewing reports would be clear. Based
off of other CoC examples, this often includes who will respond to such
concerns and how they will respond. CoCs often go further to clearly
identify which steps will be taken for certain offenses and what response
and support the original person reporting the issue can receive. I feel
education is a huge part of CoC violation response. Perhaps the person
violating the CoC can do better after becoming aware of how their behavior
impacts others and still be a valuable member of the community.

If you are still genuinely confused about how what you said is offensive, I
am more than happy to discuss this with you via phone or video chat. I find
that text-based communication provides complications for discussions about
emotional topics. I can see you feel passionate about this situation and
upset about the result.

Best,

Jackie

On Thu, Sep 10, 2020 at 7:23 AM Joseph Seddon 
wrote:

> Wikipedia has been a third tier social media platform since its inception.
> Luckily we are better known for being an encyclopedia.
>
> On Thu, Sep 10, 2020 at 10:31 AM Dan Szymborski 
> wrote:
>
> > I am absolutely flabbergasted that a generic reference of an organization
> > to flatulence, something we see in rated-G television isn't considered
> > "collegial" enough yet the actions that the WMF has taken over the last
> 18
> > months, many of which were pushed by people on this list *are* considered
> > collegial.
> >
> > If a joke that would be appropriate for a four-year-old leads to special
> > moderation, what action ought be taken for someone on the list pushing
> the
> > failure of a collaborative process that WMF is foisting upon the
> community?
> > One of the people "doth protesting too much" about the reference is also
> > someone banned from English Wikipedia for a whole litany of *actual*
> things
> > that took up countless hours of community time, including making legal
> > threats based on finding offense in normal Wikipedia actions.
> >
> > I am a longtime, accredited journalist, possibly even slightly respected
> in
> > the field -- though there's always that risk of Dunning-Kruger -- who has
> > written for a ton of outlets and there's not an editor in the world that
> > I've worked with who would've asked me to change the *very* gentle
> wording.
> > If anything, I was too mild. *I'm* grossly offended by the WMF's actions
> > over the last 18 months. *I'm* grossly offended by the perversion of a
> free
> > information movement being converted into a third-tier social media app.
> > *I'm* grossly offended by board policies that empower the vested, the
> > connected, the politically adept to 

Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-10 Thread Peter Southwood
Anders, I think you are referring to jargon. I agree that it should be avoided 
in the interests of clarity and ease of reliable translation. 
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Anders Wennersten
Sent: 10 September 2020 16:48
To: wikimedia-l@lists.wikimedia.org
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review

I want to echo Jackies two mail

The community for svwp is not so big and complicated issues on conduct 
are uncommon. But when they occur we often get caught in argument like " 
you who claim to decide over svwp CoC are just a small kabal of some 
10-120 admins, you are unrepresentative and the enwp CoC says 
otherwise". It will be of big help for us when we need not go into 
detailed discussion over every abuse, but can refer to the UCoC (and not 
just ToU).

And wordings... We consist of people form many different culture and 
language, so what one small group can be seen as acceptable wording can 
be seen as offensive to other.

When I worked in the Swedish global company Ericsson, the interal 
language was English. But in reality that internal vocabulary only used 
5-10% of the English words, and never puns or sarcasm, and often rather 
blunt expressions than too "flowery". I think something similar must be 
what we use in our internal communication of Wikimedia. And that will be 
welcome for all non-native English people, but can be harder for native 
English people. I have given feedback to top WMF people when the used 
too complicated/flowery sentences that made it hard for non-natives to 
understand what was said.

Anders


Den 2020-09-10 kl. 16:16, skrev Jackie:
> Dan,
>
> I am so glad you have given us a real-world example as to how a Universal
> Code of Conduct would be super helpful. It would provide you with a clear
> understanding of how your comments impacted others. It wasn't just your use
> of the word "flatulence" (which, funny enough, I had to reference spelling
> from your email because I have *never* written this word in any
> correspondence). As a parent, I certainly understand the place of such
> words in juvenile humor, but your use here was to implicate an organization
> of professionals is simply operating in bad faith. That sort of comment is
> hostile and denigrates people who *actually* work very hard to empower
> people in the free knowledge movement.
>
> This language serves to alienate people from participation and sews
> discord. These mailing lists are already missing a lot of the people who
> *should* be at the table in these discussions. The mailing lists are rather
> homogeneous in participation because of responses like this call for
> discussion. I hope the future means we move to something more inclusive and
> covered by a Code of Conduct.
>
> In a situation like this where someone has said something offensive, a CoC
> would provide a process for everyone to follow and understand. The people
> reporting the concern would have avenues on which to do so without facing
> public backlash and the steps for reviewing reports would be clear. Based
> off of other CoC examples, this often includes who will respond to such
> concerns and how they will respond. CoCs often go further to clearly
> identify which steps will be taken for certain offenses and what response
> and support the original person reporting the issue can receive. I feel
> education is a huge part of CoC violation response. Perhaps the person
> violating the CoC can do better after becoming aware of how their behavior
> impacts others and still be a valuable member of the community.
>
> If you are still genuinely confused about how what you said is offensive, I
> am more than happy to discuss this with you via phone or video chat. I find
> that text-based communication provides complications for discussions about
> emotional topics. I can see you feel passionate about this situation and
> upset about the result.
>
> Best,
>
> Jackie
>
> On Thu, Sep 10, 2020 at 7:23 AM Joseph Seddon 
> wrote:
>
>> Wikipedia has been a third tier social media platform since its inception.
>> Luckily we are better known for being an encyclopedia.
>>
>> On Thu, Sep 10, 2020 at 10:31 AM Dan Szymborski 
>> wrote:
>>
>>> I am absolutely flabbergasted that a generic reference of an organization
>>> to flatulence, something we see in rated-G television isn't considered
>>> "collegial" enough yet the actions that the WMF has taken over the last
>> 18
>>> months, many of which were pushed by people on this list *are* considered
>>> collegial.
>>>
>>> If a joke that would be appropriate for a four-year-old leads to special
>>> moderation, what action ought be taken for someone on the list pushing
>> the
>>> failure of a collaborative process that WMF is foisting upon the
>> community?
>>> One of the people "doth protesting too much" about the reference is also
>>> someone banned from English Wikipedia for a whole litany 

Re: [Wikimedia-l] Moderation notice

2020-09-10 Thread Peter Southwood
You read my mind...
P

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Gnangarra
Sent: 10 September 2020 13:50
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Moderation notice

one measure of good judgement would those decline the opportunity to be a
list administrator :D

On Thu, 10 Sep 2020 at 19:41, Peter Southwood 
wrote:

> Good judgement is often such a subjective thing, Everyone thinks they have
> it. A bit like the Dunning-Kruger effect.
> Cheers,
> Peter
>
> -Original Message-
> From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> Behalf
> Of Asaf Bartov
> Sent: 10 September 2020 12:55
> To: Wikimedia Mailing List
> Subject: Re: [Wikimedia-l] Moderation notice
>
> I would say first and foremost, good judgment. As measured by the person's
> track record on-wiki and on this list.
>
> Preferring to err on the side of caution, people under community
sanctions,
> or who have themselves been moderated for on-list misconduct, need not
> apply.
>
>A.
>
> On Thu, 10 Sep 2020, 12:58 Peter Southwood 
> wrote:
>
> > Asaf,
> > What are the criteria for eligibility as moderator for this list?
> > Cheers,
> > Peter
> >
> > -Original Message-
> > From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> > Behalf
> > Of Asaf Bartov
> > Sent: 10 September 2020 11:07
> > To: Wikimedia Mailing List
> > Subject: Re: [Wikimedia-l] Moderation notice
> >
> > Indeed, there is a potential conflict of interest here.  This is why I
> > strongly tend to leniency, *especially* when unacceptable discourse
> > coincides with criticism of the Foundation.  In this case, we received
> > requests from two list subscribers to moderate Dan.  We did so, while
> > underscoring that it was *not* for criticizing the Foundation.
> >
> > I think I have something of a track record of supporting open debate and
> of
> > encouraging and engaging with criticism of the Foundation.  I think
there
> > is indeed plenty to criticize; the Foundation is far from flawless.
> >
> > But people don't have to endure coarse language and vitriol at the same
> > time.  By all means, express disappointment, lack of confidence,
> suspicion,
> > whatever, but do it in a civil manner.  Dan can continue to do as well,
> of
> > course. I have already let one message of this through moderation.
> >
> > All that said, it would of course have been better if we had a couple of
> > list-admins more, without ties to the Foundation, so perhaps it is time
> to
> > recruit them.  Is anyone interested?
> >
> >A.
> >
> > On Thu, Sep 10, 2020 at 1:56 AM Todd Allen  wrote:
> >
> > > Erm, wait. He said what, "fart"?
> > >
> > > It's not a particularly good look for a WMF employee to be moderating
> > > someone critiquing the WMF, especially when, while their statement may
> > have
> > > been strongly worded, it used pretty mild language. This should either
> be
> > > undone, or at least decided upon by someone who doesn't work for WMF.
> > > That's a substantial conflict of interest.
> > >
> > > Todd
> > >
> > > On Wed, Sep 9, 2020 at 1:57 PM Asaf Bartov 
> > wrote:
> > >
> > > > Dear Wikimedians,
> > > >
> > > > List subscriber Dan Szymborski has been placed under moderation, due
> to
> > > > posts with unacceptable language.
> > > >
> > > > I remind everyone that criticism is appropriate and welcome on this
> > list,
> > > > so long as it remains civil and respectful of the people involved.
> > > >
> > > >Asaf (volunteer capacity)
> > > >on behalf of Wikimedia-l list moderators
> > > > --
> > > > Asaf Bartov 
> > > > ___
> > > > Wikimedia-l mailing list, guidelines at:
> > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > > > https://meta.wikimedia.org/wiki/Wikimedia-l
> > > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > > Unsubscribe:
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > > >
> > > ___
> > > Wikimedia-l mailing list, guidelines at:
> > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > > http

Re: [Wikimedia-l] A Universal Code of Conduct draft for review

2020-09-10 Thread Peter Southwood
Are those things not already covered by the terms of use?
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Amir Sarabadani
Sent: 10 September 2020 13:22
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] A Universal Code of Conduct draft for review

I just want to say while I agree IMO there's a growing disconnect in some
parts of WMF with the communities but it's not happening here. In fact it's
also the other way around. Some people in communities and some communities
in general have been growing too disconnected from the framework they are
working in. In the past two weeks I had to go head to head to two
communities on my volunteer developer/sysadmin role and I had to explain no
matter the consensus, you can't enable an extension that would bring down
(literally) not just your wiki but also 900 other ones or ban IP editing
which is widely considered against founding principles of Wikimedia.

Communities are self-governed but they have limits, you can't change the
privacy policy and give admins access to IP, you can't change copyright
policy or terms of use and I don't see any problem with adding one more
framework to make sure we would have a healthier movement (Each community
IMO should build on top of UCoC and won't just rely on it for conduct
policies but this would be the least, the base, the foundation, ..., you
get the idea). Thank you for coming to my TedTalk.

On Thu, Sep 10, 2020 at 11:45 AM Asaf Bartov  wrote:

> As you can see, Dan, your choice of imagery, appreciated and encouraged in
> less buttoned-up journalism, is offensive to some subscribers here.  Your
> strong criticism of the Foundation, on the other hand, is perfectly
> acceptable.
>
> As a professional wordsmith, I am confident you can continue to voice this
> criticism while employing milder imagery, or indeed dispensing with
> figurative language entirely.
>
> A.
>
> On Thu, Sep 10, 2020 at 12:31 PM Dan Szymborski 
> wrote:
>
> > I am absolutely flabbergasted that a generic reference of an organization
> > to flatulence, something we see in rated-G television isn't considered
> > "collegial" enough yet the actions that the WMF has taken over the last
> 18
> > months, many of which were pushed by people on this list *are* considered
> > collegial.
> >
> > If a joke that would be appropriate for a four-year-old leads to special
> > moderation, what action ought be taken for someone on the list pushing
> the
> > failure of a collaborative process that WMF is foisting upon the
> community?
> > One of the people "doth protesting too much" about the reference is also
> > someone banned from English Wikipedia for a whole litany of *actual*
> things
> > that took up countless hours of community time, including making legal
> > threats based on finding offense in normal Wikipedia actions.
> >
> > I am a longtime, accredited journalist, possibly even slightly respected
> in
> > the field -- though there's always that risk of Dunning-Kruger -- who has
> > written for a ton of outlets and there's not an editor in the world that
> > I've worked with who would've asked me to change the *very* gentle
> wording.
> > If anything, I was too mild. *I'm* grossly offended by the WMF's actions
> > over the last 18 months. *I'm* grossly offended by the perversion of a
> free
> > information movement being converted into a third-tier social media app.
> > *I'm* grossly offended by board policies that empower the vested, the
> > connected, the politically adept to judge the weak and the voiceless.
> *I'm*
> > grossly offended by the people here who cheerfully announce the board
> > arbitrarily changing board terms or that the community has no actual say
> in
> > what the *community* (not the board) built. The Wiki movement is far
> bigger
> > than the WMF; which is a good thing because I can't imagine it being
> > smaller than the board's self-dealing petty bourgeoisie affair.
> >
> > No, I didn't mean petit.
> >
> > Yet I don't call for anyone to be silenced because, well, disagreeing
> > vigorously is what adults are able to do.
> >
> > It matters not if this message is censored by the list overlords. One of
> > the few benefits of being a journalist is that combination of
> > self-righteousness and having myriad ways to prevent an opinion from
> being
> > suppressed on dubious grounds.
> >
> > Cheers,
> >
> > Dan
> >
> > On Thu, Sep 10, 2020 at 2:55 AM Natacha Rault via Wikimedia-l <
> > wikimedia-l@lists.wikimedia.org> wrote:
> >
> > > Hello,
> > >
> > > A code of conduct id something many of us have asked the WMF to write
> for
> > > many years. We are asking the WMF to take an active part in stopping
> > > abusive behaviors in our community.
> > >
> > > On fr wiki, many admins say they are tired of conflicts and that they
> did
> > > not enroll to deal with them. A code of conduct could help then take
> > action
> > > because it offers a frame.
> > >
> > > This is 

Re: [Wikimedia-l] Moderation notice

2020-09-10 Thread Peter Southwood
Good judgement is often such a subjective thing, Everyone thinks they have
it. A bit like the Dunning-Kruger effect.
Cheers, 
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Asaf Bartov
Sent: 10 September 2020 12:55
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Moderation notice

I would say first and foremost, good judgment. As measured by the person's
track record on-wiki and on this list.

Preferring to err on the side of caution, people under community sanctions,
or who have themselves been moderated for on-list misconduct, need not
apply.

   A.

On Thu, 10 Sep 2020, 12:58 Peter Southwood 
wrote:

> Asaf,
> What are the criteria for eligibility as moderator for this list?
> Cheers,
> Peter
>
> -Original Message-
> From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> Behalf
> Of Asaf Bartov
> Sent: 10 September 2020 11:07
> To: Wikimedia Mailing List
> Subject: Re: [Wikimedia-l] Moderation notice
>
> Indeed, there is a potential conflict of interest here.  This is why I
> strongly tend to leniency, *especially* when unacceptable discourse
> coincides with criticism of the Foundation.  In this case, we received
> requests from two list subscribers to moderate Dan.  We did so, while
> underscoring that it was *not* for criticizing the Foundation.
>
> I think I have something of a track record of supporting open debate and
of
> encouraging and engaging with criticism of the Foundation.  I think there
> is indeed plenty to criticize; the Foundation is far from flawless.
>
> But people don't have to endure coarse language and vitriol at the same
> time.  By all means, express disappointment, lack of confidence,
suspicion,
> whatever, but do it in a civil manner.  Dan can continue to do as well, of
> course. I have already let one message of this through moderation.
>
> All that said, it would of course have been better if we had a couple of
> list-admins more, without ties to the Foundation, so perhaps it is time to
> recruit them.  Is anyone interested?
>
>A.
>
> On Thu, Sep 10, 2020 at 1:56 AM Todd Allen  wrote:
>
> > Erm, wait. He said what, "fart"?
> >
> > It's not a particularly good look for a WMF employee to be moderating
> > someone critiquing the WMF, especially when, while their statement may
> have
> > been strongly worded, it used pretty mild language. This should either
be
> > undone, or at least decided upon by someone who doesn't work for WMF.
> > That's a substantial conflict of interest.
> >
> > Todd
> >
> > On Wed, Sep 9, 2020 at 1:57 PM Asaf Bartov 
> wrote:
> >
> > > Dear Wikimedians,
> > >
> > > List subscriber Dan Szymborski has been placed under moderation, due
to
> > > posts with unacceptable language.
> > >
> > > I remind everyone that criticism is appropriate and welcome on this
> list,
> > > so long as it remains civil and respectful of the people involved.
> > >
> > >Asaf (volunteer capacity)
> > >on behalf of Wikimedia-l list moderators
> > > --
> > > Asaf Bartov 
> > > ___
> > > Wikimedia-l mailing list, guidelines at:
> > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > > https://meta.wikimedia.org/wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > >
> > ___
> > Wikimedia-l mailing list, guidelines at:
> > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > https://meta.wikimedia.org/wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> >
>
>
> --
> Asaf Bartov 
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
>
>
> ___
> Wikimedia-l mailing lis

Re: [Wikimedia-l] Moderation notice

2020-09-10 Thread Peter Southwood
Asaf,
What are the criteria for eligibility as moderator for this list?
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Asaf Bartov
Sent: 10 September 2020 11:07
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Moderation notice

Indeed, there is a potential conflict of interest here.  This is why I
strongly tend to leniency, *especially* when unacceptable discourse
coincides with criticism of the Foundation.  In this case, we received
requests from two list subscribers to moderate Dan.  We did so, while
underscoring that it was *not* for criticizing the Foundation.

I think I have something of a track record of supporting open debate and of
encouraging and engaging with criticism of the Foundation.  I think there
is indeed plenty to criticize; the Foundation is far from flawless.

But people don't have to endure coarse language and vitriol at the same
time.  By all means, express disappointment, lack of confidence, suspicion,
whatever, but do it in a civil manner.  Dan can continue to do as well, of
course. I have already let one message of this through moderation.

All that said, it would of course have been better if we had a couple of
list-admins more, without ties to the Foundation, so perhaps it is time to
recruit them.  Is anyone interested?

   A.

On Thu, Sep 10, 2020 at 1:56 AM Todd Allen  wrote:

> Erm, wait. He said what, "fart"?
>
> It's not a particularly good look for a WMF employee to be moderating
> someone critiquing the WMF, especially when, while their statement may
have
> been strongly worded, it used pretty mild language. This should either be
> undone, or at least decided upon by someone who doesn't work for WMF.
> That's a substantial conflict of interest.
>
> Todd
>
> On Wed, Sep 9, 2020 at 1:57 PM Asaf Bartov  wrote:
>
> > Dear Wikimedians,
> >
> > List subscriber Dan Szymborski has been placed under moderation, due to
> > posts with unacceptable language.
> >
> > I remind everyone that criticism is appropriate and welcome on this
list,
> > so long as it remains civil and respectful of the people involved.
> >
> >Asaf (volunteer capacity)
> >on behalf of Wikimedia-l list moderators
> > --
> > Asaf Bartov 
> > ___
> > Wikimedia-l mailing list, guidelines at:
> > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > https://meta.wikimedia.org/wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
> >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>


-- 
Asaf Bartov 
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


-- 
This email has been checked for viruses by AVG.
https://www.avg.com



___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Moderation notice

2020-09-10 Thread Peter Southwood
Is there a record somewhere of what unacceptable language was used and
against what standard it was judged to be unacceptable? 
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Asaf Bartov
Sent: 09 September 2020 21:57
To: Wikimedia Mailing List
Subject: [Wikimedia-l] Moderation notice

Dear Wikimedians,

List subscriber Dan Szymborski has been placed under moderation, due to
posts with unacceptable language.

I remind everyone that criticism is appropriate and welcome on this list,
so long as it remains civil and respectful of the people involved.

   Asaf (volunteer capacity)
   on behalf of Wikimedia-l list moderators
-- 
Asaf Bartov 
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


-- 
This email has been checked for viruses by AVG.
https://www.avg.com



___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Institutional memory @ WMF

2020-08-28 Thread Peter Southwood
Maybe you could take on an official historian.
Cheers,
P

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Delphine Ménard
Sent: Wednesday, August 26, 2020 19:06
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Institutional memory @ WMF

Dan, you're right, it's a bit of all, formal and informal, and it is
important that we keep this process flexible. This allows us to adapt to
changing circumstances and a movement which well... moves. :-)

This fiscal year, Talent & Culture (HR) will be working on streamlining the
onboarding experience at the Foundation. This is why I joined the Talent &
Culture department, to coordinate this project and contribute my Wikimedia
experience. One of my mandates is to tackle the piece of onboarding that
takes into account our history as a movement, our common failures and
successes and the cultural pieces that are at the heart of our relationship
with each other (Individuals in the community, Foundation, affiliates,
external partners...).

Our movement is complex, and there are no amount of explanations that will
portray its richness. I will be working to make sure that new hires at the
Foundation know to ask the right questions at the right time and to the
right people to minimize errors. Of course, I want to set realistic
expectations, this will not happen in a day, nor will it happen in a year
only. My goal is to start a process that will change and evolve with time,
as does our movement.

If any of you have any questions about how we are working on this, or want
to contribute ideas, please talk to me offlist!

Best,

Delphine

Le mer. 26 août 2020 à 14:40, Dan Garry (Deskana)  a
écrit :

> On Wed, 26 Aug 2020 at 12:16, Strainu  wrote:
>
> > Thanks for the response Dan!
> >
> > A rigorous study is IMHO impossible, since we're lacking a rigorous
> > definition of the limits between WMF and community.
> >
>
> Absolutely agreed.
>
>
> > OK, but how is this done precisely? Are there written docs? Mentors?
> > Is cross-team help common? Or is this kept at the anecdotal level ("oh
> > yeah, you should also keep in mind..." )?
> >
>
> In my experience, all of the above. What is done exactly depends on the
> situation, but all of those things you've listed can and do happen,
> depending on the nature and size of the project, the people involved, and
> so on. People keep their eye out, through both formal and informal
> mechanisms, and help out if they think they can.
>
> I don't want to go into specific details, as I'm doing it purely from
> memory and might misremember things, and things might've changed since I
> left the WMF two years ago. To be clear, I'm not under any kind of
> non-disclosure agreement, I just don't want to be inaccurate.
>
> Dan
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>


-- 
*Delphine Ménard* (she/her)
Lead Orientation Specialist
User:Delphine_(WMF)
Wikimedia Foundation 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Institutional memory @ WMF

2020-08-28 Thread Peter Southwood
This is the sort of information that should be in the official history.
Cheers,
P

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf
Of Pete Forsyth
Sent: Wednesday, August 26, 2020 22:37
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Institutional memory @ WMF

Correction:

It's been pointed out that I erred in two significant ways when discussing
Katherine's background: Prior to becoming CEO, she was Chief Communications
Officer, which is a more senior position than the one I named; and, where I
said that prior to her time at WMF her career was "largely in
communications," I was simply mistaken. Her background is covered in her
Wikipedia bio, and is indeed quite varied.

I regret both of those errors.

Pete

>
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,



-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 



Re: [Wikimedia-l] Universal Code of Conduct Drafting Committee - Call for participation

2020-08-04 Thread Peter Southwood
Thanks,
P

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Christel Steigenberger
Sent: Tuesday, August 4, 2020 12:50
To: Wikimedia Mailing List
Subject: Re: [Wikimedia-l] Universal Code of Conduct Drafting Committee - Call 
for participation

Hi Peter,

Thank you for coming back to me with this clarifying question and comment.
And sorry for having broken the threading with my previous mail.

The community feedback will be mainly gathered on Meta, but we will try and
reach out to communities on different channels on- and off-wiki to
encourage them to take part in the process. We will also accept comments
that come in through other channels and post them in aggregate form on
Meta, if users are not comfortable going there themselves. While we are
already spending time and energy to prepare for outreach in different
languages, we are also aware of the fact that we cannot do this alone. We
appreciate every bit of help from you and others on the mailing list, to
spread the word that the community comment period will be between August 24
and September 23 and to help us translate the content in more languages
than we alone might be able to do. If you know of good channels to spread
the word, or know about people willing and able to translate the content
into lesser known languages, please let us know!

Within the drafting committee we have people speaking 12 different
languages that I am aware of - and possibly more. Besides English and
Arabic, those are five European, three African and two Indic languages. In
addition we have hired facilitators from the community who speak Arabic,
Georgian, Persian, Russian and Swahili and we will be getting help from the
translator’s pool in our communications department.

Please always feel free to let us know of other ideas to improve the
process for community feedback gathering!

Best regards,
Christel

Christel Steigenberger (she/her)

Trust and Safety Specialist

Wikimedia Foundation <https://wikimediafoundation.org/>



On Sat, Aug 1, 2020 at 8:44 PM Peter Southwood 
wrote:

> Hi Christel
> I am glad to hear that, and I hope that proper consultation will occur
> with all potentially affected parties, in places where they can comment and
> point out problems on user friendly or at least familiar software, over at
> least a reasonably representative range of languages, and with sufficient
> time to discuss issues without  an excessively tight deadline.
> Speaking of which, what is the language spread  of the drafting committee?
> Cheers,
> Peter
>
> -Original Message-
> From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> Behalf Of Christel Steigenberger
> Sent: 31 July 2020 17:48
> To: wikimedia-l@lists.wikimedia.org
> Subject: Re: [Wikimedia-l] Universal Code of Conduct Drafting Committee -
> Call for participation
>
> Hi Peter,
>
> I hear and understand your worries. I’d like to reassure you that we are
> very aware of the fact that no single person and no selected group of
> people can speak for the community as a whole. This is one of the big
> challenges all such efforts have to tackle. Representation here is not
> meant in the sense of legal or political representation. But by speaking
> for themselves, we hope that volunteers and staff coming from different
> language communities, holding different roles within the movement and
> bringing different experiences of engagement with the movement into the
> process will at least bring diverse valuable perspectives to the creation
> of the draft for the Universal Code of Conduct.
>
> Before they start drafting, they are already now working their way through
> a reading kit which will make them familiar with the input from the
> movement strategy process as well as prior community consultations our team
> has done at regional Wikimedia conferences and Wikimania as well as through
> facilitated conversations with 19 different language communities. The data
> is published on Meta here
>
> https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Community_feedback_at_conferences
> and here
>
> https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Initial_2020_Consultations
> .
> This community feedback will inform the drafting process.
>
> This draft will then be brought to the communities for review starting
> August 24, as outlined in the timeline here:
> https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct#Timeline. We are
> still looking for ways to make more people aware of this important part of
> the process. Please spread the word of this upcoming community comment
> period, to help us get wider participation!
>
> I hope the above makes sense to you, looking forward to your engagement
> with the draft end of August and in September,
>
> Christel Steig

Re: [Wikimedia-l] Universal Code of Conduct Drafting Committee - Call for participation

2020-08-01 Thread Peter Southwood
Hi Christel
I am glad to hear that, and I hope that proper consultation will occur with all 
potentially affected parties, in places where they can comment and point out 
problems on user friendly or at least familiar software, over at least a 
reasonably representative range of languages, and with sufficient time to 
discuss issues without  an excessively tight deadline.
Speaking of which, what is the language spread  of the drafting committee?
Cheers,
Peter

-Original Message-
From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On Behalf Of 
Christel Steigenberger
Sent: 31 July 2020 17:48
To: wikimedia-l@lists.wikimedia.org
Subject: Re: [Wikimedia-l] Universal Code of Conduct Drafting Committee - Call 
for participation

Hi Peter,

I hear and understand your worries. I’d like to reassure you that we are
very aware of the fact that no single person and no selected group of
people can speak for the community as a whole. This is one of the big
challenges all such efforts have to tackle. Representation here is not
meant in the sense of legal or political representation. But by speaking
for themselves, we hope that volunteers and staff coming from different
language communities, holding different roles within the movement and
bringing different experiences of engagement with the movement into the
process will at least bring diverse valuable perspectives to the creation
of the draft for the Universal Code of Conduct.

Before they start drafting, they are already now working their way through
a reading kit which will make them familiar with the input from the
movement strategy process as well as prior community consultations our team
has done at regional Wikimedia conferences and Wikimania as well as through
facilitated conversations with 19 different language communities. The data
is published on Meta here
https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Community_feedback_at_conferences
and here
https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Initial_2020_Consultations.
This community feedback will inform the drafting process.

This draft will then be brought to the communities for review starting
August 24, as outlined in the timeline here:
https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct#Timeline. We are
still looking for ways to make more people aware of this important part of
the process. Please spread the word of this upcoming community comment
period, to help us get wider participation!

I hope the above makes sense to you, looking forward to your engagement
with the draft end of August and in September,

Christel Steigenberger (she/her)

Trust and Safety Specialist

Wikimedia Foundation 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


-- 
This email has been checked for viruses by AVG.
https://www.avg.com


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


  1   2   3   4   5   6   >