Wikikutip:Warung Kopi/Arsip/2018
Editing News #1—2018
[sunting]Read this in another language • Subscription list for this multilingual newsletter
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
[sunting]- 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. [1]
- Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [2]
- 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
[sunting]- 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. [3] - 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. Terima kasih!
2 Maret 2018 20.56 (UTC)
AdvancedSearch
[sunting]Birgit Müller (WMDE) 7 Mei 2018 14.53 (UTC)
Update on page issues on mobile web
[sunting]Update on page issues on mobile web
Tolong bantu terjemahkan ke bahasa Anda Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.
So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:
- The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
- Page issues make sense to readers and they understand how they work
- Readers care about page issues and consider them important
- Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues
Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.
CKoerner (WMF) (talk) 12 Juni 2018 20.58 (UTC)
Global preferences are available
[sunting]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 Juli 2018 19.19 (UTC)
Consultation on the creation of a separate user group for editing sitewide CSS/JS
[sunting](Tolong bantu terjemahkan ke bahasa Anda)
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 Juli 2018 08.45 (UTC) (via global message delivery)
New user group for editing sitewide CSS/JS
[sunting](Tolong bantu terjemahkan ke bahasa Anda)
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 Juli 2018 13.08 (UTC) (via global message delivery)
Editing of sitewide CSS/JS is only possible for interface administrators from now
[sunting](Tolong bantu terjemahkan ke bahasa Anda)
Hi all,
as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin
(Pengurus antarmuka) 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) 27 Agustus 2018 12.39 (UTC) (via global message delivery)
Read-only mode for up to an hour on 12 September and 10 October
[sunting]Read this message in another language • Tolong bantu terjemahkan ke bahasa Anda
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)
6 September 2018 13.33 (UTC)
Permintaan menjadi Pengurus oleh Rachmat04
[sunting]Halo, melalui Warung Kopi ini saya ingin mencalonkan diri menjadi pengurus di proyek Wikiquote ini, setidaknya Pengurus sementara, untuk membenahi halaman yang perlu dihapus dan diperbaiki dari kontributor vandalisme. Mohon bantuannya memberikan suara setuju atau tidak setuju di bawah ini. Trims, Rachmat04 (bicara) 8 Oktober 2018 10.13 (UTC)
Setuju
[sunting]- Setuju -- Bagas Chrisara (bicara) 10 Oktober 2018 14.09 (UTC)
- Setuju Farras (bicara) 10 Oktober 2018 16.44 (UTC)
- Setuju Ezagren (bicara) 11 Oktober 2018 07.42 (UTC)
Tidak setuju
[sunting]Abstain
[sunting]The Community Wishlist Survey
[sunting]The Community Wishlist Survey. Tolong bantu terjemahkan ke bahasa Anda.
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)30 Oktober 2018 11.06 (UTC)
Editing News #2—2018
[sunting]Read this in another language • Subscription list for this multilingual newsletter
Did you know?
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
[sunting]- 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. [4]
Let's work together
[sunting]- 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. Terima kasih!
2 November 2018 14.17 (UTC)
Change coming to how certain templates will appear on the mobile web
[sunting]Change coming to how certain templates will appear on the mobile web
Tolong bantu terjemahkan ke bahasa Anda
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.
Terima kasih!
CKoerner (WMF) (talk) 13 November 2018 19.34 (UTC)
Community Wishlist Survey vote
[sunting]The Community Wishlist Survey. Tolong bantu terjemahkan ke bahasa Anda.
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)22 November 2018 18.13 (UTC)
Advanced Search
[sunting]Johanna Strodt (WMDE) (talk) 26 November 2018 11.02 (UTC)
New Wikimedia password policy and requirements
[sunting]Tolong bantu terjemahkan ke bahasa Anda
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.
Terima kasih!
CKoerner (WMF) (talk) 6 Desember 2018 20.03 (UTC)
Invitation from Wiki Loves Love 2019
[sunting]Tolong bantu terjemahkan ke bahasa Anda
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,
Imagine... the sum of all love!
--MediaWiki message delivery (bicara) 27 Desember 2018 10.12 (UTC)