Wikipedia:𐌱𐌰𐌿𐍂𐌲𐍃 𐌱𐍂𐌿𐌽𐌽𐌰

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

𐌷𐌰𐌹𐌻𐌰 𐌰𐌻𐌻𐌰 𐌰𐌽𐌰 𐌱𐌰𐌿𐍂𐌲𐍃 𐌱𐍂𐌿𐌽𐌽𐌹𐌽

𐌱𐌰𐌿𐍂𐌲𐍃𐌱𐍂𐌿𐌽𐌽𐌰 𐌹𐍃𐍄 𐍃𐍄𐌰𐌸𐍃 𐌹𐌽 𐌸𐌰𐌼𐌼𐌴𐌹 𐌱𐌹 𐌸𐍉 𐌲𐌿𐍄𐌹𐍃𐌺𐍉𐌽 𐍅𐌹𐌺𐌹𐍀𐌰𐌹𐌳𐌾𐌰 𐍂𐍉𐌳𐌾𐌰𐌹𐌼𐌰.

𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰

connectivity project

Hallo, my name is Anastasiya Lvova, I'm "duty" in Connectivity project. The essence of the "Connectivity" project is to study and enhance the coherence of Wikipedia, or, in other words, to improve hypertext navigation between articles. The project deals with deadends, isolated articles, non-categorized articles, transitivity of the category tree, etc.

We want to work with your language version, but we need configured MediaWiki:Disambiguationspage for it (with direct links to template namespace pages, for example, ru:MediaWiki:Disambiguationspage/de:MediaWiki:Disambiguationspage/fr:MediaWiki:Disambiguationspage). Is it possible to set it up for our usage?

thanks in advance, Lvova 18:52, 12 Warmmenoþs 2010 (UTC)

Betawiki: better support for your language in MediaWiki

Dear community. I am writing to you to promote a special wiki called Betawiki. This wiki facilitates the localisation (l10n) of the MediaWiki interface. You may have changed many messages here to use your language in the interface, but if you would log in to for example the English language Wiktionary, you would not be able to use the interface as well translated as here. Infact, of the 1798 messages in the core of MediaWiki, 0 messages have been translated. Betawiki also supports the translation of messages of about 80 extensions, with almost 1000 messages.

If you wish to contribute to better support of your language in MediaWiki, as well as for many MediaWiki extensions, please visit Betawiki, create an account and request translator priviledges. You can see the current status of localisation of your language on meta and do not forget to get in touch with others that may already be working on your language on Betawiki.

If you have any further questions, please let me know on my talk page on Betawiki. We will try and assist you as much as possible, for example by importing all messages from a local wiki for you to start with, if you so desire.

You can also find us on the Freenode IRC network in the channel #mediawiki-i18n where we would be happy to help you get started.

Thank you very much for your attention and I do hope to see some of you on Betawiki soon! Cheers! Siebrand@Betawiki 09:29, 28 September 2007 (UTC)

"𐌺𐌰𐌽𐌽 𐌸𐌿 𐌸𐌰𐍄𐌰" 𐌰𐌽𐌰 𐌷𐌰𐌿𐌱𐌹𐌳𐌰𐍃𐌴𐌹𐌳𐍉

• 𐌿𐍃𐌻𐌰𐌿𐌱𐌾𐌰𐌽 𐌹𐌺? --Jacques Pirat 05:37, 2 September 2007 (UTC)

𐍃𐌹𐌴𐌱𐍉𐍄 𐌱𐍉𐍄-𐌼𐌴𐌻𐌾𐌰𐌽

Hey guys, we need more votes to have this bot approved... Thanks in advance. nl:User:Siebrand 09:23, 29 August 2007 (UTC)

• 𐌱𐌹𐌽𐌰𐌷 --Jacques Pirat 20:01, 24 August 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 --Ooswesthoesbes 15:12, 2 September 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 --Alexander Gerashchenko 16:59, 5 September 2007 (UTC)

Done. —Pathoschild 19:45, 7 September 2007 (UTC)

𐌾𐌰𐌳𐌰𐌽𐌰𐍀𐌾𐌰 𐌲𐌰𐌹𐍂𐌽𐌴𐌹𐌸 𐍅𐌰𐌻𐌳𐌿𐍆𐌽𐌾𐌹𐍃𐌼𐌰𐌽𐌽𐌰 𐍅𐌰𐌹𐍂𐌸𐌰𐌽

+6

• 𐌱𐌹𐌽𐌰𐌷 --Jacques Pirat 17:28, 13 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 -- Yadönapya 09:14, 14 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 --Manie 07:02, 17 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 𐌷𐍂𐍉𐌸𐌱𐌰𐌹𐍂𐌷𐍄 21:03, 20 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 -- Alexander Gerashchenko 03:45, 21 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 --𐍆𐌿𐌲𐌻𐍃 _(:> )=| 23:32, 23 July 2007 (UTC)

𐌾𐌰𐌺 𐍀𐌹𐍂𐌰𐍄 𐌲𐌰𐌹𐍂𐌽𐌴𐌹𐌸 𐍅𐌰𐌻𐌳𐌿𐍆𐌽𐌾𐌹𐍃𐌼𐌰𐌽𐌽𐌰 𐍅𐌰𐌹𐍂𐌸𐌰𐌽

+6

• 𐌱𐌹𐌽𐌰𐌷 --Jacques Pirat 17:28, 13 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 -- Yadönapya 09:14, 14 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 --Manie 07:02, 17 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 𐌷𐍂𐍉𐌸𐌱𐌰𐌹𐍂𐌷𐍄 21:03, 20 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 -- Alexander Gerashchenko 03:45, 21 July 2007 (UTC)
• 𐌱𐌹𐌽𐌰𐌷 --𐍆𐌿𐌲𐌻𐍃 _(:> )=| 23:32, 23 July 2007 (UTC)

34y

Please delete it. --Flrn 17:41, 24 March 2008 (UTC)

Done ! -- Yadönapya 10:07, 26 March 2008 (UTC)

SpBot

Hello. I would like to get a bot-flag on this wiki.

• Operator: de:User:Euku
• Purpose: Interwiki links: It adds/modifies/deletes interwiki links.
• Software: pywikipediabot framework via SVN
• Already has bot flag on: >74 Wikipedias, for example: ar, bn, ca, cs, de, en, es, eu, da, fr, he, hu, it, pl, ro, ru, sq, tr. (Since 2006 on German Wikipedia, with >69.000 edits), look at details

Thank you! --Euku 08:23, 14 June 2008 (UTC)

SpaceBirdyBot

Hello, I would like to replace the wrong i here with the correct version ‎  to 𐌹̈
I did that already in the Afrikaan Wiktionary (there was not as much to replace as here, but searching for the wrong character in all entries by hand would have been insane).

• operator:: m:User:Spacebirdy
• purpose:: correct  to 𐌹̈ in all entries
• software:: pywikipediabot (modified replace.py, working expamples: [1], [2], [3]...)
• already botflag on: 115 Wiktionaries, mostly working as replacebot(correcting errors/templates/etc.)/interwikibot there; see also vvv's sul-tool

Best regards, --𐍆𐌿𐌲𐌻𐍃 _(:> )=| 18:24, 18 Asanmenoþs 2008 (UTC)

This bot is fine to run on this wiki. Jacques Pirat 20:20, 18 Asanmenoþs 2008 (UTC)

pro

1. --Manie 22:35, 18 Asanmenoþs 2008 (UTC)

comments

Ok, I have set it to run already, I throttled it to 60seconds between page savings, if You think it spams the recentchanges too much please let me know, I will turn it off then again, best regards, --𐍆𐌿𐌲𐌻𐍃 _(:> )=| 23:57, 18 Asanmenoþs 2008 (UTC)

Ok, I think I am through.

Please delete [4], [5], [6], and [7], nothing links to them anymore. Best regards, --𐍆𐌿𐌲𐌻𐍃 _(:> )=| 00:31, 19 Asanmenoþs 2008 (UTC)

Accents

Do we use accents in the Latin alphabet pages or not? I see inconsistency here; the title of the editing page is "Máidjan af...", but on 𐌲𐌿𐍄𐌰𐍂𐌰𐌶𐌳𐌰/Gutarazda there are no accents. Which do we go with? I personally think the accents make it easier to read, but it's not impossible without them.

Also, hyphenation: I prefer not to hyphenate, for example, "gameljan" ("ga-meljan"), but I wasn't sure if there was a definite policy on this; it can lead to some slightly ugly words sometimes (my latest update of Gutarazda includes the word "gaainaida" ("isolated"), which is pretty hideous, especially without accents..."gaáináida" is an improvement).

Just some thoughts. I know the English version has some standards of usage; it would probably be a good idea to have some here. Sectori 23:22, 21 Akranmenoþs 2008 (UTC)

Also, 𐍈 or 𐌸? The front page uses both: it might be more sensible to just choose one. Sectori 13:18, 25 Akranmenoþs 2008 (UTC)

𐌸 of course; 𐍈 is wrong. 𐌷𐍂𐍉𐌸𐌱𐌰𐌹𐍂𐌷𐍄 10:14, 2 Blomamenoþs 2009 (UTC)

Bot policy

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

This policy makes bot access requesting much easier for local users, operators, and stewards. To implement it we only need to create a redirect to this page from Project:Bot policy, and add a line at the top noting that it is used here. Please read the text at m:Bot policy before commenting. If you object, please say so; I hope to implement in one week if there is no objection, since it is particularly written to streamline bot requests on wikis with little or no community interested in bot access requests. Malafaya 09:50, 9 Weinmenoþs 2008 (UTC)

Implemented. Malafaya 14:57, 22 Weinmenoþs 2008 (UTC)

I'd like to learn Gothic

Hallo there, gothicspeakers. I bought a Gothic bible in summer and I understand quite a bit of it. I spend most of my free time learning latin. If I had someone who learns gothic too, that would motivate me. Do you know any beginners who would join me? Thanks a load. - Capsicaciolum, friday, jannuary 16, 2009, 21:22 (CET)

- Sean (sjheiss@comcast.net) I'm learning Gothic, but I think it's too late, seeing as this was posted almost 5 months ago, but if you or anyone else learning Gothic happen to see this, and would like someone to practice with, contact me through my e-mail, and put Gothic somewhere in the subject so I know what it's for. ;)

-No, it is deffinitely not to late. I am glad finally someone answered. I just starded to learn more Gothic again some days ago and I am sending you an e-mail before you read this post. - Capsicaciolum 17:36, 20 Hawimenoþs 2009 (UTC)

Fonts and Logo

𐍆𐌰𐌲𐌹𐌽𐍉𐌸!

I have now finished the "flagship" of my fonts, the new version of Ulfilas. It is available for download at my site.

Further, I have created a new version of the Wikipedia logo using Ulfilas. I have made the suggestion to use it towards Jaques Pirat, but as he seems to be away for a while, I'd like to advise the rest of the community of this suggestion.

Best regards, 𐌷𐍂𐍉𐌸𐌱𐌰𐌹𐍂𐌷𐍄 19:54, 13 Blomamenoþs 2009 (UTC)

2010 Fundraising Is Almost Here

Hello Wikipedians, I am Theo and I am working for the Wikimedia Foundation during the 2010 Fundraiser. My job is to be the liaison between your community and the Foundation. This year's fundraiser is intended to be a collaborative and global effort; we recognize that banner messages which may perform well in the United States don't necessarily translate well, or appeal to international audiences.

I'm contacting you as I am currently looking for translators who are willing to contribute to this project by helping translate and localize messages into different languages and suggesting messages that would appeal to your readers on the Fundraising Meta Page. We've started the setup on meta for both banner submission, statistical analysis, and grouping volunteers together.
Use the talk pages on meta, talk to your local communities, talk to others, talk to us, and add your feedback to the proposed messages as well! I look forward to working with you during this year's fundraiser. If someone could translate this message I would really appreciate it so that everyone is able to understand our goals and contribute to this year's campaign.
Theo (WMF) 20:12, 20 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2010 (UTC)

Survey on this wikipedia

