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-lDecember 2023

wikitech-l@lists.wikimedia.org
  • 50 participants
  • 44 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

17 Apr '25
Hoi,This is an inquiry from my friend in academia, researching about Wikipedia.He would like to know whether there's a way to acquire a list of templatesincluding external links. Here are some examples including external links.https://ja.wikipedia.org/wiki/Template:JOI/dochttps://ja.wikipedia.org/wiki/Template:Twitter/docSuch links are stored in externallinks.sql.gz, in an expanded form.When you want to check increase/decrease of linked domains in chronologicalorder through edit history, you have to check pages-meta-history1.xml etc.In a such case, traditional links and links by templates are mixed,Therefore, the latter ones (links by templates) should be expanded totraditional link forms.Sorry if what I am saying does not make sense.Thanks in advance,--Takashi Ota [[U:Takot]]
13 24
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

25 Mar '25
Do your eyes glaze over when trying to make sense of Phabricator tasks with a long and troubled history of patches? Do you struggle to find the real people in the sea of automated bot comments?I've made myself a user style to compact the Gerritbot comments on Phabricator. You might like it too:https://userstyles.world/style/13140/wikimedia-phabricator-reduce-gerritbot…(See screenshots and installation instructions there.)-- Bartosz Dziewoński
8 12
0 0
Phabricator upstream shutdown
by Brian Wolff 21 Mar '25

21 Mar '25
It sounds like phabricator upstream is going away:https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_op…Just curious, are we planning to continue using it long term or move tosomething else?--Brian
10 12
0 0
Changes to JavaScript documentation tools
by Alexandra Paskulin 13 Nov '24

13 Nov '24
Hi everyone,tl;dr The tools we use to document Wikimedia JavaScript code are changing.In the short term, you can read the complete MediaWiki core JavaScript docsusing the 1.41 version[0] while we migrate to the new system[1]. If you useJavaScript documentation ondoc.wikimedia.org, please share your feedbackon wiki[2].Wikimedia JavaScript codebases are switching from using JSDuck[3] toJSDoc[4] for documentation. Started in 2016, this migration is necessarybecause JSDuck is currently unmaintained and does not support the ES6standard[5]. Several Wikimedia JavaScript codebases, including Vector andGlobalWatchlist, already use JSDoc, while several others, such asVisualEditor and MediaWiki core, still use JSDuck.The migration project consists of two parts: changing the codebases tosupport JSDoc and improving the usability of the JSDoc WMF theme. For moreinformation, see phab:T138401[6].== Migrating MediaWiki core to JSDoc ==We are migrating MediaWiki core to JSDoc incrementally. While the migrationis in progress, the master branch docs will be incomplete, containing onlythose modules that have been migrated. To read the old JSDuck docs, see theMediaWiki 1.41 docs[0].To help with migration, choose a module from the list in phab:T352308[7],and follow the guide on phab:T138401[6] to translate the tags from JSDuckto JSDoc.== Migrating other codebases ==You can find a list of codebases that use JSDuck on phab:T138401[6].(Please add any that are missing.) To help migrate a codebase that usesJSDuck, follow the instructions to set up JSDoc[8], and use the guide inphab:T138401[6] to translate the tags from JSDuck to JSDoc.== Improving the JSDoc WMF theme ==One of the biggest differences between JSDuck and JSDoc is the HTMLinterface for reading the docs. The WMF theme for JSDoc is not asfull-featured as the JSDuck theme, but to support this migration, theWikimedia Foundation Web, Design Systems, and Technical Documentation teamsare working to prioritize and complete a set of improvements to the JSDoctheme, with the goal of releasing version 1 of jsdoc-wmf-theme in 2024.If you use JavaScript documentation ondoc.wikimedia.org, please leave acomment on the JSDoc WMF theme talk page[2] and let us know how you use thedocs and which features of the theme are the most important to you.Thank you for reading!Alex, Kamil, Jon, Roan, and Anne[0]:https://doc.wikimedia.org/mediawiki-core/REL1_41/js/[1]:https://doc.wikimedia.org/mediawiki-core/master/js/[2]:https://www.mediawiki.org/wiki/Talk:JSDoc_WMF_theme[3]:https://github.com/senchalabs/jsduck[4]:https://en.wikipedia.org/wiki/JSDoc[5]https://en.wikipedia.org/wiki/ECMAScript[6]:https://phabricator.wikimedia.org/T138401[7]:https://phabricator.wikimedia.org/T352308[8]:https://www.mediawiki.org/wiki/JSDoc-- Alex PaskulinTechnical WriterWikimedia Foundation
1 2
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
Hi there,I'm User:Diskdance, and recently I'm developing a default gadget for Chinese Wikipedia enhancing MediaWiki's variant handling logic, and under certain circumstances a prompt is shown at page load asking for a user's preferred variant. Consider it as a conditional Cookie notice, and its English screenshot can be found athttps://commons.wikimedia.org/wiki/File:VariantAlly-En.png.Iknowthis can be very disruptive on UX, so I tend to be careful about its negative impact on page views. If the gadget can collect telemetry data about the prompt's display frequency and user interactions(using e.g. WikimediaEvents), I can know about its possible impact.Is this possible? It would be much appreciated if anybody could provide assistance.Best wishes,Diskdance
6 8
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
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp