Wiktionary:Landsbybrønden

Landsbybrønd i Den Gamle By

Velkommen nybegyndere og andre forundrede brugere! Hvis du har et spørgsmål om Wiktionary og hvordan det hele virker, så placer det i bunden af listen, og nogen vil forsøge at besvare det for dig.

Før du stiller et spørgsmål, så check lige om det ikke allerede er besvaret under ofte stillede spørgsmål.

NOTE - spørgsmål og svar bliver ikke på denne side for evigt. Efter et stykke tid bliver de flyttet til et mere passende sted, for eksempel under ofte stillede spørgsmål.

(purge)

Sådan skriver man et indlæg på Landsbybrønden

1. Tryk på rediger
2. Gå til redigeringsfeltet og indsæt

   {{Brønd|Overskrift=Overskrift for emne}}

   under alle de andre indlæg og gem siden.
3. Gå til bunden af siden og tryk på et af de røde links der svarer til dit nye indlæg
4. Skriv dit indlæg, du skal starte med overskriften:

   == Overskrift for emne ==

5. Gem siden

Benyt ikke det rediger-link der er nederst på Landsbybrønden. Det vil placere dit indlæg sammen med den hidtil nyeste men uvedkommende diskussion.

Hvis ovenstående giver dig problemer, så gør du det bare så godt du kan, så kommer der sikkert en mere rutineret bruger og retter det til for dig.

Se også den detaljerede vejledning.

Wiktionary:Landsbybrønden/

Rediger · Overvåg · Se kun underside

function showSeeAlso()

Finds er mulighed automatisering av skabelonen

{{også|...}}

Se [1]. Ville anvende her? Bedsten (diskussion) 29. apr 2014, 12:05 (UTC)

Hvad indebærer den funktion?
- Sarrus (d • b) d. 10. maj 2014, 10:15 (UTC)

Hvis er i side Vorlage_Siehe_auch (Skabelon_også) vis Skabelon_også.

Medmindre ikke er in side Vorlage_Siehe_auch (Skabelon_også) og der er to siden som adskiller sig genom minuskel og majuskel vis ... . Bedsten (diskussion) 12. maj 2014, 05:13 (UTC)

Støtter Tyskeren (diskussion) 10. aug 2016, 12:29 (UTC)

Rediger · Overvåg · Se kun underside

Skabeloner for #Bestemt ental af ..  ?

Hej, findes der skabeloner for den bestemte entalsform og de ubestemte og bestemte flertalsformer af danske navneord?
Så man slipper for at måtte skrive #Bestemt ental af '''[[ditordher]]'''., etc ?
Hvis ej, har det været diskuteret før? Jeg søgte lidt, men fandt intet om dette. Tak på forhånd, B Lemeukx 7. jan 2017, 00:54 (UTC).

Jeg har ikke lige fundet nogen med den ordlyd, men jeg har fundet nogle andre, som jeg nu har placeret i Kategori:Bøjningsskabeloner. Jeg opretter aldrig opslag om bøjede ord, så kan have overset dem. Du kan selv søge efter det, ved at gå ind på Speciel:Søgning, klikke på "avanceret", fjerne markeringen ved "(Hoved)", aktivere markeringen ved "Skabelon", skrive et søgeord og derefter klikke på "søg" (eller "enter" på tastaturet).
- Sarrus (d • b) d. 7. jan 2017, 11:21 (UTC)

En enkel model for at bestemme en-ord eller et-ord samt bøgningerne ?

Hej, findes der allerede nogle ordlister der er baseret på "logik"?
Jer er ellers startet på at lave nogle beskrivelser selv (Bruger:B Lemeux/Discussion/nom-da-en+et) til at fine ud af om et dansk navneord er intetkøn eller fælleskøn, samt i hvilken bøgningsgruppe det falder (løst baseret på Kategori:Bøjningsskabeloner til dansk). Men hvis der allerede er nogle fastbrændte lister her på stedet, kan jeg måske stoppe med mine lister :-) ? Tak på forhånd, B Lemeukx (diskussion) 7. jan 2017, 08:51 (UTC)

Hvis du er i tvivl om, hvilket køn et ord er, kan du slå det op i en ordbog. Det er ikke rigtigt muligt, at lave en regel om det. Omend de fleste ord, der omtaler mennesker (familierelationer, stillingsbetegnelser, aldersrelaterede ord osv.) er fælleskøn, men der er udtagelser, f.eks. er barn intetkøn. Du kan finde en liste over internetbaserede ordbøger på Wiktionary:Ordbøger. Du må gerne opdatere ordbogsoversigten, hvis du kender nogen, der ikke er angivet.
- Sarrus (d • b) d. 7. jan 2017, 11:27 (UTC)

Hej og tak Sarrus,
Hvor meget må vi bruge fra Wiktionary:Ordbøger (der står intet om begrænsninger/tilladelser på denne side) eller andre ordbøger, før vi får copy-dan på halsen? Ifølge Kinamand var en bruger for nogen tid siden i farezonen.

Øh, tænker du på ophavsret? Det eneste, der kan være ophavsret på, er vel definitionen, så den bør man selv formulere. Der er vel ikke ophavsret på oplysninger om, hvordan et ord bøjes og hvilket køn ordene er? Ordenes etymologi og evt. andre oplysninger om ordet kan der vel ikke være ophavsret på?
- Sarrus (d • b) d. 7. jan 2017, 23:02 (UTC)

Gælder det også udtaleformer som /ˈmʌd̥ə/? Jeg har hidtil kun brugt kilder indenfor wiki-verdenen, B Lemeukx (diskussion).

Kan du ikke prøve at stille ophavsretsspørgsmålene på Nybegynderforummet på Wikipedia. Der er flere aktive brugere og de samme ophavsretsregler må gøre sig gældende på både Wikipedia og Wiktionary.
- Sarrus (d • b) d. 8. jan 2017, 12:42 (UTC)

Hvis andre brugere har alligevel mod på det, prøv at se mine lister igennem, om de holder? :-) For eksempel at navneord der slutter på "~graf" altid følger "en|er" eller om der findes undtagelser? Tak på forhånd. B Lemeukx (diskussion) 7. jan 2017, 19:50 (UTC)

Kom lige i tanke om det: Hvordan kan vi søge på artikler der slutter med en bestemt endelse? At finde ord der starter med "abc" er en barneleg, men det modsætte ???

Hvad angår endelser, kan du kigge i Kategori:Endelsers underkategorier, men den er sikkert ikke komplet. Desuden ser det ud til, at man kan f.eks. kan skrive "*tion" i Speciel:Søgning og så få ord frem, der ender på "tion".
- Sarrus (d • b) d. 7. jan 2017, 23:02 (UTC)

Genialos, merci, B Lemeukx (diskussion) 8. jan 2017, 12:29 (UTC).

Artikelstrukturen : hund-da vs hund-no og hund-sv ??

Hej, mønsterartiklen hund har strukturen "noun etym pronun decl" for den danske del, men "etym pronun noun decl" for den norske og svenske. Er den danske struktur den rigtige? Tak, B Lemeukx (diskussion) 8. jan 2017, 21:59 (UTC)

Etymologi og udtale bør stå før ordklassen (altså øverst efter sprogkoden), hvis begge dele er fælles for alle ordklasser (for det tilfælde, at et ord tilhører flere ordklasser). Ellers ser det ud til, at det kun gør sig gældende for den ene ordklasse. For at opslagene er nogenlunde ensartede bør det også gælde opslag, der kun dækker én ordklasse (såsom hund).
- Sarrus (d • b) d. 9. jan 2017, 14:52 (UTC)

Tak, jeg har rettet. B Lemeukx (diskussion) 23. jan 2017, 22:42 (UTC)

Skabelon:User ... ???

Der er et fåtal gamle skabeloner tilbage med navne der starter med:
Skabelon:User
Fundet via følgende søgning (som giver lidt for meget, men any way).
Da de nuværende, brugte, skabeloner er lokaliserede, kunne de med "User" vist fjernes, eller?
De sider, der bruger dem, forbliver allesammen i deres økosystem, eg Skabelon:User lang-2 bruges kun af Skabelon:User nn-2,Skabelon:User sv-2 og Skabelon:User fr-2.
Eventuelt skal der laves lidt ved én af dem: User_lang_subcat . B Lemeukx (diskussion) 23. jan 2017, 22:48 (UTC)

Jeg markerer dem med "hurtigslet" nu, B Lemeukx (diskussion) 25. jun 2017, 03:52 (UTC)

Skabelon : da-noun-infl folder sammen, hvorfor ??

Hej, artiklen mus og insulin bruger begge bøjningsskabelonen da-noun-infl. Hos mus-artiklen vises alle bøjningsformer hele tiden. Når jeg læser insulin-artiklen ind, vises bøjningsformen i sin helhed kun i omkring 1 sekund, så folder den sammen og man skal trykke på "Show"-lænken. Hvorfor?
Kan man indstille det at de bøjningsformer altid vises udfoldet?
Og hvorfor hedder det "Show" og "Hide", og ej "Vis" og "Skjul"? B Lemeukx (diskussion) 5. feb 2017, 21:32 (UTC)

Skabelonen da-noun-infl, der er brugt i insulin, henviser inernt til skabelonen da-noun-infl-base. Der er altså tale af forskellige versioner af samme skabelon. Med venlig hilsen --Olelog (diskussion) 6. feb 2017, 09:15 (UTC)

If you want to change the text "Show" and "Hide" into "Vis" and "Skjul", I believe page MediaWiki:Common.js should be adjusted. Only an admin can change that page (Sarrus?).

MediaWiki:Common.js, lines 9 & 10, currently:

var NavigationBarHide = '[Hide]';

var NavigationBarShow = '[Show]';

This could be changed into something like:

var NavigationBarHide = '[Skjul]';

var NavigationBarShow = '[Vis]';

Kind regards, Curious (diskussion) 20. feb 2017, 19:56 (UTC)

2 modeller -da- og =da=

Hej, jeg finder to modeller
{{-da-}}
og
{{=da=}}
Har vi brug for begge, eller kunne den første erstattes af den sidste? Det ser ud til at vi kun har -da- for danske artikler her, alle andre sprog er med dobbelt-streger. Tak, B Lemeukx (diskussion) 3. jun 2017, 12:44 (UTC)

Nej, en er nok. Dansk er ikke det eneste sprog, der har begge: se f.eks. {{-eo-}}/=eo=, {{-en-}}/=en=, {{-de-}}/=de=. Personligt bruger jeg altid ligmedtegnsversionerne, fordi de skiller sig ud fra de andre overskriftsskabeloner. En ulempe ved at bruge det format er, at man ikke kan bruge {{vis}}-skabelonen, men det virker ikke betydningsfuldt.__Gamren (diskussion) 4. jun 2017, 10:18 (UTC)

Etymologie-skabeloner giver ekstra linjeskift

Hej,
jeg ville lave dokumentation på etymologi-skabelonerne {{term}}, {{suffix}} og {{prefix}}, men det har de det tilsyneladende rigtigt dårligt med. For suffix så det sådan ud:

• ven +‎ -skab giver

ven

+‎ -skab

• bouquin +‎ -iste giver

bouquin

+‎ -iste

Hvordan kan man lave en ordentlig dokumentation på disse skabeloner, dvs rækkefølge af elementer og deres betydning? Det er absolut nødvendigt hvis vore brugere skal kunne bruge dem rigtig.
Jeg forstår faktisk overhovedet ej; på den franske wikti har jeg rettet flere end én skabelondokumentation - allesammen uden de problemer jeg støder på her!
I al fald, hvis nogen kan udrette disse skabeloner igen, tak på forskud, B Lemeukx (diskussion) 2. jul 2017, 19:03 (UTC)

Etymologie-skabeloner igen uden fejl idag

efter /doc-siden : Suffix giver problemer, prefix også

efter /doc-siden : Suffix+prefix giver problemer på da:Wiktionary:Skabeloner

Hmm, idag ser alt igen OK ud på Skabelon:term/doc, Skabelon:prefix/doc, Skabelon:suffix/doc og da:Wiktionary:Skabeloner. Men igår så de ud som på vedhæftede skærmaftryk!

Jeg ville dog gerne have at vi laver lidt bedre dokumentation på hvad disse modeller forventer for at give de rigtige resultater. Tak, B Lemeukx (diskussion) 3. jul 2017, 19:49 (UTC).

Rediger · Overvåg · Se kun underside

Enabling Page Previews

Enabling Page Previews

Hello,

Based on the positive results of a series of quantitative and qualitative tests, the Reading web team at the Wikimedia Foundation would like to enable the Page Previews feature for this project.

Page Previews provide a preview of any linked article, giving readers a quick understanding of a related article without leaving the current page. However, we realize the needs of the Wiktionary community will not be satisfied by the current implementation of the feature. We are interested in developing separate previews for Wiktionary that will display the wiktionary definition of an item, as well as an image, if available.

We'd like to invite some discussion around interest in this feature, as well as the requirements and elements that would make it useful for the Wiktionary community.

CKoerner (WMF) 6. jul 2017, 15:02 (UTC)

Flottere bøjningsskabelon for "bager-model"