Hails, I am from Germany, Bremen, and I am studying linguistics and I have a seminar on language ausbau. This is, when a language doesn't have enough words to express all the modern things and it gets then upgrated with new expressions to fulfill it. And I want to study how Wikipedia can help on that and this is why I am doing those surveys. I have two questions for you: 1. What do you think is the contribution of Wikipedia that your languages gets beter developped and gets new expressions for modern things, 2. How do you build new words, are there certain patterns or methods? I would be really thankful, if there came some meanings and answers together. Thank you very much, Sincerely Liufos goleineis, Zylbath 07:20, 14 𐌰𐌺𐍂𐌰𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2011 (UTC)

The prospects of a revival may be doubtful, since the Goths did not hold onto their ethnic self-consciousness and assimilated into the local populations (the last holdouts being in the Crimea). Perhaps one day modern admirers of Gothic fashion might become interested in the ancient language. Although the ancient Goths have nothing to do with the modern fashion-Goths except in name, there's no reason they couldn't adopt the old language. That may be unlikely, but no more unusual than people learning Klingon or Elvish. To answer your question, there probably aren't very many projects involved in creating new texts in Gothic, so this site may end up being influential if there ever is a revival. One thing in particular to look for here is that this site has standardized for its own uses the names of the days and months (see the entries for 𐌾𐌴𐍂 and 𐍅𐌹𐌺𐍉). We have only fragmentary original information of what these actually were. There are other interpretations (such as http://www.oe.eclipse.co.uk/nom/calendar.htm); so one sign would be to see if, after a revival takes place and usages become more or less standard, the month and day names given here prevail. In the unlikely event of a major resurgence, this will lead to a divergence into ancient Gothic and modern Gothic (perhaps the old could be called "gutisk" and the new "gutarazda"), and expect a lot of pedantic discussion about what is authentic versus made-up, and what new word is most faithful to the old language. I would imagine a similar process has happened for Modern Hebrew and Katharevouza.

As for how new words may be created, loan words are one possibility; the ancient Goths themselves did this sometimes, typically from Greek or Latin; a contemporary example you can see used here is "seido" for web page, after "site". Or new words can be built from cognates in other languages, such as "Banda-reikja" for United States, after the Icelandic "Bandaríkin". And I feel that any deduced word, such as "gutarazda", is fair game (though I wouldn't personally include the * in front of it as is done in academic usage). Or, one could break down the word into its roots and translate them directly, for instance, "in-de-pend-ence" means "not hang from condition" and in German becomes Un-ab-hängig-keit. A new Gothic example would be "káuli-blóma" for "cauliflower" (Blumenkohl). Or the meaning could be translated into a new compound, such as "witirahnjands" for computer (I believe this would be something like "knowledge reckoner") or -- as I have done -- "fair-weitl-waurstwa" for "actor". Also, look for the entries on Wikipedia:Razdagaruni and Wikipedia:𐌽𐌹𐌿𐌾𐌰_𐍅𐌰𐌵𐍂𐌳𐌰 -- you may find these informative. Allsbairhts 10:32, 18 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2011 (UTC)

I really thank you for that interesting introduction. Unfortunately the paper I hold in this is already over, but still, this was very interesting. But for further things on Wikipedia's influence this could be very useful. It seems that you are quite often here in the last time, which is very good. And BTW, the pages in wikipedia you posted were created by me. ;) Liubos goleineis, Zylbath 10:52, 18 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2011 (UTC)

Well, silly me, I didn't see that. Anyway, that was some good work! Allsbairhts 10:20, 21 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2011 (UTC)

No need to excuse ;) I think that was overdue. Liubos goleineis, Zylbath 11:54, 21 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2011 (UTC)

HiW-Bot

• Operator  : Hedwig in Washington
• Automatic or Manually Assisted : automatic
• Programming Language(s)  : Python (pywikipedia), daily update
• Function Summary  : Interwiki, Internationalization by removing chaos in Babel-Category so it can be used properly and easy. Double redirects will be added shortly
• Already has a bot flag (Y/N)  : Yes: 31 Wikis so far, others pending. see here
• Function Details  : just using the standard interwiki.py; parameters: -auto -all - log -catr

I humbly request bot status on this wiki in order to update Interwiki, and improve Internationalization by removing chaos in Babel so it can be used properly and easy by everyone.

Thank you for consideration! --Hedwig in Washington 20:44, 15 𐌰𐌺𐍂𐌰𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2011 (UTC)

Admin candidature

Hello, please vote for me on this page: Admin candidatures so that this page gets an admin, that is really present. Thank you. Liubos goleineis, Zylbath 11:24, 18 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2011 (UTC)

𐌻𐌹𐍃𐍄𐌰 𐍃𐌴𐌹𐌳𐍉 𐌸𐍉𐌶𐌴𐌹 𐌰𐌻𐌻𐍉𐍃 𐍅𐌹𐌺𐌹𐍀𐌰𐌹𐌳𐌾𐍉𐍃 𐍃𐌺𐌿𐌻𐌿𐌽 𐌷𐌰𐌱𐌰𐌽

Please help to fulfill this list: 𐌻𐌹𐍃𐍄𐌰 𐍃𐌴𐌹𐌳𐍉 𐌸𐍉𐌶𐌴𐌹 𐌰𐌻𐌻𐍉𐍃 𐍅𐌹𐌺𐌹𐍀𐌰𐌹𐌳𐌾𐍉𐍃 𐍃𐌺𐌿𐌻𐌿𐌽 𐌷𐌰𐌱𐌰𐌽 Zylbath 15:02, 30 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2011 (UTC)

300

𐌾𐌹𐌷𐌰!!! 𐍅𐌴𐌹𐍃 𐌷𐌰𐌱𐌰𐌼 𐌽𐌿 𐌰𐌽𐌳𐌰𐌻𐌴𐌹𐌺𐍃 300 𐍃𐌴𐌹𐌳𐍉𐍃 𐌰𐌽𐌰 𐍅𐌹𐌺𐌹𐍀𐌰𐌹𐌳𐌾𐌰𐌹! =) 𐍃𐍉 𐌸𐍂𐌴𐌹𐍃 𐌷𐌿𐌽𐌳𐌰 𐍃𐌴𐌹𐌳𐍉 𐌹𐍃𐍄 𐍆𐌰𐌹𐌷𐌿𐌺𐌹𐌽𐌳𐍃. Zylbath 18:38, 3 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2012 (UTC)

The double art of script

Hello, I would like to here your opinions to whether the articles should be in both versions the latin and the gothic one or just in gothic. I personally prefer to keep it all in gothic or as a minority runic, since the original scripture is gothic (or runic) and not latin. Sure, it's easier to read espacially for those without the font. But even if they don't have it, on the main page there is a box in English which tells which font to install and where to find it. Furthermore the gothic alphabet isn't that hard to read and it is kind of a gothic culture. And I don't find it helpfully or beautiful when there are both versions at once. If both versions should be kept, I would be totally agreeing if we do it with those links at the bottom of an article which says to let the text appear in latin alphabet even if the version might be not up to date. What do you think of all this? Zylbath 00:49, 25 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2012 (UTC)

I'm in favor of having both versions in parallel, if possible. The Wulfilas script is pretty, and it's traditional, but there are some drawbacks. It's easier to learn than (for instance) Arabic, but even so, transliterated text will make it a lot easier for newcomers. Speaking for myself, I haven't been able to get it to display in MSIE. Firefox works, but the font I'm using (skeirs) is rather small, which makes it tougher to read. There are some other fonts I could try, but they're rather more ornate, so they probably won't be any more "skeirs" than that! Also, I don't have a way of typing in it, so I have to copy and paste the tiny letters. I'm sure there are some solutions out there, which I may research some time, but for now creating text is fairly painstaking as it is. Allsbairhts 11:14, 26 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2012 (UTC)

So, when thinking of having both the gothic and latin alphabet, what would you think of displaying the gothic alphabet as default and having a link under or above (which I'd prefer) the article where you can click on to have the latin text? That would destroy the asthetic of the article, because in my opinion the same version of an article with pictures, cards, tablets etc. twice isn't that asthetic.

I guess I should write a tutorial here to install the fonts that way, one can use them for writing. Actually, it isn't very difficult. =) Zylbath 23:18, 26 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2012 (UTC)

What I envision is that in each section, the Wulfilas script would be first, followed by the Latin version. There's no need for duplicate graphics; they would just appear once. How about that? Also, if both scripts are visible at once, then it would be helpful for learners. Allsbairhts 06:06, 28 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2012 (UTC)

But wikipedia shouldn't be a place where to learn an alphabet, at least not in the articles. In most wikipedias different dialects or scriptures are always seperated by own links or sections and not written under each other, that's the standard. I would actually like to follow that here, too. But for learning the language or even the alphabet we can create an own section, where a tutorial or guide explains how to read it etc. We can link that to the main page. I still would propose a link at the top of an article which is written in latin alphabet to get to the latin version. I'm going to make a first version for you to see. And for the main page I thought of something like that: Plattdüütsch Wiktionary. There the dialects are seperated in own pages, we can do that with our page aswell in gothic and latin alphabet. What do you think? Zylbath 11:06, 28 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2012 (UTC)

Regarding the first point, generally speaking, this is so. But, Gothic has a unique situation, and the fussy Wiki way isn't an ideal one-size-fits-all solution. If we wish to breathe a little life into a dead language, then it makes sense to help newcomers past hurdles in comprehension and technology. Given that the Wulfilas alphabet has less common use than Elvish and (until they invent time travel) no native speakers are going to be scratching their heads wondering why we wrote the encyclopedia this way, then parallel transliterated text as an aid to newcomers to Gothic (pretty much everybody besides a few professors and grad students) might not be such a bad thing. That being said, I would like to see an example of what you had in mind as a proof of concept. The "Namne tala" article is one of the few articles long enough to be unwieldy, and it would benefit from this approach. Allsbairhts 09:03, 3 𐍆𐌰𐌽𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

Well, the problem is, Gothic is closed for translations. I am trying since some days to talk to the responsables, because there is still so much english text on the side of wikipedia. The reason for the closing is, that the translators used the latin script, albeit they were supposed to use the gothic one, since that's the genuin one. Having the same text on the same page in both writings is really not like wikipedia and might help to close this whole gothic wikipedia. Either we really use only the Gothic alphabet or we try to find a way, to have Gothic as default but an extra box or so where the latin script is in. Do you know the english side of wiktionary? Do you know the translation boxes? I want these ones for the latin script, either at the top or at the bottom of a page. Then a user can click on it and the latin text appears. This is maybe the best solution we have for a double script, since it's really not recommended to have two own pages for the same article but in different scripts, which would be the only way when working with an link to click on to get to the latin scripted article.

I really hope, they are going to open the translation function. Otherwise I guess I am going to start a subscribing petition and alarming the gothic mailing list. ;) This side is more like a construction side, we need more articles, a better translated page and more users.

And by the way, the gothic alphabet is really not that hard to read, even the Ulfila font which might be harder to read then others, is fast to learn. For some learners (me included) the stranger script is another reason to learn the language. We should stick to that how gothic is traditionally, otherwise this wikipedia would not try its best to document the oldest germanic language, which we know of.

If I weren't be so dumb for computational things I would have already made that box I am talking of. But I really don't succeed, but I am already talking which some people from the english wiktionary about how that template is working. Some day I will bring it to start. ;) Zylbath 13:12, 5 𐍆𐌰𐌽𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

YEAH!! I got it, finally. With the big help of some people from the English wiktionary. 𐍆𐌹𐌻𐌿 𐌸𐌰𐌲𐌺𐍉𐍃!!! =) So, now I can show you, how I ment it with the dropdownmenubox. See the article 𐌲𐌿𐍄𐌰𐍂𐌰𐌶𐌳𐌰. There is a box at the top where you can click on and then the latin scripted text appears. I think it is kind of cool and way more asthetic then before. What do you think of it? The handling is quite easy:

{{𐌻𐌰𐍄𐌹𐌽𐍃𐌺𐌰 𐌼𐌴𐌻𐌴𐌹𐌽𐍃}}
BLABLABLABLATEXTBLABLABLA
{{𐌰𐌽𐌳𐌰}}

Or with latin skript:
{{latinska meleins}}
TEEEEEEEEXT
{{anda}}

This way it wouldn't take to much space of the gothic written text, the gothic text is still default and it is easy to get to the latin text without having an extra link and so double articles for each script, which would be totally not worth it.

