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-lMay 2014

wikitech-l@lists.wikimedia.org
  • 132 participants
  • 141 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
New RFC: better JS minification
by Max Semenik 01 Nov '15

01 Nov '15
Hi, I'd like to present a new RFC for your consideration:https://www.mediawiki.org/wiki/Requests_for_comment/MinifierIt is about how we can shave 10-15% off the size if JavaScriptdelivered to users.Your comments are highly welcome!:)-- Best regards, Max Semenik ([[User:MaxSem]])
9 12
0 0

25 May '15
Thank you for the quick fix!Best,--SukyoungOn Jan 29, 2014, at 9:55 AM, Nathan wrote:> FYI in case you aren't subscribed to the list. > > ---------- Forwarded message ----------> From: Yair Rand <yyairrand(a)gmail.com>> Date: Tue, Jan 28, 2014 at 7:25 PM> Subject: Re: [Wikitech-l] Bug in the Wikipedia main web page> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>> > > Thank you for pointing out this bug. Your suggested change to> MediaWiki:Gadget-wm-portal.js has been implemented by Meta-Wiki> administrator User:PiRSquared17.> > > On Tue, Jan 28, 2014 at 6:50 PM, Sukyoung Ryu <sukyoung.ryu(a)gmail.com>wrote:> > > Dear all,> >> > We are researchers at KAIST in Korea working on finding JavaScript bugs in> > web pages. While analyzing top websites fromAlexa.com, we found an issue,> > which seems to be a bug, on the Wikipedia main web page (wikipedia.org).> > We would be grateful if you can either confirm that it is a bug and even> > better fix it or let us know what we're missing.> >> > Here's the issue. When a user selects a language in which search results> > are displayed via the language selection button from the Wikipedia main web> > page, the following JavaScript function is executed:> >> > 1 function setLang(lang) {> > 2 var uiLang = navigator.language || navigator.userLanguage, date> > = new Date();> > 3> > 4 if (uiLang.match(/^\w+/) === lang) {> > 5 date.setTime(date.getTime() - 1);> > 6 } else {> > 7 date.setFullYear(date.getFullYear() + 1);> > 8 }> > 9> > 10 document.cookie = "searchLang=" + lang + ";expires=" +> > date.toUTCString() + ";domain=" + location.host + ";";> > 11 }> >> > Depending on the evaluation result of the conditional expression on line> > 4, "uiLang.match(/^\w+/) === lang", the function leaves or dose not leave> > the selected language information on the user's computer through a cookie.> > But we found that the expression, "uiLang.match(/^\w+/) === lang", always> > evaluates to false, which results in that the function always leaves> > cookies on users' computers. We think that changing the contidional> > expression, "uiLang.match(/^\w+/) === lang", to the expression,> > "uiLang.match(/^\w+/) == lang", will solve the problem.> >> > This problem may occur in the main web pages of all the Wikimedia sites.> > Could you kindly let us know what you think? Thank you in advance.> >> > Best,> > Changhee Park and Sukyoung Ryu> >> >> > _______________________________________________> > Wikitech-l mailing list> > Wikitech-l(a)lists.wikimedia.org> >https://lists.wikimedia.org/mailman/listinfo/wikitech-l> _______________________________________________> Wikitech-l mailing list> Wikitech-l(a)lists.wikimedia.org>https://lists.wikimedia.org/mailman/listinfo/wikitech-l>
3 3
0 0