Hej,
en tidligere kommentar på Wiktionary:Skabeloner i underafsnittet af {{-decl-}} ====Bøjning==== sagde om Skabelon:da-noun-infl: Det er ikke det kønneste layout, så du må meget gerne forbedre det.
Jeg har tænkt på at lave farverne mere i stil af vores basismodel Skabelon:da-noun. Et eksempel er på følgende side:
Bruger:B Lemeux/superbager
Kunne I sige hvad I mener?
Jeg har også lavet en "bager-model", for at gøre det nemt at angiver bøjningerne for stort set alle danske stillingsbetegnelser der ender i -er. Man kan direkte bruge den uden at måtte angive formerne for pl-def og pl-def-gen (se eg infl-diskussion). Skal vi have denne skabelon generelt? Tak, B Lemeukx (diskussion) 15. jul 2017, 17:07 (UTC)

Rediger · Overvåg · Se kun underside

Skabeloner: Salmonsens og Salmonsen2 er stort set ens ?

Hej, vi har to referenceskabeloner til dansk som er stort set ens, Salmonsens Konversationsleksikon. - 2. udg. 26 bind, 1915-1930, og heldigvis er ingen af dem endnu brugt, burde vi slette en af dem?, B Lemeukx (diskussion) 21. aug 2017, 19:57 (UTC)

• Skabelon:Salmonsens
• Skabelon:Salmonsen2

Det lader ikke til, at nogen af dem er i brug. Måske kunne vi slette dem begge to? Du kan prøve at tage det op på Wiktionary:Sider der bør slettes.
- Sarrus (d • b) d. 22. aug 2017, 09:56 (UTC)

Rediger · Overvåg · Se kun underside

Anmodning om sletninger

I skrivende stund er der 26 sider, der er foreslået slettet i Kategori:Sider der er foreslået slettet hurtigt. Måske kunne Bruger:Kinamand eller Bruger:Palnatoke lokkes til at se på dem :-). Samt evt. konkludere på forslagene på Wiktionary:Sider der bør slettes, når det er passende.
- Sarrus (d • b) d. 26. aug 2017, 09:45 (UTC)

Det er sket nu (af Palnatoke :-) ). Kinamand (diskussion) 28. aug 2017, 13:18 (UTC)

Rediger · Overvåg · Se kun underside

Columns for references

Hjælp venligst med at oversætte til dit sprog • Read this in another language

Hello,

At the request of Wikipedia editors, a new feature has been added to MediaWiki. Long lists of references (also called citations or footnotes) will automatically be displayed in columns. This will make it easier for most people to read the references, especially on narrow screens. Short lists of references will not be affected.

I plan to enable this new feature at this wiki on Monday, 11 September 2017. After that date, use the normal <references /> tag on any page with many references to see this feature. If you do not want columns used on that page, then use this wikitext code instead: <references responsive="0" />

If you believe that this new feature is not appropriate for this wiki, or if you need help adjusting templates, then please contact me at mw:Contributors/Projects/Columns for references. --User:Whatamidoing (WMF) (talk)

1. sep 2017, 18:23 (UTC)

For mange løse lænker i Wiktionary:Velkommen nybegynder

Hej,

jeg synes der er for mange løse sider i Wiktionary:Velkommen nybegynder. Jeg nævner i flæng:

• opslagsordets diskussionsside
• på Wiktionary politik
• de mest almindelige begynderfejl på Wiktionary.
• se vores svar til kritikere.
• Hvis du har lyst til at være med, så kan du fortsætte på Wiktionary:Kom hurtigt i gang.

Er der nogen der kunne stramme teksten til? Den ser ud til at være så gammel hine steder at der er ej længere relevante emner den beskriver. Eller tager jeg fejl? Tak, B Lemeukx (diskussion) 3. sep 2017, 21:23 (UTC)

Rediger · Overvåg · Se kun underside

Ejendomsmægler søger fuge-s

Hej,
hvordan kan jeg bedst udtrykke her på da-wikt i etymologi-delen at et sammensat ord "holdes sammen" af fuge-s? Som jeg har startet på i artiklen ejendomsmægler. Er brugen af compound godt nok, eller bliver det for tungt med al den henvisningstekst: ejendom +‎ s (interfix) +‎ mægler, eller skal vi lave specielle skabeloner (til fuge-s, fuge-e, fuge-n, ...) ? Tak, B Lemeukx (diskussion) 4. sep 2017, 19:57 (UTC)

Kan man ikke bare gøre som i denne version? Det plejer jeg at gøre. Er der nogen grund til, at der skal stå (interfix) midt i etymologien? Måske skulle man lave skabelonen om, så der henvises til en artikel med navnet -s-, -e- eller -n-, På enwikt findes opslaget en:-s-#Danish eksempelvis.
- Sarrus (d • b) d. 5. sep 2017, 17:31 (UTC)

På en.wikt angiver jeg altid, at et fugebogstav er brugt (f.eks. her, her, her), ud fra princippet om, at man ikke kan tillade sig at betragte nogle af morfemerne og se bort fra resten, selvom jeg sagtens kan forstå hvis nogen anser dem for betydningsløse. At skrive interfix (som forresten staves interfiks på dansk, jf. suffiks, præfiks) virker ikke nødvendigt. Som regel markerer man blot morfemer der kræver et element på hver side med med bindestreger på hver side.__Gamren (diskussion) 7. sep 2017, 15:59 (UTC)

OK, altså ligesom hos en:helhedsvurdering der henviser til et afsnit med overskrift Interfix også hos os: ejendom +‎ -s- +‎ mægler, og så lave en artikel om fuge-s: -s-, etc. Skal vi gøre dette? , B Lemeukx (diskussion) 17. sep 2017, 19:08 (UTC)

Og hvad skal overskriften hedde? Interfiks som hos w:Bindebogstav (eller det skal ændres dér?), Fugebogstav, Bindebogstav, Interfiks, eller noget helt andet? Tak, B Lemeukx (diskussion) 17. sep 2017, 19:13 (UTC)

Hmm, det ser ud til at jeg selv må tage beslutningen og vil gøre sådan:

• Ingen ændring af skabelonen compound. På et tidspunkt findes der måske et ord der er sammensat med s ej som bindebogstav men som et eget ord. Denne fare forekommer mig ej ved -s-.
• -s- følger standarden på andre wikter, en, nl, sv, fr, etc.
• ny artikler -s-, -e-, -n-, -er- + -nt- med beskrivelsen: Interfiks (selvom kun Informationshåndbogen skriver det sådan, andre danske sider sætter Interfix). Jeg vil kopiere den del der står nu i s.
• Lidt flere krydshenvisninger indenfor interfiks (skal skrives dd!), interfix, bindebogstav, fugebogstav, vidensform, dobbeltform, etc.
• Andet arbejde: erstatning af tidligere brugt s i nogle tilfælde af compound eller som direkte henvisning. Hvis nogen har en bot til at gøre dette, ville det være fint. Der er lidt under 250 sider der henviser til s på nuværende tidspunkt. Øvelsen skal også gøres for n og e.

God weekend, B Lemeukx (diskussion) 29. sep 2017, 19:11 (UTC)

Rediger · Overvåg · Se kun underside

Forvirrende : Sådan skriver man et indlæg på Landsbybrønden

Hej, det er rigtigt forvirrende med de to modsatrettede råd man får hhv på selve Landsbybrønden og hvad man ser, når man har trykket på lænken rediger.
Sådan ser det omtrentligt ud hos mig:
<!-- Landsbybrønden er konverteret til et The Danish village pump has been
redigeringsvenligt format. Nye emner changed to a more editable format. New
tilføjes sådan: topics are added like this:

1. Kopier {{Brønd|Overskrift=}} ind 1. Paste {{Brønd|Overskrift=}} into
over denne kommentar. the text above this comment.
2. Indsæt din overskrift på emnet 2. Insert the subject after =
efter = 3. Save this page.
3. Gem siden 4. Follow the red link ''rediger'' (edit) at the bottom of
4. I bunden af siden er der nu et the page, and create your topic there.
rødt link. Følg dette, og Remember to place a heading (== ... ==)
opret emnet som normalt. at the top of that page.
Husk at starte siden med
en overskrift (== ... ==)

Bevar venligst denne kommentar. Please preserve this comment.
--> Det læser jeg som at jeg skal indsætte overskrift-delen ovenover denne forklaring: Kopier Brønd|Overskrift= ind over denne kommentar.!
Mens på selve Landsbybrønden står der:

1. Tryk på rediger
2. Gå til redigeringsfeltet og indsæt

   {{Brønd|Overskrift=Overskrift for emne}}

   under alle de andre indlæg og gem siden.
3. Gå til bunden af siden og tryk på et af de røde links der svarer til dit nye indlæg
4. Skriv dit indlæg, du skal starte med overskriften:

   == Overskrift for emne ==

5. Gem siden

Altså skal man faktisk ej indsætte sin overskriftsdel ind over men faktisk i bunden af siden (under alle de andre indlæg).
Jeg forslår at vi ændrer hjælpeteksten i de to ubehjælpsomme søjler til to blokke, først dansk og så engelsk, og så også gør klarere at man bør indsætte overskrift... i bunden af siden.
Allerhelst så jeg, at man kunne lave denne rediger lænke så den automatisk indsætte lænket i bunden af siden. Kan vi ej finde ud af dette?
Tak, B Lemeukx (diskussion) 21. aug 2017, 20:17 (UTC)

Rediger · Overvåg · Se kun underside

etymologiebank.nl - Bronverwijsning: Sijs, Nicoline van der ...

Hej,
når jeg bruger etymologiebank.nl synes de i bunden på hver artikel og på deres hovedside at gøre opmærksom på en fuld kildehenvisning. Jeg har derfor bragt vores tilsvarende skabelon på højde med dette. Men er det nødvendigt? Kan vi "nøjes" med bare at have den fulde kildebeskrivelse i selve skabelonopsætningen? Så at den tekst vi indsætter i vore opslagsordsartikler bliver kort som før:

• i etymologiebank.nl/

Og i skabelonen er der tilføjet en noinclude-del som følger:

• Sijs, Nicoline van der (samensteller) (2010), Etymologiebank, op etymologiebank.nl/

Så at man kan se fuld kildeangivelse ved at bruge vores interne lænke til skabelonen og den ej fylder vore artikler op? Ville vi være "god" på denne måde?, B Lemeukx (diskussion) 21. okt 2017, 13:16 (UTC)

Værker har sommetider en sådan anvisning om, hvordan de gerne vil citeres, men det plejer jeg at læse som et høfligt forslag; hvis jeg f.eks. skriver en artikel, vil jeg som regel gerne bruge en konsistent referencestandard, og det må vel være skribentens valg. Især skal kildeangivelsen naturligvis stå på det sprog, som der skrives i, hvilket her er dansk (så "samensteller" og "op" går ikke). Samtidig kan jeg ikke se fordelen ved at udelade proveniens. Skabelonsiden er til os der redigerer og bruger skabeloner, og bør i princippet være "usynlig" for den ikke-redigerende bruger, dvs. det bør ikke være nødvendigt at se på den, medmindre man er bidrager.__Gamren (diskussion) 21. okt 2017, 14:47 (UTC)

Rediger · Overvåg · Se kun underside

Skabelon:also og også Skabelon:også ?

Hej, jeg ser vi har yderligere en dublet på to skabeloner: {{also}} og {{også}}. Den sidste bliver flittigt brugt og er den mest danske, den første kom vist fra opstarten, pardon startup og bruges "kun" mellem 250 og under 500 gange.
Begge er begrænsede til kun 10 eller 9 elementer. Angives flere, som i dé-, optræder de i følgende: Kategori:Limit of template reached; og kun de 10 eller 9 første elementer vises.
Jeg vil forslå at vi laver to ting:

• Finder en venlig bot-tæmmer der erstatter {{also}} med {{også}}.
  • Måske er nogen i jule(gave)humør ;-)?
