Re: [Wikimedia-l] Re: [All-affiliates] Re: Community response to WMF layoffs and labor concerns
Pine W via Wikitech-l <[email protected]> Sat, 23 May 2026 12:01:11 -0700
| Newsgroups | gmane.science.linguistics.wikipedia.technical,gmane.org.wikimedia.foundation |
|---|---|
| Message-ID | <CAF=dyJhUOp+JUvE7oysMQc5tXeq23R_qAE5UWY=Y_i6wQD2FzA@mail.gmail.com> |
--===============0800484328853688368== Content-Type: multipart/alternative; boundary="000000000000a1ab93065280c457" --000000000000a1ab93065280c457 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (removed wikimediaannounce-l from the distribution) Hi Selena, Thank you for engaging at https://meta.wikimedia.org/wiki/Talk:Community_Wishlist#c-SDeckelmann-WMF-2= 0260522160700-Update_from_Selena. I will understand if there are no further updates until next week. Indeed, I highly encourage people to take occasional time for their personal needs = ( burnout <https://en.wikipedia.org/wiki/Burnout_(disambiguation)> can be a problem), and also for US-based staff for the Memorial Day holiday <https://en.wikipedia.org/wiki/Memorial_Day>. When you return next week, I'd appreciate you commenting further on concerns being raised regarding the organizational restructuring and the Community Wishlist <https://meta.wikimedia.org/wiki/Community_Wishlist> (I understand trying to improve the Wishlist process, although disbanding the team and displacing its members before there's consensus on what to do next might have been the wrong order of operations), but also a troubling cluster of issues in P&T this year. 1. 10 February 2026: "etherpad.wikimedia.org cleanup: April 30, Save your pads!": https://lists.wikimedia.org/hyperkitty/list/[email protected]/= thread/CMYID3FRNL7OKUNEH3O3OTGT6UQSQN3X/ 2. 5 March 2026: "March 2026 User Script Incident": https://meta.wikimedia.org/wiki/Wikimedia_Foundation/Product_and_Technology= /Product_Safety_and_Integrity/March_2026_User_Script_Incident 3. 30 March 2026: "Mass-abandonment of many 2+-year-old Gerrit patches to mediawiki/core": https://lists.wikimedia.org/hyperkitty/list/[email protected]/= thread/56NSY3OYOIBKCBRLLL3I2V3OYSVZTTQF/ 4. Concerns being expressed regarding this reorganization. Each of these events in isolation is concerning. The clustering of them in the space of a few months makes me wonder if there are deeper issues which should be addressed by the C-suite <https://meta.wikimedia.org/wiki/Wikimedia_Foundation/Executive_and_Leaders= hip_teams>. I would appreciate hearing your thoughts on that, perhaps in a separate thread. Also, if you think it would help, I'm willing to schedule a Wikimed= ia Caf=C3=A9 <https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9> session to = for a public live discussion of any or all of the above. Thank you, Pine=F0=9F=8C=B2 On Sat, May 23, 2026 at 7:24=E2=80=AFAM James Heilman via Wikimedia-l < [email protected]> wrote: > One issue with trying to move community tech work outside the foundation > is how do we get improvements approved by those within the foundation? We > for example have consensus for MP4 upload and conversion on Commons via t= he > upload wizard. But are waiting now on the WMF, maybe legal team. > > J > > > Sent from Gmail Mobile > > On Sat, May 23, 2026 at 03:57 Gnangarra via Wikimedia-l < > [email protected]> wrote: > >> What I find troubling is that the Community Tech caught a lot of tasks >> that have fallen through the gaps between teams or when teams have been >> remodelled and staff move to new areas. >> >> What is most troubling is that the team being laid off and told to apply >> for new positions within the new hiring framework that mean some of thes= e >> will be ineligible under the current hiring policies. When those change >> were announced it was said that existing employees would not be affect y= et >> here we are only a couple of months past that and it to being applied to >> existing employees. >> >> While 10,000's of are just volunteers every staff loss is painful >> especially highly experienced technical staff because we know that it th= e >> front end and volunteers who sufffer from these changes. If the new CEO >> wants to rattle employee cages dont do it to the detriment on the commun= ity >> thats make these project viable. >> >> On Sat, 23 May 2026 at 03:14, Kimmo Virtanen via Wikimedia-l < >> [email protected]> wrote: >> >>> > Many of you have likely already seen the Wikimedia Foundation's >>> announcement that the Community Tech team is being dissolved and that f= ive >>> engineers and one manager are losing their roles as part of a restructu= ring >>> of the Community Wishlist process. >>> >>> Based on previous years' experience, WMF software development teams >>> focus on specific tasks and generally avoid tasks outside their immedia= te >>> focus. This means for examplke that extensions such as Maps and Upload >>> Wizard largely lost support because the responsible team was dissolved.= The >>> Community Tech team also handled tasks that did not specifically fall u= nder >>> any other team's responsibility. (such as >>> https://meta.wikimedia.org/wiki/Community_Wishlist but not only that, >>> for example, the Upload Wizard was afaik picked up by community tech) >>> >>> In any case I would have liked to see that number of Community Tech >>> people would have increase instead of decrease. >>> >>> Br, >>> -- Kimmo Virtanen, Zache >>> >>> On Fri, May 22, 2026 at 9:15=E2=80=AFPM Jaluj Wikipedista via All-affil= iates < >>> [email protected]> wrote: >>> >>>> I understand the anguish of those who will lose a paid job but I don't >>>> see why the volunteers who have never been paid for their work and are= the >>>> ones who build wikipedia and sister projects should be bothered that >>>> Community Tech will become a cross-team program rather than a dedicate= d >>>> team. >>>> >>>> El vie, 22 may 2026 a las 14:04, James Heilman via All-affiliates (< >>>> [email protected]>) escribi=C3=B3: >>>> >>>>> I always thought we should double the community tech team. One for >>>>> Wikipedia and one for the sister projects. >>>>> >>>>> I guess the question is should the community try to take on this work= ? >>>>> With movement funds of course. >>>>> >>>>> J >>>>> >>>>> >>>>> Sent from Gmail Mobile >>>>> >>>>> On Thu, May 21, 2026 at 22:30 Nemoralis via All-affiliates < >>>>> [email protected]> wrote: >>>>> >>>>>> Fellow Wikimedians, >>>>>> >>>>>> Many of you have likely already seen the Wikimedia Foundation's >>>>>> announcement that the Community Tech team is being dissolved and tha= t five >>>>>> engineers and one manager are losing their roles as part of a restru= cturing >>>>>> of the Community Wishlist process. >>>>>> >>>>>> The official explanation is that Community Tech will become a >>>>>> cross-team "program" rather than a dedicated team, and that this mod= el will >>>>>> supposedly allow more teams to work on community wishes. However, ma= ny >>>>>> editors, functionaries, and technical contributors across Wikimedia >>>>>> projects have raised serious concerns about both the substance and t= iming >>>>>> of this decision. >>>>>> >>>>>> Several issues are driving alarm within the community: >>>>>> >>>>>> =E2=80=A2 The Community Tech team was one of the few WMF engineering= groups >>>>>> explicitly focused on community-requested technical work. >>>>>> =E2=80=A2 The engineers affected include highly experienced contribu= tors with >>>>>> deep institutional and community knowledge, including former steward= s and >>>>>> longtime technical volunteers. >>>>>> =E2=80=A2 WMF leadership has stated that this is not a budget reduct= ion, >>>>>> which raises the question of why layoffs were necessary at all inste= ad of >>>>>> reassignment. >>>>>> =E2=80=A2 The restructuring was announced amid ongoing organizing ef= forts >>>>>> connected to Wiki Workers United (WWU), leading many contributors to= fear >>>>>> retaliation or union-busting behavior, regardless of WMF denials. >>>>>> =E2=80=A2 There is currently little concrete information about >>>>>> accountability, staffing, or ownership under the new =E2=80=9Cprogra= m=E2=80=9D structure. >>>>>> >>>>>> This is no longer being viewed by many contributors as merely an >>>>>> internal staffing change. It is increasingly seen as part of a broad= er >>>>>> pattern of disconnect between WMF leadership and the volunteer commu= nities >>>>>> that build and maintain Wikimedia projects. >>>>>> >>>>>> In response, editors have begun organizing solidarity actions and a >>>>>> strike mandate petition expressing willingness to support Wiki Worke= rs >>>>>> United if collective action becomes necessary. >>>>>> >>>>>> The petition is not itself a strike. It is a statement that >>>>>> contributors are prepared to stand in solidarity with Wikimedia work= ers and >>>>>> defend community accountability if requested. >>>>>> >>>>>> You can read the ongoing discussions here: >>>>>> >>>>>> - >>>>>> >>>>>> >>>>>> https://meta.wikimedia.org/wiki/Talk:Community_Wishlist#May_20_up= date >>>>>> - >>>>>> >>>>>> https://w.wiki/Nt5V >>>>>> >>>>>> If you are concerned about: >>>>>> >>>>>> - >>>>>> >>>>>> the future of community-driven technical development, >>>>>> - >>>>>> >>>>>> the treatment of Wikimedia staff, >>>>>> - >>>>>> >>>>>> possible anti-union retaliation, >>>>>> - >>>>>> >>>>>> or the growing disconnect between WMF leadership and the editing >>>>>> community, >>>>>> >>>>>> please consider joining the discussion, spreading awareness, and >>>>>> signing the solidarity petition. >>>>>> >>>>>> Take action: https://wikiworkersunited.org/take-action-community/ >>>>>> Sign the petition: https://w.wiki/Nt5n >>>>>> >>>>>> In solidarity, >>>>>> Nemoralis >>>>>> >>>>>> _______________________________________________ >>>>>> All-affiliates mailing list -- [email protected] >>>>>> To unsubscribe send an email to >>>>>> [email protected] >>>>>> >>>>> _______________________________________________ >>>>> All-affiliates mailing list -- [email protected] >>>>> To unsubscribe send an email to >>>>> [email protected] >>>>> >>>> _______________________________________________ >>>> All-affiliates mailing list -- [email protected] >>>> To unsubscribe send an email to >>>> [email protected] >>>> >>> _______________________________________________ >>> Wikimedia-l mailing list -- [email protected], 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/[email protected]= .org/message/VIGJ4DD5NTO5CWF2ZJNTEK5KTYPSZIDV/ >>> To unsubscribe send an email to [email protected] >> >> >> >> -- >> Boodarwun >> Gnangarra >> 'ngany dabakarn koorliny arn boodjera dardon nlangan Nyungar koortabodja= r' >> >> _______________________________________________ >> Wikimedia-l mailing list -- [email protected], 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/[email protected].= org/message/JWUBZBE34NRR73U7VK7AD2QZ22DDET7Y/ >> To unsubscribe send an email to [email protected] > > _______________________________________________ > Wikimedia-l mailing list -- [email protected], 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/[email protected]= rg/message/NTIEESDW3L7MIACDONMWAF2JB6LG7YQI/ > To unsubscribe send an email to [email protected] --000000000000a1ab93065280c457 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail_signature" data-smart= mail=3D"gmail_signature"><div dir=3D"ltr"><div> <div>(removed=C2=A0<span class=3D"gmail-gI"><span>wikimediaannounce-l from = the distribution)</span></span></div><div><span class=3D"gmail-gI"><span><b= r></span></span></div><div>Hi Selena,</div><div><br></div><div>Thank you fo= r engaging at=C2=A0<a href=3D"https://meta.wikimedia.org/wiki/Talk:Communit= y_Wishlist#c-SDeckelmann-WMF-20260522160700-Update_from_Selena">https://met= a.wikimedia.org/wiki/Talk:Community_Wishlist#c-SDeckelmann-WMF-202605221607= 00-Update_from_Selena</a>. I will understand if there are no further update= s until next week. Indeed, I highly encourage people to take occasional tim= e for their personal needs (<a href=3D"https://en.wikipedia.org/wiki/Burnou= t_(disambiguation)">burnout</a>=C2=A0can be a problem), and also for US-bas= ed staff for the <a href=3D"https://en.wikipedia.org/wiki/Memorial_Day">Mem= orial Day holiday</a>.</div><div><br></div><div>When you return next week, = I'd appreciate you commenting=C2=A0further=C2=A0on concerns being raise= d regarding the organizational restructuring and the <a href=3D"https://met= a.wikimedia.org/wiki/Community_Wishlist">Community Wishlist</a> (I understa= nd trying to improve the Wishlist process, although disbanding the team and= displacing its members before there's consensus on what to do next mig= ht have been the wrong order of operations), but also a troubling cluster o= f issues in P&T this year.</div><div><br></div><div>1. 10 February 2026= : "<a href=3D"http://etherpad.wikimedia.org">etherpad.wikimedia.org</a= > cleanup: April 30, Save your=20 pads!": <a href=3D"https://lists.wikimedia.org/hyperkitty/list/wikitec= [email protected]/thread/CMYID3FRNL7OKUNEH3O3OTGT6UQSQN3X/">https://l= ists.wikimedia.org/hyperkitty/list/[email protected]/thread/CM= YID3FRNL7OKUNEH3O3OTGT6UQSQN3X/</a></div><div>2. 5 March 2026: "<span = lang=3D"en" dir=3D"ltr"><span class=3D"gmail-mw-page-title-main">March 2026= User Script Incident":</span></span>=C2=A0<a href=3D"https://meta.wik= imedia.org/wiki/Wikimedia_Foundation/Product_and_Technology/Product_Safety_= and_Integrity/March_2026_User_Script_Incident">https://meta.wikimedia.org/w= iki/Wikimedia_Foundation/Product_and_Technology/Product_Safety_and_Integrit= y/March_2026_User_Script_Incident </a></div><div>3. 30 March 2026: "Mass-abandonment of many 2+-year-old= Gerrit patches to=20 mediawiki/core": <a href=3D"https://lists.wikimedia.org/hyperkitty/lis= t/[email protected]/thread/56NSY3OYOIBKCBRLLL3I2V3OYSVZTTQF/">= https://lists.wikimedia.org/hyperkitty/list/[email protected]/= thread/56NSY3OYOIBKCBRLLL3I2V3OYSVZTTQF/</a></div><div></div><div>4. Concer= ns being expressed regarding this reorganization.</div><div><br></div><div>= Each of these events in isolation is concerning. The clustering of them in = the space of a few months makes me wonder if there are deeper issues which = should be addressed by the <a href=3D"https://meta.wikimedia.org/wiki/Wikim= edia_Foundation/Executive_and_Leadership_teams">C-suite</a>. I would apprec= iate hearing your thoughts on that, perhaps in a separate thread. Also, if = you think it would help, I'm willing to schedule a=C2=A0<a href=3D"http= s://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9">Wikimedia Caf=C3=A9</a> se= ssion to for a public live discussion of any or all of the above.</div><div= ><br></div><div>Thank you,</div></div><div>Pine=F0=9F=8C=B2</div></div></di= v></div></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir= =3D"ltr" class=3D"gmail_attr">On Sat, May 23, 2026 at 7:24=E2=80=AFAM James= Heilman via Wikimedia-l <<a href=3D"mailto:[email protected].= org">[email protected]</a>> wrote:<br></div><blockquote cl= ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid= rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">One issue with trying= to move community tech work outside the foundation is how do we get improv= ements approved by those within the foundation? We for example have consens= us for MP4 upload and conversion on Commons via the upload wizard. But are = waiting now on the WMF, maybe legal team.</div><div dir=3D"auto"><br></div>= <div dir=3D"auto">J</div><div><br clear=3D"all"><br clear=3D"all"><div><div= dir=3D"ltr" class=3D"gmail_signature">Sent from Gmail Mobile</div></div></= div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att= r">On Sat, May 23, 2026 at 03:57 Gnangarra via Wikimedia-l <<a href=3D"m= ailto:[email protected]" target=3D"_blank">wikimedia-l@lists.= wikimedia.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" sty= le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi= ng-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-fa= mily:georgia,serif" dir=3D"auto">What I find troubling is that the Communit= y Tech caught a lot of tasks that have fallen through the gaps between team= s or when teams have been remodelled and staff move to new areas.</div><div= class=3D"gmail_default" style=3D"font-family:georgia,serif"><br></div><div= class=3D"gmail_default" style=3D"font-family:georgia,serif">What is most t= roubling is that the team being laid off and told to apply for new position= s within the new hiring framework that mean some of these will be ineligibl= e=C2=A0under the current hiring policies. When those change were announced = it was said that existing=C2=A0employees would not be affect yet here we ar= e only a couple of months past that and it to being applied to existing=C2= =A0employees.<br><br>While 10,000's of are just volunteers every staff = loss is painful especially highly experienced technical staff because we kn= ow that it the front end and volunteers who sufffer=C2=A0from these changes= .=C2=A0 If the new CEO wants to rattle employee cages dont do it to the det= riment=C2=A0on the community thats make these project viable.</div></div><b= r><div class=3D"gmail_quote"></div><div class=3D"gmail_quote"><div dir=3D"l= tr" class=3D"gmail_attr">On Sat, 23 May 2026 at 03:14, Kimmo Virtanen via W= ikimedia-l <<a href=3D"mailto:[email protected]" target=3D= "_blank">[email protected]</a>> wrote:<br></div></div><div= class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0p= x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"></= blockquote></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"><div dir=3D"ltr">> Many of you have likely already se= en the Wikimedia Foundation's announcement that the Community Tech team= is being dissolved and that five engineers and one manager are losing thei= r roles as part of a restructuring of the Community Wishlist process.<div><= br></div><div>Based on previous years' experience, WMF software develop= ment teams focus on specific tasks and generally avoid tasks outside their = immediate focus. This means for examplke that extensions=C2=A0such as Maps = and Upload Wizard=C2=A0largely lost support because the responsible team wa= s dissolved. The Community Tech team also handled tasks that did not specif= ically fall under any other team's responsibility. =C2=A0(such as=C2=A0= <a href=3D"https://meta.wikimedia.org/wiki/Community_Wishlist" target=3D"_b= lank">https://meta.wikimedia.org/wiki/Community_Wishlist</a> but not only t= hat, for example, the Upload Wizard was afaik picked up by community tech)<= /div><div><br></div><div>In any case I would have liked to see that number = of Community Tech people would have increase instead of decrease.</div><div= ><br></div><div>Br,</div><div>-- Kimmo Virtanen, Zache</div></div><br><div = class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 22,= 2026 at 9:15=E2=80=AFPM Jaluj Wikipedista via All-affiliates <<a href= =3D"mailto:[email protected]" target=3D"_blank">all-affili= [email protected]</a>> wrote:<br></div><blockquote class=3D"gmail= _quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204= ,204);padding-left:1ex"><div dir=3D"ltr">I understand the anguish of those = who will lose a paid job but I don't see why the volunteers who have ne= ver been paid for their work and are the ones who build wikipedia and siste= r projects should be bothered that Community Tech will become a cross-team = program rather than a dedicated team.=C2=A0</div><br><div class=3D"gmail_qu= ote"><div dir=3D"ltr" class=3D"gmail_attr">El vie, 22 may 2026 a las 14:04,= James Heilman via All-affiliates (<<a href=3D"mailto:all-affiliates@lis= ts.wikimedia.org" target=3D"_blank">[email protected]</a>&= gt;) escribi=C3=B3:<br></div><blockquote class=3D"gmail_quote" style=3D"mar= gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1= ex"><div dir=3D"auto">I always thought we should double the community tech = team. One for Wikipedia and one for the sister projects.</div><div dir=3D"a= uto"><br></div><div dir=3D"auto">I guess the question is should the communi= ty try to take on this work? With movement funds of course.</div><div dir= =3D"auto"><br></div><div dir=3D"auto">J</div><div><br clear=3D"all"><br cle= ar=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signature">Sent from Gmail = Mobile</div></div></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr= " class=3D"gmail_attr">On Thu, May 21, 2026 at 22:30 Nemoralis via All-affi= liates <<a href=3D"mailto:[email protected]" target=3D"= _blank">[email protected]</a>> wrote:<br></div><blockqu= ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px= solid rgb(204,204,204);padding-left:1ex"><u></u> =20 =20 =20 <div> <p>Fellow Wikimedians,</p> <p>Many of you have likely already seen the Wikimedia Foundation's announcement that the Community Tech team is being dissolved and that five engineers and one manager are losing their roles as part of a restructuring of the Community Wishlist process.</p> <p>The official explanation is that Community Tech will become a cross-team "program" rather than a dedicated team, and that= this model will supposedly allow more teams to work on community wishes. However, many editors, functionaries, and technical contributors across Wikimedia projects have raised serious concerns about both the substance and timing of this decision.</p> <p>Several issues are driving alarm within the community:</p> <p>=E2=80=A2 The Community Tech team was one of the few WMF engineering groups explicitly focused on community-requested technical work.<br> =E2=80=A2 The engineers affected include highly experienced contribut= ors with deep institutional and community knowledge, including former stewards and longtime technical volunteers.<br> =E2=80=A2 WMF leadership has stated that this is not a budget reducti= on, which raises the question of why layoffs were necessary at all instead of reassignment.<br> =E2=80=A2 The restructuring was announced amid ongoing organizing eff= orts connected to Wiki Workers United (WWU), leading many contributors to fear retaliation or union-busting behavior, regardless of WMF denials.<br> =E2=80=A2 There is currently little concrete information about accountability, staffing, or ownership under the new =E2=80=9Cprogram= =E2=80=9D structure.</p> <p>This is no longer being viewed by many contributors as merely an internal staffing change. It is increasingly seen as part of a broader pattern of disconnect between WMF leadership and the volunteer communities that build and maintain Wikimedia projects.</p> <p>In response, editors have begun organizing solidarity actions and a strike mandate petition expressing willingness to support Wiki Workers United if collective action becomes necessary.</p> <p>The petition is not itself a strike. It is a statement that contributors are prepared to stand in solidarity with Wikimedia workers and defend community accountability if requested.</p> <p>You can read the ongoing discussions here:</p> <ul> <li> <p><a href=3D"https://meta.wikimedia.org/wiki/Talk:Community_Wishli= st#May_20_update" target=3D"_blank">https://meta.wikimedia.org/wiki/Talk:Co= mmunity_Wishlist#May_20_update</a></p> </li> <li> <p><a href=3D"https://w.wiki/Nt5V" target=3D"_blank">https://w.wiki= /Nt5V</a></p> </li> </ul> <p>If you are concerned about:</p> <ul> <li> <p>the future of community-driven technical development,</p> </li> <li> <p>the treatment of Wikimedia staff,</p> </li> <li> <p>possible anti-union retaliation,</p> </li> <li> <p>or the growing disconnect between WMF leadership and the editing community,</p> </li> </ul> <p>please consider joining the discussion, spreading awareness, and signing the solidarity petition.<br> <br> Take action: <a href=3D"https://wikiworkersunited.org/take-action-com= munity/" target=3D"_blank">https://wikiworkersunited.org/take-action-commun= ity/</a><br> Sign the petition: <a href=3D"https://w.wiki/Nt5n" target=3D"_blank">= https://w.wiki/Nt5n</a></p> <p>In solidarity,<br> Nemoralis</p> <br> </div> _______________________________________________<br> All-affiliates mailing list -- <a href=3D"mailto:[email protected]= edia.org" target=3D"_blank">[email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:all-affiliates-leave@list= s.wikimedia.org" target=3D"_blank">[email protected]= </a><br> </blockquote></div></div> _______________________________________________<br> All-affiliates mailing list -- <a href=3D"mailto:[email protected]= edia.org" target=3D"_blank">[email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:all-affiliates-leave@list= s.wikimedia.org" target=3D"_blank">[email protected]= </a><br> </blockquote></div> _______________________________________________<br> All-affiliates mailing list -- <a href=3D"mailto:[email protected]= edia.org" target=3D"_blank">[email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:all-affiliates-leave@list= s.wikimedia.org" target=3D"_blank">[email protected]= </a><br> </blockquote></div></blockquote></div><div class=3D"gmail_quote"><blockquot= e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s= olid rgb(204,204,204);padding-left:1ex"> _______________________________________________<br> Wikimedia-l mailing list -- <a href=3D"mailto:[email protected]= rg" target=3D"_blank">[email protected]</a>, guidelines at: <= a href=3D"https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines" rel=3D"= noreferrer" target=3D"_blank">https://meta.wikimedia.org/wiki/Mailing_lists= /Guidelines</a> and <a href=3D"https://meta.wikimedia.org/wiki/Wikimedia-l"= rel=3D"noreferrer" target=3D"_blank">https://meta.wikimedia.org/wiki/Wikim= edia-l</a><br> Public archives at <a href=3D"https://lists.wikimedia.org/hyperkitty/list/w= [email protected]/message/VIGJ4DD5NTO5CWF2ZJNTEK5KTYPSZIDV/" r= el=3D"noreferrer" target=3D"_blank">https://lists.wikimedia.org/hyperkitty/= list/[email protected]/message/VIGJ4DD5NTO5CWF2ZJNTEK5KTYPSZI= DV/</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]= ikimedia.org" target=3D"_blank">[email protected]</a></= blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=3D= "gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_sign= ature"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">= <div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di= r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font-family:georg= ia,serif;color:rgb(34,34,34)"><font style=3D"vertical-align:inherit;font-fa= mily:georgia,serif;color:rgb(34,34,34)"><font style=3D"vertical-align:inher= it;font-family:georgia,serif;color:rgb(34,34,34)"><font style=3D"vertical-a= lign:inherit;font-family:georgia,serif;color:rgb(34,34,34)"><font style=3D"= vertical-align:inherit;font-family:georgia,serif;color:rgb(34,34,34)">Booda= rwun</font></font></font></font><br><font style=3D"vertical-align:inherit;f= ont-family:georgia,serif;color:rgb(34,34,34)"><font style=3D"vertical-align= :inherit;font-family:georgia,serif;color:rgb(34,34,34)"><font style=3D"vert= ical-align:inherit;font-family:georgia,serif;color:rgb(34,34,34)"><font sty= le=3D"vertical-align:inherit;font-family:georgia,serif;color:rgb(34,34,34)"= >Gnangarra</font></font></font></font></div><div style=3D"font-family:georg= ia,serif;color:rgb(34,34,34)"><font style=3D"vertical-align:inherit;font-fa= mily:georgia,serif;color:rgb(34,34,34)"><font style=3D"vertical-align:inher= it;font-family:georgia,serif;color:rgb(34,34,34)"><font style=3D"vertical-a= lign:inherit;font-family:georgia,serif;color:rgb(34,34,34)"><font style=3D"= vertical-align:inherit;font-family:georgia,serif;color:rgb(34,34,34)">'= ngany dabakarn koorliny arn boodjera dardon nlangan Nyungar koortabodjar= 9;</font></font></font></font></div></div><div><i style=3D"text-align:cente= r">=C2=A0=C2=A0</i></div></div></div></div></div></div></div></div></div></= div></div></div> _______________________________________________<br> Wikimedia-l mailing list -- <a href=3D"mailto:[email protected]= rg" target=3D"_blank">[email protected]</a>, guidelines at: <= a href=3D"https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines" rel=3D"= noreferrer" target=3D"_blank">https://meta.wikimedia.org/wiki/Mailing_lists= /Guidelines</a> and <a href=3D"https://meta.wikimedia.org/wiki/Wikimedia-l"= rel=3D"noreferrer" target=3D"_blank">https://meta.wikimedia.org/wiki/Wikim= edia-l</a><br> Public archives at <a href=3D"https://lists.wikimedia.org/hyperkitty/list/w= [email protected]/message/JWUBZBE34NRR73U7VK7AD2QZ22DDET7Y/" r= el=3D"noreferrer" target=3D"_blank">https://lists.wikimedia.org/hyperkitty/= list/[email protected]/message/JWUBZBE34NRR73U7VK7AD2QZ22DDET= 7Y/</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]= ikimedia.org" target=3D"_blank">[email protected]</a></= blockquote></div></div> _______________________________________________<br> Wikimedia-l mailing list -- <a href=3D"mailto:[email protected]= rg" target=3D"_blank">[email protected]</a>, guidelines at: <= a href=3D"https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines" rel=3D"= noreferrer" target=3D"_blank">https://meta.wikimedia.org/wiki/Mailing_lists= /Guidelines</a> and <a href=3D"https://meta.wikimedia.org/wiki/Wikimedia-l"= rel=3D"noreferrer" target=3D"_blank">https://meta.wikimedia.org/wiki/Wikim= edia-l</a><br> Public archives at <a href=3D"https://lists.wikimedia.org/hyperkitty/list/w= [email protected]/message/NTIEESDW3L7MIACDONMWAF2JB6LG7YQI/" r= el=3D"noreferrer" target=3D"_blank">https://lists.wikimedia.org/hyperkitty/= list/[email protected]/message/NTIEESDW3L7MIACDONMWAF2JB6LG7Y= QI/</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]= ikimedia.org" target=3D"_blank">[email protected]</a></= blockquote></div> --000000000000a1ab93065280c457-- --===============0800484328853688368== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Wikitech-l mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ --===============0800484328853688368==--