Wikimammenn:An davarn/Miz Gouere 2018

Dielloù
2022	Genver	C’hwevrer	Meurzh	Ebrel	Mae	Mezheven
	Gouere	Eost	Gwengolo	Here	Du	Kerzu
2023	Genver	C’hwevrer	Meurzh	Ebrel	Mae	Mezheven
	Gouere	Eost	Gwengolo	Here	Du	Kerzu
2024	Genver	C’hwevrer	Meurzh	Ebrel	Mae	Mezheven
	Gouere	Eost	Gwengolo	Here	Du	Kerzu

Ouzhpennañ ur gemennadenn

Miz Gouere 2018

⇑ An davarn • Miz Mezheven 2018 ≪ Miz Gouere 2018 ≫ Miz Eost 2018 • Rann nevez e tavarn miz Gouere 2018

Global preferences are available

Global preferences are now available, you can set them by visiting your new global preferences page. Visit mediawiki.org for information on how to use them and leave feedback. -- Keegan (WMF) (talk)

10 Gou 2018 da 21:19 (CEST)

Consultation on the creation of a separate user group for editing sitewide CSS/JS

(Please help translate to your language)

Hi all,

I'm preparing a change in who can edit sitewide CSS/JS pages. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which are executed in the browser of all readers and editors.) Currently all administrators are able to edit these pages, which poses a serious and unnecessary security risk. Soon, a dedicated, smaller user group will take over this task. Your community will be able to decide who belongs in this group, so this should mean very little change for you. You can find out more and provide feedback at the consultation page on Meta. If you are involved in maintaining CSS/JS code, or policymaking around adminship requests, please give it a look!

Thanks!
Tgr (talk) 12 Gou 2018 da 10:45 (CEST) (via global message delivery)

Bot rights for User:Wikisource-bot

Hi. With the requirement to fix the page categorisation as notified at phab:T198470, I would like to propose to the community to have our bot run through and address the problem with the solution identified. The bot has been used to resolve issue previously on the Wikisources.

• special:centralauth/Wikisource-bot

Thanks. Billinghurst (kaozeal) 7 Gou 2018 da 10:39 (CEST)

Addition of brWS to global bots

Above I have added a bot request, as this wiki is not within the global bot project, per list m:Special:WikiSets/2. Would the community consider opting in to the global bots, so that when we have Wikisource-wide fixes for mw:Extension:ProofreadPage that is possible to organise the bots to do the jobs within Phabricator, and simply get the fix in place. Billinghurst (kaozeal) 7 Gou 2018 da 10:39 (CEST)

Words hyphenated across pages in Wikisource are now joined

Hi, this is a message by Can da Lua as discussed here for wikisource communities

The ProofreadPage extension can now join together a word that is split between a page and the next.

In the past, when a page was ending with "concat-" and the next page was beginning with "enation", the resulting transclusion would have been "concat- enation", and a special template like d:Q15630535 had to be used to obtain the word "concatenation".

Now the default behavior has changed: the hyphen at the end of a page is suppressed and in this case no space is inserted, so the result of the transclusion will be: "concatenation", without the need of a template. The "joiner" character is defined by default as "-" (the regular hyphen), but it is possible to change this. A template may still be needed to deal with particular cases when the hyphen needs to be preserved.

Please share this information with your community.

MediaWiki message delivery (kaozeal) 30 Gwe 2018 da 12:28 (CEST)

Hi @Tgr:,

Thanks for your message. We are a small community (~5 active users), I'm the only active admin and I don’t do a lot of css/js coding (a bit of css here and there but I don’t master js and I’m only copy-pasting code from other Wikisources). Indeed it will be very little change for us.

Cheers, Vigneron * ^diskut. 12 Gou 2018 da 11:14 (CEST)

New user group for editing sitewide CSS/JS

(Please help translate to your language)

Hi all!

To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.) A new user group, interface-admin, has been created. Starting four weeks from now, only members of this group will be able 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).

You can learn more about the motivation behind the change here.

Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats). This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).

Thanks!
Tgr (talk) 30 Gou 2018 da 15:08 (CEST) (via global message delivery)

New user group for editing sitewide CSS / JS

(Please help translate to your language)

Hi all!

To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.) A new user group, interface-admin, has been created. Starting four weeks from now, only members of this group will be able 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).

You can learn more about the motivation behind the change here.

Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats). This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).

Thanks!
Tgr (talk) 30 Gou 2018 da 19:44 (CEST) (via global message delivery)