Movatterモバイル変換

[0]ホーム
URL:

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview
List overview
Download

Wikitech-lAugust 2013

wikitech-l@lists.wikimedia.org
  • 133 participants
  • 134 discussions
Start a nNew thread
Database dumps
by Byrial Jensen 17 Apr '25

17 Apr '25
Until some weeks agohttp://dumps.wikimedia.org/backup-index.html usedto show 4 dumps in progress at the same time. That meant that newdatabase dumps normally was available within about 3 weeks for alldatabases except for enwiki and maybe dewiki where the dump process dueto size took longer time.However the 4 dumps processes at one time become 3 some weeks ago. Andafter massive failures at June 4, only one dump has been in progress atthe same time. So at the current speed it will take several months tocome thru all dumps.Is it possible to speed up the process again using several dumpprocesses at the same time?Thank you,Byrial
3 2
0 0
User-Agent:
by Domas Mituzas 17 Apr '25

17 Apr '25
Hi!from now on specific per-bot/per-software/per-client User-Agent header is mandatory for contacting Wikimedia sites.Domas
19 61
0 0
EBNF grammar project status?
by Steve Bennett 01 Apr '25

01 Apr '25
What's the status of the project to create a grammar for Wikitext in EBNF?There are two pages:http://meta.wikimedia.org/wiki/Wikitext_Metasyntaxhttp://www.mediawiki.org/wiki/Markup_specNothing seems to have happened since January this year. Also the comments onthe latter page seem to indicate a lack of clear goal: is this just a funproject, is it to improve the existing parser, or is it to facilititate anew parser? It's obviously a lot of work, so it needs to be of clearbenefit.Brion requested the grammar IIRC (and there's a comment to that effect athttp://bugzilla.wikimedia.org/show_bug.cgi?id=7), so I'm wondering what became of it.Is there still a goal of replacing the parser? Or is there some alternativeplan?Steve
26 217
0 0
Missing Section Headings
by Marc Riddell 13 Sep '24

13 Sep '24
Hello,I have been a WP editor since 2006. I hope you can help me. For some reasonI no longer have Section Heading titles showing in the Articles. This istrue of all Headings including the one that carries the Article subject'sname. When there is a Table of Contents, it appears fine and, when I clickon a particular Section, it goes to that Section, but all that is there is astraight line separating the Sections. There is also no button to edit aSection. If I edit the page and remove the "== ==" markers from the SectionTitles, the Title then shows up, but not as a Section Heading. Also, I don'thave any Date separators on my Want List. This started 2 days ago. Anythoughts?Thanks,Marc Riddell[[User:Michael David]]
10 11
0 0
I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here.tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.)(Is there a place onmw.org to put this tidbit on?)------- Forwarded message -------From: "Brian Levine" <support(a)github.com> (GitHub Staff)To: matma.rex(a)gmail.comCc:Subject: Re: Commits in mirrored repositories not showing up on my profileDate: Tue, 09 Jul 2013 06:47:19 +0200Hi BartoszIn order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit.The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits.CheersBrian-- Matma Rex
3 3
0 0
MediaWiki 1.19.0beta2
by Sam Reed 09 May '14