𐌱𐍉𐌺𐍉𐍃 - Text fragment

Now, you have to say yes, because it took some time and it is cool. ;)

Zylbath 15:03, 6 𐍆𐌰𐌽𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

AWESOME, even templates, graphics and all other stuff work in that box. Zylbath 15:19, 6 𐍆𐌰𐌽𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

OK, looks good. I tried it out on the article for dearest Amy. One suggestion I have would be to make the instructions on the home page (Haubdiseido) of where to go to install the fonts more prominent. Any newcomer to the site is going to see a bunch of tiny squares at first, after all, and the instructions are in small text. Perhaps the "Gutans" box could stretch across the whole page horizontally, and the text be made larger and vertically centered on the right of Gizur's picture. It might also mention that some articles will have drop down boxes for convenience. Allsbairhts 12:20, 10 𐍆𐌰𐌽𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

Hello. Yes, I already thought of that. I guess I will make a little box at the very top of the page with an english text or so, where to install the fonts. And I wanted to make the main page also in a latin version. A link or so should be above then. But I would always recommend the Ulfila font. I know Robert Pfeffer made another font for the wikipedia (Skeirs) and for electronic things, but that font didn't really work here. The wikipedia logo is made with Ulfila and it is by far the most beautiful font in gothic. So, I would recommend that if we have the chance, we should tell the people to download that font. Which one are you using? BTW: Please step by to the discussion side of amy winehouse, if you have some time. ;) Thank you very much for you dedication here. Zylbath 13:54, 11 𐍆𐌰𐌽𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

Suggestions for improvement

Hello, do you have any suggestions for improvement on this wikipedia? I can change now many things here, and most of the things here are pretty antiqued. So if you have any ideas for a better wikipedia, anyhow, tell me! ;) Zylbath 02:40, 26 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2012 (UTC)

𐌷𐌰𐌿𐌱𐌹𐌳𐌰𐍃𐌴𐌹𐌳𐍉 𐌽𐌿 𐌰𐌿𐌺 𐌹𐍃𐍄 𐌹𐌽 𐌻𐌰𐍄𐌹𐌽𐍃𐌺𐌰 𐌼𐌴𐌻𐌴𐌹𐌽𐍃

𐌷𐌰𐌹𐌻𐍃, 𐌹𐌺 𐌲𐌰𐌼𐌰𐌹𐌳𐌹𐌳𐌰 𐌸𐍉 𐌷𐌰𐌿𐌱𐌹𐌳𐌰𐍃𐌴𐌹𐌳𐍉𐌽 𐌾𐌰𐌷 𐍃𐌹 𐌹𐍃𐍄 𐌽𐌿 𐌰𐌿𐌺 𐌹𐌽 𐌻𐌰𐍄𐌹𐌽𐍃𐌺𐌰 𐌼𐌴𐌻𐌴𐌹𐌽𐍃 𐌸𐌰𐌹𐍂𐌷 𐌸𐌰𐌼𐌼𐌰 𐌽𐌹𐌿𐌾𐌹𐌽 𐍆𐌰𐌿𐍂𐌰𐌼𐌴𐌻𐌴𐌹𐌽𐌰. Zylbath (talk) 11:58, 20 𐌺𐌰𐌻𐌳𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

Call for Papers - Gothic book project

Hello, I'm writing as the leader of the association of the gothic language (www.vereindergotischensprache.de) to inform you about our book project. We want to publish a scientific work on Neogothic, sprachausbau and revitalisation. Here you have the Call for Papers:

Call for Papers

As we discussed in our member meeting, it is our goal to establish a book project. We are searching for authors to write this book, as it will to become an anthology. There is already a potential publisher (Verlag Inspiration Un Limited) who is interested in publishing such.

About the project:

There are many previously-available works on historical Gothic. Therein the traditional text material and the grammar and lexicon that arise from it are dealt with. But there are topics similar to “Sprachausbau” and “Revitalisation” for which almost nothing has been published as of yet. This is where our work comes to fruition; these will be our main topics that will be put to the fore of our work. Besides contributions on newer developments in the research of Gothic, we would like to see topics that outrun the manner(s) with which Gothic has been treated so far. This means that all handlings on modern Gothic, often called Neogothic, are possible. We would like to see contributions that give an overview on the current efforts to the revitalisation of Gothic and inform about the methods, problems, motivation, status, network of these projects and/or about similarities or differences to other projects of the sprachausbau and revitalisation. A contribution could also be to inform about the Gothic Wikipedia. Especially desired are articles that make a contribution to the sprachausbau itself on their own. You can always deliberate with us about topic(s) that would be acceptable and possible.

Every author can submit several articles, in either German or English.

We have in principle a scientific demand for the contributions. It is not a prerequisite for authors to have a previous knowledge in the topic of linguistics; but have to be able to argue seriously, and to stick to the usual rules of scientific writing and citing. If there are problems or questions while writing, just contact us. We can certainly help you.

Dates: Individual topics must be submitted by no later than the 31th of August 2012.

(The term for the submission of your articles will be given later; it will be most likely at the end of this year.)

For questions, consultation and submissions; please use this e-mail address: kontakt@vereindergotischensprache.de

Take pleasure in finding a topic and writing: The team of the “association of the gothic language”. Zylbath (talk) 21:46, 4 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

Survey on "Language Skills of the Gothic Language

The association of the gothic language is asking people to fill out a survey they created. We want to find out how many people there are that have any noteworthy skills in Gothic. So, please follow the link, the survey won't take more than 1 minute, it's just four questions long. We thank you a lot!
Survey on "Language Skills of the Gothic Language"
Zylbath (talk) 13:43, 24 𐌰𐌺𐍂𐌰𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2012 (UTC)

How to deal with transcription of foreign names? A poll.

Hello. As Wikipedia let us know recently (espacially by closing the translation function for us because of using Latin script in articles in the past) we need to have every article in Gothic script, espacially the article's name. Well, but coming to foreign names this is quite a problem as we haven't agreed on a way to transcript them. There have been several attempts. One of them was to analyse the names morpho-semantically, like Allsbairhts tried to do; see discussion on 𐌰𐌼𐌹 𐍅𐌰𐌹𐌽𐌷𐌰𐌿𐍃. I must say I don't agree with that manner because transcripting every foreign name by its morpho-semantic and translating it to Gothic is really not an accurate way; actually no language with a different script is doing it at that extent. Two other possibilities I see and about which we should vote are either: Keeping the shape of foreign names as much as possible but using some special transcription patterns when a letter doesn't exist in Gothic or is pronounced in a total different way (i. e. "Dixie Carter" 𐌳𐌹𐌺𐍃𐌹𐌴 𐌺𐌰𐍂𐍄𐌴𐍂: "x" would be 𐍇 but has a different pronounciation, so 𐌺𐍃 seems to be more appropriate, and "c" doesn't exist in Gothic. So, for the pronounciation of [k] 𐌺 should be used); or: We don't try to keep the shape of foreign names but transcript them totally after a Gothic shape and pattern like "Jonathan Winters" or "Douglas Engelbart" -> 𐌳𐍃𐌾𐌰𐌿𐌽𐌰𐌸𐌰𐌽 𐍅𐌹𐌽𐍄𐌰𐌹𐍂𐍃 and 𐌳𐌰𐌲𐌻𐌴𐍃 𐌰𐌹𐌲𐌲𐌴𐌻𐌱𐌰𐍂𐍄. (But then it might get hard to get the equivalent of a name [but anyway having the English name in brackets after it and redirects might be a helpful way and should be advisable]) For so far I don't see other solution and of course we would have to discuss in detail the exact rules of both of these ways. I would therefore ask you to vote and/or add another serious alternative if you have one. Thanks a lot! Zylbath (talk) 20:33, 10 𐌺𐌰𐌻𐌳𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

Transcription way 1: keep the shape, only different letters if needed

In favour:

Comments:

Transcription way 2: always use Gothic patterns

In favour: Gadrauhts (talk) 17:49, 13 𐌺𐌰𐌻𐌳𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

Comments: Of the existing suggestions I vote for number 2. But I have a third suggestion. Gadrauhts (talk) 17:49, 13 𐌺𐌰𐌻𐌳𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

Transcription way 3: Use gothic versions of the names (both first and last name). Translate of necessary and decline all names

In favour:

Comments:

• Could you please define that more? So you mean that names should indeed rather transcripted and translated by their semantic-morphological structure like proposed as for Amy Winehouse -> Ami Wainahus? Zylbath (talk) 19:32, 14 𐌺𐌰𐌻𐌳𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

Bad articles

Hey. I created some new templates to put some order in this wikipedia which is quite a mess and construction site. I would ask you to pay attention to bad articles as well and put those templates in those pages. They get into special categories where I can handle them alltogether.
To do so please write {{𐍄𐌰𐌹𐍂𐌰𐌽}} at the beginning of an article that should be deleted. (When there are doublets, vandalism or those articles with / in its name.) But don't delete the content, only put the template code in the beginning. If there is a bad article that should be written over urgently please write {{𐌽𐌹𐌿𐌾𐌰𐌽}} at the beginning. That appeals to articles who are only written in Latin script, have a Latin script name or have hardly a layout that looks really bad. When there are articles that are very short but seem alright so far, please put the template {{𐍆𐍂𐌿𐌼}} at the end of the article. They are okay so far but should be get more content soon, but they won't be deleted in the future. And if an article contains unattested words that aren't in any dictionary, not even ours, than write {{𐌿𐌽𐍅𐌴𐌹𐍄𐍅𐍉𐌳𐌹𐌸𐍃}} at the beginning and write the unattested words on the discussion page.
All those articles appear in the respective category where could be taken care of individually. Thank you. Kevin Behrens (talk) 20:57, 9 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

Latin script titles

As far as I can see now I have deleted or changed all the titles that were only written in Latin script. Some of them still exist but with the note for speedy deletion which will happen soon. The next will it be to change all the titles that contain both Gothic and Latin script divided by a / into Gothic only titles, as well as deleting all the catogories that contain any Latin script and expand the network of categories so that they relate to each other and are a helpful guide through this wikipedia. Feels like sysiphos work. ;) Kevin Behrens (talk) 13:50, 10 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

The transliterator should work everywhere, not just for displaying the article content, but also in the page title displayed (HTML1 h1 tag), the navigation bar, the search input bar, the wiki editor, the Visual Editor, and the code editor, as well as in the edit comment input box, possibly as well in the preferences page for its own input boxes. Unfortunately this is not the case.

Additionally the site still suggests using a font (in the preferences of Universal Language selector) that is actually NOT encoded with Unicode, but is a hack of the Latin script to show the Gothic script instead.

A better font is now available: "Noto" (unfortunately it has only one style "Noto Sans Regular"; the absence of a monospaced version is not really a problem, (for a serif version, you have "Roboto") but absence of bold and italic styles is a problem for the UI. Noto has the enormous advantage of playing in harmony with all other fonts in the Noto family for all scripts supported by Unicode; additionally it is freely available (offered by Google, developped for Android but in fact widely used elsewhere). Microsoft also released as "Segoe UI Gothic" font for Windows but also only in regular style (no bold and no italic).

There are other good quality fonts, well hinted, but unfortunately not encoded with Unicode in Plane 1 but still using the Latin-hack override.

Various articles on this wiki have been created with the Latin-hack, they are not compatible and will need to be converted (I suggest using the Latin-Gothic transliterator for that). Verdy p (talk) 05:43, 25 𐌼𐌰𐌾𐌿𐍃 2016 (UTC)

Co-Adminship

Hello there. I have asked at the Steward Requests if I could become a co-admin. According to one user who replied it might be possible, but the stewards first need to see that there is support.

I would like to ask here if it's ok if I become a co-admin together with Zylbath? I will mostly use my admin-function to correct mistakes in Gothic and before I change things like certain words I will first discuss it with Zylbath. I will also be able to look at some implementations to improve this Wikipedia.

An advantage is that if Zylbath is away I can deal with some of the things here. Bokareis (talk) 21:44, 21 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

I don't really see an implication for that since most of the pages are editable for everybody except for the dictionary, which will get only updated after discussions on the page. (And for I am online almost every day there won't be much delay in that.) And javascript could be always added after conferring with me. But if you think it's neccessary that you have admin rights, too, I am fine with it. But then you really have to pay more attention to your tone or change it towards others, learn more about the basics of creating new articles and learn more about the rules and policies made on this Wikipedia. Kevin Behrens (talk) 12:31, 22 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