• Laver {{også}} mere generelt, så den kan klare flere elementer.
  • Jeg har set lige omkring, og den "nyeste" er nok fra fr-wikt, hvor de bruger en <div class="bandeau-voir"><span class="bandeau-voir-icone">''Voir aussi''</span> : {{#invoke:voir|liste_voir}}</div><noinclude>, dvs der ser ej ud til at være en numerisk begrænsning på 9 eller 10 eller 50 (es-wikt) elementer.
  • fr-wikt har ændret fra "kun" 100 elementer til brugen af <nowiki>#invoke:voir|liste_voir<nowiki> i 2013 [2].
  • Vi har brug for at kunne kalde på noget lignende end <nowiki>#invoke:voir|liste_voir<nowiki>! Har vi det allerede her?

Tak, B Lemeukx (diskussion) 23. dec 2017, 11:56 (UTC)

Ser lige at vore nynorske venner har en fin listefunktionalitet nn:Modul:Template:also som de bruger i nn:Mal:sjå òg siden juli iår.

• Jeg tror jeg starter med at udvide {{også}} til flere elementer, så har vi noget at gå videre med, og så kan vi tage det tunge arbejde med listefunktioner i næste år. Glædelig jul, godt nytår, fra : B Lemeukx (diskussion) 23. dec 2017, 12:12 (UTC)

Kan {{also}} erstattes af {{også}} i alle opslagsord uden problemer? Har de helt samme funktionalitet? Det burde ikke være noget problem at gøre med AutoWikiBrowser, men jeg har bare ikke en konto med botflag her på dawiktionary (har på dawiki og nowiktionary). Ifølge AWB er der 291 opslag, der bruger {{also}} og 607 opslag, der bruger {{også}}.
- Sarrus (d • b) d. 23. dec 2017, 12:42 (UTC)

Tak, Sarrus, vi kan erstatte {{also}} med {{også}} på alle, med undtagelse af dé-, da dens liste er længere end 9 elementer. B Lemeukx (diskussion) 23. dec 2017, 13:34 (UTC)

Jeg har opgivet at ændre {{også}}, den er for indviklet at udvide med bare ét element nå! :-( Det må blive den rigtige løsning med en liste-funktionalitet senere, B Lemeukx (diskussion) 23. dec 2017, 13:34 (UTC)

Rediger · Overvåg · Se kun underside

Skabelon:decl og også Skabelon:bøjn ?

Hej igen, vi har også en dublet her med {{-bøjn-}} som kun bruges lidt over 100 gange. Normalt bruger vi {{-decl-}}.

• Vi har brug for en bot-tæmmer til der erstatter {{-bøjn-}} med {{-decl-}} ;-) B Lemeukx (diskussion) 23. dec 2017, 13:42 (UTC)

Rediger · Overvåg · Se kun underside

Oversættelseværktøj

Hej B Lemeux og andre,

Du har tidligere udtrykt et ønske om et oversættelseværktøj. Jeg har kopieret translation_editor fra sv.wikt. Vil du (og andre interesserede) installere det (under Mine indstillinger > Gadgets) og fortælle mig hvad I synes? Det virker kun sammen med {{trans-top}} ({{(}} bliver vist også brugt til andre ting, så at ændre den ville nok være en dårlig idé). Desuden bliver navnet på sproget givet direkte, og ikke ved skabelon, hvilket jeg selv synes er en fordel. Jeg kan også få sprognavnet til at være med stort begyndelsesbogstav, hvis der er flertal for det (selv foretrækker jeg lille).__Gamren (diskussion) 16. dec 2017, 18:48 (UTC)

Det ser ud til, at den skriver “u” for fælleskøn. Her på stedet plejer vi at bruge “c”. Hvis man bruger “u”, vises ordets køn ikke.
- Sarrus (d • b) d. 16. dec 2017, 19:06 (UTC)

Tak for det, hermed rettet.__Gamren (diskussion) 16. dec 2017, 22:29 (UTC)

Der er stadig nogle svenske reminiscenser hist og pist. Det kunne måske også overvejes, om køn og bøjninger kunne fremstå på dansk. Det er eksempelvis ikke sikkert, at alle kan regne ud, at “mask.”=“maskulinum”=“hankøn”. Desuden kan det måske overvejes at erstatte “Læg oversættelse til” med “Tilføj oversættelse”? Derudover: På svwikt. kan man med et tilsvarende system tilføje oversættelser til et opslag, der endnu ikke har nogen oversættelser. Mon man kan tilføje det her også? På nowikt. er der også et tilsvarende system, men der kan man ikke. Når de forslag er nævnt, ser det ud til at virke :-).
- Sarrus (d • b) d. 17. dec 2017, 08:22 (UTC)

Jeg tror jeg har fået det sidste svenske væk nu (bortset fra det sted hvor Mall:sidnamn bliver kaldt). Forkortelserne er skrevet ud som hele ord. Muligheden for at tilføje nye oversættelsesskabeloner bliver sørget for af en anden gadget. Jeg kan prøve at kopiere den over, men den ser ud til at forvente at overskrifter angives med lighedstegn (==Dansk==, ====Oversættelser====) og ikke skabeloner ({=da=}, {-trans-}). En anden grund til at ønske at gøre det på den første måde er, at det gør det muligt at redigere enkelte afsnit ad gangen, og en tredje er at vi manuelt kan bestemme niveauet. Det kræver bare, at vi finder en anden måde at kategorisere efter sprog på. På en.wikt (og tilsyneladende også sv.wikt) bliver det gjort via den skabelon, der angiver navnet på ordet (og evt. andre data såsom køn, nogle få bøjninger, aspekt (for f.eks. russiske verber) eller klasse (for substantiver på zulu)), umiddelbart over definitionerne, altså det vi på en.wikt kalder the headword-line template.__Gamren (diskussion) 17. dec 2017, 09:57 (UTC)

Nu kan jeg slet ikke få funktionen til at virke. Kan det være fordi du er kommet til at slette et tegn efter “Kan ikke balancere pga. indskudte linjer”? Hvad siger du til at oversætte den tekst, der er ved knapperne? Resultatet står jo på dansk, så hvorfor ikke knappernes tekster?
- Sarrus (d • b) d. 17. dec 2017, 11:32 (UTC)

Tak. Jeg forsøgte lidt på land. Da jeg arbejdede med værktøjet, stod de tre sidste oversættelser sidst. Kan vi samle de to for [en]: country og state? Når jeg nu genkælder siden, står de først. De grønne pile for at flytte fra venstre til højre, eller omvendt, hjalp ej. Tak, B Lemeukx (diskussion) 20. dec 2017, 01:13 (UTC)

Det er fordi den forventer, at sprogene er skrevet som ord og alfabetiserer derefter, hvorimod de eksisterende oversættelser var skrevet med sprogskabeloner. Hvis I er enige i at skrive sprognavnene på den måde værktøjet nu gør, kan vi bede nogen med en bot rette de gamle oversættelser.__Gamren (diskussion) 20. dec 2017, 20:51 (UTC)

PS: Jeg er ikke sikker på hvad du mener med at genkælde/genkalde?__Gamren (diskussion) 20. dec 2017, 20:58 (UTC)

Så spørger jeg for tredje gang (kan ikke se, at nogen har kommenteret på det endnu, hvad enten I er for, imod eller ligeglade): Hvad siger I til, at teksten ved siden af oversættelsesknapperne skal stå på dansk, da ikke alle kan forventes at forstå, hvad eksempelvis “maskulinum” (hankøn), “femininum” (hunkøn), “neutrum” (intetkøn) og “pluralis” (flertal) betyder? Denne Wiktionary er trods alt en dansksproget ordbog. Resultatet står jo på dansk, så hvorfor ikke også “knapteksten”?
- Sarrus (d • b) d. 21. dec 2017, 13:20 (UTC)

Mener du at ændre ordene i gåseøjne til ordene i parenteser? Jeg er fuldstændig ligeglad. Jeg forstår ikke dit argument med dansksprogethed, når alle ordene er danske. Jeg brugte de ord jeg mente var hyppigst brugt, men alle ordene i parenteser har opslag her, så folk kan bare slå dem op, hvis de ikke kender dem.__Gamren (diskussion) 21. dec 2017, 19:45 (UTC)

Det er i hvert fald fagsprog så. Der er nok flere, der kender ordet "hankøn" end "maskulinum". Hvis man vil have folk til at bruge Wiktionary, må man bruge et sprog, som flest muligt forstår :-). Jeg ved ikke, hvorfor man har valgt at bruge skabeloner til at angive sprogkoder i oversættelsesafsnittet. Måske Bruger:Kinamand og/eller Bruger:Palnatoke kan svare på det. De har været her længere tid end mig. Det ser ikke ud til, at en skabelon som {{el}} gør andet end at skrive sprognavnet. Kan du eller andre gennemskue det?
- Sarrus (d • b) d. 21. dec 2017, 20:17 (UTC)

Mit gæt er at sprogkodeskabelonerne er der for at gøre det lettere at copy/paste mellem sprogene. Man skal stort set bare rette ordforklaringen. --Palnatoke (diskussion) 22. dec 2017, 07:38 (UTC)

Mener du at kopiere mellem forskellige sprogversioner? I princippet en god idé, hvis vi alle brugte samme format. de.wikt bruger sprogskabeloner, en.wikt og som sagt sv.wikt bruger selve navnene, fr.wikt bruger {T}.__Gamren (diskussion) 22. dec 2017, 11:14 (UTC)

B Lemeukx (diskussion) 22. dec 2017, 20:51 (UTC) : >>

* For: genkælde/genkalde, når jeg genindlæser siden via e.g. F5

* For: land, nu er der blandet engelsk (som tekst), Esperanto (fra {{eo}}), .... Jeg vil foretrække at sprognavnene bliver skrevet med stort, jeg synes det ser kønnest ud.

* For: at kopiere mellem forskellige sprogversioner?, med det ny værktøj kan de brugere bidrage der ej vil lære den underliggende wikt-programmering. Til gengæld vil vi med de udskrevne sprognavne gøre denne kopiering sværere for brugere der bruger kildeeditoren.

* For: teksten ved siden af oversættelsesknapperne skal stå på dansk, da ikke alle kan forventes at forstå, hvad eksempelvis “maskulinum” (hankøn), “femininum” (hunkøn), “neutrum” (intetkøn) og “pluralis” (flertal) betyder? :

* De fleste andre wikter bruger de lokale udtryk, men nogle sprog er mere "forkælede" ved at de som romanske sprog bruger de latinske udtryk - som "alle" kan forstå. Den islandske bruger de islandske udtryk, og jeg regner ej med at alle danskere kan tyde hvad hvorugkyn betyder.

* Antallet af sådanne fagudtryk er begrænsede; jeg vil mene de fleste internationale brugere nemt kan lære hvornår de skal trykke ved fælleskøn eller intetkøn for de danske ord og hankøn, hunkøn eller intetkøn for de fleste andre sprog.

* Hvis vi vil være ekstraflinke kan vi tilføje de latinske betegnelser i parenteser, eg: fælleskøn (utrum).

<< B Lemeukx (diskussion) 22. dec 2017, 20:51 (UTC)

PS: Jeg har ikke sat default til, hvilket vil sige at IP'er ikke kan bruge det endnu.__Gamren (diskussion) 3. jan 2018, 15:36 (UTC)

Dipsacus fullonum, kunne du stå for udskiftningen? Altså: I oversættelsesskabeloner (mellem {trans-top} og {trans-bottom}) at udskifte {en} med Engelsk, {de} med Tysk osv., og desuden {O|de|erinnern} med Tysk: {t|de|erinnern}? Det er måske også muligt at udskifte {(}, {-} og {)}, som mange steder bruges til oversættelser, med {trans-top}, {trans-mid} og {trans-bottom}? F.eks. vil der sandsynligvis være tale om en oversættelsestabel hvis {en} og/eller {de} forekommer.__Gamren (diskussion) 10. jan 2018, 15:57 (UTC)

Rediger · Overvåg · Se kun underside

Nynorsk / bokmål

Jeg har ofte lyst til å legge inn oversettelser til norsk når jeg ser det mangler; kanskje også opprette oppslag for ord som ikke har det. Men norsk kommer i flere former (offisielle målformer bokmål og nynorsk, uoffisielle målformer riksmål og høgnorsk), og jeg vet ikke om dere har en politikk på hvordan dere angir dette? Det er et noe komplisert tema, og ikke opplagt hvilken måte man bør gjøre det på (f.eks. behandles det som ett språk på no-wikt, men to på nn-wikt) – men ihvertfall virker det logisk å ha en felles rettningslinje på det, så oppslagene får noenlunde likt oppsett. Det virker litt unødvendig å legge inn oversettelser før noe slikt er på plass, for man må muligens gjøre alt om igjen .. Mewasul (diskussion) 8. feb 2018, 04:26 (UTC)

Hvis du gør det på en ensartet måde kan man senere skrive en bot der ændre det hele til noget andet. Kinamand (diskussion) 8. feb 2018, 13:36 (UTC)

På den anden måde er der ingen grund til at udskyde diskussionen. Personligt synes jeg bedst om at behandle norsk som ét sprog ligesom no.wikt gør (idet der selvf. gøres opmærksom på forskelle i bøjninger, køn osv. og at ord kun findes på en variant, som her) , primært fordi vi, hvis vi opretter bokmål og nynorsk, ikke har et sted at gøre af ord og former der falder udenfor de to normer. Det er garanteret blevet diskuteret på de norske wikter, og jeg ved det er blevet diskuteret på en.wikt, bl.a. var der en afstemning om det. Men hvad siger I der har arbejdet med norsk her, som f.eks. Bruger:Teodor605, Bruger:Mede?__Gamren (diskussion) 8. feb 2018, 17:18 (UTC)

Norsk er greit, men undertiden umuligt altid at angive de rigtige genusformer. Lad os se på første definition af no:brus. Alt i alt har vi brug for mindst tre forme, idet der skelnes mellem:

• brus m (Bokmål/Nynorsk), c (Riksmål).

Her ser vi sammenfald på bokmål og nynorsk, men det kunne jo være at genus er forskelligt for alle tre sprog!

Vi kan lave følgende oversættelser på da-wikt, men hvordan skal vi angi Riksmål (eller høgnorsk?) korrekt? Via {{no}}?:

• {{O|no|brus|c}} : Norsk: brus ^(no) fælleskøn
• {{O|nb|brus|m}} : Norsk bokmål: brus ^(nb) hankøn
• {{O|nn|brus|m}} : Nynorsk: brus ⁽ⁿⁿ⁾ hankøn

Faldt lige over et ekstremt tilfælde - no:søppel :

søppel m, f eller n (Bokmål), m, f eller n (Nynorsk), c eller n (Riksmål)

Kanske det bedste er at udelade genus på norske oversættelser?

Det næste er: skal vi understøtte alle tre forme som nu; eller endda udbygge med en fjerde: {{nr}} (for riksmål)? Eller skal vi slå sammen {{nb}} og {{no}}? Og bibeholde {{nn}}? Der findes en nn-wikt men ej en nb-wikt; så, er det den "mest gangbare" vej?

B Lemeukx (diskussion) 10. feb 2018, 11:12 (UTC)

Jeg forstår ikke hvorfor du mener at det er "umuligt altid at angive de rigtige genusformer"? Hvis vi samler norsk, bruger vi kun en enkelt kode - no - og specificerer i oversættelsestabeller. Jeg har lagt et parameter til {t} kaldet d der også kan bruges til at specificere dialekter og accenter (det skal selvfølgelig flyttes et andet sted hen for at undgå spagettikode), se her.__Gamren (diskussion) 10. feb 2018, 14:04 (UTC)

OK, jeg prøver lige med søppel som jo har alle fire genusformer, og som så måtte blive (med en ny parameter g for multiple genusformer; jeg skriver dem bare i rentekst bagved for at vise hvad jeg mener):

* {{t|no|søppel|d=nb|g=m,f,n}} : søppel (bokmål) ^(no) hankøn, hunkøn, intetkøn

* {{t|no|søppel|d=nn|g=m,f,n}} : søppel (nynorsk) ^(no) hankøn, hunkøn, intetkøn

* {{t|no|søppel|d=no|g=n,c}} : søppel (no) ^(no) intetkøn, fælleskøn

Hvis vi altså afbilder alle genusangivelserne fra no-wikt også her! (Sideidé: Findes der mon en nemmere måde via wikimedia, så at alle navneord indsættes dér - med alle deres genusangivelser, som så kommer automatisk med?), B Lemeukx (diskussion) 10. feb 2018, 15:32 (UTC)

Gamren: det at en del ord faller utenfor gitte normer er også en del av min motivasjon for å behandle norsk som ett språk, på no-wikt. :) Ellers: alt er mulig, man må bare tenke litt og se hva som vil virke hensiktsmessig.