09 May '14
I'm happy to announce the availability of the second beta release of thenew MediaWiki 1.19 release series.Please try it out and let us know what you think. Don't run it on anywikis that you really care about, unless you are both very brave andvery confident in your MediaWiki administration skills.MediaWiki 1.19 is a large release that contains many new features andbug fixes. This is a summary of the major changes of interest to users.You can consult the RELEASE-NOTES-1.19 file for the full list of changesin this version.Five security issues were discovered.It was discovered that the api had a cross-site request forgery (CSRF)vulnerability in the block/unblock modules. It was possible for a useraccount with the block privileges to block or unblock another user withoutproviding a token.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=34212It was discovered that the resource loader can leak certain kinds of privatedata across domain origin boundaries, by providing the data as an executableJavaScript file. In MediaWiki 1.18 and later, this includes the leaking ofCSRFprotection tokens. This allows compromise of the wiki's user accounts, saybychanging the user's email address and then requesting a password reset.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=34907Jan Schejbal ofHatforce.com discovered a cross-site request forgery (CSRF)vulnerability in Special:Upload. Modern browsers (since at least as early asDecember 2010) are able to post file uploads without user interaction,violating previous security assumptions within MediaWiki. Depending on the wiki's configuration, this vulnerability could lead tofurthercompromise, especially on private wikis where the set of allowed file typesisbroader than on public wikis. Note that CSRF allows compromise of a wikifroman external website even if the wiki is behind a firewall.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=35317George Argyros and Aggelos Kiayias reported that the method used to generatepassword reset tokens is not sufficiently secure. Instead we use variousmoresecure random number generators, depending on what is available on theplatform. Windows users are strongly advised to install either the opensslextension or the mcrypt extension for PHP so that MediaWiki can takeadvantageof the cryptographic random number facility provided by Windows.Any extension developers using mt_rand() to generate random numbers incontextswhere security is required are encouraged to instead make use of theMWCryptRand class introduced with this release.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=35078A long-standing bug in the wikitext parser (bug 22555) was discovered tohavesecurity implications. In the presence of the popular CharInsert extension,itleads to cross-site scripting (XSS). XSS may be possible with otherextensionsor perhaps even the MediaWiki core alone, although this is not confirmed atthis time. A denial-of-service attack (infinite loop) is also possibleregardless of configuration.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=35315********************************************************************* What's new?*********************************************************************MediaWiki 1.19 brings the usual host of various bugfixes and new features.Comprehensive list of what's new is in the release notes.* Bumped MySQL version requirement to 5.0.2.* Disable the partial HTML and MathML rendering options for Math, and render as PNG by default. * MathML mode was so incomplete most people thought it simply didn't work.* New skins/common/*.css files usable by skins instead of having to copypiles of generic styles from MonoBook or Vector's css.* The default user signature now contains a talk link in addition to theuser link.* Searching blocked usernames in block log is now clearer.* Better timezone recognition in user preferences.* Extensions can now participate in the extraction of titles from URL paths.* The command-line installer supports various RDBMSes better.* The interwiki links table can now be accessed also when the interwikicache is used (used in the API and the Interwiki extension).Internationalization- --------------------* More gender support (for instance in user lists).* Add languages: Canadian English.* Language converter improved, e.g. it now works depending on the page content language.* Time and number-formatting magic words also now depend on the page content language.* Bidirectional support further improved after 1.18.Release notes- -------------Full release notes:https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob_plain;f=RELEASE-NOTES-1.19;hb=1.19.0beta2https://www.mediawiki.org/wiki/Release_notes/1.19Co-inciding with these security releases, the MediaWiki source coderepository hasmoved from SVN (athttps://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3)to Git (https://gerrit.wikimedia.org/gitweb/mediawiki/core.git). So therelevantcommits for these releases will not be appearing in our SVN repository. Ifyou useSVN checkouts of MediaWiki for version control, you need to migrate these toGit.If you up are using tarballs, there should be no change in the process foryou.Please note that any WMF-deployed extensions have also been migrated to Gitalso, along with some other non WMF-maintained ones.Please bear with us, some of the Git related links for this release may notwork instantly,but should later on.To do a simple Git clone, the command is:git clonehttps://gerrit.wikimedia.org/r/p/mediawiki/core.gitMore information is available athttps://www.mediawiki.org/wiki/GitFor more help, please visit the #mediawiki IRC channel onfreenode.netirc://irc.freenode.net/mediawiki or email The MediaWiki-l mailing listat mediawiki-l(a)lists.wikimedia.org.**********************************************************************Download:http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.tar.gzPatch to previous version (1.19.0beta1), without interface text:http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.patch.gzInterface text changes:http://download.wikimedia.org/mediawiki/1.19/mediawiki-i18n-1.19.0beta2.patch.gzGPG signatures:http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.patch.gz.sighttp://download.wikimedia.org/mediawiki/1.19/mediawiki-i18n-1.19.0beta2.patch.gz.sigPublic keys:https://secure.wikimedia.org/keys.html
5 5
0 0
On Sun, Aug 25, 2013 at 7:46 PM, Yuvi Panda <yuvipanda(a)gmail.com> wrote:> Hey rupert!>> On Sun, Aug 25, 2013 at 10:21 PM, rupert THURNER> <rupert.thurner(a)gmail.com> wrote:>> hi brion,>>>> thank you so much for that! where is the source code? i tried to>> search for "commons" onhttps://git.wikimedia.org/. i wanted to look>> Android:https://git.wikimedia.org/summary/apps%2Fandroid%2Fcommons.git> iOS:github.com/wikimedia/Commons-iOS>>> if there is really no account creation at the login screen or it is>> just my phone which does not display one, and which URL the aplication>> Mediawiki doesn't have API support for creating accounts, and hence> the apps don't have create account support yet.createdhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53328, maybeyou could detail a little bit more how this api should look like?rupert.
4 8
0 0

28 Jan '14
Hello all,I’m delighted to announce that Ken Snider is joining the Wikimediaoperations team. He will start as an international contractor workingremotely from Toronto, Canada on June 10, and will be visiting SF inthe week of June 17. We’re currently in the process of seeking workauthorization in the United States in the Director of TechOpsposition.CT has graciously agreed to support the ops leadership transitionfull-time through June, and part-time through July. We’ll be startingthe handover while Ken is working remotely.A bit more about Ken: Ken was apparently genetically predisposed tobecome a sysadmin since he joined one of Canada’s first large ISPs,Primus, straight out of school in 1997 and helped build theirinfrastructure til 2001. He then joined a startup called OpenCOLA in2001 which was co-founded by Cory Doctorow and developed early P2Pprecursors to tools like BitTorrent and Steam. It’s best known todayfor the development of an open source (GPL’d) cola recipe which isstill in use (more than 150,000 cans sold if Wikipedia is to bebelieved).Ken got involved in one of Cory’s pet projects,BoingBoing.net whichsome of you may have heard of ;-), and has been their sysadmin since2003. After a stint from 2001-2005 at DataWire, Ken became Director ofTech Ops at Federated Media, a role he held from 2005-2012.Federated Media is an ad network that was founded to support hightraffic blogs and sites that want to stay independent of largepublishers, with a network that supports more than 1B requests/day.One of the unusual challenges at FM was that the company grew throughacquisitions of various blogging and publishing networks. This led tothe challenge of integrating very heterogeneous operations andengineering infrastructure, including multiple geographicallydistributed ops teams and data-center locations. As DTO, Ken led theseefforts, such as OS standardization, development of a unifieddeployment infrastructure, etc. Ken also ensured that the operationsgroup partnered effectively with the various engineering teamsdeveloping site features and enhancements.I want to again take this opportunity to thank CT Woo for his tirelessoperations leadership since December 2010. I’d also like to thankeveryone who’s participated in the Director of TechOps search process.Please join me in welcoming Ken to the Wikimedia Foundation and thecommunity. :-)All best,Erik--Erik MöllerVP of Engineering and Product Development, Wikimedia Foundation
4 4
0 0
!ask
by Ori Livneh 24 Jan '14

24 Jan '14
Can we deprecate usage of '!ask' on IRC?> ori-l: !ask> wm-bot: Hi, how can we help you? Just ask your question.It's annoying when people ask to ask, but the people who do so do it out ofinsecurity or lack of experience, and so they're the last people we shouldbe siccing our bots on.I've used '!ask' a lot before but I'm going to stop. I hope others do thesame.
9 10
0 0
migrating hooks doc to doxygen?
by Antoine Musso 13 Nov '13

13 Nov '13
Hello,Since we introduced hooks in MediaWiki, the documentation has beenmaintained in a flat file /docs/hooks.txt . Over the week-end I haveconverted the content of that file to let Doxygen recognize it.The patchset is:https://gerrit.wikimedia.org/r/#/c/66128/I have used that patch to generate a temporary documentation. That letseveryone browse the result easily. The produced result is:A landing page:https://doc.wikimedia.org/mw-hooks/hooks_mainpage.htmlThe doc overview:https://doc.wikimedia.org/mw-hooks/page_hooks_documentation.htmlA list of hooks with their documentation:https://doc.wikimedia.org/mw-hooks/page_hooks_list.htmlI think that makes it a bit more accessible to everyone and Doxygenautolink to referenced classes.Some issues I have: - the hooks are listed alphabetically when they could be regrouped bytheme (like API, SpecialPages, HTML Forms ...). - The hooks are documented in a separate file (still docs/hooks.txt),when we might want to have the doc near the wfRunHooks() call.Thoughts ?-- Antoine "hashar" Musso
13 17
0 0
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp