Wikisource:Warung kopi

Warung Kopi

---

Bicarakan topik baru

Komunitas

Halaman bantuan
Pengumuman
Milis

Arsip

2005-2011

2012-2016

---

---

Selamat datang kawan-kawan para wikiwan dan wikiwati! Warung kopi ini merupakan forum di mana anda-anda sekalian bisa mengungkapkan segala komentar, saran dan uneg-uneg. Untuk masalah yang lebih pelik anda bisa pula menghubungi para pengurus Wikisource secara langsung. Apabila anda memberi komentar, jangan lupa untuk mengetik ~~~~, empat kali tanda gelombang (tilde), supaya jatidiri anda dan tanggal penulisan terlihat. Terima kasih.

---

---

• Wikipedia
• Wiktionary
• Wikibooks
• Wikiquote

Pengajuan menjadi pengurus

Halo, para pengguna Wikisource ID. Saya, Raymond Sutanto, mengajukan diri sebagai pengurus Wikisource bahasa Indonesia untuk membantu merawat dan bersih-bersih disini. Tanggungjawab sudah saya buktikan di Wikipedia bahasa Indonesia (masih aktif hampir setiap hari) dan Wikibuku bahasa Indonesia (beberapa kali dalam sebulan). Salam, RaymondSutanto (bicara) 10 Oktober 2017 18.49 (UTC)

Setuju

•  Setuju, untuk menambah pengurus yang aktif dalam proyek ini. ··· 🌸 Rachmat04 · ☕ 13 Oktober 2017 01.08 (UTC)
•  Setuju per alasan di atas. -- Bagas Chrisara (bicara) 17 Oktober 2017 02.24 (UTC)
•  Setuju semoga amanah. --Beeyan (bicara) 17 Oktober 2017 07.53 (UTC)

Keputusan

Dengan ini pemilihan saya nyatakan tutup dengan hasil 3 orang setuju (100%) dan 0 orang tidak setuju. Maka saya mengangkat pengguna:RaymondSutanto sebagai pengurus baru. Meursault2004 (bicara) 31 Oktober 2017 12.20 (UTC)

Terima kasih Pak Revo. Saya berjanji akan menggunakannya dengan baik. Salam, RaymondSutanto (bicara) 31 Oktober 2017 12.27 (UTC)

New print to pdf feature for mobile web readers

New print to pdf feature for mobile web readers

The Readers web team will be deploying a new feature this week to make it easier to download PDF versions of articles on the mobile website.

Providing better offline functionality was one of the highlighted areas from the research done by the New Readers team in Mexico, Nigeria, and India. The teams created a prototype for mobile PDFs which was evaluated by user research and community feedback. The prototype evaluation received positive feedback and results, so development continued.

For the initial deployment, the feature will be available to Google Chrome browsers on Android. Support for other mobile browsers to come in the future. For Chrome, the feature will use the native Android print functionality. Users can choose to download a webpage as a PDF. Mobile print styles will be used for these PDFs to ensure optimal readability for smaller screens.

The feature is available starting Wednesday, Nov 15. For more information, see the project page on MediaWiki.org.

Terima kasih!

CKoerner (WMF) (talk) 20 November 2017 22.07 (UTC)

AdvancedSearch

From May 8, AdvancedSearch will be available as a beta feature in your wiki. The feature enhances the search page through an advanced parameters form and aims to make existing search options more visible and accessible for everyone. AdvancedSearch is a project by WMDE Technical Wishes. Everyone is invited to test the feature and we hope that it will serve you well in your work!

Birgit Müller (WMDE) 7 Mei 2018 14.53 (UTC)

Update on page issues on mobile web

Update on page issues on mobile web

Please help translate to your language 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)

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 (bicara) 7 Juli 2018 09.59 (UTC)

Hi, . You can activate the Wikisource-bot here. Regards, RaymondSutanto (bicara) 9 Juli 2018 16.18 (UTC)

@Meursault2004 your decision? Ankry (bicara) 8 Agustus 2018 06.58 (UTC)

The bot flag assigned by a steward. Ankry (bicara) 16 Agustus 2018 06.39 (UTC)

Addition of idWS 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 (bicara) 7 Juli 2018 10.00 (UTC)

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 Juli 2018 19.19 (UTC)

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 Juli 2018 08.45 (UTC) (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 Juli 2018 13.08 (UTC) (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 Juli 2018 17.44 (UTC) (via global message delivery)