• Antatt at vi behandler norsk som ett språk, er det ønskelig å oppgi hvilken målform ved oversettelser? (Er egentlig en større ting enn norsk - oppgir dere f.eks. om det er amerikansk eller britisk skrivemåte for engelsk?) På en side gir det jo mer informasjon, på en annen side kan det lett bli litt overveldende, med mange gjentagelser, og (sett at oppslaget finnes) er dette samme informasjon som angis i oppslaget i seg selv.
• Det også er mulig å angi alle kjønn i oversettelsestabellen uten å angi målform, og så gi mer informasjon på hovedoppslaget.
• Mange ord på norsk kan skrives litt ulikt (som kanskje kan være forvirrende til tider - men som også gjør at man har større mulighet til å tilpasse skriftspråket sin egen dialekt). F.eks. kan man skrive sten eller stein, hvit eller kvit, øst eller aust. I nynorsk kan verb slutte på -e eller -a: legge, legga, leggje, leggja; samme gjelder (enda flere varianter) bøteleggja, bøteleggje, bøtelegga, bøtelegge, bøtlegga, bøtlegge, bøtleggja, bøtleggje. Dette sprer seg videre i sammensetninger: stenlegge, steinlegge, steinlegga, steinleggje, steinleggja. (Merk at dette også er et spørsmål vi må jobbe mer med på no-wikt :))
  • Skal alle disse formene oppgis i oversettelsestabellen?
  • Skal alle formene ha all informasjon? Igjen er det fristende å se på engelsk: Hvor mye informasjon ville dere lagt inn dobbelt på ordparet organise og organize?

Dette er vel større spørsmål enn norsk, men er ganske relevante i denne diskusjonen. Og hvis dere allerede har en praksis på dette er det kanskje lettest å følge den videre :)

• (Sideidé svar: Jeg har en ønskedrøm om at all grammatisk informasjon, og kanskje andre ting også, kan legges inn et sted sentralt slik at alt man trenger å gjøre lokalt er å tilby et grensesnitt. Tenk deg f.eks. at man ikke trenger å angi bøyning på alle språkversjoner, men bare har en mal som henter dette fra noe ala Wikidata. Men tror ikke det kommer i nær fremtid ihvertfall ..)

Mewasul (diskussion) 14. feb 2018, 02:44 (UTC)

Der er ikke som sådan noget behov for at angive hverken køn eller sprogvariant i oversættelsestabeller; pointen var nok bare, at man så ikke skulle behøve besøge siden, men mange former vil nok gøre det mere besværligt. Hvad angår selve siderne, så udvælger jeg en ordvariant som får al information samt en liste over alternative former (se f.eks. bismuth, fandeme).

Mht. centralisering af grammatisk info: Under alle omstændigheder ville det kræve noget viden, da der findes ord der staves ens men bøjes forskelligt, som f.eks. øl.__Gamren (diskussion) 14. feb 2018, 12:50 (UTC)

Jeg prøvde meg litt frem – men er fortsatt litt usikker. Hvis dere, som er kjent med deres struktur, skulle legge inn et ord på norsk – det være godkjent i alle målformer, som kaffe, eller kun i bokmål og riksmål, som være (nynorsk har vere eller vera) – hvor ville dere angitt målform? Mewasul (diskussion) 25. mar 2018, 06:07 (UTC)

Rediger · Overvåg · Se kun underside

Selection of the Tremendous Wiktionary User Group representative to the Wikimedia Summit 2019

Dear all,

Sorry for posting this message in English and last minute notification. The Tremendous Wiktionary User Group could send one representative to the Wikimedia Summit 2019 (formerly "Wikimedia Conference"). The Wikimedia Summit is an yearly conference of all organizations affiliated to the Wikimedia Movement (including our Tremendous Wiktionary User Group). It is a great place to talk about Wiktionary needs to the chapters and other user groups that compose the Wikimedia movement.

For context, there is a short report on what happened last year. The deadline is very close to 24 hrs. The last date for registration is 17 December 2018. As a last minute effort, there is a page on meta to decide who will be the representative of the user group to the Wikimedia Summit created.

Please feel free to ask any question on the wiktionary-l mailing list or on the talk page.

For the Tremendous Wiktionary User Group, -- Balajijagadesh 16. dec 2018, 05:56 (UTC)

Invitation from Wiki Loves Love 2019

Hjælp venligst med at oversætte til dit sprog

Love is an important subject for humanity and it is expressed in different cultures and regions in different ways across the world through different gestures, ceremonies, festivals and to document expression of this rich and beautiful emotion, we need your help so we can share and spread the depth of cultures that each region has, the best of how people of that region, celebrate love.

Wiki Loves Love (WLL) is an international photography competition of Wikimedia Commons with the subject love testimonials happening in the month of February.

The primary goal of the competition is to document love testimonials through human cultural diversity such as monuments, ceremonies, snapshot of tender gesture, and miscellaneous objects used as symbol of love; to illustrate articles in the worldwide free encyclopedia Wikipedia, and other Wikimedia Foundation (WMF) projects.

The theme of 2019 iteration is Celebrations, Festivals, Ceremonies and rituals of love.

Sign up your affiliate or individually at Participants page.

To know more about the contest, check out our Commons Page and FAQs

There are several prizes to grab. Hope to see you spreading love this February with Wiki Loves Love!

Kind regards,

Wiki Loves Love Team

Imagine... the sum of all love!

--MediaWiki message delivery (diskussion) 27. dec 2018, 10:12 (UTC)

FileExporter beta feature

Coming soon: the beta feature FileExporter

A new beta feature will soon be released on all wikis: The FileExporter. It allows exports of files from a local wiki to Wikimedia Commons, including their file history and page history. Which files can be exported is defined by each wiki's community: Please check your wiki's configuration file if you want to use this feature.

The FileExporter has already been a beta feature on mediawiki.org, meta.wikimedia, deWP, faWP, arWP, koWP and on wikisource.org. After some functionality was added, it's now becoming a beta feature on all wikis. Deployment is planned for January 16. More information can be found on the project page.

As always, feedback is highly appreciated. If you want to test the FileExporter, please activate it in your user preferences. The best place for feedback is the central talk page. Thank you from Wikimedia Deutschland's Technical Wishes project.

Johanna Strodt (WMDE) 14. jan 2019, 09:41 (UTC)

No editing for 30 minutes 17 January

You will not be able to edit the wikis for up to 30 minutes on 17 January 07:00 UTC. This is because of a database problem that has to be fixed immediately. You can still read the wikis. Some wikis are not affected. They don't get this message. You can see which wikis are not affected on this page. Most wikis are affected. The time you can't edit might be shorter than 30 minutes. /Johan (WMF)

16. jan 2019, 14:47 (UTC)

Talk to us about talking

The Wikimedia Foundation is planning a global consultation about communication. The goal is to bring Wikimedians and wiki-minded people together to improve tools for communication.

We want all contributors to be able to talk to each other on the wikis, whatever their experience, their skills or their devices.

We are looking for input from as many different parts of the Wikimedia community as possible. It will come from multiple projects, in multiple languages, and with multiple perspectives.

We are currently planning the consultation. We need your help.

We need volunteers to help talk to their communities or user groups.

You can help by hosting a discussion at your wiki. Here's what to do:

1. First, sign up your group here.
2. Next, create a page (or a section on a Village pump, or an e-mail thread – whatever is natural for your group) to collect information from other people in your group. This is not a vote or decision-making discussion: we are just collecting feedback.
3. Then ask people what they think about communication processes. We want to hear stories and other information about how people communicate with each other on and off wiki. Please consider asking these five questions:
   1. When you want to discuss a topic with your community, what tools work for you, and what problems block you?
   2. What about talk pages works for newcomers, and what blocks them?
   3. What do others struggle with in your community about talk pages?
   4. What do you wish you could do on talk pages, but can't due to the technical limitations?
   5. What are the important aspects of a "wiki discussion"?
4. Finally, please go to Talk pages consultation 2019 on Mediawiki.org and report what you learned from your group. Please include links if the discussion is available to the public.

You can also help build the list of the many different ways people talk to each other.

Not all groups active on wikis or around wikis use the same way to discuss things: it can happen on wiki, on social networks, through external tools... Tell us how your group communicates.

You can read more about the overall process on mediawiki.org. If you have questions or ideas, you can leave feedback about the consultation process in the language you prefer.

Thank you! We're looking forward to talking with you.

Trizek (WMF) 21. feb 2019, 15:01 (UTC)

Read-only mode for up to 30 minutes on 11 April

You will not be able to edit most Wikimedia wikis for up to 30 minutes on 11 April 05:00 UTC. This is because of a hardware problem. You can still read the wikis. You can see which wikis are affected. The time you can not edit might be shorter than 30 minutes. /Johan (WMF)

8. apr 2019, 10:56 (UTC)

Wikimedia Foundation Medium-Term Plan feedback request

Hjælp venligst med at oversætte til dit sprog

The Wikimedia Foundation has published a Medium-Term Plan proposal covering the next 3–5 years. We want your feedback! Please leave all comments and questions, in any language, on the talk page, by April 20. Tak! Quiddity (WMF) (talk) 12. apr 2019, 17:35 (UTC)

Input ang. affiliate-udvalgte bestyrelsesmedlemmer 2019

Wikimedia Foundation, organisationen der står for driften af Wikipedia og Wikipedias søsterprojekter, og som Wikimedia Danmark er et "chapter" af, ledes af en bestyrelse på 10 personer. Fem af disse personer vælges af Wikimedia-bevægelsen, enten gennem direkte valg (3 personer) eller af Wikimedia affiliate-organisationer (2 personer). Begge typer positioner vælges hvert tredje år, dog forskudt med et år.

I 2019 skal affiliate-organisationerne vælge to personer til bestyrelsen. Fra den 15. til 30. april stiller kandiaterne op på meta-wiki, hvor man også kan stille dem spørgsmål. En kandidat skal være godkendt (endorsed) af 2 affiliate-organisationer for at kunne stille op. Fra den 1. til 7. maj "låses" listen over kandidater, og fællesskabet kan granske dem nærmere. Fra den 8. til 31. maj kan affiliate-organisationerne stemme på de kandidater, de ønsker skal sidde i bestyrelsen. Afstemningen anvender rangorden-systemet (single transferable vote)

Wikimedia Danmark er som chapter berettiget til at deltage i processen. Beslutningen om godkendelse (endorsement) af kandidater og hvem der stemmes på, træffes af bestyrelsen, men vi hører meget gerne fra medlemmer af foreningen samt fra det danske Wikimedia-miljø, hvis der er bestemte kandidater som man mener vi bør godkende eller stemme på. Skriv her eller på WikimediaDK-diskussionslisten med forslag. -- InsaneHacker (diskussion) 19. apr 2019, 13:22 (UTC)

Rediger · Overvåg · Se kun underside

WMDK-legater til Wikimania 2019

Fra den 14. til den 18. august 2019 afvikles Wikimania-konferencen i Stockholm. Konferencen er en samling af alle interessenter i Wikimedia-bevægelsen, og årets tema er Stronger Together: Wikimedia, Free Knowledge and the Sustainable Development Goals, en anskuelse af Wikimedia-bevægelsen ud fra FN's verdensmål.

Wikimedia Danmark agter at stille 3 legater af 2000 kr. til rådighed, hvilket er nok til at dække registreringsomkostningerne for hovedkonferencen d. 16.-18. august (midlerne må dog også gerne anvendes til deltagelse i konferencens "pre-days" d. 14.-15. august), samt en del af rejseomkostningerne. Legaterne er tiltænkt personer der er aktive i det danske Wikimedia-miljø. Modtagere vil skulle forpligte sig til at anvende midlerne til deltagelse i Wikimania-konferencen, og at dokumentere denne anvendelse af midlerne. Personer der allerede har tilmeldt sig konferencen kan også ansøge med henblik på at få dækket nogle af omkostningerne.

Interesserede bedes sende en email til bestyrelsewikimedia.dk med en kort beskrivelse af dem selv og deres tilknytning til det danske Wikimedia-miljø senest den 10. juni. Ansøgere til legaterne indvilliger i, at oplyse deres identitet og andre relevante informationer. De, der bliver valgt, vil blive kontaktet senest den 15. juni med henblik på at fastlægge det praktiske.

InsaneHacker (diskussion) 31. maj 2019, 08:12 (UTC)

Rediger · Overvåg · Se kun underside

Update on the consultation about office actions

Hello all,

Last month, the Wikimedia Foundation's Trust & Safety team announced a future consultation about partial and/or temporary office actions. We want to let you know that the draft version of this consultation has now been posted on Meta.

This is a draft. It is not intended to be the consultation itself, which will be posted on Meta likely in early September. Please do not treat this draft as a consultation. Instead, we ask your assistance in forming the final language for the consultation.

For that end, we would like your input over the next couple of weeks about what questions the consultation should ask about partial and temporary Foundation office action bans and how it should be formatted. Please post it on the draft talk page. Our goal is to provide space for the community to discuss all the aspects of these office actions that need to be discussed, and we want to ensure with your feedback that the consultation is presented in the best way to encourage frank and constructive conversation.

Please visit the consultation draft on Meta-wiki and leave your comments on the draft’s talk page about what the consultation should look like and what questions it should ask.

Thank you for your input! -- The Trust & Safety team 16. aug 2019, 08:03 (UTC)

New tools and IP masking

Hey everyone,

The Wikimedia Foundation wants to work on two things that affect how we patrol changes and handle vandalism and harassment. We want to make the tools that are used to handle bad edits better. We also want to get better privacy for unregistered users so their IP addresses are no longer shown to everyone in the world. We would not hide IP addresses until we have better tools for patrolling.

We have an idea of what tools could be working better and how a more limited access to IP addresses would change things, but we need to hear from more wikis. You can read more about the project on Meta and post comments and feedback. Now is when we need to hear from you to be able to give you better tools to handle vandalism, spam and harassment.

You can post in your language if you can't write in English.

Johan (WMF)

21. aug 2019, 14:19 (UTC)

Forbedring af skabeloner

Hej, jeg har begyndt at deltage mere på en:wiktionary og jeg kan rigtig godt li' deres oversættelsesskablon som tydeligt angiver oversættelser og muliggør let at tilføje nye. Er det nogen som ved hvordan vi får en lignende sådan her på da:wiktionary?

Ligeledes ønsker jeg en oversyn af vores brug af skabeloner sådan at det er lettere at ændre i ordbogen når man kommer fx fra en:wiktionary. Er der nogen imod at vi anpasser vores skabeloner og sider sådan at de følger en:wiktionary? (det bliver lettere for alle om wiktionary på tværs af sprog har en nogenlunde lignende struktur på siderne)

Jeg ser at de er kommet længere med dette på sv:wiktionary hvor de fx har gjort sig af med {{-decl-}} {{-rel-}} {{-ref-}} og lignende og erstattet dem med rigtige overskrifter.--So9q (diskussion) 26. aug 2019, 13:20 (UTC)

Hej @So9q,

1. hvad angår oversættelsesskabelon kan du bruge samme syntaks som på engelsk, som på bruttotonnage. Eksisterende artikler angiver som regel navnet på sproget vha. skabeloner som {{en}} og {{de}}, men alle disse skabeloner er noget rodede. Nuværende funktion er det samme, men med lille begyndelsesbogstav (koden er her, den relevante linje er text: 'Skabelon:' + lang code + '', og man skal være sysop for at ændre det). Jeg burde kunne lave et modul der tager en sprogkode og giver et sprognavn. Udover en admin skal vi bruge en botejer til at rette eksisterende artikler, når vi har fået fastlagt præcs hvad vi vil have. Vi talte tidligere om det her.
2. Mht. overskriftsskabeloner: Jeg ville også foretrække manuelle overskrifter. En ulempe ved overskrlanlang codeiftsskabelonerne er, man ikke kan redigere enkelte sektioner. Jeg opdagede, at hvis man sletter i skabelonkoden (for alle skabeloner der bruges på en bestemt side, hvis jeg husker ret), så vil redigérlinket på artiklen føre til skabelonsiden, og ikke artiklen. Overskriftsskabeloner er dog også ansvarlige for kategorisering, så deres afskaffelse forudsætter indførelse af anden metode. F.eks. noget tilsvarende {{head}} (som jeg oprettede i imitation af den vi bruger på en.wikt).
3. I det hele taget er færre skabeloner og mere centralisering mere overskueligt, og lettere at ændre på.__Gamren (diskussion) 26. aug 2019, 15:28 (UTC)

Hej Gamren :) Tak for det udførlige svar. Det lyder som vi tænker i de samme baner. I øvrigt savner jeg den værktøjskasse med links som findes i bunden af redigeringsvinduet på en:- og sv:wiktionary.

Har du noget forslag til næste skridt fremad?--So9q (diskussion) 28. aug 2019, 10:33 (UTC)

Jeg er helt enige i jeres tanker og kender desværre ikke løsningen. Så vidt jeg husker fra sidst jeg kiggede på det kom jeg frem til at man skulle lave nogle moduler i programmeringssproget lua for at kunne lave de smarte skabeloner de bruge på en.wiktionary. Kinamand (diskussion) 29. aug 2019, 12:22 (UTC)

Jeg har lavet Modul:lang og Modul:lang/data (se kommentarer indledt med "--"), baseret på skabelonerne i Kategori:Wiktionary:Sprogforkortelser. I den sammenhæng faldt jeg over nogle fejl og mangler, bl.a. sprog med mere end en kode (se Kategori:Sider der er foreslået slettet hurtigt), sprog der ikke havde noget navn overhovedet (kky og zai) og sprog med mere end et navn (dsb/nedersorbisk vs. lsb/nedresorbisk).
syreregn bruger et format lignende det på en.wikt. {{head}} har den samme basale funktion som dens navnebror på en.wikt. Er det tilfredsstillende?__Gamren (diskussion) 29. aug 2019, 14:02 (UTC)

Bruger:Kinamand, Kan du fortælle mig mere præcist hvilke skabeloner eller hvilken funktionalitet fra en.wikt du mener vi bør have her?__Gamren (diskussion) 29. aug 2019, 14:13 (UTC)

Fx {{character info/new}} Kinamand (diskussion) 29. aug 2019, 19:47 (UTC)

syreregn ser godt ud @Gamren. Jeg har netop importeret Skabelon:ping og Skabelon:svar_til men sidstnævnte savner dette modul: https://en.wiktionary.org/wiki/Module:ping_user kan du importere det?--So9q (diskussion) 30. aug 2019, 08:09 (UTC)

Rediger · Overvåg · Se kun underside

Roboterstatning af overskrifter

Hej, ad samtalen oven har jeg følgende udkast til masseerstatning af overskrifter:

1. {{=da=}} -> == Dansk ==
2. {{=sv=}} -> == Svensk ==
3. {{=ru=}} -> == Russisk ==
4. {{=de=}} -> == Tysk ==
5. {{-etym-}} -> \n==== Etymologi ====
6. {{-pronun-}} -> \n==== Udtale ====
7. {{-noun-|da}} -> \n=== Substantiv ===\n{{head|da|substantiv}}
8. {{-verb-|da}} -> \n=== Verbum ===\n{{head|da|verbum}}
9. {{-adv-|da}} -> \n=== Adverbium ===\n{{head|da|adverbium}}
10. {{-adv-|da}} -> \n=== Adjektiv ===\n{{head|da|adjektiv}}
11. {{-interj-|da}} -> \n=== Verbum ===\n{{head|da|interjektion}}
12. {{-ang-}} -> \n==== Anagrammer ====
13. {{-ant-}} -> \n==== Antonymer ====
14. {{-decl-}} -> \n==== Bøjning ====
15. {{-ref-}} -> \n=== Kilder ===
16. {{-rel-}} -> \n==== Beslægtede ord og fraser ====
17. {{-syn-}} -> \n==== Synonymer ====
18. {{-trans-}} -> \n==== Oversættelser ====
19. {{(}} -> {{trans-top|}}
20. {{-}} -> {{trans-mid}}
21. {{)}} -> {{trans-bottom}}

Nogen reaktion på det?

Lyder fint. Kinamand (diskussion) 31. aug 2019, 08:29 (UTC)

Hvad skulle fordelen være ved det? Ved brug at skabelonerne kan ikke-danskkyndige til dels også bidrage. Desuden ryger den kategorisering, skabelonerne laver.
- Sarrus (d • b) d. 31. aug 2019, 10:15 (UTC)

Tak for dit spørgsmål @Sarrus. Hovedargumenterne er 3 fra diskussionen her ovenfor:

1. Mere overskuelig wikitekst som ikke nødvendigvis fordrer at man kender til et hav af skabeloner.
2. Mulighed at ændre i sektioner baseret på overskrifternes inddeling af teksten.
3. Vi anpasser os til udviklingen på flagskibet en:wiktionary og det bliver nemmere at underholde wikien med den lille mandkraft vi har til rådighed.

Jeg synes personligt at wikier som fx den tyske, den polske er noget værre rod med alle talhenvisninger og skabeloner. I modsætning har fx svenskerne nærmet sig den engelske og lykkes meget bedre synes jeg.

Dit argument, om at skabeloner med forkortelser skulle være nemmere end overskrifter, synes jeg ikke opvejer ulemperne eftersom at overskrifterne er ganske få og ganske lig de andre sprog. Fx antonym, antonym (sv), antonym (en), osv.

Jeg foreslår i tillæg til denne ændring at vi installerer tegn-boksen under redigeringsvinduet og ligesom på en:wikt fylder den med almindelige overskrifter så de kan indsættes med et klik.--So9q (diskussion) 31. aug 2019, 13:33 (UTC)

Grundet studiestart har jeg ikke så meget tid til at hjælpe til, men jeg vil foreslå at du venter med dette til efter kategoriseringen er blevet sørget for.__Gamren (diskussion) 3. sep 2019, 20:30 (UTC)

Ekstra lille bemærkning: ang, som åbenbart står for anagram, er også sprogkoden for oldengelsk.

Rediger · Overvåg · Se kun underside

common.js fungerer ikke

Hej. Når jeg indsætter js på min brugers common.js så fungerer det ikke. På en:wiktionary fungerer det fint.--So9q (diskussion) 31. aug 2019, 11:01 (UTC)

1) Kan det være et cache-problem? 2) Kan det være et Javascript-problem: Får du fejlmeddelelser nå du ser debug informationen med F12-knappen trykket. — Fnielsen (diskussion) 13. sep 2019, 14:54 (UTC)

Rediger · Overvåg · Se kun underside

Ophavsret, Wikionary og Wikidata

Jeg ser nu at der er en bot der i stort omfang kopiere visse dele af den russiske Wiktionary til Wikidata lexemer. Yuri som har stået for det har henvist til Wikimedia Foundations "perspective" omkring emnet. Spørgsmålet er hvad der er ophavsretsmæssigt beskyttet på Wiktionary. Konklussionen som går under "This Is Not Legal Advice" er at grammatikken ikke er ophavsretsbeskyttet, — og det derfor burde være muligt at kopiere lemma og bøjninger fra Wiktionary til Creative Commons Zero-baserede Wikidata (men ikke for eksempel, brugseksempler og definitioner). Jeg gad vide hvordan danske Wiktionary-redaktører stiller sig over for den problematik. Ville det være en idé at kopiere danske ord og deres bøjninger til Wikidata, eller er det problematisk?

Der er iøjeblikket også opråb fra Lea Lacroix om input til hvordan og hvilke funktionaliteter Wikidata-til-Wiktionary der er ønsket.

Jeg ser også at den russiske Wiktionary har skabt en lille sideboks der linker fra Wiktionary-sider til relevante Wikidata-leksemer. Måske skulle vi også have en sådan på den danske Wiktionary?

— Fnielsen (diskussion) 13. sep 2019, 14:52 (UTC)

Intet er ophavsretsmæssigt beskyttet på Wiktionary. Hele ideen med Wiktionary og Wikipedia er at indholdet frit skal kunne bruges af alle og til hvad som helst. Kan du give et link til at eksempel på en side på den russiske Wiktionary der har den lille sideboks du snakker om så vi kan se hvad du mener? Kinamand (diskussion) 15. sep 2019, 11:00 (UTC)

@Kinamand Det er ikke Wikimedia Foundations non-legal-advice mening at intet på er ophavsretsmæssigt beskyttet på Wiktionary. WMF konklussion er netop at "Microstructure and Macrostructure", "Definitions with room for creativity", "Pragmatic information" og "Encyclopedic information and example sentences" er ophavsretsmæssigt beskyttet og "kun" er tilgængelig under den sædvanlige CC BY-SA licens. Da Wikidata benytter CC0 er det WMF's tro at visse dele af Wiktionary ikke kan kopieres til Wikidata. Som jeg forstår på den russiske Wiktionary er Yuri i gang med at forsøge at få skribenter til at relicensere deres Wiktionary-bidrag så det falder ind under CC0 og kan kopieres til Wikidata. Yuri's hidtidige arbejder har været med bøjningerne og lemma som WMF mener ikke er ophavsretsbeskyttet. Mht. sideboksen: Der er oversigt over de russiske leksemer i Ordia her: https://tools.wmflabs.org/ordia/language/Q7737 Et eksempel er https://ru.wiktionary.org/wiki/%D0%B0%D0%B2%D0%B8%D0%B0%D0%BA%D1%80%D1%83%D0%B6%D0%BE%D0%BA hvor sideboksen findes som den første boks til højre. — Fnielsen (diskussion) 16. sep 2019, 09:58 (UTC)