I sometimes get annoyed of inconsistencies and some mistakes in articles, therefore my tone can be a bit hard sometimes because this is wikipedia. he problem is that since I joined this wikipedia it's completely unclear where to find the rules and policies, in hilpa you can find help with creating articles but it isn't clear to me where it is. One of the main reasons for the Admin application is this: Above here you see "utgaggan", while you keep your mouse over it it changes into "leithan", which is a much better alternative. The word next to it has "tala af thein", which should be "tala af theinamma" or the female form, as "af" gives a dative. Meina brukeins and meinos maidjabrukeineis, I 'm not sure if this can be correct, because that would mean that the singular is female and the plural changes to masculine. And I sometimes see "seida" and "seido" used both, while as far as I know "seido" is the correct one. Bokareis (talk) 22:18, 22 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

I am also speaking of your general defient tone when it comes to neologisms and discussions on them. It can be hard sometimes to keep being neutral. But don't get me wrong, I am really impressed of your motivation and I am happy that you write articles here.

To the translations: I know, there are a lot of things wrong on here. But the translation function for the Gothic wikipedia has been closed so we cannot really work on it. That's a shame and it's ridiculous. I argued so often about that on the translatewiki where the translation has to be done, but they always argued that there is no point in having a Wikipedia in a dead language. But someone is already notified who might help in that. So, maybe in the near future you can work on the translation on the translatewiki.

To the rules: The general rules of building articles etc. can be found on the English, Dutch or German Wikipedia. But the special rules on Gothic reconstruction here is something you'll get to know rather after dealing with it for a long time and reading through this Wikipedia. I am not following those instructions blindly, but I agree with them in most points. (Especially as most of the rules are also in use outside of this Wikipedia.) Kevin Behrens (talk) 08:51, 23 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

You have to understand that if you have translated 50% of a website, and you have used a wrong neologism everywhere, you indeed become "defiant" if the neologism suddenly changes and you need to change the word everywhere again, which wasn't needed in the first place. I wouldn't be "defiant" if I wouldn't do these translations, because in that case it wouldn't really matter for me, but if you have been using a word a lot it's not fun if someone comes and tell you that a word which is written down as a neologism is actually wrong afterwards. I hope the translation wiki get's open. I also started a wordpress blog to submit our neologisms, I gave you rights to it too. I hope that you will use it. I put all the neologisms there which we agreed upon. Bokareis (talk) 21:39, 23 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2014 (UTC)

IMPORTANT: Admin activity review

Hello. A new policy regarding the removal of "advanced rights" (administrator, bureaucrat, etc) was adopted by global community consensus in 2013. According to this policy, the stewards are reviewing administrators' activity on smaller wikis. To the best of our knowledge, your wiki does not have a formal process for removing "advanced rights" from inactive accounts. This means that the stewards will take care of this according to the admin activity review.

We have determined that the following users meet the inactivity criteria (no edits and no log actions for more than 2 years):

1. Node ue (administrator)

These users will receive a notification soon, asking them to start a community discussion if they want to retain some or all of their rights. If the users do not respond, then their advanced rights will be removed by the stewards.

However, if you as a community would like to create your own activity review process superseding the global one, want to make another decision about these inactive rights holders, or already have a policy that we missed, then please notify the stewards on Meta-Wiki so that we know not to proceed with the rights review on your wiki. Thanks, Rschen7754 04:12, 13 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2015 (UTC)

IMPORTANT: Admin activity review

Hello. A new policy regarding the removal of "advanced rights" (administrator, bureaucrat, etc) was adopted by global community consensus in 2013. According to this policy, the stewards are reviewing administrators' activity on smaller wikis. To the best of our knowledge, your wiki does not have a formal process for removing "advanced rights" from inactive accounts. This means that the stewards will take care of this according to the admin activity review.

We have determined that the following users meet the inactivity criteria (no edits and no log actions for more than 2 years):

1. Jacques Pirat (administrator)

These users will receive a notification soon, asking them to start a community discussion if they want to retain some or all of their rights. If the users do not respond, then their advanced rights will be removed by the stewards.

However, if you as a community would like to create your own activity review process superseding the global one, want to make another decision about these inactive rights holders, or already have a policy that we missed, then please notify the stewards on Meta-Wiki so that we know not to proceed with the rights review on your wiki. Thanks, Rschen7754 06:00, 9 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2016 (UTC)

The visual editor will be enabled on this wiki in some days

Hello again. Please excuse the English. Please help translate to your language. Thank you!

As per previous announcements earlier this year, the visual editor (VisualEditor) will be enabled at this Wikipedia in some days. It allows people to edit articles as if they were using a typical word processor. Here's a quick explanation of what is going to happen: you can find a more detailed one, with pictures, at mediawiki.org.

What's changing?

In the new system, you get a single edit tab which follows your preferences, and that therefore will launch the wikitext editor or the visual editor depending on which one you opened the last (Remember my last editor).
This applies to everyone who edited recently, including anonymous users.

How do I switch to the other editor then?

Buttons on the toolbars of both editors were added months ago so that you can switch from one to the other every time you want to, without losing your changes and without having to save first.
The button, located on the right side of the toolbar, looks like square brackets ([[ ]]) in the visual editor, and like a pencil () in the wikitext editor.

Are there other options available?

Yes. You can choose whether you want:

• Always give me the visual editor if possible (if you temporarily switch to the wikitext editor through the button on the toolbar, the system won't remember it; also, it only applies to namespaces where the visual editor is available).
• Always give me the source editor (if you temporarily switch to the visual editor through the button on the toolbar, the system won't remember it)
• Show me both editor tabs (a system in place at multiple wikis since 2013. You are familiar with this option if you have been using the visual editor here.)
  • Please note: all the users will always have the opportunity to switch to the other editor via buttons on the toolbars, for occasional edits.

How do I set my preference?

• If you want to try or to stay in the new system: you don't need to do anything.
• If you had explicitly disabled the visual editor in the past and want to keep it disabled: you don't need to do anything.
• All the registered users have a dropdown menu in the Editing tab of their Preferences (Editing --> Editing mode:), where they can choose from. This only needs to be done once. Don't forget to save ;)
  • Users with the visual editor disabled need to re-enable it if they're interested in accessing that menu!
• People who use the visual editor regularly will see a pop-up (only once after the single edit tab system is introduced), and they can choose their favorite setting there. Of course, they can change their mind at any time just like the others, and pick a different setting from their Preferences.
  • Anonymous users who have used the visual editor recently will also be able to choose which editor they want to edit with.
  • Reminder: all the users will always have the opportunity to switch to the other editor via buttons on the toolbars, for occasional edits.

Final remarks

• Please spread the word about this major change in any way that you deem appropriate for this community, by linking to this announcement elsewhere, putting up a site notice, etc. Please note it will affect all the registered users at first, and after some days it will reach logged-out contributors as well if no major technical issues have arisen. Don't hesitate to ask questions, I'll be around for a while to help!
• Please do let us know about any anomalies you think you're experiencing, and do post any other feedback below. I'd like to thank everyone who works to make the transition easier for this community, and whoever will help me processing feedback in your language.
• You can learn more about optimizing the visual editor experience here by reading a guide on mediawiki.org.

Thank you! --Elitre (WMF) (talk) 08:22, 4 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2016 (UTC)

The visual editor is now active here

Hello again. This message is only available in English at this time: Please help translate to your language. Thank you!

• 

  In the wikitext editor, the pencil icon allows you to switch to the visual editor.

• 

  In the visual editor, the [[ ]] (square brackets) icon allows you to switch to the wikitext editor. Please note that the button will soon say 𐌼𐌴𐍂𐌴𐌹 𐌻𐌰𐌿𐍆 or 𐌼𐌴𐍂𐌴𐌹 𐌹𐌽𐌼𐌰𐌹𐌳𐌹𐌽𐌹𐌽𐍃, due to an unrelated change.

As some of you have noticed, this Wikipedia now has the visual editor (VisualEditor) enabled for all registered users. The rollout to logged-out users will likely happen in a week or so.

For an explanation of how the editing system now works and how to choose/go back to your favorite setting, please see my previous announcement above. If you wish to change your editing system preferences now, this can be done from this link to your Preferences --> Editing --> Editing mode:.

All edits using the visual editor will be tagged with "Visual edit" in recent changes, watchlists, and page histories. To access the User Guide for the visual editor, click on the "(?)" icon in its toolbar.

Please let us know if you find any problems. You can report issues directly in Phabricator, the new bug tracking system or on at mw:VisualEditor/Feedback; by all means, feel free to also ping or contact me directly if you prefer. In case of emergency (like an unexpected bug causing widespread problems), please contact James Forrester, the product manager, at jforrester@wikimedia.org or on IRC in the #mediawiki-visualeditor channel.

Happy editing! Respectfully, Elitre (WMF) --18:55, 11 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2016 (UTC)

PS: Are you seeing interface messages that are not in this wiki's language? Please fix this by providing translations here. Translations may be also provided for the user guide. Please contact me if you want guidance in contributing translations!

Just a heads-up that rollout of the visual editor on this wiki is now complete. Please refer to my previous messages for details. You can read the "checklist" that was written to help communities like yours in their process of adapting the visual editor to their customs and needs. Best, Elitre (WMF) 18:22, 20 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2016 (UTC)

Editing News #3—2016

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

Did you know?

Did you know that you can easily re-arrange columns and rows in the visual editor?

Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.

Recent changes

• You can now set text as small or big.[8]
• Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[9] A similar feature will display the first part of hidden HTML comments.[10]
• Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[11]
• At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.[12]
• The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[13] In the future, the "𐌲𐌰𐍆𐌰𐍃𐍄𐌰𐌹 𐌻𐌰𐌿𐍆" button will say "𐌼𐌴𐍂𐌴𐌹 𐌻𐌰𐌿𐍆". This will affect both the visual and wikitext editing systems. More information is available on Meta.
• Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[14]

Future changes

The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.

The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.

• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

—Elitre (WMF)

17:49, 15 𐍅𐌴𐌹𐌽𐌼𐌴𐌽𐍉𐌸𐍃 2016 (UTC)

Editing News #1—2017

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

Did you know?

Did you know that you can review your changes visually?

When you are finished editing the page, type your edit summary and then choose "Review your changes".

In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.

Click the toggle button to switch between visual and wikitext diffs.

The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history. You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has spent most of their time supporting the 2017 wikitext editor mode which is available inside the visual editor as a Beta Feature, and adding the new visual diff tool. Their workboard is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor as a beta feature, and improving the visual diff tool.

Recent changes

• A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the New wikitext mode.
• A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [15]
• The team have added multi-column support for lists of footnotes. The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [16]
• You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [17]
• The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [18]
• The Categories item has been moved to the top of the Page options menu (from clicking on the "hamburger" icon) for quicker access. [19] There is also now a "Templates used on this page" feature there. [20]
• You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [21]
• Tables can be set as collapsed or un-collapsed. [22]
• The Special character menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [23]
• A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [24]
• There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K or Command+K respectively. [25]

Future changes

• The team is working on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [26]
• The kind of button used to 𐌱𐌰𐌽𐌳𐍅𐌴𐌹 𐍆𐌰𐌿𐍂𐌰𐍃𐌹𐌿𐌽, 𐌱𐌰𐌽𐌳𐍅𐌴𐌹 𐌹𐌽𐌼𐌰𐌹𐌳𐌹𐌽𐌹𐌽𐍃, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [27]
• The outdated 2006 wikitext editor will be removed later this year. It is used by approximately 0.03% of active editors. See a list of editing tools on mediawiki.org if you are uncertain which one you use. [28]
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

—Elitre (WMF)

18:05, 12 𐌼𐌰𐌾𐌿𐍃 2017 (UTC)

presenting the project Wikipedia Cultural Diversity Observatory and asking for a vounteer in Gothic Wikipedia

Hello everyone, My name is Marc Miquel and I am a researcher from Barcelona (Universitat Pompeu Fabra). While I was doing my PhD I studied whether an identity-based motivation could be important for editor participation and I analyzed content representing the editors' cultural context in 40 Wikipedia language editions. Few months later, I propose creating the Wikipedia Cultural Diversity Observatory in order to raise awareness on Wikipedia’s current state of cultural diversity, providing datasets, visualizations and statistics, and pointing out solutions to improve intercultural coverage.

I am presenting this project to a grant and I expect that the site becomes a useful tool to help communities create more multicultural encyclopaedias and bridge the content culture gap that exists across language editions (one particular type of systemic bias). For instance, this would help spreading cultural content local to Gothic Wikipedia into the rest of Wikipedia language editions, and viceversa, make Gothic Wikipedia much more multicultural. Here is the link of the project proposal: https://meta.wikimedia.org/wiki/Grants:Project/Wikipedia_Cultural_Diversity_Observatory_(WCDO)

I am searching for a volunteer in each language community: I still need one for the Gothic Wikipedia. If you feel like it, you can contact me at: marcmiquel *at* gmail.com I need a contact in your every community who can (1) check the quality of the cultural context article list I generate to be imported-exported to other language editions, (2) test the interface/data visualizations in their language, and (3) communicate the existance of the tool/site when ready to the language community and especially to those editors involved in projects which could use it or be aligned with it. Communicating it might not be a lot of work, but it will surely have a greater impact if done in native language! :). If you like the project, I'd ask you to endorse it in the page I provided. In any case, I will appreciate any feedback, comments,... Thanks in advance for your time! Best regards, --Marcmiquel (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 08:04, 11 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2017 (UTC) Universitat Pompeu Fabra, Barcelona

Editing News #1—2018

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

Did you know?

Did you know that you can now use the visual diff tool on any page?

Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.

If you enable the Beta Feature for "Visual differences", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

Click the toggle button to switch between visual and wikitext diffs.

In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.

This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.

Recent changes

• The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
• The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [29]
• Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [30]
• The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. It is very popular and useful to editors, although it can be a bit tricky to set up. Your wiki can have this service. Please read the instructions. You can ask the team to help you enable citoid at your wiki.

Let's work together

• The team will talk about editing tools at an upcoming Wikimedia Foundation metrics and activities meeting.
• Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
• The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [31]
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!

—Elitre (WMF)

20:56, 2 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2018 (UTC)

Editing of sitewide CSS/JS is only possible for interface administrators from now

(Please help translate to your language)

Hi all,

as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin (Interface administrators) group, and a few highly privileged global groups such as stewards, can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage). This is done to improve the security of readers and editors of Wikimedia projects. More information is available at Creation of separate user group for editing sitewide CSS/JS. If you encounter any unexpected problems, please contact me or file a bug.

