Re: [Wikitech-l] FlaggedRevs/PendingChanges in only specific pages (e.g. Biographies of living persons)
Thank you, all. I will tell your answer to Japanese Wikipedians. Thanks again Original Message Subject: Re: [Wikitech-l] FlaggedRevs/PendingChanges in only specific pages (e.g. Biographies of living persons) From: Risker risker...@gmail.com To: Wikimedia developers wikitech-l@lists.wikimedia.org Date: 2013/04/27 5:45 On 26 April 2013 13:40, maill...@enmps.net wrote: Hi all! Nowadays we, Japanese Wikipedians, are discussing what we should do for the next election of the Diet, which is the first one after the Election Law allows online election campaigning. And there are an idea to install FlaggedRevs or PendingChanges extension to hide the unreviewed edits to avoid defamation and vandalism and so on. So I have a question; can we apply such functions to the specific pages (e.g. with a template or a magic word)? or are there any other suited functions/extensions to handle such problem? Thank you. I cannot speak about FlaggedRevs, which I believe is enabled on German and Russian Wikipedias, but I can give you some practical, non-technical information about PendingChanges, which is enabled on English Wikipedia. PendingChanges allows an administrator to set the article to require that edits from a specific group of editors (usually non-confirmed editors, which includes all unregistered editors) be held in pending status, and not displayed to the reader. It is done through the page protection interface. Editors with reviewer permissions, which includes all administrators and any other group that the project wants to include, review the pending edits and decide whether or not they should be included in the article. Even if the pending edit is rejected by the reviewer, it remains in the history of the page. English Wikipedia is currently using PendingChanges on a small number of pages, usually those that have a lot of vandalism or inappropriate edits from unregistered or new editors. It is not perfect - for example, it can cause time-outs on really large pages - but it is useful provided that there are enough editors with reviewer permissions to keep up with any backlog. Your project would have to decide on the criteria for deciding whether or not an edit is accepted; on English Wikipedia, we reject edits that are obviously vandalism, as well as unreferenced negative information about living people. I'd be happy to give you a tour and some further information off-list if you think this would be helpful in making a decision. Meanwhile, the main participants of this list can probably answer more of the technical questions. Best, Risker ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- 青子守歌 aokomoriuta e-mail: aokomori...@enmps.net URL: http://j.mp/ao_komoriuta twitter: http://twitter.com/aokomoriuta jawp: http://ja.wikipedia.org/wiki/User:aokomoriuta mixi: http://mixi.jp/show_friend.pl?id=19926155 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [ResourceLoader] JavaScript may break on your wiki: Fix it before that happens
What kind of issues are expected concretely? Is there any kinds of checklist or todo? Original Message Subject: [Wikitech-l] [ResourceLoader] JavaScript may break on your wiki: Fix it before that happens From: Guillaume Paumier gpaum...@wikimedia.org To: Wikimedia Foundation mailing list foundatio...@lists.wikimedia.org, Wikimedia Developers wikitech-l@lists.wikimedia.org, Coordination of technology deployments across languages/projects wikitech-ambassad...@lists.wikimedia.org Date: 2011年2月12日 18:49:27 Greetings, As you may know, the Wikimedia teach team has started to upgrade MediaWiki on some wikis. MediaWiki is the software that runs all Wikimedia wikis. The most visible change for Wikimedia users will be the deployment of ResourceLoader [1]. ResourceLoader optimizes the use of JavaScript in MediaWiki, speeding up its delivery by compressing it sometimes, and cutting down on the amount of unused JavaScript that gets delivered to the browser in the first place. The installation of ResourceLoader may cause compatibility issues with existing JavaScript code. Trevor Parscal and Roan Kattouw, the main developers of ResourceLoader, will be available on IRC [2] on Monday, February 14th, at 18:00 (UTC) [3], to answer questions and help fix issues related to ResourceLoader. *If you maintain JavaScript code on your home wiki, please attend.* Don't wait until your wiki's JavaScript is all broken. Please spread this information as widely as possible; it's critical to reach as many local JavaScript maintainers as possible. Logs of the session will be published publicly. [1] http://www.mediawiki.org/wiki/ResourceLoader [2] http://meta.wikimedia.org/wiki/IRC_office_hours [3] All timezones: http://ur1.ca/3819u -- 青子守歌 aokomoriuta e-mail: aokomori...@enmps.net URL: http://bgs.jpn.ph/ blog: http://bgs.jpn.ph/blog/ twitter: http://twitter.com/aokomoriuta jawp: http://ja.wikipedia.org/wiki/User:aokomoriuta mixi: http://mixi.jp/show_friend.pl?id=19926155 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [ResourceLoader] JavaScript may break on your wiki: Fix it before that happens
Thank you for your advice. You mean we should be careful about upgrading jQuery's version if the script uses jQuery, i.e. the problem you refer to is not caused if we dont' use jQuery, right? Original Message Subject: Re: [Wikitech-l] [ResourceLoader] JavaScript may break on your wiki: Fix it before that happens From: Roan Kattouw roan.katt...@gmail.com To: Wikimedia developers wikitech-l@lists.wikimedia.org Date: 2011年2月12日 20:23:14 2011/2/12 青子守歌 (aokomoriuta)maill...@enmps.net: What kind of issues are expected concretely? Is there any kinds of checklist or todo? Trevor probably knows more about this, but what I can tell you at least is that some wikis load their own version of jQuery in their site JS, which can break things terribly because plugins can get deregistered. Also, site JS overwriting jQuery with a different version can obviously cause issues. A few subtleties with regards to the timing of JS loading and execution have changed, but Trevor is really the person to ask about that. Also, site and user JS/CSS is now served from bits.wikimedia.org as well, which means things like relative @import statements in CSS are broken at this time; we're working on a fix for that. Roan Kattouw (Catrope) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- 青子守歌 aokomoriuta e-mail: aokomori...@enmps.net URL: http://bgs.jpn.ph/ blog: http://bgs.jpn.ph/blog/ twitter: http://twitter.com/aokomoriuta jawp: http://ja.wikipedia.org/wiki/User:aokomoriuta mixi: http://mixi.jp/show_friend.pl?id=19926155 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