Rediger · Overvåg · Se kun underside

The consultation on partial and temporary Foundation bans just started

Hello,

In a recent statement, the Wikimedia Foundation Board of Trustees requested that staff hold a consultation to "re-evaluat[e] or add community input to the two new office action policy tools (temporary and partial Foundation bans)".

Accordingly, the Foundation's Trust & Safety team invites all Wikimedians to join this consultation and give their feedback from 30 September to 30 October.

How can you help?

• Suggest how partial and temporary Foundation bans should be used, if they should (eg: On all projects, or only on a subset);

• Give ideas about how partial and temporary Foundation bans should ideally implemented, if they should be; and/or

• Propose changes to the existing Office Actions policy on partial and temporary bans.

We offer our thanks in advance for your contributions, and we hope to get as much input as possible from community members during this consultation!

-- Kbrown (WMF) 30. sep 2019, 17:14 (UTC)

Feedback wanted on Desktop Improvements project

Hjælp venligst med at oversætte til dit sprog

Hello. The Readers Web team at the WMF will work on some improvements to the desktop interface over the next couple of years. The goal is to increase usability without removing any functionality. We have been inspired by changes made by volunteers, but that currently only exist as local gadgets and user scripts, prototypes, and volunteer-led skins. We would like to begin the process of bringing some of these changes into the default experience on all Wikimedia projects.

We are currently in the research stage of this project and are looking for ideas for improvements, as well as feedback on our current ideas and mockups. So far, we have performed interviews with community members at Wikimania. We have gathered lists of previous volunteer and WMF work in this area. We are examining possible technical approaches for such changes.

We would like individual feedback on the following:

• Identifying focus areas for the project we have not yet discovered
• Expanding the list of existing gadgets and user scripts that are related to providing a better desktop experience. If you can think of some of these from your wiki, please let us know
• Feedback on the ideas and mockups we have collected so far

We would also like to gather a list of wikis that would be interested in being test wikis for this project - these wikis would be the first to receive the updates once we’re ready to start building.

When giving feedback, please consider the following goals of the project:

• Make it easier for readers to focus on the content
• Provide easier access to everyday actions (e.g. search, language switching, editing)
• Put things in logical and useful places
• Increase consistency in the interface with other platforms - mobile web and the apps
• Eliminate clutter
• Plan for future growth

As well as the following constraints:

• Not touching the content - no work will be done in terms of styling templates or to the structure of page contents themselves
• Not removing any functionality - things might move around, but all navigational items and other functionality currently available by default will remain
• No drastic changes to the layout - we're taking an evolutionary approach to the changes and want the site to continue feeling familiar to readers and editors

Please give all feedback (in any language) at mw:Talk:Reading/Web/Desktop Improvements

After this round of feedback, we plan on building a prototype of suggested changes based on the feedback we receive. You’ll hear from us again asking for feedback on this prototype.

Tak! Quiddity (WMF) (talk)

16. okt 2019, 07:15 (UTC)

Community Wishlist 2020

The 2020 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on November 11, 2019, or comment on other proposals to help make them better.

This year, we’re exclusively focusing on smaller projects (i.e., Wikibooks, Wiktionary, Wikiquote, Wikisource, Wikiversity, Wikispecies, Wikivoyage, and Wikinews). We want to help these projects and provide meaningful improvements to diverse communities. If you’re a member of any of these projects, please participate in the survey! To submit proposals, see the guidelines on the survey page. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!

IFried (WMF) 4. nov 2019, 19:30 (UTC)

Wiki Loves Folklore

Hello Folks,

Wiki Loves Love is back again in 2020 iteration as Wiki Loves Folklore from 1 February, 2020 - 29 February, 2020. Join us to celebrate the local cultural heritage of your region with the theme of folklore in the international photography contest at Wikimedia Commons. Images, videos and audios representing different forms of folk cultures and new forms of heritage that haven’t otherwise been documented so far are welcome submissions in Wiki Loves Folklore. Learn more about the contest at Meta-Wiki and Commons.

Kind regards,
Wiki Loves Folklore International Team
— Tulsi Bhagat (contribs | talk)
sent using MediaWiki message delivery (diskussion) 18. jan 2020, 06:14 (UTC)

Movement Learning and Leadership Development Project

Hello

The Wikimedia Foundation’s Community Development team is seeking to learn more about the way volunteers learn and develop into the many different roles that exist in the movement. Our goal is to build a movement informed framework that provides shared clarity and outlines accessible pathways on how to grow and develop skills within the movement. To this end, we are looking to speak with you, our community to learn about your journey as a Wikimedia volunteer. Whether you joined yesterday or have been here from the very start, we want to hear about the many ways volunteers join and contribute to our movement.

To learn more about the project, please visit the Meta page. If you are interested in participating in the project, please complete this simple Google form. Although we may not be able to speak to everyone who expresses interest, we encourage you to complete this short form if you are interested in participating!

-- LMiranda (WMF) (talk) 22. jan 2020, 19:01 (UTC)

Feedback on movement names

Hello. Apologies if you are not reading this message in your native language. Hjælp venligst med at oversætte til dit sprog if necessary. Tak!

There are a lot of conversations happening about the future of our movement names. We hope that you are part of these discussions and that your community is represented.

Since 16 June, the Foundation Brand Team has been running a survey in 7 languages about 3 naming options. There are also community members sharing concerns about renaming in a Community Open Letter.

Our goal in this call for feedback is to hear from across the community, so we encourage you to participate in the survey, the open letter, or both. The survey will go through 7 July in all timezones. Input from the survey and discussions will be analyzed and published on Meta-Wiki.

Thanks for thinking about the future of the movement, --The Brand Project team, 2. jul 2020, 19:39 (UTC)

Note: The survey is conducted via a third-party service, which may subject it to additional terms. For more information on privacy and data-handling, see the survey privacy statement.

Announcing a new wiki project! Welcome, Abstract Wikipedia

Hi all,

It is my honor to introduce Abstract Wikipedia, a new project that has been unanimously approved by the Wikimedia Foundation Board of Trustees. Abstract Wikipedia proposes a new way to generate baseline encyclopedic content in a multilingual fashion, allowing more contributors and more readers to share more knowledge in more languages. It is an approach that aims to make cross-lingual cooperation easier on our projects, increase the sustainability of our movement through expanding access to participation, improve the user experience for readers of all languages, and innovate in free knowledge by connecting some of the strengths of our movement to create something new.

This is our first new project in over seven years. Abstract Wikipedia was submitted as a project proposal by Denny Vrandečić in May 2020 after years of preparation and research, leading to a detailed plan and lively discussions in the Wikimedia communities. We know that the energy and the creativity of the community often runs up against language barriers, and information that is available in one language may not make it to other language Wikipedias. Abstract Wikipedia intends to look and feel like a Wikipedia, but build on the powerful, language-independent conceptual models of Wikidata, with the goal of letting volunteers create and maintain Wikipedia articles across our polyglot Wikimedia world.

The project will allow volunteers to assemble the fundamentals of an article using words and entities from Wikidata. Because Wikidata uses conceptual models that are meant to be universal across languages, it should be possible to use and extend these building blocks of knowledge to create models for articles that also have universal value. Using code, volunteers will be able to translate these abstract “articles” into their own languages. If successful, this could eventually allow everyone to read about any topic in Wikidata in their own language.

As you can imagine, this work will require a lot of software development, and a lot of cooperation among Wikimedians. In order to make this effort possible, Denny will join the Foundation as a staff member in July and lead this initiative. You may know Denny as the creator of Wikidata, a long-time community member, a former staff member at Wikimedia Deutschland, and a former Trustee at the Wikimedia Foundation . We are very excited that Denny will bring his skills and expertise to work on this project alongside the Foundation’s product, technology, and community liaison teams.

It is important to acknowledge that this is an experimental project, and that every Wikipedia community has different needs. This project may offer some communities great advantages. Other communities may engage less. Every language Wikipedia community will be free to choose and moderate whether or how they would use content from this project.

We are excited that this new wiki-project has the possibility to advance knowledge equity through increased access to knowledge. It also invites us to consider and engage with critical questions about how and by whom knowledge is constructed. We look forward to working in cooperation with the communities to think through these important questions.

There is much to do as we begin designing a plan for Abstract Wikipedia in close collaboration with our communities. I encourage you to get involved by going to the project page and joining the new mailing list . We recognize that Abstract Wikipedia is ambitious, but we also recognize its potential. We invite you all to join us on a new, unexplored path.

Yours,

Katherine Maher (Executive Director, Wikimedia Foundation)

Sent by m:User:Elitre (WMF) 9. jul 2020, 20:13 (UTC) - m:Special:MyLanguage/Abstract Wikipedia/July 2020 announcement

Technical Wishes: FileExporter and FileImporter become default features on all Wikis

The FileExporter and FileImporter will become a default features on all wikis until August 7, 2020. They are planned to help you to move files from your local wiki to Wikimedia Commons easier while keeping all original file information (Description, Source, Date, Author, View History) intact. Additionally, the move is documented in the files view history. How does it work?

Step 1: If you are an auto-confirmed user, you will see a link "Move file to Wikimedia Commons" on the local file page.

Step 2: When you click on this link, the FileImporter checks if the file can in fact be moved to Wikimedia Commons. These checks are performed based on the wiki's configuration file which is created and maintained by each local wiki community.

Step 3: If the file is compatible with Wikimedia Commons, you will be taken to an import page, at which you can update or add information regarding the file, such as the description. You can also add the 'Now Commons' template to the file on the local wiki by clicking the corresponding check box in the import form. Admins can delete the file from the local wiki by enabling the corresponding checkbox. By clicking on the 'Import' button at the end of the page, the file is imported to Wikimedia Commons.

If you want to know more about the FileImporter extension or the Technical Wishes Project, follow the links. --For the Technical Wishes Team:

Max Klemm (WMDE) 6. aug 2020, 09:13 (UTC)

Important: maintenance operation on September 1st

Read this message in another language • Hjælp venligst med at oversætte til dit sprog

The Wikimedia Foundation will be testing its secondary data centre. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic to the secondary data centre on Tuesday, September 1st 2020.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for up to an hour on Tuesday, September 1st. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 19:30 IST, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday September 2).
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• There will be code freezes for the week of September 1st, 2020. Non-essential code deployments will not happen.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. Please share this information with your community.

Trizek (WMF) (talk) 26. aug 2020, 13:49 (UTC)

Invitation to participate in the conversation

Hello. Apologies for cross-posting, and that you may not be reading this message in your native language: translations of the following announcement may be available on Meta. Hjælp venligst med at oversætte til dit sprog. Tak!

We are excited to share a draft of the Universal Code of Conduct, which the Wikimedia Foundation Board of Trustees called for earlier this year, for your review and feedback. The discussion will be open until October 6, 2020.

The UCoC Drafting Committee wants to learn which parts of the draft would present challenges for you or your work. What is missing from this draft? What do you like, and what could be improved?

Please join the conversation and share this invitation with others who may be interested to join, too.

To reduce language barriers during the process, you are welcomed to translate this message and the Universal Code of Conduct/Draft review. You and your community may choose to provide your opinions/feedback using your local languages.

To learn more about the UCoC project, see the Universal Code of Conduct page, and the FAQ, on Meta.

Thanks in advance for your attention and contributions, The Trust and Safety team at Wikimedia Foundation, 10. sep 2020, 17:55 (UTC) 

Wiktionary sitelinks dashboard: URL update

Hello all, and sorry for writing in English. Feel free to translate this message below.

The Wiktionary Cognate Dashboard presents interesting data about the extension powering your sitelinks. I just wanted to let you know that the URL of this tool changed: it is now accessible at https://wiktionary-analytics.wmcloud.org/Wiktionary_CognateDashboard/ . The former URLs, https://wmdeanalytics.wmflabs.org/Wiktionary_CognateDashboard/ and https://wdcm.wmflabs.org/Wiktionary_CognateDashboard/ , will be disabled on September 25th. Don't forget to update your documentation pages accordingly.

If you have questions about the tool or the URL switch, feel free to ping me. Cheers, Lea Lacroix (WMDE) 14. sep 2020, 11:46 (UTC)

Wiki of functions naming contest

Hjælp venligst med at oversætte til dit sprog.

Hello. Please help pick a name for the new Wikimedia wiki project. This project will be a wiki where the community can work together on a library of functions. The community can create new functions, read about them, discuss them, and share them. Some of these functions will be used to help create language-independent Wikipedia articles that can be displayed in any language, as part of the Abstract Wikipedia project. But functions will also be usable in many other situations.

There will be two rounds of voting, each followed by legal review of candidates, with voting beginning on 29 September and 27 October. Our goal is to have a final project name selected on 8 December. If you would like to participate, then please learn more and vote now at meta-wiki. Tak! --Quiddity (WMF)

29. sep 2020, 21:16 (UTC)

Call for feedback about Wikimedia Foundation Bylaws changes and Board candidate rubric

Hello. Apologies if you are not reading this message in your native language. Hjælp venligst med at oversætte til dit sprog.

Today the Wikimedia Foundation Board of Trustees starts two calls for feedback. One is about changes to the Bylaws mainly to increase the Board size from 10 to 16 members. The other one is about a trustee candidate rubric to introduce new, more effective ways to evaluate new Board candidates. The Board welcomes your comments through 26 October. For more details, check the full announcement.

Tak! Qgil-WMF (talk) 7. okt 2020, 17:11 (UTC)

Important: maintenance operation on October 27

Read this message in another language • Hjælp venligst med at oversætte til dit sprog

The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic back to the primary data center on Tuesday, October 27 2020.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for up to an hour on Tuesday, October 27. The test will start at 14:00 UTC (14:00 WET, 15:00 CET, 10:00 EDT, 19:30 IST, 07:00 PDT, 23:00 JST, and in New Zealand at 03:00 NZDT on Wednesday October 28).
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• There will be code freezes for the week of October 26, 2020. Non-essential code deployments will not happen.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. A banner will be displayed on all wikis 30 minutes before this operation happens. Please share this information with your community.

-- Trizek (WMF) (talk) 21. okt 2020, 17:12 (UTC)

Wiki of functions naming contest - Round 2

Hello. Reminder: Please help to choose the name for the new Wikimedia wiki project - the library of functions. The finalist vote starts today. The finalists for the name are: Wikicode, Wikicodex, Wikifunctions, Wikifusion, Wikilambda, Wikimedia Functions. If you would like to participate, then please learn more and vote now at Meta-wiki. Tak! --Quiddity (WMF)

5. nov 2020, 22:11 (UTC)

Community Wishlist Survey 2021

The 2021 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 november, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 december and 21 december.

The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!

SGrabarczuk (WMF)

20. nov 2020, 18:09 (UTC)

Global bot policy proposal: invitation to a Meta discussion

Hello!

I apologize for sending a message in English. Hjælp venligst med at oversætte til dit sprog. According to the list, your wiki project currently is opted in to the global bot policy. Under this policy, bots that fix double redirects or maintain interwiki links are allowed to operate under a global bot flag that is assigned directly by the stewards.

As the Wikimedia projects developed, the need for the current global bot policy decreased, and in the past years, no bots were appointed via that policy. That is mainly given Wikidata were estabilished in 2013, and it is no longer necessary to have dozens of bots that maintain interwiki links.

A proposal was made at Meta-Wiki, which proposes that the stewards will be authorized to determine whether an uncontroversial task may be assigned a global bot flag. The stewards already assign permissions that are more impactful on many wikis, namely, global sysops and global renamers, and I do not think that trust should be an issue. The stewards will assign the permission only to time-proven bots that are already approved at a number of projects, like ListeriaBot.

By this message, I would like to invite you to comment in the global RFC, to voice your opinion about this matter.

Thank you for your time.

Best regards,
Martin Urbanec (diskussion) 24. nov 2020, 11:49 (UTC)

Wikidata descriptions changes to be included more often in Recent Changes and Watchlist

Sorry for sending this message in English. Translations are available on this page. Feel free to translate it in more languages!

As you may know, you can include changes coming from Wikidata in your Watchlist and Recent Changes (in your preferences). Until now, this feature didn’t always include changes made on Wikidata descriptions due to the way Wikidata tracks the data used in a given article.

Starting on December 3rd, the Watchlist and Recent Changes will include changes on the descriptions of Wikidata Items that are used in the pages that you watch. This will only include descriptions in the language of your wiki to make sure that you’re only seeing changes that are relevant to your wiki.

This improvement was requested by many users from different projects. We hope that it can help you monitor the changes on Wikidata descriptions that affect your wiki and participate in the effort of improving the data quality on Wikidata for all Wikimedia wikis and beyond.

Note: if you didn’t use the Wikidata watchlist integration feature for a long time, feel free to give it another chance! The feature has been improved since the beginning and the content it displays is more precise and useful than at the beginning of the feature in 2015.

If you encounter any issue or want to provide feedback, feel free to use this Phabricator ticket. Thanks!

Lea Lacroix (WMDE) 30. nov 2020, 14:39 (UTC)

2020 Coolest Tool Award Ceremony on December 11th

Hello all,

The ceremony of the 2020 Wikimedia Coolest Tool Award will take place virtually on Friday, December 11th, at 17:00 GMT. This award is highlighting tools that have been nominated by contributors to the Wikimedia projects, and the ceremony will be a nice moment to show appreciation to the tools developers and maybe discover new tools!

You will find more information here about the livestream and the discussions channels. Thanks for your attention, Lea Lacroix (WMDE) 7. dec 2020, 10:55 (UTC)

Community Wishlist Survey 2021

We invite all registered users to vote on the 2021 Community Wishlist Survey. You can vote from now until 21 December for as many different wishes as you want.

In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones.

We, the Community Tech, are one of the Wikimedia Foundation teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams.

You can view and vote all proposals here.

We are waiting for your votes. Thank you!

SGrabarczuk (WMF)

15. dec 2020, 00:52 (UTC)

Moving Wikimania 2021 to a Virtual Event

Hello. Apologies if you are not reading this message in your native language. Hjælp venligst med at oversætte til dit sprog. Tak!

Wikimania will be a virtual event this year, and hosted by a wide group of community members. Whenever the next in-person large gathering is possible again, the ESEAP Core Organizing Team will be in charge of it. Stay tuned for more information about how you can get involved in the planning process and other aspects of the event. Please read the longer version of this announcement on wikimedia-l.

ESEAP Core Organizing Team, Wikimania Steering Committee, Wikimedia Foundation Events Team, 27. jan 2021, 15:16 (UTC)

Project Grant Open Call

This is the announcement for the Project Grants program open call that started on January 11, with the submission deadline of February 10, 2021.
This first open call will be focussed on Community Organizing proposals. A second open call focused on research and software proposals is scheduled from February 15 with a submission deadline of March 16, 2021.

For the Round 1 open call, we invite you to propose grant applications that fall under community development and organizing (offline and online) categories. Project Grant funds are available to support individuals, groups, and organizations to implement new experiments and proven ideas, from organizing a better process on your wiki, coordinating a campaign or editathon series to providing other support for community building. We offer the following resources to help you plan your project and complete a grant proposal:

• Weekly proposals clinics via Zoom during the Open Call. Join us for #Upcoming_Proposal_Clinics|real-time discussions with Program Officers and select thematic experts and get live feedback about your Project Grants proposal. We’ll answer questions and help you make your proposal better. We also offer these support pages to help you build your proposal:
• Video tutorials for writing a strong application
  
• General planning page for Project Grants
  
• Program guidelines and criteria
  

Program officers are also available to offer individualized proposal support upon request. Contact us if you would like feedback or more information.

We are excited to see your grant ideas that will support our community and make an impact on the future of Wikimedia projects. Put your idea into motion, and submit your proposal by February 10, 2021!

Please feel free to get in touch with questions about getting started with your grant application, or about serving on the Project Grants Committee. Contact us at projectgrantsSkabelon:atwikimedia.org. Please help us translate this message to your local language. MediaWiki message delivery (diskussion) 28. jan 2021, 08:01 (UTC)

Wiki Loves Folklore 2021 is back!

Hjælp venligst med at oversætte til dit sprog

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 (diskussion) 6. feb 2021, 13:25 (UTC)

Proposal: Set two-letter project shortcuts as alias to project namespace globally

Hjælp venligst med at oversætte til dit sprog

Hello everyone,

I apologize for posting in English. I would like to inform everyone that I created a new global request for comment (GRFC) at Meta Wiki, which may affect your project: m:Requests for comment/Set short project namespace aliases by default globally.

In this GRFC, I propose that two-project shortcuts for project names will become a default alias for the project namespace. For instance, on all Wikipedias, WP will be an alias to the Wikipedia: namespace (and similar for other projects). Full list is available in the GRFC.

This is already the case for Wikivoyages, and many individual projects asked for this alias to be implemented. I believe this makes it easier to access the materials in the project namespace, as well as creating shortcuts like WP:NPOV, as well as helps new projects to use this feature, without having to figure out how to request site configuration changes first.

As far as I can see, Wiktionary currently does not have such an alias set. This means that such an alias will be set for you, if the GRFC is accepted by the global community.

I would like to ask all community members to participate in the request for comment at Meta-Wiki, see m:Requests for comment/Set short project namespace aliases by default globally.

Please feel free to ask me if you have any questions about this proposal.

Best regards,
--Martin Urbanec (talk) 18. feb 2021, 14:12 (UTC)

Wikifunctions logo contest

Hello. Hjælp med at vælge et designkoncept til logoet på den nye Wikifunctions wiki. Afstemningen starter i dag og vil være åben i 2 uger. Hvis du gerne vil deltage, så læs mere og stem nu på Meta-Wiki. Tak! --Quiddity (WMF)

2. mar 2021, 01:51 (UTC)

Universal Code of Conduct – 2021 consultations

Universal Code of Conduct Phase 2

Hjælp venligst med at oversætte til dit sprog

The Universal Code of Conduct (UCoC) provides a universal baseline of acceptable behavior for the entire Wikimedia movement and all its projects. The project is currently in Phase 2, outlining clear enforcement pathways. You can read more about the whole project on its project page.

Drafting Committee: Call for applications

The Wikimedia Foundation is recruiting volunteers to join a committee to draft how to make the code enforceable. Volunteers on the committee will commit between 2 and 6 hours per week from late April through July and again in October and November. It is important that the committee be diverse and inclusive, and have a range of experiences, including both experienced users and newcomers, and those who have received or responded to, as well as those who have been falsely accused of harassment.

To apply and learn more about the process, see Universal Code of Conduct/Drafting committee.

2021 community consultations: Notice and call for volunteers / translators

From 5 April – 5 May 2021 there will be conversations on many Wikimedia projects about how to enforce the UCoC. We are looking for volunteers to translate key material, as well as to help host consultations on their own languages or projects using suggested key questions. If you are interested in volunteering for either of these roles, please contact us in whatever language you are most comfortable.

To learn more about this work and other conversations taking place, see Universal Code of Conduct/2021 consultations.

-- Xeno (WMF) (talk) 5. apr 2021, 22:20 (UTC)

Global bot policy changes

Hello!

I apologize for sending a message in English. Hjælp venligst med at oversætte til dit sprog. According to the list, your wiki project is currently opted in to the global bot policy. As such, I want to let you know about some changes that were made after the global RfC was closed.

• Global bots are now subject to a 2 week discussion, and it'll be publicized via a MassMessage list, available at Bot policy/New global bot discussion on Meta. Please subscribe yourself or your wiki if you are interested in new global bots proposals.
• For a bot to be considered for approval, it must demonstrate it is welcomed in multiple projects, and a good way to do that is to have the bot flag on at least 5 wikis for a single task.
• The bot operator should make sure to adhere to the wiki's preference as related to the use of the bot flag (i.e., if a wiki doesn't want a bot to use the flag as it edits, that should be followed).

Thank you for your time.

Best regards,
—Thanks for the fish! ^{talk•contribs} 6. apr 2021, 18:48 (UTC)

Line numbering coming soon to all wikis

Example

From April 15, you can enable line numbering in some wikitext editors - for now in the template namespace, coming to more namespaces soon. This will make it easier to detect line breaks and to refer to a particular line in discussions. These numbers will be shown if you enable the syntax highlighting feature (CodeMirror extension), which is supported in the 2010 and 2017 wikitext editors.

More information can be found on this project page. Everyone is invited to test the feature, and to give feedback on this talk page.

-- Johanna Strodt (WMDE) 12. apr 2021, 15:07 (UTC)

Suggested Values

From April 29, it will be possible to suggest values for parameters in templates. Suggested values can be added to TemplateData and will then be shown as a drop-down list in VisualEditor. This allows template users to quickly select an appropriate value. This way, it prevents potential errors and reduces the effort needed to fill the template with values. It will still be possible to fill in values other than the suggested ones.

More information, including the supported parameter types and how to create suggested values: [1] [2]. Everyone is invited to test the feature, and to give feedback on this talk page.

Timur Vorkul (WMDE) 22. apr 2021, 14:08 (UTC)

Universal Code of Conduct News – Issue 1

Universal Code of Conduct News
Issue 1, June 2021Read the full newsletter

---

Welcome to the first issue of Universal Code of Conduct News! This newsletter will help Wikimedians stay involved with the development of the new code, and will distribute relevant news, research, and upcoming events related to the UCoC.

Please note, this is the first issue of UCoC Newsletter which is delivered to all subscribers and projects as an announcement of the initiative. If you want the future issues delivered to your talk page, village pumps, or any specific pages you find appropriate, you need to subscribe here.

You can help us by translating the newsletter issues in your languages to spread the news and create awareness of the new conduct to keep our beloved community safe for all of us. Please add your name here if you want to be informed of the draft issue to translate beforehand. Your participation is valued and appreciated.

• Affiliate consultations – Wikimedia affiliates of all sizes and types were invited to participate in the UCoC affiliate consultation throughout March and April 2021. (continue reading)
• 2021 key consultations – The Wikimedia Foundation held enforcement key questions consultations in April and May 2021 to request input about UCoC enforcement from the broader Wikimedia community. (continue reading)
• Roundtable discussions – The UCoC facilitation team hosted two 90-minute-long public roundtable discussions in May 2021 to discuss UCoC key enforcement questions. More conversations are scheduled. (continue reading)
• Phase 2 drafting committee – The drafting committee for the phase 2 of the UCoC started their work on 12 May 2021. Read more about their work. (continue reading)
• Diff blogs – The UCoC facilitators wrote several blog posts based on interesting findings and insights from each community during local project consultation that took place in the 1st quarter of 2021. (continue reading)

--MediaWiki message delivery (diskussion) 11. jun 2021, 23:06 (UTC)

Wikimania 2021: Individual Program Submissions

Dear all,

Wikimania 2021 will be hosted virtually for the first time in the event's 15-year history. Since there is no in-person host, the event is being organized by a diverse group of Wikimedia volunteers that form the Core Organizing Team (COT) for Wikimania 2021.

Event Program - Individuals or a group of individuals can submit their session proposals to be a part of the program. There will be translation support for sessions provided in a number of languages. See more information here.

Below are some links to guide you through;

• Program Submissions
• Session Submission Guidelines
• FAQ

Please note that the deadline for submission is 18th June 2021.

Announcements- To keep up to date with the developments around Wikimania, the COT sends out weekly updates. You can view them in the Announcement section here.

Office Hour - If you are left with questions, the COT will be hosting some office hours (in multiple languages), in multiple time-zones, to answer any programming questions that you might have. Details can be found here.

Best regards,

MediaWiki message delivery (diskussion) 16. jun 2021, 04:18 (UTC)

On behalf of Wikimania 2021 Core Organizing Team

Editing news 2021 #2

Read this in another language • Subscription list for this multilingual newsletter

When newcomers had the Reply tool and tried to post on a talk page, they were more successful at posting a comment. (Source)

Earlier this year, the Editing team ran a large study of the Reply Tool. The main goal was to find out whether the Reply Tool helped newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.

The key results were:

• Newer editors who had automatic ("default on") access to the Reply tool were more likely to post a comment on a talk page.
• The comments that newer editors made with the Reply Tool were also less likely to be reverted than the comments that newer editors made with page editing.

These results give the Editing team confidence that the tool is helpful.

Looking ahead

The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.

The next step is to resolve a technical challenge. Then, they will deploy the Reply tool first to the Wikipedias that participated in the study. After that, they will deploy it, in stages, to the other Wikipedias and all WMF-hosted wikis.

You can turn on "Discussion tools" in Beta Features now. After you get the Reply tool, you can change your preferences at any time in Special:Preferences#mw-prefsection-editing-discussion.

–Whatamidoing (WMF) (talk)

24. jun 2021, 14:15 (UTC)

Server switch

Read this message in another language • Hjælp venligst med at oversætte til dit sprog

The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for up to an hour on Tuesday, 29 June 2021. The test will start at 14:00 UTC (07:00 PDT, 10:00 EDT, 15:00 WEST/BST, 16:00 CEST, 19:30 IST, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday 30 June).
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• There will be code freezes for the week of June 28. Non-essential code deployments will not happen.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. A banner will be displayed on all wikis 30 minutes before this operation happens. Please share this information with your community.

SGrabarczuk (WMF) 27. jun 2021, 01:19 (UTC)

Universal Code of Conduct - Enforcement draft guidelines review

The Universal Code of Conduct Phase 2 drafting committee would like comments about the enforcement draft guidelines for the Universal Code of Conduct (UCoC). This review period is planned for 17 August 2021 through 17 October 2021.

These guidelines are not final but you can help move the progress forward. The committee will revise the guidelines based upon community input.

Comments can be shared in any language on the draft review talk page and multiple other venues. Community members are encouraged to organize conversations in their communities.

There are planned live discussions about the UCoC enforcement draft guidelines:

Wikimania 2021 session (recorded 16 August)

Conversation hours - 24 August, 31 August, 7 September @ 03:00 UTC & 14:00 UTC

Roundtable calls - 18 September @ 03:00 UTC & 15:00 UTC

Summaries of discussions will be posted every two weeks here.

Please let me know if you have any questions.

Xeno (WMF) 17. aug 2021, 22:59 (UTC)

Wikimedia Foundation Board of Trustees election has come to an end

Thank you for participating in the 2021 Wikimedia Foundation Board of Trustees election! Voting closed August 31 at 23:59. The official data, including the four most voted candidates, will be announced as soon as the Elections Committee completes their review of the ballots. The official announcement of the new trustees appointed will happen later, once the selected candidates have been confirmed by the Board.

6,946 community members from 216 wiki projects have voted. This makes 10.2% global participation, 1.1% higher than in the last Board elections. In 2017, 5167 people from 202 wiki projects cast their vote. A full analysis is planned to be published in a few days when the confirmed results are announced. In the meantime, you can check the data produced during the election.

Diversity was an important goal with these elections. Messages about the Board election were translated into 61 languages. This outreach worked well. There were 70 communities with eligible voters voting in this election for the first time. With your help, next year’s Board of Trustees election will be even better.

1. sep 2021, 20:58 (UTC)

The 2022 Community Wishlist Survey will happen in January

Hello everyone,

We hope all of you are as well and safe as possible during these trying times! We wanted to share some news about a change to the Community Wishlist Survey 2022. We would like to hear your opinions as well.

Summary:

We will be running the Community Wishlist Survey 2022 in January 2022. We need more time to work on the 2021 wishes. We also need time to prepare some changes to the Wishlist 2022. In the meantime, you can use a dedicated sandbox to leave early ideas for the 2022 wishes.

Proposing and wish-fulfillment will happen during the same year

In the past, the Community Tech team has run the Community Wishlist Survey for the following year in November of the prior year. For example, we ran the Wishlist for 2021 in November 2020. That worked well a few years ago. At that time, we used to start working on the Wishlist soon after the results of the voting were published.

However, in 2021, there was a delay between the voting and the time when we could start working on the new wishes. Until July 2021, we were working on wishes from the Wishlist for 2020.

We hope having the Wishlist 2022 in January 2022 will be more intuitive. This will also give us time to fulfill more wishes from the 2021 Wishlist.

Encouraging wider participation from historically excluded communities

We are thinking how to make the Wishlist easier to participate in. We want to support more translations, and encourage under-resourced communities to be more active. We would like to have some time to make these changes.

A new space to talk to us about priorities and wishes not granted yet

We will have gone 365 days without a Wishlist. We encourage you to approach us. We hope to hear from you in the talk page, but we also hope to see you at our bi-monthly Talk to Us meetings! These will be hosted at two different times friendly to time zones around the globe.

We will begin our first meeting September 15th at 23:00 UTC. More details about the agenda and format coming soon!

Brainstorm and draft proposals before the proposal phase

If you have early ideas for wishes, you can use the new Community Wishlist Survey sandbox. This way, you will not forget about these before January 2022. You will be able to come back and refine your ideas. Remember, edits in the sandbox don't count as wishes!

Feedback

• What should we do to improve the Wishlist pages?
• How would you like to use our new sandbox?
• What, if any, risks do you foresee in our decision to change the date of the Wishlist 2022?
• What will help more people participate in the Wishlist 2022?

Answer on the talk page (in any language you prefer) or at our Talk to Us meetings.

SGrabarczuk (WMF) (talk) 7. sep 2021, 00:24 (UTC)

Call for Candidates for the Movement Charter Drafting Committee ending 14 September 2021

Movement Strategy announces the Call for Candidates for the Movement Charter Drafting Committee. The Call opens August 2, 2021 and closes September 14, 2021.

The Committee is expected to represent diversity in the Movement. Diversity includes gender, language, geography, and experience. This comprises participation in projects, affiliates, and the Wikimedia Foundation.

English fluency is not required to become a member. If needed, translation and interpretation support is provided. Members will receive an allowance to offset participation costs. It is US$100 every two months.

We are looking for people who have some of the following skills:

• Know how to write collaboratively. (demonstrated experience is a plus)
• Are ready to find compromises.
• Focus on inclusion and diversity.
• Have knowledge of community consultations.
• Have intercultural communication experience.
• Have governance or organization experience in non-profits or communities.
• Have experience negotiating with different parties.

The Committee is expected to start with 15 people. If there are 20 or more candidates, a mixed election and selection process will happen. If there are 19 or fewer candidates, then the process of selection without election takes place.

Will you help move Wikimedia forward in this important role? Submit your candidacy here. Please contact strategy2030wikimedia.org with questions.

Xeno (WMF) 10. sep 2021, 17:10 (UTC)

Server switch

Read this message in another language • Hjælp venligst med at oversætte til dit sprog

The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic back to the primary data center on Tuesday, 14 September 2021.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for up to an hour on Tuesday, 14 September 2021. The test will start at 14:00 UTC (07:00 PDT, 10:00 EDT, 15:00 WEST/BST, 16:00 CEST, 19:30 IST, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday, 15 September).
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. A banner will be displayed on all wikis 30 minutes before this operation happens. Please share this information with your community.

SGrabarczuk (WMF) (diskussion) 11. sep 2021, 00:46 (UTC)

Talk to the Community Tech

Read this message in another language • Hjælp venligst med at oversætte til dit sprog

Hello!

As we have recently announced, we, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on September 15th, 23:00 UTC on Zoom, and will last an hour. Click here to join.

Agenda

• How we prioritize the wishes to be granted
• Why we decided to change the date from November 2021 to January 2022
• Update on the disambiguation and the real-time preview wishes
• Questions and answers

Format

The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (first three points in the agenda) will be given in English.

We can answer questions asked in English, French, Polish, and Spanish. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.

Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.

Invitation link

• Join online
• Meeting ID: 898 2861 5390
• One tap mobile
  • +16465588656,,89828615390# US (New York)
  • +16699006833,,89828615390# US (San Jose)
• Dial by your location

See you! SGrabarczuk (WMF) (diskussion) 11. sep 2021, 03:04 (UTC)

Voting for the election for the members for the Movement Charter drafting committee is now open

På andre sprog • Hjælp venligst med at oversætte til dit sprog

Voting for the election for the members for the Movement Charter drafting committee is now open. In total, 70 Wikimedians from around the world are running for 7 seats in these elections.

Voting is open from October 12 to October 24, 2021.

The committee will consist of 15 members in total: The online communities vote for 7 members, 6 members will be selected by the Wikimedia affiliates through a parallel process, and 2 members will be appointed by the Wikimedia Foundation. The plan is to assemble the committee by November 1, 2021.

Learn about each candidate to inform your vote in the language that you prefer: <https://meta.wikimedia.org/wiki/Special:MyLanguage/Movement_Charter/Drafting_Committee/Candidates>

Learn about the Drafting Committee: <https://meta.wikimedia.org/wiki/Special:MyLanguage/Movement_Charter/Drafting_Committee>

We are piloting a voting advice application for this election. Click yourself through the tool and you will see which candidate is closest to you! Check at <https://mcdc-election-compass.toolforge.org/>

Read the full announcement: <https://meta.wikimedia.org/wiki/Special:MyLanguage/Movement_Charter/Drafting_Committee/Elections>

Go vote at SecurePoll on: <https://meta.wikimedia.org/wiki/Special:MyLanguage/Movement_Charter/Drafting_Committee/Elections>

Best,

Movement Strategy & Governance Team, Wikimedia Foundation

Xeno (WMF) 15. okt 2021, 01:53 (UTC)

Learn how Movement Strategy Implementation Grants can support your Movement Strategy plans

Movement Strategy Implementation grants now provide more than $2,000 USD to put Movement Strategy plans into action. Find out more about Movement Strategy Implementation grants, the criteria, and how to apply.

MNadzikiewicz (WMF) (talk) 13:30, 29 October 2021 (UTC)

Meet the new Movement Charter Drafting Committee members

Flere sprog • Hjælp venligst med at oversætte til dit sprog

The Movement Charter Drafting Committee election and selection processes are complete.

• The election results have been published. 1018 participants voted to elect seven members to the committee: Richard Knipel (Pharos), Anne Clin (Risker), Alice Wiegand (Lyzzy), Michał Buczyński (Aegis Maelstrom), Richard (Nosebagbear), Ravan J Al-Taie (Ravan), Ciell (Ciell).
• The affiliate process has selected six members: Anass Sedrati (Anass Sedrati), Érica Azzellini (EricaAzzellini), Jamie Li-Yun Lin (Li-Yun Lin), Georges Fodouop (Geugeor), Manavpreet Kaur (Manavpreet Kaur), Pepe Flores (Padaguan).
• The Wikimedia Foundation has appointed two members: Runa Bhattacharjee (Runab WMF), Jorge Vargas (JVargas (WMF)).

The committee will convene soon to start its work. The committee can appoint up to three more members to bridge diversity and expertise gaps.

If you are interested in engaging with Movement Charter drafting process, follow the updates on Meta and join the Telegram group.

With thanks from the Movement Strategy and Governance team

5. nov. 2021, 15:53 (UTC)

Skabelon:Plattmakers-Wöörbook

Hej! I tried to edit Skabelon:Plattmakers-Wöörbook but my edit was rejected because of the abuse filter disallowing changing external links. Could someone please change the link to "https://plattmakers.de/en/find=" instead of "http://nds.plattmakers.de/index.php?q="? The old one doesn't work anymore. Thank you! --Slomox (diskussion) 16. dec. 2021, 08:18 (UTC)