Thanks!
Tgr (talk) 12:39, 27 𐌰𐌲𐌿𐍃𐍄𐌿𐍃 2018 (UTC) (via global message delivery)

Read-only mode for up to an hour on 12 September and 10 October

Read this message in another language • Please help translate to your language

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 center on Wednesday, 12 September 2018. On Wednesday, 10 October 2018, they will switch back to the primary data center.

Unfortunately, because of some limitations in MediaWiki, all editing must stop when we switch. 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 Wednesday, 12 September and Wednesday, 10 October. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 13 September and Thursday 11 October).
• 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 weeks of 10 September 2018 and 8 October 2018. 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. /User:Johan(WMF) (talk)

13:33, 6 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2018 (UTC)

The Community Wishlist Survey

The Community Wishlist Survey. Please help translate to your language.

Hey everyone,

The Community Wishlist Survey is the process when the Wikimedia communities decide what the Wikimedia Foundation Community Tech should work on over the next year.

The Community Tech team is focused on tools for experienced Wikimedia editors. You can post technical proposals from now until 11 November. The communities will vote on the proposals between 16 November and 30 November. You can read more on the wishlist survey page.

/User:Johan (WMF)

11:05, 30 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2018 (UTC)

Editing News #2—2018

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

Did you know?

Did you know that you can use the visual editor on a mobile device?

Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.

You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.

Remember to publish your changes when you're done.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.

Recent changes

• The Editing team has published an initial report about mobile editing.
• The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles. You can read the report.
• The Reading team is working on a separate mobile-based contributions project.
• The 2006 wikitext editor is no longer supported. If you used that toolbar, then you will no longer see any toolbar. You may choose another editing tool in your editing preferences, local gadgets, or beta features.
• The Editing team described the history and status of VisualEditor in this recorded public presentation (starting at 29 minutes, 30 seconds).
• The Language team released a new version of Content Translation (CX2) last month, on International Translation Day. It integrates the visual editor to support templates, tables, and images. It also produces better wikitext when the translated article is published. [32]

Let's work together

• The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
• The Community Wishlist Survey begins next week.
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!

—Whatamidoing (WMF) (talk)

14:17, 2 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2018 (UTC)

Change coming to how certain templates will appear on the mobile web

Change coming to how certain templates will appear on the mobile web

Please help translate to your language

Example of improvements

Hello,

In a few weeks the Readers web team will be changing how some templates look on the mobile web site. We will make these templates more noticeable when viewing the article. We ask for your help in updating any templates that don't look correct.

What kind of templates? Specifically templates that notify readers and contributors about issues with the content of an article – the text and information in the article. Examples like Template:Unreferenced or Template:More citations needed. Right now these notifications are hidden behind a link under the title of an article. We will format templates like these (mostly those that use Template:Ambox or message box templates in general) to show a short summary under the page title. You can tap on the "Learn more" link to get more information.

For template editors we have some recommendations on how to make templates that are mobile-friendly and also further documentation on our work so far.

If you have questions about formatting templates for mobile, please leave a note on the project talk page or file a task in Phabricator and we will help you.

Thank you!

CKoerner (WMF) (talk) 19:34, 13 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2018 (UTC)

Community Wishlist Survey vote

The Community Wishlist Survey. Please help translate to your language.

Hey everyone,

The Community Wishlist Survey is the process when the Wikimedia communities decide what the Wikimedia Foundation Community Tech should work on over the next year.

The Community Tech team is focused on tools for experienced Wikimedia editors. The communities have now posted a long list of technical proposals. You can vote on the proposals from now until 30 November. You can read more on the wishlist survey page.

/User:Johan (WMF)

18:13, 22 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2018 (UTC)

New Wikimedia password policy and requirements

Please help translate to your language

The Wikimedia Foundation security team is implementing a new password policy and requirements. You can learn more about the project on MediaWiki.org.

These new requirements will apply to new accounts and privileged accounts. New accounts will be required to create a password with a minimum length of 8 characters. Privileged accounts will be prompted to update their password to one that is at least 10 characters in length.

These changes are planned to be in effect on December 13th. If you think your work or tools will be affected by this change, please let us know on the talk page.

Thank you!

CKoerner (WMF) (talk) 20:03, 6 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2018 (UTC)

Invitation from Wiki Loves Love 2019

Please help translate to your language

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 (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 10:12, 27 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2018 (UTC)

No editing for 30 minutes on 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 not edit might be shorter than 30 minutes. /Johan (WMF)

18:40, 16 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2019 (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) 15:01, 21 𐍆𐌰𐌹𐌱𐍂𐌿𐌰𐍂𐌴𐌹𐍃 2019 (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)

10:56, 8 𐌰𐍀𐍂𐌴𐌹𐌻𐌹𐍃 2019 (UTC)

Wikimedia Foundation Medium-Term Plan feedback request

Please help translate to your language

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. Thank you! Quiddity (WMF) (talk) 17:35, 12 𐌰𐍀𐍂𐌴𐌹𐌻𐌹𐍃 2019 (UTC)

Editing News #1—July 2019

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

Did you know?

Did you know that you can use the visual editor on a mobile device?

Every article has a pencil icon at the top. Tap on the pencil icon to start editing.

Edit Cards

This is what the new Edit Cards for editing links in the mobile visual editor look like. You can try the prototype here: 📲 Try Edit Cards.

Welcome back to the Editing newsletter.

Since the last newsletter, the team has released two new features for the mobile visual editor and has started developing three more. All of this work is part of the team's goal to make editing on mobile web simpler.

Before talking about the team's recent releases, we have a question for you:

Are you willing to try a new way to add and change links?

If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.

Follow these instructions and share your experience:

📲 Try Edit Cards.

Recent releases

The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team recently launched two new features to improve the mobile visual editor:

1. Section editing
   • The purpose is to help contributors focus on their edits.
   • The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
2. Loading overlay
   • The purpose is to smooth the transition between reading and editing.

Section editing and the new loading overlay are now available to everyone using the mobile visual editor.

New and active projects

This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.

• Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how: 📲 Try Edit Cards.
• Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
• Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
• Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.

Looking ahead

• Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to the team about how editing can be improved.
• Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.

Learning more

The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.

PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

18:32, 23 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2019 (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)

14:18, 21 𐌰𐌲𐌿𐍃𐍄𐌿𐍃 2019 (UTC)

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) 17:14, 30 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2019 (UTC)

Feedback wanted on Desktop Improvements project

Please help translate to your language

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.

Thank you! Quiddity (WMF) (talk)

07:18, 16 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2019 (UTC)

Editing News #2 – Mobile editing and talk pages

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

Inside this newsletter, the Editing team talks about their work on the mobile visual editor, on the new talk pages project, and at Wikimania 2019.

Help

What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!

Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team wants your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.

Talk pages project

The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.

The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.

Mobile visual editor

The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.

Edit Cards

What happens when you click on a link. The new Edit Card is bigger and has more options for editing links.

• On 3 September, the Editing team released version 3 of Edit Cards. Anyone could use the new version in the mobile visual editor.
• There is an updated design on the Edit Card for adding and modifying links. There is also a new, combined workflow for editing a link's display text and target.
• Feedback: You can try the new Edit Cards by opening the mobile visual editor on a smartphone. Please post your feedback on the Edit cards talk page.

Toolbar

The editing toolbar is changing in the mobile visual editor. The old system had two different toolbars. Now, all the buttons are together. Tell the team what you think about the new toolbar.

• In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
  • One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
  • New navigation: The buttons for moving forward and backward in the edit flow have changed.
  • Seamless switching: an improved workflow for switching between the visual and wikitext modes.
• Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.

Wikimania

The Editing Team attended Wikimania 2019 in Sweden. They led a session on the mobile visual editor and a session on the new talk pages project. They tested two new features in the mobile visual editor with contributors. You can read more about what the team did and learned in the team's report on Wikimania 2019.

Looking ahead

• Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
• Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
• Measuring the impact of Edit Cards: This study asks whether the project helped editors add links and citations. The Editing team hopes to share results in November. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

11:12, 29 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2019 (UTC)

How to write in Gothic font?

When I type something it's in Latin script, how can I change to the Gothic font?--Gentenaar~nlwiki (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 16:14, 5 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2019 (UTC)

S𐍉𐍂𐍂𐍊, I 𐍆𐍉𐌿𐌽𐌳 𐌹𐍄.--Gentenaar~nlwiki (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 16:17, 5 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2019 (UTC)

Old Norse

Some people here may be also interested in Old Norse wiki (incubator): https://incubator.wikimedia.org/wiki/Wp/non

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) 19:01, 22 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2020 (UTC)

Editing news 2020 #1 – Discussion tools

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

This early version of the Reply tool automatically signs and indents comments.

The Editing team has been working on the talk pages project. The goal of the talk pages project is to help contributors communicate on wiki more easily. This project is the result of the Talk pages consultation 2019.

In a future update, the team plans to test a tool for easily linking to another user's name, a rich-text editing option, and other tools.

The team is building a new tool for replying to comments now. This early version can sign and indent comments automatically. Please test the new Reply tool.

• On 31 March 2020, the new reply tool was offered as a Beta Feature editors at four Wikipedias: Arabic, Dutch, French, and Hungarian. If your community also wants early access to the new tool, contact User:Whatamidoing (WMF).
• The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
  • an easy way to mention another editor ("pinging"),
  • a rich-text visual editing option, and
  • other features identified through user testing or recommended by editors.

To hear more about Editing Team updates, please add your name to the "Get involved" section of the project page. You can also watch these pages: the main project page, Updates, Replying, and User testing.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

19:24, 8 𐌰𐍀𐍂𐌴𐌹𐌻𐌹𐍃 2020 (UTC)