02 Dec '14
Hey all,TL;DR: jQuery will soon be upgraded from v1.8.3 to v1.11.x (the latest). Thismajor release removes deprecated functionality. Please migrate away from thisdeprecated functionality as soon as possible.It's been a long time coming but we're now finally upgrading the jQuery packagethat ships with MediaWiki.We used to regularly upgrade jQuery in the past, but got stuck at v1.8 a coupleof years ago due to lack of time and concern about disruption. Because of this,many developers have needed to work around bugs that were already fixed in laterversions of jQuery. Thankfully, jQuery v1.9 (and its v2 counterpart) has beenthe first release in jQuery history that needed an upgrade guide[1][2]. It's amajor release that cleans up deprecated and dubious functionality.Migration of existing code in extensions, gadgets, and user & site scriptsshould be trivial (swapping one method for another, maybe with a slight changeto the parameters passed). This is all documented in the upgrade guide[1][2].The upgrade guide may look scary (as it lists many of your favourite methods),but they are mostly just addressing edge cases.== Call to action ==This is a call for you, to:1) Get familiar withhttp://jquery.com/upgrade-guide/1.9/.2) Start migrating your code.jQuery v1.9 is about removing deprecated functionality. The new functionality isalready present in jQuery 1.8 or, in some cases, earlier.3) Look out for deprecation warnings.Once instrumentation has begun, using "?debug=true" will log jQuery deprecationwarnings to the console. Look for ones marked "JQMIGRATE" [7]. You might alsofind deprecation notices from mediawiki.js, for more about those see the mailfrom last October [8].== Plan ==1) Instrumentation and loggingThe first phase is to instrument jQuery to work out all the areas which willneed work. I have started work on loading jQuery Migrate alongside the currentversion of jQuery. I expect that to land in master this week [6], and roll out onWikimedia wikis the week after. This will enable you to detect usage of mostdeprecated functionality through your browser console. Don't forget the upgradeguide[1], as Migrate cannot detect everything.2) Upgrade and MigrateAfter this, the actual upgrade will take place, whilst Migrate stays. Thisshould not break anything since Migrate covers almost all functionality thatwill be removed. The instrumentation and logging will remain during this phase;the only effective change at this point is whatever jQuery didn't think wasworth covering in Migrate or were just one of many bug fixes.3) Finalise upgradeFinally, we will remove the migration plugin (both the Migrate compatibilitylayer and its instrumentation). This will bring us to a clean version of latestjQuery v1.x without compatibility hacks.A rough timeline:* 12 May 2014 (1.24wmf4 [9]): Phase 1 – Instrumentation and logging starts. This will run for 4 weeks (until June 9).* 19 May 2014 (1.24wmf5): Phase 2 – "Upgrade and Migrate". This will run for 3 weeks (upto June 9). The instrumentation continues during this period.* 1 June 2014 (1.24wmf7) Finalise upgrade.== FAQ ==Q: The upgrade guide is for jQuery v1.9, what about jQuery v1.10 and v1.11?A: Those are regular updates that only fix bugs and/or introduce non-breakingenhancements. Like jQuery v1.7 and v1.8, we can upgrade to those without anyhassle. We'll be fast-forwarding straight from v1.8 to v1.11.Q: What about the jQuery Migrate plugin?A: jQuery developed a plugin that adds back some of the removed features (notall, consult the upgrade guide[2] for details). It also logs usage of these tothe console.Q: When will the upgrade happen?A: In the next few weeks, once we are happy that the impact is reasonably low.An update will be sent to wikitech-l just before this is done as a final reminder.This will be well before the MediaWiki 1.24 branch point for extension authorslooking to maintain compatibility.Q: When are we moving to jQuery v2.x?A: We are not currently planing to do this. Despite the name, jQuery v2.xdoesn't contain any new features compared to jQuery v1 [3]. The main differenceis in the reduced support for different browsers and environments; mostnoticeably, jQuery 2.x drops support for Internet Explorer 8 and below, whichMediaWiki is still supporting for now, and is outside the scope of this work.Both v1 and v2 continue to enjoy simultaneous releases for bug fixes and newfeatures. For example, jQuery released v1.11 and v2.1 together[4][5].-- Krinkle[1]http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-final-released/[2]http://jquery.com/upgrade-guide/1.9/[3]http://blog.jquery.com/2013/04/18/jquery-2-0-released/[4]http://blog.jquery.com/2014/01/24/jquery-1-11-and-2-1-released/[5]http://blog.jquery.com/2013/05/24/jquery-1-10-0-and-2-0-1-released/[6]https://gerrit.wikimedia.org/r/131494[7]https://github.com/jquery/jquery-migrate/blob/master/warnings.md[8]http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg72198.html[9]https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap
6 14
0 0
Are you good in swearing? WE NEED YOUHuggle 3 comes with vandalism-prediction as it is precaching the diffseven before they are enqueued including their contents. Each edit hasso called "score" which is a numerical value that if higher, the editis more likely a vandalism.If you want to help us improve this feature, it is necessary to definea "score words" list for every wiki where huggle is about to be used,for example on English wiki.Each list has following syntax:(seehttps://en.wikipedia.org/w/index.php?title=Wikipedia:Huggle/Config&diff=573…)score-words(score): list of words separated by comma, can contain newlines but commamust be presentexamplescore-words(200): these, are, some, words, which, presence, of, increases, the, score, each, word, by, 200,So, if you know english better than me, which you likely do, go aheadand improve the configuration file there, no worries, huggle's configparser is very syntax-error proof.If you have any other suggestion how to improve huggle's prediction,go ahead and tell us!
8 8
0 0

17 Aug '14
I just love this Google I/O 2013 talk on human perception andcognition, and its implications for interactive and visual design. Itis accessible, but with a lot of information and applies very well tous I think.I'm sure that many designers know all about this and some haveprobably seen the clip before, but it is also very good fordevelopers, because many of these things we know subconsciously, butit's not really part of our vocabulary.https://www.youtube.com/watch?v=z2exxj4COhUDJ
3 2
0 0
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp