• lij: Agiuttine a tradue inta to lengua.
• en: Requests for the bot flag should be made on this page. This wiki uses the standard bot policy, and allows global bots and automatic approval of certain types of bots. Other bots should apply below, and then request access from a steward if there is no objection.

First off, my apologies for the English--I don't know Ligurian and only have a vague understanding of Italian (but I know Spanish pretty well if anyone needs to converse in that). User:MF-Warburg seems to have imported most of the content but files like mul:File:Chittarrin-1772.jpg are still at the old Wikisource. Can the community confirm that you will accept these files? Koavf (discuscioin) 01:59, 21 lùg 2020 (CEST)Rispondi

m:Requests_for_new_languages/Wikisource_Ligurian#Import. Looks like this is being discussed on Meta. I'll review the copyright guidelines at c:. Thanks. Koavf (discuscioin) 02:07, 21 lùg 2020 (CEST)Rispondi

Al momento chi può usare Speçiale:Importa (senza poter importare tramite caricamento di file) può importare solo da Meta e da Commons. Io proporrei di aggiungere alla lista delle Wiki da cui è possibile importare anche Itwikisource, lijwiki, oldwikisource, frwikisource, enwikisource e vec.wikisource. --Samuele2002 (discuscioin) 09:54, 21 lùg 2020 (CEST)Rispondi

It makes much sense to do so; I was just coming here to propose you do this as well. Especially because it will probably be a frequent need to import templates from it.ws or others. --MF-Warburg (discuscioin) 14:47, 30 lùg 2020 (CEST)Rispondi

(IT) Ciao Samuele, per me va benissimo perché è utile! Concordo anche con quello che dice MF-Warburg.

(EN) Hi Samuele, for me it's fine because it's useful! I also agree what MF-Warburg says. --S4b1nuz ᴇ.656^(SMS) 15:50, 30 lùg 2020 (CEST)Rispondi

phab:T259633 --Samuele2002 (discuscioin) 18:51, 4 agó 2020 (CEST)Rispondi

E dæto che emmo creòu a Wikisource Lìgure "indipendente", demmo `n salûo de benvegnûo a tûtti in Zeneize e l'augûrio de poéi vedde a Wikivivagna cresce ancon de ciû! Alêgri! --Luensu1959 (discuscioin) 20:37, 21 lùg 2020 (CEST)Rispondi

Su itwikisource esistono molti sistemi gadget e template di base che ci possono essere molto utili:

• Il sistema qualità con i riquadri e la posizione dei messaggi (it:Aiuto:Stato di Avanzamento del Lavoro)
• La creazione di altri due riquadri uno di intestazione e uno di Piè di pagina in fase di modifica di pagine in ns Pagina entrambi che automaticamente non verranno inclusi (evitando così aggiunte manuali di noinclude) esempio
• Alcuni gadget come it:MediaWiki:Gadget-eis.js (che velocizza la modifica di pagine di uno stesso libro evitando il caricamento completo della pagina )
• Come vengono formattati gli indici es. it:Indice:Decurtins - Rätoromanische chrestomathie, VI.djvu (it:Template:Proofreadpage index template
• ... e le intestazioni it:La Histoargia dalg filg pertz (it:Template:Intestazione)
• La serie di tl di formattazione presenti in (it:MediaWiki:Wikimedia-copyrightwarning) es. larger, centrato, smaller ecc.
• Gli Strumenti per la rilettura.
• it:Template:Autore es. it:Autore:Giacomo Leopardi

Cosa ne pensate? --Samuele2002 (discuscioin) 10:16, 22 lùg 2020 (CEST)Rispondi

Grande Samuele! E primme 3000 paggine i ho transcrite proppiu lì, e me-i ricordu quelli belli angæxi (gadgets): bastava sciacâ un pumellu e ti cangiavi tütti i apostrufi. Però po-u mumentu mi saiæ za cuntentu de puei tradüe in liggüre i duî mudelli (templates) "header" e "author". Ti ti u sæ cumme l'è che se fa? G.Musso (discuscioin) 11:10, 24 lùg 2020 (CEST)Rispondi

Molte bene! Aggiungo anche MediaWiki:Sidebar che controlla il menu laterale (quella di it ha altre pagine che a voi non servono, però senz'altro va tolto il link Atoalitæ a meno che non decidiate di creare la pagina, e magari vorrete cambiare "Pòrtego da comunitæ" con qualche nome tipo Bar o Scriptorium. Se poi volete cambiare il MediaWiki:Proofreadpage_index_template, tenete conto che se cambiate i nomi dei campi (es. Author) le pagine Indice già esistenti non funzioneranno più a meno di cancellarle e rifarle; consiglio magari di partire dall'esistente, tradurre le scritte in ligure e fare poi piccole modifiche graduali se volete dei campi in più. Comunque per fare queste modifiche vi serve almeno un amministratore: chi si vuole candidare? --Candalua (discuscioin) 16:01, 24 lùg 2020 (CEST)Rispondi

Invece per il template Autore, considerate che quello italiano è molto complesso e genera un sacco di categorie che vanno poi create via bot; è roba fatta per gestire decine di migliaia di autori di tutti i tipi. Vi consiglio invece di importare quello veneto, che è molto simile (l'ho fatto sempre io) ma nettamente più semplice. --Candalua (discuscioin) 16:58, 24 lùg 2020 (CEST)Rispondi

Brau Candalua, sun proppiu d'acordiu cun ti! G.Musso (discuscioin) 12:31, 26 lùg 2020 (CEST)Rispondi

Pòrtego da comunitæ me pâ u megiu numme in zeneize cuscì cumme ghe l'emmu in sciâ Wikipedia Liggüre. Mi nu so perchè i Italien veuan pe forsa cangialu. Pe piaxei lascemmulu cuscì ch'u l'é ciù seriu.--Luensu1959 (discuscioin) 23:16, 28 lùg 2020 (CEST)Rispondi

Luensu1959: in realtà il portale Comunità in genere è una cosa diversa dal Bar, vedi per esempio it:w:Portale:Comunità. Il portale solitamente è un punto di ingresso a varie pagine utili, il Bar è invece un luogo di discussione tra utenti. Niente vieta di creare entrambe le pagine, la mia osservazione nasceva dal fatto che per come è stata impostata la pagina su cui siamo, assomiglia più al concetto del "bar" che a quelle del portale, quindi il nome rischia di essere fuorviante per chi viene da "fuori" e non conosce il progetto. (Infatti se vedi i link a sinistra sono stati agganciati ai portali comunità). --Candalua (discuscioin) 12:23, 29 lùg 2020 (CEST)Rispondi

Candalua: Portale se dixe Portâ in Zeneize, mentre Pòrtego o veu dî Portico, e chi o vive inte 'na çitæ dove gh'é i pòrteghi o gh'a za 'n'idea de comme e personn-e de lì vivan a vitta püblica. In sciâ Wiki Ligure, dove semmo 4 gatti, o bar o no l'à mai fonçionòu, mentre o pòrtego sci. Chi in sciâ Wikivivagna semmo torna 4 gatti. A ogni mòddo, l'é bello che ghe seggen de diferense. Alegri! --Luensu1959 (discuscioin) 14:22, 29 lùg 2020 (CEST)Rispondi

Pe dîla tütta u "pòrtegu" a Zena u l'è quellu che in tuscan ciamman atrio o vestibolo, mentre i Ingreixi ghe dieivan hall o lobby ("logia"), saiv'à dî, ti t'arvi u purtun du palaççiu e ti t'intri intu portegu, cu-e culonne, a curte, e scainæ cu-i balöistri, u purtê, u cægâ etc... Ciü antigamente, intu Meddiu Evu, gh'ea ascì i porteghi che davan insci-a stradda, ançi, insci-u caruggiu (cumm'à Ciâvai ancö), cuscì e gente pueivan passagiâ belli larghi o-u cuvertu, ma cian cianin i prupietai se i han seræ pe fâ de bütêghe, e i caruggi sun vegnüi belli streiti. Quindi cumme definiçiun de "spaççiu cumünitaiu", portegu u va ben. Alegri! G.Musso (discuscioin) 16:37, 29 lùg 2020 (CEST)Rispondi

Per avere un'idea delle convenzioni in cui le varie Wikisource si sono trovate a discutere consiglio di compilare la riga di questo progetto in mul:Wikisource:Subdomain_coordination. Dalle soluzioni scelte da ciascun dominio si trovano spunti per decidere come regolarsi qui. - OrbiliusMagister (discuscioin) 10:18, 24 lùg 2020 (CEST)Rispondi

Può essere utile anche confrontarsi con l'esperienza ancora "fresca" di nap.source, aperta l'anno scorso: la parte iniziale di nap:Wikisource:Bar contiene molte discussioni importanti per l'avvio di un progetto Wikisource. --Candalua (discuscioin) 17:31, 24 lùg 2020 (CEST)Rispondi

Come è emerso anche nelle discussioni precedenti serve qualcuno che sia amministratore (e in alcuni casi anche amministratore dell'interfaccia) per effettuare le modifiche necessarie all'avvio del progetto oltre all'ordinaria manuntenzione. Chi vuole dedicarsi al progetto e a questo lavoro si faccia avanti ;)

G.Musso mi ha proposto di diventare aministratû per occuparmi delle modifiche e azioni necessarie per garantire un buon inizio a Wikivivagna. Per questo mi candido come: Aministratô e Aministratô de l'interfaccia. --Samuele2002 (discuscioin) 10:43, 27 lùg 2020 (CEST)Rispondi

• Favorévole Ovviamente sì (oua ghe semmu?) — for steward looking at this: strong support. - OrbiliusMagister (discuscioin) 15:16, 27 lùg 2020 (CEST)Rispondi
• Favorévole strong support --Candalua (discuscioin) 18:23, 27 lùg 2020 (CEST)Rispondi
• Favorévole Giromin Cangiaxo (discuscioin) 08:44, 28 lùg 2020 (CEST)Rispondi
• Favorévole, ançi Favuéive, e brâu Samuêlìn! G.Musso (discuscioin) 16:47, 28 lùg 2020 (CEST)Rispondi
• Favorévole--Mizardellorsa (discuscioin) 18:32, 28 lùg 2020 (CEST)Rispondi
• Favorévole Pe mi o va ben (per me va bene) --S4b1nuz ᴇ.656^(SMS) 22:57, 28 lùg 2020 (CEST)Rispondi
• Favorévole/ Favuéive a Samuælu --Luensu1959 (discuscioin) 23:20, 28 lùg 2020 (CEST)Rispondi
• Favorévole/ Favoéive a l'eleçion do Samuæle--Giodiassi5 (discuscioin) 09:18, 30 lùg 2020 (CEST)Rispondi

Ovviamente sono tante e ci vorrà del tempo, io intanto inizio a segnarle man mano che le noto:

• tradurre MediaWiki:Proofreadpage index data config (solo i valori di "label" e "help", il resto va tenuto uguale ma potete aggiungere campi nuovi se servisse)
• ci sono molte pagine con errori di script, dovuti a indici non importati, bisogna individuarli tutti e importarli.
• le pagine proveniente da it.source usano Template:Intestazione, quelle provenienti da mul.source usano Template:Header. Le pagine "italiane" non funzionano benissimo, manca qualche template e le categorie sono tutte rosse. Il template Header invece funziona, ma sarebbe il caso di tradurlo in ligure (anche i nomi dei parametri, intendo). Bisogna decidere cosa fare: convertire tutto a Header? Convertire tutto a Intestazione con i dovuti aggiustamenti? O fare un nuovo template da zero? Io vi consiglierei quest'ultima soluzione, ma valutate voi come procedere. Candalua (discuscioin) 18:11, 11 agó 2020 (CEST)Rispondi
• creare queste pagine che servono per l'esportazione epub/mobi/pdf (potete tradurre le corrispondenti di mul.wikisource o it):

• MediaWiki:Wsexport i18n.ini
• MediaWiki:Wsexport about --Candalua (discuscioin) 18:49, 20 agó 2020 (CEST)Rispondi

• in MediaWiki:Proofreadpage index data config, sotto "Pages" aggiungere la riga: "data": "pagelist" e poi creare MediaWiki:Proofreadpage pagelist dropdown values.json traducendo quello italiano. Pingo [@ Samuele2002] per questa e le aaltre ttività che richiedono un admin. Candalua (discuscioin) 18:33, 24 set 2020 (CEST)Rispondi

Ciao, ho aggiunto questo sito alle ProofreadPage Statistics (https://phetools.toolforge.org/statistics.php), dove trovate i conteggi precisi del lavoro svolto, aggiornati giornalmente. Candalua (discuscioin) 09:43, 25 agó 2020 (CEST)Rispondi

Agiuttine a tradue inta to lengua

You are humbly invited to participate in the Wiki Loves Folklore 2021 an international photography contest organized on Wikimedia Commons to document folklore and intangible cultural heritage from different regions, including, folk creative activities and many more. It is held every year from the 1st till the 28th of February.

You can help in enriching the folklore documentation on Commons from your region by taking photos, audios, videos, and submitting them in this commons contest.

Please support us in translating the project page and a banner message to help us spread the word in your native language.

Kind regards,

Wiki loves Folklore International Team

MediaWiki message delivery (discuscioin) 14:25, 6 fre 2021 (CET)Rispondi

Cara comunità,
con l'obiettivo di facilitare l'organizzazione delle future itWikiCon, un gruppo di organizzatori delle edizioni passate, con all'interno anche rappresentanti di WMI e WMCH, ha pensato di proporre questo regolamento: lo scopo è quello di riuscire ogni anno in tempi rapidi ad assegnare l'organizzazione di itWikiCon e ottenere, se necessario, il supporto economico dei chapter.
Nel caso in cui ci siano più proposte concomitanti, il procedimento servirebbe anche a decidere quale candidatura sostenere. Ovviamente è solo una bozza che proponiamo alla comunità di lingua italiana di commentare e approvare. L'obiettivo sarebbe avere un testo approvato entro fine aprile in modo da dare tempo a chi si volesse organizzarne una dal vivo per il 2022 (per il 2021 sarà necessariamente ancora on-line). --CristianNX, Ferdi2005, Ilario, Jaqen, Ruthven, Yiyi, Ysogo, Valerio Bozzolan, Superchilum (discuscioin) 22:48, 23 màr 2021 (CET)Rispondi

Cari amici,

scusate l'italiano, ma non provo nemmeno a scrivere in un genovese che a malapena capisco se parlato. Vi scrivo proprio qui per un problema di trascrizione del genovese in due pagine di Edmondo di Amicis: questa e questa. Avete già incontrato questo modo di rendere il dittongo ligure? E c'è già una convenzione per renderlo tipograficamente senza ricorrere ai tag <math>? - εΔω 07:01, 5 agó 2021 (CEST)Rispondi

Ciao εΔω!

Grazie per la "chicca" di De Amicis (e scusa per i tempi geologici di risposta)

La risposta alla tua domanda è già contenuta nello stesso libro a pagina 74: vêuggio. In più a pag 75 troviamo anche vergêugna un refuso (sarebbe verghêugna o vergoeugna) che la dice lunga sulla travagliata grafia dell'o turbata genovese.

Se vuoi te la conto: ai tempi del Congresso di Vienna... e qui avrai già chiuso la pagina! no ma seriamente... riproviamo.

Innanzitutto quel circonflesso non serve a niente. Poi per fortuna è abbastanza raro. Immagino che per i tipografi fosse un bel grattacapo e ne avranno avute le tasche piene. Io l'ho incontrato solo in quattro testi: l'Esopo Zeneize del 1822, la Cittara Zeneize del 1823 e poi la Colombiade del 1870 con conseguente dizionario Bacigalupo del 1873. Immagino che il De Amicis si sia ispirato a uno degli ultimi due.

La grafia in voga prima dell'annessione al Piemonte (1815) prevedeva "œu" per l'ho turbata (es. "cœu" = it. "cuore"), ma mi sembra che la "eu" avesse già iniziato ad insinuarsi pianpiano fin dai tempi dell'annessione alla Francia (1805). Fattostà che nel 1822 Martino Piaggio, o chi per lui, la ufficializzò nelle regole ortografiche posposte al suo libro di favole dopo averla già usata irregolarmente nei suoi lunari a partire dal 1815 (un po "œ", un po "êu", un po "eû", ma magari era il tipografo Pagano quello che faceva confusione, forse nei manoscritti il Piaggio scriveva sempre ${\displaystyle {\widehat {eu}}}$, chissà). E poi c'era il problema degli strafalcioni tipo appunto "vergêugna" e "cêu", dato che prima erano abituati a scrivere "vergœugna" e "cœu" (pr. /'kø:/).

In più il Piaggio introdusse anche un'altra novità, ${\displaystyle {\widehat {ou}}}$ al posto del precedente "ao", col circonflesso ancor più inutile, perchè se ${\displaystyle {\widehat {eu}}}$ è un'o turbata pronunciata alla francese, ${\displaystyle {\widehat {ou}}}$ invece non si pronuncia affatto alla francese, come un'unica "u" italiana, ma è un dittongo, cioè un monosillabo composto da "o" seguito da "u". Forse il circonflesso era proprio per indicare che è un monosillabo (per intenderci in genovese l${\displaystyle {\widehat {ou}}}$ "lavoro" pr. /'lɔw/ è diverso da "l'öo" "l'oro" pr. /'lɔ:u/), ma del tutto inutile perchè la "u" italiana nella grafia del Piaggio era comunque già resa con la lettera "o"... a meno che in un primo momento il Piaggio non avesse pensato di riformare la grafia fino in fondo e sostituire la "o" con la "u", salvo poi ripensarci scordandosi però di togliere quei due fastidiosissimi circonflessi. Sì perchè poi ${\displaystyle {\widehat {eu}}}$ è diventato "êu" e ${\displaystyle {\widehat {ou}}}$ "ôu", aggiungendo confusione in una grafia dove il circonflesso dovrebbe servire ad indicare la vocale lunga. Credo di aver un po' divagato...

E comunque sì, credo che l'unico modo per renderlo sia il tag <math> come avevo dovuto fare qui. Quanto a "convenzioni" mi par di capire che chi usa "eu" per "o turbata" (anzichè "œu" "œ" o "ö") o non ci mette sopra niente oppure scrive "êu" per vocale lunga e "éu" per vocale corta. Degna di nota la grafia di Teresa Giaimo che nel 1924 scriveva "éù".

Grazie ancora!

Alegri!

G.Musso (discuscioin) G.Musso (discuscioin) 10:51, 14 nov 2021 (CET)Rispondi

Buongiorno a tutti,

Il comitato di redazione della fase 2 del codice universale di condotta ha completato i lavori, qui trovate la bozza delle linee guida sull'applicazione del codice universale di condotta (UCoC).

La bozza è basata sui risultati delle consultazioni, discussioni e ricerche, tra queste anche la consultazione in cui è stata coinvolta la comunità di lingua italiana ad inizio 2021.

La bozza è, appunto, una bozza, è quindi possibile (anzi, caldamente auspicato) che tutti coloro che sono interessati esprimano opinioni e commenti, anche suggerimenti su come migliorare la traduzione. Il comitato revisionerà la bozza tenendo conto del feedback ricevuto da parte delle comunità.

Il periodo di revisione comincia oggi 17 agosto 2021 e durerà fino al 17 ottobre.

La bozza può essere commentata in diversi "luoghi":

• direttamente su meta, nella pagina di discussione della bozza (pagina che probabilmente sarà ad alto traffico)
• sempre su meta nella pagina di discussione della traduzione in italiano (ambiente più intimo)
• nella Wikipedia:Codice universale di condotta pagina di discussione del codice universale di condotta che si trova sulla Wikipedia in italiano
• potete anche inviarmi commenti o osservazioni via email

Sono previsti inoltre degli incontri e tavole rotonde online (in inglese):

• Incontri online - 24 agosto, 31 agosto, 7 settembre @ 03:00 UTC & 14:00 UTC
• Tavole rotonde online - 18 settembre @ 03:00 UTC & 15:00 UTC

I commenti e le osservazioni verranno poi riassunte in un riepilogo quindicinale che verrà pubblicato qui.

Mi rendo conto che il documento è lungo e a tratti complesso, suggerisco però di prendersi il tempo per leggerlo dato il potenziale impatto che avrà.
Grazie per l'attenzione! --Civvi (WMF) (discuscioin) 22:20, 17 agó 2021 (CEST)Rispondi

Agiuttine a tradue inta to lengua

You are humbly invited to participate in the Wiki Loves Folklore 2022 an international photography contest organized on Wikimedia Commons to document folklore and intangible cultural heritage from different regions, including, folk creative activities and many more. It is held every year from the 1st till the 28th of February.

You can help in enriching the folklore documentation on Commons from your region by taking photos, audios, videos, and submitting them in this commons contest.

You can also organize a local contest in your country and support us in translating the project pages to help us spread the word in your native language.

Feel free to contact us on our project Talk page if you need any assistance.

Kind regards,

Wiki loves Folklore International Team

--MediaWiki message delivery (discuscioìn) 14:15, 9 zen 2022 (CET)Rispondi

Buongiorno a tutti,

Come forse saprete già, la prossima settimana, precisamente dal 7 al 21 marzo, si terrà la votazione per la ratifica delle linee guida per l'applicazione del Codice Universale di Condotta (UCoC). In quanto componenti del movimento Wikimedia, la vostra voce e le vostre opinioni sono importanti, ed è quindi necessaria la vostra rappresentanza in questa votazione.

In quanto volontario di supporto per tutta la durata della votazione, se avete domande o bisogno di ulteriori informazioni potete contattarmi in qualsiasi momento. Potete trovare su meta-wiki maggiori informazioni sull'UCoC, sulle linee guida per l'applicazione e sul processo di voto. Infine, vi informo che recentemente si è svolto un incontro online (in inglese) sulle linee guida per l'applicazione dell'UCoC e sulla necessità di votare, in particolare per le comunità di piccole e medie dimensioni, e che è possibile visualizzare la registrazione integrale qui.

Un caro saluto --Superpes15 (discuscioìn) 07:13, 6 màr 2022 (CET)Rispondi

Hello. To facilitate steward granting of bot access, I suggest implementing the standard bot policy on this wiki. In particular, this policy allows stewards to automatically flag known interlanguage linking bots (if this page says that is acceptable) or bots that fix double redirects. The policy also enables global bots on this wiki (if this page says that is acceptable), which are trusted bots that will be given bot access on every wiki that allows global bots.

This policy makes bot access requesting much easier for local users, operators, and stewards. To implement it we only need to create a redirect to this page from Project:Bot policy, and add a line at the top noting that it is used here. If you use or prefer to use a dedicated project page for handling bot flag requests, that is also acceptable. Please read the text at Meta-Wiki before commenting. If you object, please say so; I hope to implement in two weeks if there is no objection, since it is particularly written to streamline bot requests on wikis with little or no community interested in bot access requests. Thank you for your consideration. --Rschen7754 22:47, 10 lùg 2022 (CEST)Rispondi

[@ Rschen7754] This project is completely inactive. I think there is no problem (even without waiting 2 weeks). Best :) Superpes15 (discuscioìn) 10:47, 13 lùg 2022 (CEST)Rispondi

Thank you @Superpes15. I'll implement it then. Any preference where requests for bot flags should happen or is this page okay? Best regards, -- MarcoAurelio (discuscioìn) 19:26, 23 lùg 2022 (CEST)Rispondi

[@ MarcoAurelio] Since there are no dedicated pages here it's ok imho :) Superpes15 (discuscioìn) 20:54, 23 lùg 2022 (CEST)Rispondi

Puoi trovare questo messaggio tradotto in altre lingue su Meta-wiki.

Altre lingue • Agiuttine a tradue inta to lengua

Ciao a tutti,

I volontari sono invitati a proporre delle dichiarazioni da utilizzare nella bussola elettorale per le elezioni del Board of Trustees del 2022.

Una bussola elettorale è uno strumento nato per aiutare gli elettori a selezionare quei candidati che meglio si conformano alle loro convinzioni e opinioni. I membri della comunità proporranno delle dichiarazioni a cui i candidati risponderanno utilizzando una scala Lickert (d'accordo/neutrale/in disaccordo). Le risposte dei candidati a queste dichiarazioni verranno caricate nella bussola elettorale. Gli elettori utilizzeranno lo strumento inserendo le proprie risposte alle dichiarazioni (d'accordo/neutrale/in disaccordo). I risultati mostreranno quei candidati che meglio si allineano alle convinzioni e ai punti di vista dell'elettore.

Il Comitato elettorale sceglierà le 15 dichiarazioni più votate all'inizio di agosto. Il Comitato elettorale supervisionerà l'intero processo, supportato dal team Movement Strategy and Governance. MSG si assicurerà che le domande siano chiare, che non vi siano duplicati, refusi, o qualsiasi altro problema.

Cordiali saluti,

Movement Strategy and Governance

Questo messaggio è stato inviato per conto della Task Force per la selezione del Board e del Comitato Elettorale
Superpes15 (discuscioìn) 10:44, 13 lùg 2022 (CEST)Rispondi

Thank you for reading! RamzyM (WMF) 03:38, 18 lùg 2022 (CEST)Rispondi

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

Altre lingue • Agiuttine a tradue inta to lengua

Hi everyone,

The Affiliate voting process has concluded. Representatives from each Affiliate organization learned about the candidates by reading candidates’ statements, reviewing candidates’ answers to questions, and considering the candidates’ ratings provided by the Analysis Committee. The selected 2022 Board of Trustees candidates are:

• Tobechukwu Precious Friday (Tochiprecious)
• Farah Jack Mustaklem (Fjmustak)
• Shani Evenstein Sigalov (Esh77)
• Kunal Mehta (Legoktm)
• Michał Buczyński (Aegis Maelstrom)
• Mike Peel (Mike Peel)

You may see more information about the Results and Statistics of this Board election.

Please take a moment to appreciate the Affiliate Representatives and Analysis Committee members for taking part in this process and helping to grow the Board of Trustees in capacity and diversity. These hours of volunteer work connect us across understanding and perspective. Thank you for your participation.

Thank you to the community members who put themselves forward as candidates for the Board of Trustees. Considering joining the Board of Trustees is no small decision. The time and dedication candidates have shown to this point speaks to their commitment to this movement. Congratulations to those candidates who have been selected. A great amount of appreciation and gratitude for those candidates not selected. Please continue to share your leadership with Wikimedia.

Thank you to those who followed the Affiliate process for this Board election. You may review the results of the Affiliate selection process.

The next part of the Board election process is the community voting period. You may view the Board election timeline here. To prepare for the community voting period, there are several things community members can engage with in the following ways:

• Read candidates’ statements and read the candidates’ answers to the questions posed by the Affiliate Representatives.
• Propose and select the 6 questions for candidates to answer during their video Q&A.
• See the Analysis Committee’s ratings of candidates on each candidate’s statement.
• Propose statements for the Election Compass voters can use to find which candidates best fit their principles.
• Encourage others in your community to take part in the election.

Best,

Movement Strategy and Governance

This message was sent on behalf of the Board Selection Task Force and the Elections Committee

MNadzikiewicz (WMF) 16:03, 27 lùg 2022 (CEST)Rispondi

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

Altre lingue • Agiuttine a tradue inta to lengua

Hi all,

Volunteers in the 2022 Board of Trustees election are invited to vote for statements to use in the Election Compass. You can vote for the statements you would like to see included in the Election Compass on Meta-wiki.

An Election Compass is a tool to help voters select the candidates that best align with their beliefs and views. The community members will propose statements for the candidates to answer using a Lickert scale (agree/neutral/disagree). The candidates’ answers to the statements will be loaded into the Election Compass tool. Voters will use the tool by entering in their answer to the statements (agree/disagree/neutral). The results will show the candidates that best align with the voter’s beliefs and views.

Here is the timeline for the Election Compass:

• July 8 - 20: Volunteers propose statements for the Election Compass
• July 21 - 22: Elections Committee reviews statements for clarity and removes off-topic statements
• July 23 - August 1: Volunteers vote on the statements
• August 2 - 4: Elections Committee selects the top 15 statements
• August 5 - 12: candidates align themselves with the statements
• August 15: The Election Compass opens for voters to use to help guide their voting decision

The Elections Committee will select the top 15 statements at the beginning of August

Best,

Movement Strategy and Governance

This message was sent on behalf of the Board Selection Task Force and the Elections Committee

MNadzikiewicz (WMF) 23:01, 27 lùg 2022 (CEST)Rispondi

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

Altre lingue • Agiuttine a tradue inta to lengua

Hi everyone,

The Community Voting period for the 2022 Board of Trustees election is now open. Here are some helpful links to get you the information you need to vote:

• Try the Election Compass, showing how candidates stand on 15 different topics.
• Read the candidate statements and answers to Affiliate questions
• Learn more about the skills the Board seeks and how the Analysis Committee found candidates align with those skills

If you are ready to vote, you may go to SecurePoll voting page to vote now. You may vote from August 23 at 00:00 UTC to September 6 at 23:59 UTC. To see about your voter eligibility, please visit the voter eligibility page.

Best,

Movement Strategy and Governance

This message was sent on behalf of the Board Selection Task Force and the Elections Committee

MNadzikiewicz (WMF)

Template:More languages

Hello everyone,

The Movement Strategy Forum (MS Forum) is a multilingual collaborative space for all conversations about Movement Strategy implementation.

We are inviting all Movement participants to collaborate on the MS Forum. The goal of the forum is to build community collaboration, using an inclusive multilingual platform.

The Movement Strategy is a collaborative effort to imagine and build the future of the Wikimedia Movement. Anyone can contribute to the Movement Strategy, from a comment to a full-time project.

Join this forum with your Wikimedia account, engage in conversations, and ask questions in your language.

The Movement Strategy and Governance team (MSG) launched the proposal for the MS Forum in May 2022. There was a 2-month community review period, which ended on 24 July 2022. The community review process included several questions that resulted in interesting conversations. You can read the Community Review Report.

We look forward to seeing you at the MS Forum!

Best regards,

the Movement Strategy and Governance Team

User:MNadzikiewicz (WMF) 13:32, 29 agó 2022 (CEST)Rispondi

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

Altre lingue • Agiuttine a tradue inta to lengua

Hello all,

During the 2022 Wikimedia Summit, the Movement Charter Drafting Committee (MCDC) presented the first outline of the Movement Charter, giving a glimpse on the direction of its future work, and the Charter itself. The MCDC then integrated the initial feedback collected during the Summit. Before proceeding with writing the Charter for the whole Movement, the MCDC wants to interact with community members and gather feedback on the drafts of the three sections: Preamble, Values & Principles, and Roles & Responsibilities (intentions statement). The Movement Charter drafts will be available on the Meta page here on November 14, 2022. Community wide consultation period on MC will take place from November 20 to December 18, 2022. Learn more about it here.

With the goal of ensuring that people are well informed to fully participate in the conversations and are empowered to contribute their perspective on the Movement Charter, three “Ask Me Anything about Movement Charter" sessions have been scheduled in different time zones. Everyone in the Wikimedia Movement is invited to attend these conversations. The aim is to learn about Movement Charter - its goal, purpose, why it matters, and how it impacts your community. MCDC members will attend these sessions to answer your questions and hear community feedback.

The “Ask Me Anything” sessions accommodate communities from different time zones. Only the presentation of the session is recorded and shared afterwards, no recording of conversations. Below is the list of planned events:

• Asia/Pacific: November 4, 2022 at 09:00 UTC (your local time). Interpretation is available in Chinese and Japanese.
• Europe/MENA/Sub Saharan Africa: November 12, 2022 at 15:00 UTC (your local time). Interpretation is available in Arabic, French and Russian.
• North and South America/ Western Europe: November 12, 2022 at 15:00 UTC (your local time). Interpretation is available in Spanish and Portuguese.

On the Meta page you will find more details; Zoom links will be shared 48 hours ahead of the call.

Call for Movement Charter Ambassadors

Individuals or groups from all communities who wish to help include and start conversations in their communities on the Movement Charter are encouraged to become Movement Charter Ambassadors (MC Ambassadors). MC Ambassadors will carry out their own activities and get financial support for enabling conversations in their own languages. Regional facilitators from the Movement Strategy and Governance team are available to support applicants with MC Ambassadors grantmaking. If you are interested please sign up here. Should you have specific questions, please reach out to the MSG team via email: strategy2030@wikimedia.org or on the MS forum.

We thank you for your time and participation.

On behalf of the Movement Charter Drafting Committee,

MNadzikiewicz (WMF) 16:33, 7 nov 2022 (CET)Rispondi

Template:More languages

The Wikimedia Movement Strategy implementation is a collaborative effort for all Wikimedians. Movement Strategy Implementation Grants support projects that take the current state of a Movement Strategy Initiative and push it one step forward. If you are looking for an example or some guide on how to engage your community further on Movement Strategy and the Movement Strategy Implementation Grants specifically, you may find this community engagement package helpful.

The goal of this community engagement package is to support more people to access the funding they might need for the implementation work. By becoming a recipient of this grant, you will be able to support other community members to develop further grant applications that fit with your local contexts to benefit your own communities. With this package, the hope is to break down language barriers and to ensure community members have needed information on Movement Strategy to connect with each other. Movement Strategy is a two-way exchange, we can always learn more from the experiences and knowledge of Wikimedians everywhere. We can train and support our peers by using this package, so more people can make use of this great funding opportunity.

If this information interests you or if you have any further thoughts or questions, please do not hesitate to reach out to us as your regional facilitators to discuss further. We will be more than happy to support you. When you are ready, follow the steps on this page to apply. We look forward to receiving your application.

Best regards,
Movement Strategy and Governance Team
Wikimedia Foundation

MNadzikiewicz (WMF) 17:26, 14 nov 2022 (CET)Rispondi

Hi everyone! The Ombuds commission (OC) and the Case Review Committee (CRC) are looking for members. People are encouraged to nominate themselves or encourage others they feel would contribute to these groups to do so. There is more information below about the opportunity and the skills that are needed.

About the Ombuds commission

The Ombuds commission (OC) works on all Wikimedia projects to investigate complaints about violations of the privacy policy, especially in use of CheckUser and Oversight (also known as Suppression) tools. The Commission mediates between the parties of the investigation and, when violations of the policies are identified, advises the Wikimedia Foundation on best handling. They may also assist the General Counsel, the Chief Executive Officer, or the Board of Trustees of the Foundation in these investigations when legally necessary. For more on the OC's duties and roles, see Ombuds commission on Meta-Wiki.

Volunteers serving in this role should be experienced Wikimedians, active on any project, who have previously used the CheckUser/Oversight tools OR who have the technical ability to understand these tools and the willingness to learn them. They must be able to communicate in English, the common language of the commission. They are expected to be able to engage neutrally in investigating these concerns and to know when to recuse when other roles and relationships may cause conflict. Commissioners will serve two-year terms (note that this is different from past years, when the terms have been for one year).

About the Case Review Committee

The Case Review Committee (CRC) reviews appeals of eligible Trust & Safety office actions. The CRC is a critical layer of oversight to ensure that Wikimedia Foundation office actions are fair and unbiased. They also make sure the Wikimedia Foundation doesn’t overstep established practices or boundaries. For more about the role, see Case Review Committee on Meta-Wiki.

We are looking for current or former functionaries and experienced volunteers with an interest in joining this group. Applicants must be fluent in English (additional languages are a strong plus) and willing to abide by the terms of the Committee charter. If the work resonates and you qualify, please apply. Committee members will serve two-year terms (note that this is different from past years, when the terms have been for one year).

Applying to join either of these groups

Members are required to sign the Confidentiality agreement for nonpublic information and must be willing to comply with the appropriate Wikimedia Foundation board policies (such as the access to non-public information policy and the Foundation privacy policy). These positions requires a high degree of discretion and trust. Members must also be over 18 years of age.

If you are interested in serving in either capacity listed above, please write in English to the Trust and Safety team at cawikimedia.org (to apply to the OC) or to the Legal Team at legalwikimedia.org (to apply to the CRC) with information about:

• Your primary projects
• Languages you speak/write
• Any experience you have serving on committees, whether movement or non-movement
• Your thoughts on what you could bring to the OC or CRC if appointed
• Any experience you have with the Checkuser or Oversight tools (OC only)
• Any other information you think is relevant

The deadline for applications is 31 December 2022 in any timezone.

Please feel free to pass this invitation along to any users who you think may be qualified and interested. Thank you!

On behalf of the Committee Support team,

Gràçie! Community Tech, STei (WMF) 17:44, 15 dex 2022 (CET)Rispondi

Per the Global bans policy, I'm informing the project of this request for comment: m:Requests for comment/Global ban for PlanespotterA320 (2) about banning a member from your community. Thank you.--Lemonaka (talk) 21:40, 6 February 2023 (UTC)

Trizek (WMF) (Discusción) 22:21, 27 fre 2023 (CET)Rispondi

Do you want to host an in-person or virtual session at Wikimania 2023? Maybe a hands-on workshop, a lively discussion, a fun performance, a catchy poster, or a memorable lightning talk? Submissions are open until March 28. The event will have dedicated hybrid blocks, so virtual submissions and pre-recorded content are also welcome. If you have any questions, please join us at an upcoming conversation on March 12 or 19, or reach out by email at wikimania@wikimedia.org or on Telegram. More information on-wiki.

Xeno (WMF) 21:01, 26 arv 2023 (CEST)Rispondi

-- UCoC Project Team, 06:21, 27 màz 2023 (CEST)

RamzyM (WMF) 20:00, 28 zùg 2023 (CEST)Rispondi

RamzyM (WMF), on behalf of the U4C Building Committee, 17:35, 28 agó 2023 (CEST)Rispondi

03:13, 17 òtô 2023 (CEST)

Read this in your language • Agiuttine a tradue inta to lengua • Please tell other users about these changes

Hello. I'm writing on behalf of the Wikimedia Foundation Web team. In three weeks, we would like to make the Vector 2022 skin the default on this wiki.

If you prefer keeping the current skin select "Vector legacy (2010)" on the appearance tab of the global preferences and save the change. We encourage you to give the new skin a try, though.

It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy as a local (but not global) preference. Logged-in users can at any time switch to any other skin. No changes are expected for these skins.

• Top of an article
• 
  Vector legacy (current default)
• 
  Vector 2022

• A section of an article
• 
  Vector legacy (current default)
• 
  Vector 2022

About the skin

[modìfica]

[Why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were 14 years ago. Since then, new users have begun using the Internet and Wikimedia projects in different ways. The old Vector does not meet their needs.

[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. The PHP code in the other available skins has been reduced by 75%. The project has also focused on making it easier to support gadgets and use APIs.

[Changes in a nutshell] The skin introduces changes that improve readability and usability. The new skin does not remove any functionality currently available on the Vector skin.

• The limited width and pin-able menus allow to adjust the interface to the screen size, and focus on editing or reading. Logged-in and logged-out users may use a toggle button to keep the full width, though.
• The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
• The new table of contents makes it easier to navigate to different sections. Readers and editors jump to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
• The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the tested wikis.
• The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.

[Customize this skin] It's possible to configure and personalize our changes. We support volunteers who create new gadgets and user scripts. Check out the repository for a list of currently available customizations and changes, or add your own.

Our plan

[modìfica]

If no large concerns are raised, we plan on deploying on 14 November. If you'd like to ask our team anything, if you have questions, concerns, or additional thoughts, please comment in any language. If this is the first comment to my message, make sure to ping me. We will gladly answer! Also, check out our FAQ. Thank you! SGrabarczuk (WMF) (discusción) 03:17, 26 òtô 2023 (CEST)Rispondi

RamzyM (WMF) 19:09, 19 zen 2024 (CET)Rispondi

RamzyM (WMF) 18:01, 31 zen 2024 (CET)Rispondi

RamzyM (WMF) 19:24, 12 fre 2024 (CET)Rispondi

RamzyM (WMF) 17:25, 5 màr 2024 (CET)Rispondi

MPossoupe_(WMF)20:57, 12 màr 2024 (CET)Rispondi

Read this in your language • Agiuttine a tradue inta to lengua • Please tell other users about these changes

Hi everyone. We are the Wikimedia Foundation Web team. As you may have read in our previous message, over the past year, we have been getting closer to switching every wiki to the Vector 2022 skin as the new default. In our previous conversations with Wikisource communities, we had identified an issue with the Index namespace that prevented switching the skin on. This issue is now resolved.

We are now ready to continue and will be deploying on Wikisource wikis on March 25th.

To learn more about the new skin and what improvements it introduces, please see our documentation. If you have any issues with the skin after the change, if you spot any gadgets not working, or notice any bugs – please comment below! We are also open to joining events like the Wikisource Community meetings to talk to you directly. Thank you! SGrabarczuk (WMF) (discusción) 21:50, 18 màr 2024 (CET)Rispondi

there used to be the option to compare different translations of the same text as in this page, it seems that with this new skin it is no longer possible ~~ G.Musso (discuscioìn) 13:12, 28 màr 2024 (CET)Rispondi

RamzyM (WMF) 22:20, 25 arv 2024 (CEST)Rispondi

MediaWiki message delivery 23:23, 14 màz 2024 (CEST)Rispondi

Puoi trovare questo messaggio tradotto in altre lingue su Meta-wiki. Agiuttine a tradue inta to lengua

Cari membri della comunità,

The Community Affairs Committee (CAC) of the Wikimedia Foundation Board of Trustees invites you to give feedback on a draft Procedure for Sibling Project Lifecycle. This draft Procedure outlines proposed steps and requirements for opening and closing Wikimedia Sibling Projects, and aims to ensure any newly approved projects are set up for success. This is separate from the procedures for opening or closing language versions of projects, which is handled by the Language Committee or closing projects policy.

Puoi trovare i dettagli su questa pagina, nonché le modalità per fornire il tuo feedback da oggi fino alla fine della giornata del 23 Giugno 2024, ovunque sulla Terra.

Puoi anche condividere informazioni a riguardo con le comunità di progetto interessate con cui lavori o che supporti, e puoi anche aiutarci a tradurre la procedura in più lingue, in modo che le persone possano partecipare alle discussioni nella propria lingua.

A nome del CAC,

RamzyM (WMF) 04:25, 22 màz 2024 (CEST)Rispondi

RamzyM (WMF) 10:15, 3 zùg 2024 (CEST)Rispondi

RamzyM (WMF) 10:45, 11 zùg 2024 (CEST)Rispondi

RamzyM (WMF) 12:52, 25 zùg 2024 (CEST)Rispondi

RamzyM (WMF) 05:47, 8 lùg 2024 (CEST)Rispondi

-- Keegan (WMF) (talk) 02:03, 10 lùg 2024 (CEST)Rispondi

MediaWiki message delivery (discuscioìn) 19:53, 18 lùg 2024 (CEST)Rispondi

Buongiorno, vi annuncio che si stanno chiudendo le opportunità per itWikiCon 2024, che quest'anno sarà a Padova!

Fino al 24 è possibile chiedere una borsa di partecipazione per coprire le spese, mentre fino al 26 è possibile fare proposte per il programma

Un saluto! -- Sciking (discuscioìn) 20:10, 22 lùg 2024 (CEST)Rispondi

RamzyM (WMF) 04:47, 27 lùg 2024 (CEST)Rispondi

-- Keegan (WMF) (talk) 17:30, 6 agó 2024 (CEST)Rispondi

Hello. For many years, community members have requested an easy way to re-use references with different details. Now, a MediaWiki solution is coming: The new sub-referencing feature will work for wikitext and Visual Editor and will enhance the existing reference system. You can continue to use different ways of referencing, but you will probably encounter sub-references in articles written by other users. More information on the project page.

We want your feedback to make sure this feature works well for you:

• Please try the current state of development on beta wiki and let us know what you think.
• Sign up here to get updates and/or invites to participate in user research activities.

Wikimedia Deutschland’s Technical Wishes team is planning to bring this feature to Wikimedia wikis later this year. We will reach out to creators/maintainers of tools and templates related to references beforehand.

Please help us spread the message. --Johannes Richter (WMDE) (talk) 10:36, 19 August 2024 (UTC)

Hi all,

The next language community meeting is scheduled in a few weeks—on August 30th at 15:00 UTC. If you're interested in joining, you can sign up on this wiki page.

This participant-driven meeting will focus on sharing language-specific updates related to various projects, discussing technical issues related to language wikis, and working together to find possible solutions. For example, in the last meeting, topics included the Language Converter, the state of language research, updates on the Incubator conversations, and technical challenges around external links not working with special characters on Bengali sites.

Do you have any ideas for topics to share technical updates or discuss challenges? Please add agenda items to the document here and reach out to ssethi(__AT__)wikimedia.org. We look forward to your participation!

MediaWiki message delivery (discuscioìn) 01:20, 23 agó 2024 (CEST)Rispondi

RamzyM (WMF) 16:06, 2 set 2024 (CEST)Rispondi

MediaWiki message delivery (discuscioìn) 14:15, 3 set 2024 (CEST)Rispondi

Dear Wikimedians,

We are thrilled to announce that the Wikisource Conference is returning after a decade! It will be held from 14 to 16 February 2025 in Denpasar, Bali, Indonesia. This event will be a great opportunity for us to come together, share experiences, and discuss the future of Wikisource and its community. We are now accepting scholarship applications for the Wikisource Conference 2025 to promote diversity and inclusion. Scholarships are open to active contributors, community members, developers, and partners involved with Wikisource or related projects.

Important Details:

• Application Period: 1 September 2024 to 20 September 2024
• Application Deadline: 20 September 2024
• Meta page: Link

We encourage everyone who is passionate about Wikisource and interested in attending this unique gathering to apply for a scholarship. The selection committee will carefully review all applications, focusing on contributions to the Wikisource project, community engagement, and the potential impact of participation in the conference.

To apply, please fill out the scholarship application form. We will provide updates soon for more information about the conference, including program details, speakers, and venue.

If you have any questions or need help with your application, feel free to reach out on the Meta Talk page or email us at wikisourceconference@gmail.com.

We look forward to receiving your applications and hope to see many of you in Bali for the Wikisource Conference 2025!

Regards,

Nitesh Gill

The Wikisource Conference 2025 Team

MediaWiki message delivery (discuscioìn) 13:14, 5 set 2024 (CEST)Rispondi

Dear Wikimedians,

This message is about the Wikisource Conference, taking place from 14 to 16 February 2025 in Denpasar, Bali, Indonesia, after a decade-long break. This conference will be a fantastic opportunity to reconnect, share insights, and discuss the future of Wikisource and its vibrant community.

In the spirit of promoting diversity and inclusion, we're pleased to inform you that the deadline for scholarship applications has been extended to 29 September 2024.

If you still need to apply, please fill out the application form.

For any questions or assistance, feel free to contact us via the Meta Talk page or by email at wikisourceconference@gmail.com.

We look forward to your applications and hope to see you at the Wikisource Conference 2025!

Thank you MediaWiki message delivery (discuscioìn) 15:32, 20 set 2024 (CEST)Rispondi

Wikisource Conference 2025 Scholarship Team

Dear Wikimedians,

This is a final reminder that the scholarship application deadline for the Wikisource Conference 2025 is 29 September 2024. The conference will take place from 14-16 February 2025 in Denpasar, Bali, Indonesia, after a decade-long break.

If you haven’t applied yet, please do so by completing the scholarship application form by 11:59 AM UTC, 29th September 2024.

For any questions, reach out via the Meta Talk page or email us at wikisourceconference@gmail.com.

We look forward to your participation!

Regards, Wikisource Conference 2025 Scholarship Team

MediaWiki message delivery (discuscioìn) 19:31, 29 set 2024 (CEST)Rispondi

MPossoupe_(WMF) 10:26, 14 òtô 2024 (CEST)Rispondi

-- Keegan (WMF) (talk) 01:09, 17 òtô 2024 (CEST)Rispondi

Hello everyone, I previously wrote on the 27th September to advise that the Wikidata item sitelink will change places in the sidebar menu, moving from the General section into the In Other Projects section. The scheduled rollout date of 04.10.2024 was delayed due to a necessary request for Mobile/MinervaNeue skin. I am happy to inform that the global rollout can now proceed and will occur later today, 22.10.2024 at 15:00 UTC-2. Please let us know if you notice any problems or bugs after this change. There should be no need for null-edits or purging cache for the changes to occur. Kind regards, -Danny Benjafield (WMDE) 13:30, 22 òtô 2024 (CEST)Rispondi

Hello everyone,

The next language community meeting is coming up next week, on November 29th, at 16:00 UTC (Zonestamp! For your timezone <https://zonestamp.toolforge.org/1732896000>). If you're interested in joining, you can sign up on this wiki page: <https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/Community_meetings#29_November_2024>.

This participant-driven meeting will be organized by the Wikimedia Foundation’s Language Product Localization team and the Language Diversity Hub. There will be presentations on topics like developing language keyboards, the creation of the Moore Wikipedia, and the language support track at Wiki Indaba. We will also have members from the Wayuunaiki community joining us to share their experiences with the Incubator and as a new community within our movement. This meeting will have a Spanish interpretation.

Looking forward to seeing you at the language community meeting! Cheers, Srishti 20:55, 21 nov 2024 (CET)Rispondi