Editing news 2020 #2

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

The new features include a toolbar. What do you think should be in the toolbar?

This issue of the Editing newsletter includes information the Talk pages project, an effort to help contributors communicate on wiki more easily.

• Reply tool: This is available as a Beta Feature at the four partner wikis (Arabic, Dutch, French, and Hungarian Wikipedias). The Beta Feature is called "Discussion tools". The Beta Feature will get new features soon. The new features include writing comments in a new visual editing mode and pinging other users by typing @. You can test the new features on the Beta Cluster now. Some other wikis will have a chance to try the Beta Feature in the coming months.
• New requirements for user signatures: Soon, users will not be able to save invalid custom signatures in Special:Preferences. This will reduce signature spoofing, prevent page corruption, and make new talk page tools more reliable. Most editors will not be affected.
• New discussion tool: The Editing team is beginning work on a simpler process for starting new discussions. You can see the initial design on the project page.
• Research on the use of talk pages: The Editing team worked with the Wikimedia research team to study how talk pages help editors improve articles. We learned that new editors who use talk pages make more edits to the main namespace than new editors who don't use talk pages.

– Whatamidoing (WMF) (talk)

20:33, 17 𐌾𐌿𐌽𐌹𐌿𐍃 2020 (UTC)

Annual contest Wikipedia Pages Wanting Photos

This is to invite you to join the Wikipedia Pages Wanting Photos (WPWP) campaign to help improve Wikipedia articles with photos and win prizes. The campaign starts today 1st July 2020 and closes 31st August 2020.

The campaign primarily aims at using images from Wikimedia Commons on Wikipedia articles that are lacking images. Participants will choose among Wikipedia pages without photo images, then add a suitable file from among the many thousands of photos in the Wikimedia Commons, especially those uploaded from thematic contests (Wiki Loves Africa, Wiki Loves Earth, Wiki Loves Folklore, etc.) over the years.

Please visit the campaign page to learn more about the WPWP Campaign.

With kind regards,

Thank you,

Deborah Schwartz Jacobs, Communities Liaison, On behalf of the Wikipedia Pages Wanting Photos Organizing Team - 08:24, 1 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2020 (UTC)

feel free to translate this message to your local language when this helps your community

Feedback on movement names

Hello. Apologies if you are not reading this message in your native language. Please help translate to your language if necessary. Thank you!

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, 19:44, 2 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2020 (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.

Editing news 2020 #3

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

More than 50 million edits have been made using the visual editor on desktop.

Seven years ago this month, the Editing team offered the visual editor to most Wikipedia editors. Since then, editors have achieved many milestones:

• More than 50 million edits have been made using the visual editor on desktop.
• More than 2 million new articles have been created in the visual editor. More than 600,000 of these new articles were created during 2019.
• The visual editor is increasingly popular. The proportion of all edits made using the visual editor has increased every year since its introduction.
• In 2019, 35% of the edits by newcomers (logged-in editors with ≤99 edits) used the visual editor. This percentage has increased every year.
• Almost 5 million edits on the mobile site have been made with the visual editor. Most of these edits have been made since the Editing team started improving the mobile visual editor in 2018.
• On 17 November 2019, the first edit from outer space was made in the mobile visual editor. 🚀 👩‍🚀
• Editors have made more than 7 million edits in the 2017 wikitext editor, including starting 600,000 new articles in it. The 2017 wikitext editor is VisualEditor's built-in wikitext mode. You can enable it in your preferences.

Whatamidoing (WMF) (talk)

12:55, 9 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2020 (UTC)

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) 20:06, 9 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2020 (UTC) - m:Special:MyLanguage/Abstract Wikipedia/July 2020 announcement

The Universal Code of Conduct (UCoC): we want to hear from you.

Hello. Apologies that you may not be reading this message in your native language: translations of the following message may be available on Meta. Please help translate to your language. Thank you!

At times, our contributor communities and projects have suffered from a lack of guidelines that can help us create an environment where free knowledge can be shared safely without fear. There has been talk about the need for a global set of conduct rules in different communities over time.

Recently, the Wikimedia Foundation Board of Trustees announced a Community Culture Statement, asking for new standards to address harassment and promote inclusivity across projects.

The universal code of conduct will be a binding minimum set of standards across all Wikimedia projects, and will apply to all of us, staff and volunteers alike, all around the globe. It is of great importance that we all participate in expressing our opinions and thoughts about UCoC and its values. We should think about what we want it to cover or include and what it shouldn’t include, and how it may create difficulties or help our groups.

This is the time to talk about it. Before starting drafting the code of conduct, we would like to hear from you and to solicit the opinions and feedback of your colleagues. In order for your voice to be heard, we encourage and invite you to read more about the universal code of conduct (UCoC) and then write down your opinions or feedback on the discussion page.

To reduce language barriers during the process, you are welcome to translate the universal code of conduct main page from English into your respective local language. You and your community may choose to provide your opinions/feedback using your local languages.

Thanks in advance for your attention and contributions, The Trust and Safety team at Wikimedia Foundation 16:42, 22 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2020 (UTC)

Important: maintenance operation on September 1st

Read this message in another language • Please help translate to your language

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) 13:48, 26 𐌰𐌲𐌿𐍃𐍄𐌿𐍃 2020 (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. Please help translate to your language. Thank you!

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, 17:55, 10 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2020 (UTC) 

Wiki of functions naming contest

Please help translate to your language.

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. Thank you! --Quiddity (WMF)

21:20, 29 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2020 (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. Please help translate to your language.

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.

Thank you! Qgil-WMF (talk) 17:17, 7 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2020 (UTC)

Important: maintenance operation on October 27

Read this message in another language • Please help translate to your language

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) 17:10, 21 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2020 (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. Thank you! --Quiddity (WMF)

22:10, 5 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2020 (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 𐍆𐍂𐌿𐌼𐌹𐌽𐍃 𐌾𐌹𐌿𐌻𐌴𐌹𐍃, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 and 21 𐌾𐌹𐌿𐌻𐌴𐌹𐍃.

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)

18:09, 20 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2020 (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) 14:39, 30 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2020 (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) 10:55, 7 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2020 (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)

00:52, 15 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2020 (UTC)

Moving Wikimania 2021 to a Virtual Event

Hello. Apologies if you are not reading this message in your native language. Please help translate to your language. Thank you!

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, 15:15, 27 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2021 (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 projectgrants𐍆𐌰𐌿𐍂𐌰𐌼𐌴𐌻𐌴𐌹𐌽𐍃:Atwikimedia.org. Please help us translate this message to your local language. MediaWiki message delivery (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 08:01, 28 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2021 (UTC)

Wikifunctions logo contest

Hello. Please help to choose a design concept for the logo of the new Wikifunctions wiki. Voting starts today and will be open for 2 weeks. If you would like to participate, then please learn more and vote now at Meta-Wiki. Thank you! --Quiddity (WMF)

01:47, 2 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2021 (UTC)

Universal Code of Conduct – 2021 consultations

Universal Code of Conduct Phase 2

Please help translate to your language

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) 21:57, 5 𐌰𐍀𐍂𐌴𐌹𐌻𐌹𐍃 2021 (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 (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 23:05, 11 𐌾𐌿𐌽𐌹𐌿𐍃 2021 (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 (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 04:18, 16 𐌾𐌿𐌽𐌹𐌿𐍃 2021 (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)

14:13, 24 𐌾𐌿𐌽𐌹𐌿𐍃 2021 (UTC)

Server switch

Read this message in another language • Please help translate to your language

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) 01:19, 27 𐌾𐌿𐌽𐌹𐌿𐍃 2021 (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) 23:19, 17 𐌰𐌲𐌿𐍃𐍄𐌿𐍃 2021 (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.

10:03, 2 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2021 (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) 00:23, 7 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2021 (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) 17:01, 10 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2021 (UTC)

Server switch

Read this message in another language • Please help translate to your language

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) (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌹) 00:45, 11 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2021 (UTC)

Talk to the Community Tech

Read this message in another language • Please help translate to your language

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) (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌹) 03:03, 11 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2021 (UTC)

What support do Ancient Languages need?

Hi all, as part of the ongoing discussions about whether the Ancient Language policy should be changed, I am reaching out to see if we can establish more about the kinds of support that Ancient Language Wikis need. Can you take a look at this page on Meta, and leave feedback? --JimKillock (бєсѣда) 19:05, сєптємврїꙗ 11 числа, 2021 (UTC)

Select You the question statements for candidates of Drafting Committee Movement Charter

Into 2021-10-04 11:59:59 UTC you can select question statements for the candidates of Drafting Committee Movement Charter. ✍️ Dušan Kreheľ (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 22:30, 29 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2021 (UTC)

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

𐌰𐌽𐌸𐌰𐍂𐌰𐌹𐌼 𐍂𐌰𐌶𐌳𐍉𐌼 • Please help translate to your language

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) 02:25, 14 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2021 (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

More languages • Please help translate to your language

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

15:53, 5 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2021 (UTC)

Upcoming Call for Feedback about the Board of Trustees elections

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

More languages • Please help translate to your language

The Board of Trustees is preparing a call for feedback about the upcoming Board Elections, from January 7 - February 10, 2022.

While details will be finalized the week before the call, we have confirmed at least two questions that will be asked during this call for feedback:

• What is the best way to ensure fair representation of emerging communities among the Board?

• What involvement should candidates have during the election?

While additional questions may be added, the Movement Strategy and Governance team wants to provide time for community members and affiliates to consider and prepare ideas on the confirmed questions before the call opens. We apologize for not having a complete list of questions at this time. The list of questions should only grow by one or two questions. The intention is to not overwhelm the community with requests, but provide notice and welcome feedback on these important questions.

Do you want to help organize local conversation during this Call?

Contact the Movement Strategy and Governance team on Meta, on Telegram, or via email at msgwikimedia.org.

Reach out if you have any questions or concerns. The Movement Strategy and Governance team will be minimally staffed until January 3. Please excuse any delayed response during this time. We also recognize some community members and affiliates are offline during the December holidays. We apologize if our message has reached you while you are on holiday.

Best,

Movement Strategy and Governance

Thank you. Xeno (WMF) 17:56, 27 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2021 (UTC)

Feminism and Folklore 2022

Please help translate to your language

Greetings! You are invited to participate in Feminism and Folklore 2022 writing competion. This year Feminism and Folklore will focus on feminism, women biographies and gender-focused topics for the project in league with Wiki Loves Folklore gender gap focus with folk culture theme on Wikipedia.

You can help us in enriching the folklore documentation on Wikipedia from your region by creating or improving articles focused on folklore around the world, including, but not limited to folk festivals, folk dances, folk music, women and queer personalities in folklore, folk culture (folk artists, folk dancers, folk singers, folk musicians, folk game athletes, women in mythology, women warriors in folklore, witches and witch hunting, fairy tales and more. You can contribute to new articles or translate from the list of suggested articles here.

You can also support us in organizing the contest on your local Wikipedia by signing up your community to participate in this project and also translating the project page and help us spread the word in your native language.

Learn more about the contest and prizes from our project page. Feel free to contact us on our talk page or via Email if you need any assistance...

Thank you.

Feminism and Folklore Team,

Tiven2240 --05:49, 11 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2022 (UTC)

Call for Feedback about the Board of Trustees elections is now open

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

More languages • Please help translate to your language

The Call for Feedback: Board of Trustees elections is now open and will close on 7 February 2022.

With this Call for Feedback, the Movement Strategy and Governance team is taking a different approach. This approach incorporates community feedback from 2021. Instead of leading with proposals, the Call is framed around key questions from the Board of Trustees. The key questions came from the feedback about the 2021 Board of Trustees election. The intention is to inspire collective conversation and collaborative proposal development about these key questions.

Join the conversation.

Best,

Movement Strategy and Governance

Xeno (WMF) 01:04, 15 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2022 (UTC)

Movement Strategy and Governance News – Issue 5

More languages • Please help translate to your language

Movement Strategy and Governance News
Issue 5, January 2022Read the full newsletter

---

Welcome to the fifth issue of Movement Strategy and Governance News (formerly known as Universal Code of Conduct News)! This revamped newsletter distributes relevant news and events about the Movement Charter, Universal Code of Conduct, Movement Strategy Implementation grants, Board elections and other relevant MSG topics.

This Newsletter will be distributed quarterly, while more frequent Updates will also be delivered weekly or bi-weekly to subscribers. Please remember to subscribe here if you would like to receive these updates.

• Call for Feedback about the Board elections - We invite you to give your feedback on the upcoming WMF Board of Trustees election. This call for feedback went live on 10th January 2022 and will be concluded on 16th February 2022. (continue reading)
• Universal Code of Conduct Ratification - In 2021, the WMF asked communities about how to enforce the Universal Code of Conduct policy text. The revised draft of the enforcement guidelines should be ready for community vote in March. (continue reading)
• Movement Strategy Implementation Grants - As we continue to review several interesting proposals, we encourage and welcome more proposals and ideas that target a specific initiative from the Movement Strategy recommendations. (continue reading)
• The New Direction for the Newsletter - As the UCoC Newsletter transitions into MSG Newsletter, join the facilitation team in envisioning and deciding on the new directions for this newsletter. (continue reading)
• Diff Blogs - Check out the most recent publications about MSG on Wikimedia Diff. (continue reading)

Xeno (WMF) 03:27, 29 𐌰𐍆𐍄𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2022 (UTC)

Updates on the Universal Code of Conduct Enforcement Guidelines Review

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

More languages • Please help translate to your language

Hello everyone,

The Wikimedia Foundation Board of Trustees released a statement on the ratification process for the Universal Code of Conduct (UCoC) Enforcement Guidelines.

The Universal Code of Conduct (UCoC) provides a baseline of acceptable behavior for the entire movement. The UCoC and the Enforcement Guidelines were written by volunteer-staff drafting committees following community consultations.

The revised guidelines were published 24 January 2022 as a proposed way to apply the policy across the movement. There is a list of changes made to the guidelines after the enforcement draft guidelines review. Comments about the guidelines can be shared on the Enforcement Guidelines talk page on Meta-wiki.

To help to understand the guidelines and process, the Movement Strategy and Governance (MSG) team will be hosting Conversation Hours on 4 February 2022 at 15:00 UTC, 25 February 2022 at 12:00 UTC, and 4 March 2022 at 15:00 UTC. Join the conversation hours to speak with the UCoC project team and drafting committee members about the updated guidelines and voting process.

The timeline is available on Meta-wiki. The voting period is March 7 to 21. All eligible voters will have an opportunity to support or oppose the adoption of the Enforcement guidelines, and share why. See the voting information page for more details.

Many participants from across the movement have provided valuable input in these ongoing conversations. The UCoC and MSG teams want to thank the Drafting Committee and the community members for their contributions to this process.

Sincerely,

Movement Strategy and Governance
Wikimedia Foundation

Xeno (WMF) 03:55, 4 𐍆𐌰𐌹𐌱𐍂𐌿𐌰𐍂𐌴𐌹𐍃 2022 (UTC)

Leadership Development Task Force: Your feedback is appreciated

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

More languages • Please help translate to your language

The Community Development team at the Wikimedia Foundation is supporting the creation of a global, community-driven Leadership Development Task Force. The purpose of the task force is to advise leadership development work.

The team is looking for feedback about the responsibilities of the Leadership Development Task Force. This Meta page shares the proposal for a Leadership Development Task Force and how you can help. Feedback on the proposal will be collected from 7 to 25 February 2022.

Xeno (WMF) 02:35, 9 𐍆𐌰𐌹𐌱𐍂𐌿𐌰𐍂𐌴𐌹𐍃 2022 (UTC)

Wiki Loves Folklore is extended till 15th March

Please help translate to your language

Greetings from Wiki Loves Folklore International Team,

We are pleased to inform you that Wiki Loves Folklore an international photographic contest on Wikimedia Commons has been extended till the 15th of March 2022. The scope of the contest is focused on folk culture of different regions on categories, such as, but not limited to, folk festivals, folk dances, folk music, folk activities, etc.

We would like to have your immense participation in the photographic contest to document your local Folk culture on Wikipedia. You can also help with the translation of project pages and share a word in your local language.

Best wishes,

International Team
Wiki Loves Folklore

MediaWiki message delivery (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 04:50, 22 𐍆𐌰𐌹𐌱𐍂𐌿𐌰𐍂𐌴𐌹𐍃 2022 (UTC)

Remember to Participate in the UCoC Conversations and Ratification Vote!

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

More languages • Please help translate to your language

Hello everyone,

A vote in SecurePoll from 7 to 21 March 2022 is scheduled as part of the ratification process for the Universal Code of Conduct (UCoC) Enforcement guidelines. Eligible voters are invited to answer a poll question and share comments. Read voter information and eligibility details. During the poll, voters will be asked if they support the enforcement of the Universal Code of Conduct based on the proposed guidelines.

The Universal Code of Conduct (UCoC) provides a baseline of acceptable behavior for the entire movement. The revised enforcement guidelines were published 24 January 2022 as a proposed way to apply the policy across the movement. A Wikimedia Foundation Board statement calls for a ratification process where eligible voters will have an opportunity to support or oppose the adoption of the UCoC Enforcement guidelines in a vote. Wikimedians are invited to translate and share important information. For more information about the UCoC, please see the project page and frequently asked questions on Meta-wiki.

There are events scheduled to learn more and discuss:

• A community panel recorded on 18 February 2022 shares perspectives from small- and medium-sized community participants.
• The Movement Strategy and Governance (MSG) team is hosting Conversation Hours on 4 March 2022 at 15:00 UTC. Please sign-up to interact with the project team and the drafting committee about the updated enforcement guidelines and the ratification process. See the Conversation Hour summaries for notes from 4 February 2022 and 25 February 2022.

You can comment on Meta-wiki talk pages in any language. You may also contact either team by email: msgwikimedia.org or ucocprojectwikimedia.org

Sincerely,

Movement Strategy and Governance
Wikimedia Foundation

Xeno (WMF) 02:17, 2 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2022 (UTC)

Universal Code of Conduct Enforcement guidelines ratification voting open from 7 to 21 March 2022

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

More languages • Please help translate to your language

Hello everyone,

The ratification voting process for the revised enforcement guidelines of the Universal Code of Conduct (UCoC) is now open! Voting commenced on SecurePoll on 7 March 2022 and will conclude on 21 March 2022. Please read more on the voter information and eligibility details.

The Universal Code of Conduct (UCoC) provides a baseline of acceptable behavior for the entire movement. The revised enforcement guidelines were published 24 January 2022 as a proposed way to apply the policy across the movement. You can read more about the UCoC project.

You can also comment on Meta-wiki talk pages in any language. You may also contact the team by email: ucocprojectwikimedia.org

Sincerely,

Movement Strategy and Governance

Wikimedia Foundation

Xeno (WMF) 00:52, 8 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2022 (UTC)

Invitation to Hubs event: Global Conversation on 2022-03-12 at 13:00 UTC

Hello!

The Movement Strategy and Governance team of the Wikimedia Foundation would like to invite you to the next event about "Regional and Thematic Hubs". The Wikimedia Movement is in the process of understanding what Regional and Thematic Hubs should be. Our workshop in November was a good start (read the report), but we're not finished yet.

Over the last weeks we conducted about 16 interviews with groups working on establishing a Hub in their context (see Hubs Dialogue). These interviews informed a report that will serve as a foundation for discussion on March 12. The report is planned to be published on March 9.

The event will take place on March 12, 13:00 to 16:00 UTC on Zoom. Interpretation will be provided in French, Spanish, Arabic, Russian, and Portuguese. Registration is open, and will close on March 10. Anyone interested in the topic is invited to join us. More information on the event on Meta-wiki.

Best regards,

Kaarel Vaidla
Movement Strategy

01:31, 10 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2022 (UTC)

Wiki Loves Folklore 2022 ends tomorrow

International photographic contest Wiki Loves Folklore 2022 ends on 15th March 2022 23:59:59 UTC. This is the last chance of the year to upload images about local folk culture, festival, cuisine, costume, folklore etc on Wikimedia Commons. Watch out our social media handles for regular updates and declaration of Winners.

(Facebook , Twitter , Instagram)

The writing competition Feminism and Folklore will run till 31st of March 2022 23:59:59 UTC. Write about your local folk tradition, women, folk festivals, folk dances, folk music, folk activities, folk games, folk cuisine, folk wear, folklore, and tradition, including ballads, folktales, fairy tales, legends, traditional song and dance, folk plays, games, seasonal events, calendar customs, folk arts, folk religion, mythology etc. on your local Wikipedia. Check if your local Wikipedia is participating

A special competition called Wiki Loves Falles is organised in Spain and the world during 15th March 2022 till 15th April 2022 to document local folk culture and Falles in Valencia, Spain. Learn more about it on Catalan Wikipedia project page.

We look forward for your immense co-operation.

Thanks Wiki Loves Folklore international Team MediaWiki message delivery (𐌲𐌰𐍅𐌰𐌿𐍂𐌳𐌾𐌰) 14:40, 14 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2022 (UTC)

Leadership Development Working Group: Apply to join! (14 March to 10 April 2022)

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

More languages • Please help translate to your language

Hello everyone,

Thank you to everyone who participated in the feedback period for the Leadership Development Working Group initiative. A summary of the feedback can be found on Meta-wiki. This feedback will be shared with the working group to inform their work. The application period to join the Working Group is now open and will close on April 10, 2022. Please review the information about the working group, share with community members who might be interested, and apply if you are interested.

Thank you,

From the Community Development team

Xeno (WMF) 02:20, 18 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2022 (UTC)

Universal Code of Conduct Enforcement guidelines ratification voting is now closed

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

More languages • Please help translate to your language

Greetings,

The ratification voting process for the revised enforcement guidelines of the Universal Code of Conduct (UCoC) came to a close on 21 March 2022. Over 2300 Wikimedians voted across different regions of our movement. Thank you to everyone who participated in this process! The scrutinizing group is now reviewing the vote for accuracy, so please allow up to two weeks for them to finish their work.

The final results from the voting process will be announced here, along with the relevant statistics and a summary of comments as soon as they are available. Please check out the voter information page to learn about the next steps. You can comment on the project talk page on Meta-wiki in any language. You may also contact the UCoC project team by email: ucocprojectwikimedia.org

Best regards,

Movement Strategy and Governance

Xeno (WMF) 01:53, 30 𐌼𐌰𐍂𐍄𐌾𐌿𐍃 2022 (UTC)

Movement Strategy and Governance News – Issue 6

Movement Strategy and Governance News
Issue 6, April 2022Read the full newsletter

---

Welcome to the sixth issue of Movement Strategy and Governance News! This revamped newsletter distributes relevant news and events about the Movement Charter, Universal Code of Conduct, Movement Strategy Implementation grants, Board of trustees elections and other relevant MSG topics.

This Newsletter will be distributed quarterly, while the more frequent Updates will also be delivered weekly. Please remember to subscribe here if you would like to receive future issues of this newsletter.

• Leadership Development - A Working Group is Forming! - The application to join the Leadership Development Working Group closed on April 10th, 2022, and up to 12 community members will be selected to participate in the working group. (continue reading)
• Universal Code of Conduct Ratification Results are out! - The global decision process on the enforcement of the UCoC via SecurePoll was held from 7 to 21 March. Over 2,300 eligible voters from at least 128 different home projects submitted their opinions and comments. (continue reading)
• Movement Discussions on Hubs - The Global Conversation event on Regional and Thematic Hubs was held on Saturday, March 12, and was attended by 84 diverse Wikimedians from across the movement. (continue reading)
• Movement Strategy Grants Remain Open! - Since the start of the year, six proposals with a total value of about $80,000 USD have been approved. Do you have a movement strategy project idea? Reach out to us! (continue reading)
• The Movement Charter Drafting Committee is All Set! - The Committee of fifteen members which was elected in October 2021, has agreed on the essential values and methods for its work, and has started to create the outline of the Movement Charter draft. (continue reading)
• Introducing Movement Strategy Weekly - Contribute and Subscribe! - The MSG team have just launched the updates portal, which is connected to the various Movement Strategy pages on Meta-wiki. Subscriber to get up-to-date news about the various ongoing projects. (continue reading)
• Diff Blogs - Check out the most recent publications about Movement Strategy on Wikimedia Diff. (continue reading)

Also, a draft of the 2022-23 Wikimedia Foundation Annual Plan has been published. Input is being sought on-wiki and during several conversations with Wikimedia Foundation CEO Maryana Iskander.

See full announcement on Meta-wiki. Xeno (WMF) 01:45, 22 𐌰𐍀𐍂𐌴𐌹𐌻𐌹𐍃 2022 (UTC)

Editing news 2022 #1

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

New editors were more successful with this new tool.

The New topic tool helps editors create new ==Sections== on discussion pages. New editors are more successful with this new tool. You can read the report. Soon, the Editing team will offer this to all editors at the 20 Wikipedias that participated in the test. You will be able to turn it off at Special:Preferences#mw-prefsection-editing-discussion.

Whatamidoing (WMF) 18:55, 2 𐌼𐌰𐌾𐌿𐍃 2022 (UTC)

2022 Board of Trustees Call for Candidates

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

More languages • Please help translate to your language

The Board of Trustees seeks candidates for the 2022 Board of Trustees election. Read more on Meta-wiki.

The 2022 Board of Trustees election is here! Please consider submitting your candidacy to serve on the Board of Trustees.

The Wikimedia Foundation Board of Trustees oversees the Wikimedia Foundation's operations. Community-and-affiliate selected trustees and Board-appointed trustees make up the Board of Trustees. Each trustee serves a three year term. The Wikimedia community has the opportunity to vote for community-and-affiliate selected trustees.

The Wikimedia community will vote to fill two seats on the Board in 2022. This is an opportunity to improve the representation, diversity, and expertise of the Board as a team.

Who are potential candidates? Are you a potential candidate? Find out more on the Apply to be a Candidate page.

Thank you for your support,

Movement Strategy and Governance on behalf of the Elections Committee and the Board of Trustees
10:39, 10 𐌼𐌰𐌾𐌿𐍃 2022 (UTC)

Revisions to the Universal Code of Conduct (UCoC) Enforcement Guidelines

More languages • Please help translate to your language

Hello all,

We'd like to provide an update on the work on the Enforcement Guidelines for the Universal Code of Conduct. After the conclusion of the community vote on the guidelines in March, the Community Affairs committee (CAC) of the Board asked that several areas of the guidelines be reviewed for improvements before the Board does its final review. These areas were identified based on community discussions and comments provided during the vote. The CAC also requested review of the controversial Note in 3.1 of the UCoC itself.

Once more, a big thank you to all who voted, especially to all who left constructive feedback and comments! The project team is working with the Board to establish a timeline for this work, and will communicate this next month.

Members of the two prior UCoC Drafting Committees have generously offered their time to help shape improvements to the Guidelines. You can read more about them and their work here, as well as read summaries of their weekly meetings in 2022.

Wikimedians have provided many valuable comments together with the vote and in other conversations. Given the size and diversity of the Wikimedia community, there are even more voices out there who can give ideas on how to improve the enforcement guidelines and add even more valuable ideas to the process. To help the Revisions committee identify improvements, input on several questions for the committee’s review is requested. Visit the Meta-wiki pages (Enforcement Guidelines revision discussions, Policy text revision discussions) to get your ideas to the Committee - it is very important that viewpoints are heard from different communities before the Committee begins drafting revision proposals.

On behalf of the UCoC project team

Xeno (WMF) 22:56, 3 𐌾𐌿𐌽𐌹𐌿𐍃 2022 (UTC)

Propose statements for the 2022 Election Compass

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

More languages • Please help translate to your language

Hi all,

Community members in the 2022 Board of Trustees election are invited to propose statements to use in the Election Compass.

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

Here is the timeline for the Election Compass

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

The Elections Committee will select the top 15 statements at the beginning of August. The Elections Committee will oversee the process, supported by the Movement Strategy and Governance team. MSG will check that the questions are clear, there are no duplicates, no typos, and so on.

Best,

Movement Strategy and Governance

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

MNadzikiewicz (WMF) (talk) 11:34, 14 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2022 (UTC)

Movement Strategy and Governance News – Issue 7

Movement Strategy and Governance News
Issue 7, July-September 2022Read the full newsletter

---

Welcome to the 7th issue of Movement Strategy and Governance News! The newsletter distributes relevant news and events about the implementation of Wikimedia's Movement Strategy recommendations, other relevant topics regarding Movement governance, as well as different projects and activities supported by the Movement Strategy and Governance (MSG) team of the Wikimedia Foundation.

The MSG Newsletter is delivered quarterly, while the more frequent Movement Strategy Weekly will be delivered weekly. Please remember to subscribe here if you would like to receive future issues of this newsletter.

• Movement sustainability: Wikimedia Foundation's annual sustainability report has been published. (continue reading)
• Improving user experience: recent improvements on the desktop interface for Wikimedia projects. (continue reading)
• Safety and inclusion: updates on the revision process of the Universal Code of Conduct Enforcement Guidelines. (continue reading)
• Equity in decisionmaking: reports from Hubs pilots conversations, recent progress from the Movement Charter Drafting Committee, and a new white paper for futures of participation in the Wikimedia movement. (continue reading)
• Stakeholders coordination: launch of a helpdesk for Affiliates and volunteer communities working on content partnership. (continue reading)
• Leadership development: updates on leadership projects by Wikimedia movement organizers in Brazil and Cape Verde. (continue reading)
• Internal knowledge management: launch of a new portal for technical documentation and community resources. (continue reading)
• Innovate in free knowledge: high-quality audiovisual resources for scientific experiments and a new toolkit to record oral transcripts. (continue reading)
• Evaluate, iterate, and adapt: results from the Equity Landscape project pilot (continue reading)
• Other news and updates: a new forum to discuss Movement Strategy implementation, upcoming Wikimedia Foundation Board of Trustees election, a new podcast to discuss Movement Strategy, and change of personnel for the Foundation's Movement Strategy and Governance team. (continue reading)

Thank you for reading! RamzyM (WMF) 01:37, 18 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2022 (UTC)

Announcing the six candidates for the 2022 Board of Trustees election

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

More languages • Please help translate to your language

Hi everyone,

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

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

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

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

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

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

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

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

Best,

Movement Strategy and Governance

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

MNadzikiewicz (WMF) 14:03, 27 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2022 (UTC)

Vote for Election Compass Statements

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

More languages • Please help translate to your language

Hi all,

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

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

Here is the timeline for the Election Compass:

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

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

Best,

Movement Strategy and Governance

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

MNadzikiewicz (WMF) 21:01, 27 𐌷𐌰𐍅𐌹𐌼𐌴𐌽𐍉𐌸𐍃 2022 (UTC)

The 2022 Board of Trustees election Community Voting period is now open

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

More languages • Please help translate to your language

Hi everyone,

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

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

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

Best,

Movement Strategy and Governance

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

MNadzikiewicz (WMF)

Invitation to join the Movement Strategy Forum

𐍆𐌰𐌿𐍂𐌰𐌼𐌴𐌻𐌴𐌹𐌽𐍃:More languages

Hello everyone,

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

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

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

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

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

We look forward to seeing you at the MS Forum!

Best regards,

the Movement Strategy and Governance Team

User:MNadzikiewicz (WMF) 11:32, 29 𐌰𐌲𐌿𐍃𐍄𐌿𐍃 2022 (UTC)

The Vector 2022 skin as the default in two weeks?

The slides for our presentation at Wikimania 2022

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

We have been working on it for the past three years. So far, it has been the default on more than 30 wikis, including sister projects, all accounting for more than 1 billion pageviews per month. On average 87% of active logged-in users of those wikis use Vector 2022.

It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy. Logged-in users can at any time switch to any other skins. No changes are expected for users of these skins.

• Top of an article
• 

  Vector legacy (current default)

• 

  Vector 2022

• A section of an article
• 

  Vector legacy (current default)

• 

  Vector 2022

About the skin

[Why is a change necessary] The current default skin meets the needs of the readers and editors as these were 13 years ago. Since then, new users have begun using Wikimedia projects. The old Vector doesn't meet their needs.

[Objective] The objective for the new skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It draws inspiration from previous requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. We reduced PHP code in Wikimedia deployed skins by 75%. The project has also focused on making it easier to support gadgets and use APIs.

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

• The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
• The new table of contents makes it easier to navigate to different sections. Readers and editors jumped to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
• The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the wikis we tested on.
• The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.

[Try it out] Try out the new skin by going to the appearance tab in your preferences and selecting Vector 2022 from the list of skins.

How can editors change and customize this skin?

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

Our plan

If no large concerns are raised, we plan on deploying in the week of October 3, 2022. If your community would like to request more time to discuss the changes, hit the button and write to us. We can adjust the calendar.

Request for more time to discuss the change

If you'd like ask our team anything, if you have questions, concerns, or additional thoughts, please ping me here or write on the talk page of the project. We will gladly answer! Also, see our FAQ. Thank you! SGrabarczuk (WMF) (talk) 04:15, 22 𐍃𐌰𐌹𐍀𐍄𐌰𐌹𐌼𐌱𐌰𐌹𐍂 2022 (UTC)

Update on Vector 2022

Hello. I'm sorry for not communicating in your language. I'll be grateful if you translated my message. I'm writing on behalf of the Web team working on the new skin, Vector 2022.

We wanted to apologize for the delays in the deployment of Vector 2022. We know many of you are waiting for this eagerly. We have been delaying the deployment because we have been working on the logos. It has taken us more time than originally expected. Once the logos are ready, we will let you know the exact date of deployment. We are planning for either the next (more likely) or the following week. If your wiki doesn't currently have a localized logo, we encourage you to reach out to us and we can help make one.

We invite you to get involved in the project. Contact us if you have any questions or need any help, particularly with the compatibility of gadgets and user scripts. Thank you! SGrabarczuk (WMF) (talk) 23:24, 19 𐌰𐌿𐌺𐍄𐍉𐌱𐌰𐌹𐍂 2022 (UTC)

Invitation to attend “Ask Me Anything about Movement Charter” Sessions

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

More languages • Please help translate to your language

Hello all,

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

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

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

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

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

Call for Movement Charter Ambassadors

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

We thank you for your time and participation.

On behalf of the Movement Charter Drafting Committee,

MNadzikiewicz (WMF) 15:33, 7 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2022 (UTC)

Apply for Funding through the Movement Strategy Community Engagement Package to Support Your Community

𐍆𐌰𐌿𐍂𐌰𐌼𐌴𐌻𐌴𐌹𐌽𐍃:More languages

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

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

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

Best regards,
Movement Strategy and Governance Team
Wikimedia Foundation

MNadzikiewicz (WMF) 16:25, 14 𐍆𐍂𐌿𐌼𐌰 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2022 (UTC)

Opportunities open for the Ombuds commission and the Case Review Committee

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

More languages • Please help translate to your language

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

About the Ombuds commission

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

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

About the Case Review Committee

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

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

Applying to join either of these groups

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

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

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

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

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

On behalf of the Committee Support team,

Community Wishlist Survey 2023 opens in January!

Please help translate to your language

Hello

The Community Wishlist Survey (CWS) 2023, which lets contributors propose and vote for tools and improvements, starts next month on Monday, 23 January 2023, at 18:00 UTC and will continue annually.

We are inviting you to share your ideas for technical improvements to our tools and platforms. Long experience in editing or technical skills is not required. If you have ever used our software and thought of an idea to improve it, this is the place to come share those ideas!

The dates for the phases of the Survey will be as follows:

• Phase 1: Submit, discuss, and revise proposals – Monday, Jan 23, 2023 to Sunday, Feb 6, 2023
• Phase 2: WMF/Community Tech reviews and organizes proposals – Monday, Jan 30, 2023 to Friday, Feb 10, 2023
• Phase 3: Vote on proposals – Friday, Feb 10, 2023 to Friday, Feb 24, 2023
• Phase 4: Results posted – Tuesday, Feb 28, 2023

If you want to start writing out your ideas ahead of the Survey, you can start thinking about your proposals and draft them in the CWS sandbox.

We are grateful to all who participated last year. See you in January 2023!

Thank you! Community Tech, STei (WMF) 12:59, 13 𐌾𐌹𐌿𐌻𐌴𐌹𐍃 2022 (UTC)