Wikitech-l April 2013

wikitech-l@lists.wikimedia.org

174 participants
209 discussions

Fwd: MobileFrontend Autodetection on Third party wikis
by Yuvi Panda 17 Apr '13

17 Apr '13

FYI ---------- Forwarded message ---------- From: Jon Robson <jrobson(a)wikimedia.org> Date: Tue, Apr 16, 2013 at 11:53 PM Subject: [WikimediaMobile] Fwd: MobileFrontend bug 45622 To: mobile-l <mobile-l(a)lists.wikimedia.org> I just received this mail from a user: "...I upgraded to Mediawiki 1.20 on me dev machine, and things seem to work fine. However using MF for MW 1.20 has no auto-detect, so it's not very useful to me :) Is there any chance you fix this on the master version as well (which has built it auto-detect)?" It seems various other people are being confused with how mobile detection works [1], myself included so I have setup this basic stub of a page [2] to hopefully document this. Please share your knowledge here! [1] http://www.mediawiki.org/w/index.php?title=Extension_talk:MobileFrontend&of… [2] http://www.mediawiki.org/wiki/Extension:MobileFrontend/Configuring_Browser_… On Wed, Apr 3, 2013 at 8:34 PM, Jon Robson <jrobson(a)wikimedia.org> wrote: > Eek. I'm afraid getting this to work on an older MediaWiki/MobileFrontend > extension is extremely problematic. So much has changed both in core and the > MobileFrontend extension to this.... > > Are you sure migrating your wiki will be as problematic as you suspect? > > Best wishes and sorry to the be the bearer of bad news!! > Jon > > > On Tue, Apr 2, 2013 at 6:50 AM, ויקיפועל <wikipoel(a)gmail.com> wrote: >> >> Hi, thank you for fixing this bug I opened. I appreciate it. However >> I'm using MW 1.18 and an older version of MobileFrontend without >> skins. I know it's a lot to ask for, but perhaps you'd be willing to >> see if such a small fix can also be applied for older versions of the >> extension? >> Migrating my entire wiki to 1.20 just for this is problematic >> >> Thank you >> >> >> https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/MobileFrontend… > > _______________________________________________ Mobile-l mailing list Mobile-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l -- Yuvi Panda T http://yuvi.in/blog

1 0

Project proposal for GSOC 2013
by Gaurav Chawla 16 Apr '13

16 Apr '13

Hi, I am Gaurav Chawla (again :P). I will be applying for this year's GSOC. I have drafted a project proposal on my user page - http://www.mediawiki.org/wiki/User:Grv99. The project aims to develop jQuery.IME extensions for Firefox and Chrome ( https://bugzilla.wikimedia.org/show_bug.cgi?id=46647) I request you to go through it and give your feedbacks and/or suggestions for addition of more features, or any amendments required. Hoping for a good response. Thankyou. PS: If you are thinking about my previous proposal (Wikicards - http://www.mediawiki.org/wiki/User:Grv99/Wikicards), I have dropped it as an application to this year's GSOC. But, I am glad to inform you, that I had already started working on it (with some less functionality), and its a work in progress. I will soon be uploading the source on github (blame classwork project submissions for the delays :P) and will provide the link to it here on wikitech-l. Also, I would like to work with wikidata team, if possible, for the same after the GSOC. Thanks for the feedback, you gave for wikicards. It helped me a lot. Regards Gaurav

1 0

Advice for an interlang anotation extension tool?
by Mathieu Stumpf 16 Apr '13

16 Apr '13

Hello, This night as was thinking about some tools which may be useful to help me improve some wikipedia article. Lately I began to participate in a discussion aiming to improve the french "philosophie" article plan[1]. So to achieve our goal, I began to look at how other chapters use it, to establish a differential overview, and hopefuly produce a better plan than what the current french article provide. In this project, I've been helped by the fact that interlang links come with a star when the article was elected "featured article". Of course I don't speak all this languages, but translation software are often enough for my purpose of comparating tables of content. Now I think that would be intereting to have: * an opt-in feature to display more information along interlang links, like size (in octet or number of symbols), view count, edit count, etc. * a tool which gather article plans of (selected) interlang relative articles, auto-translate them to a target language and display the result. You may look at [2] to get an idea of what the result of such a tool may look like (but design brain storm is welcome), although I didn't performed translations yet. So I post here so I may have some critical feedback, and hint on which way would probably make more sense to implement this tools. As I see it, I have now three (non-exclusive) way to develop something which integrate in the mediawiki ecosystem: php extension, javascript gadget, lua template. Thank you in advance for your comments. [1] https://fr.wikipedia.org/wiki/Philosophie Which is about philosophy, you wouldn't have guess, would you? [2] https://fr.wikipedia.org/wiki/Discussion:Philosophie#Plans_utilis.C3.A9s_su… -- Association Culture-Libre http://www.culture-libre.org/

2 1

What needs fixing re LevelUp; complain till Apr 16
by Sumana Harihareswara 16 Apr '13

16 Apr '13

Once upon a time there was 20% time, which had various problems and we thus ended[0] and turned into LevelUp[1]. The point is to increase our capacity to do engineering, broadly defined. LevelUp has had various problems and so I have some ideas about what to do next, but I want to open a bit of discussion first to make sure I'm getting the problems right. I'll wind up this discussion late on Tuesday the 16th, I hope, and get the new programs in motion by the end of that week. Problems/unmet needs: a. People in our technical community (volunteers, WMF, WMDE, and others) want to be more effective but aren't consistently getting what they need. Sometimes that's code/design review, sometimes that's looking over someone's shoulder to learn by example, sometimes it's tutoring, sometimes it's a project guided to completion, sometimes it's simply learning what resources, guidelines, and tools are available, and sometimes it's HOWTOs, reference guides, inventories, and directories. We get glimpses of this when I ask what people want to learn; see [0] and the 2013 Jan-March LevelUp signups[2]. Different people learn in different ways[3] so there is no one-size-fits-all solution. b. Code review backlog. Per (a) this is keeping tech contributors from learning -- it's also important that it keeps improvements from reaching users. And it's just dispiriting; the number of unresolved commits in mediawiki/* has gone from ~360 to ~815 in the last 6 months[4][5], and most of the "can we deploy this?" queues haven't moved in a few months.[6][7] c. Some people say they want to mentor or be mentored but then do not perform teaching or learning activities unless a meta-mentor prods them several times a month, or do not set reasonable goals. The plan for LevelUp was that people's managers would check on progress. Thus LevelUp in the most recent round did not lead to most participants meeting their goals. OPW and to a lesser extent GSoC and UCOSP seem to work partly because there's a pre-qualification process including goal-setting, partly because the student and mentor strongly commit to carving out time, and partly because my team does strong hands-on meta-mentorship. d. Some WMF engineering contributors want to help increase our community's capacity via individual mentoring or learning. Some want to just review code and design. Some want to create and lead teaching sessions. Some feel as though they haven't been allotted the time to do any of this kind of work. e. Related to (a) and (d), we have frustrating bottlenecks in our capacity for some key engineering activities, *especially* user experience design, community liaising, performance, front-end (especially JS) coding and review, ResourceLoader, and operations work. These affect everyone but hit volunteers disproportionately. f. I have to rename LevelUp because of the name conflict with some company. I can come up with a suitable name for whatever the next thing is, don't worry, no bikeshedding necessary here, but I just wanted to mention it.[8] Do these seem like the right problems to address in trying to build our community's capacity for technical contributions? Was there anything you liked about 20% time or LevelUp that you want to retain? I am especially interested in what you have to say if you rarely speak up on this list, and it is okay to email me off-list. [0] http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064615.html [1] https://www.mediawiki.org/wiki/Mentorship_programs/LevelUp [2] https://www.mediawiki.org/wiki/Mentorship_programs/LevelUp/Q1_2013 [3] https://blogs.msdn.com/b/susantodd/archive/2011/05/06/quot-people-in-contex… [4] https://blog.wikimedia.org/2012/10/03/engineering-september-2012-report/ [5] https://blog.wikimedia.org/2013/04/04/engineering-march-2013-report/ [6] https://www.mediawiki.org/wiki/Review_queue#Extensions [7] https://www.mediawiki.org/wiki/User_experience_review_queue [8] "I feel that solving a problem is more interesting than finding a name for the solution. I realize that I stand in the minority of the open source community on this." -Kevin Maples -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation P.S. We do have twelve non-WMF core maintainers of MediaWiki right now, compared to nearly none a year ago at this time. And per https://wikitech.wikimedia.org/wiki/Deployments#Near_Term we're scheduling some volunteer-written extensions for deployment in the next few months. And I think OPW went pretty well in helping new folks achieve stuff. We do have some successes. But we can do better. P.P.S. Sorry for the length. /me offers a stroopwafel of penance

2 1

emails in html or in nicely formatted plain text?
by Yury Katkov 16 Apr '13

16 Apr '13

Hi everyone! Is there a way to configure email notifications and emails so that the users of the wiki receive emails in html format? Or in text format without wiki-markup. I haven't found any extension that can do that. Cheers, ----- Yury Katkov, WikiVote

2 1

Wikivoyage and Universal Language Selector
by roger＠rogerchrisman.com 16 Apr '13

16 Apr '13

Hi, What is the best way to install, modify and configure the Universal Language Selector extension so that I can see how it might work with Wikivoyage? I created an account at https://wikitech.wikimedia.org/wiki/User:Rogerhc but it is not clear to me what my next step should be towards above stated objective. Could someone with clue please nudge me in the right direction? Thanks! Roger http://meta.wikimedia.org/wiki/User:Rogerhc

2 1

Database Maintenance - Wednesday April 17th @ 18:00 UTC
by Greg Grossmeier 16 Apr '13

16 Apr '13

There is scheduled database maintenance on Wednesday April 17th from 18:00 - 20:00 UTC (11am - 1pm Pacific) for Wikidata and the English and German Wikipedias. During this window there may be brief (30 seconds - 2 minutes) moments where affected wikis are read-only. The purpose for the maintenance is to update our "master" database servers for those wikis to MariaDB (https://mariadb.org/). This is part of our on-going migration to MariaDB from MySQL at the Wikimedia Foundation (blog post forth-coming!). Please report any issues after 20:00 UTC/1pm Pacific to #wikimedia-operations or https://bugzilla.wikimedia.org/ (see this[1] page for tips on reporting bugs). Best, Greg [1] https://blog.wikimedia.org/2013/03/18/how-to-create-a-good-first-bug-report/ -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

1 0

MediaWiki Security Release: 1.20.4 and 1.19.5
by Chris Steipp 16 Apr '13

16 Apr '13

I would like to announce the release of MediaWiki 1.20.4 and 1.19.5. These releases fix 3 security related bugs that could affect users of MediaWiki. Download links are given at the end of this email. * An internal review discovered that specially crafted Lua function names could lead to XSS. <https://bugzilla.wikimedia.org/show_bug.cgi?id=46084> * Daniel Franke reported that during SVG parsing, MediaWiki failed to prevent XML external entity (XXE) processing. This could lead to local file disclosure, or potentially remote command execution in environments that have enabled expect:// handling. <https://bugzilla.wikimedia.org/show_bug.cgi?id=46859> * Internal review also discovered that Special:Import, and Extension:RSS failed to prevent XML external entity (XXE) processing. <https://bugzilla.wikimedia.org/show_bug.cgi?id=47251> Full release notes for 1.20.4: <https://www.mediawiki.org/wiki/Release_notes/1.20> Full release notes for 1.19.5: <https://www.mediawiki.org/wiki/Release_notes/1.19> For information about how to upgrade, see <https://www.mediawiki.org/wiki/Manual:Upgrading> ********************************************************************** 1.20.4 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.20/mediawiki-1.20.4.tar.gz Patch to previous version (1.20.3): http://download.wikimedia.org/mediawiki/1.20/mediawiki-1.20.4.patch.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.20/mediawiki-1.20.4.tar.gz.sig http://download.wikimedia.org/mediawiki/1.20/mediawiki-1.20.4.patch.gz.sig Public keys: https://secure.wikimedia.org/keys.html ********************************************************************** 1.19.5 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.5.tar.gz Patch to previous version (1.19.4): http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.5.patch.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.5.tar.gz.sig http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.5.patch.gz.sig Public keys: https://secure.wikimedia.org/keys.html ********************************************************************** Extension:RSS ********************************************************************** Information and Download: https://www.mediawiki.org/wiki/Extension:RSS

1 0

Pushing Technical changes to Wikimedia projects
by Denny Vrandečić 16 Apr '13

16 Apr '13

Technical changes on the Wikimedia projects can be hairy. We are currently having a discussion about the Wikidata deployment to the Wikipedias, and there have been many examples in the past of deployments that raised discussions. One of my statements in this discussion is that the a priori discussion of such features is highly undemocratic. What I mean with that is that design and deployment decisions are often made by a very small group, which are in the best case a part of the affected community, but, in many cases, even external to the affected community. So the decisions are made by a group that does not represent or is constituted by the community - which I mean with undemocratic. This has repeatedly raised criticism. And I think that criticism is often unfair. Additionally, it is usually true (which makes is not anymore fair, though). I thought that in order to discuss these design decisions with the community before hand, telling them on their respective village pump is sufficient. Not so it seems. No single channel would find acceptance to communicate with the community. This, obviously means, that it is not actionable to communicate with the community. What about setting up a community selected body of representatives to discuss such issues beforehand? At first, it sounds like a good idea - but the issue is, it makes the process only more complicated without at all resolving the underlying issues. Does anyone really think that such a body would stop the criticism before or after the deployment of the change in question? Yeah, right. Doesn't change a thing. So, what do I want to achieve with this Mail? Merely to ask some community members to be a bit more constructive in their comments. Claiming that the product managers and designers have no idea of the Wikimedia communities and the use of wikis is often neither help- nor truthful. What would be even better would be to come up with processes or mechanisms to avoid these issues in the future. I would be very glad if the people who are often critically accompanying such changes would help in building effective channels for their discussion. Any thoughts? -- Project director Wikidata Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin Tel. +49-30-219 158 26-0 | http://wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

9 12

Gadget-Reviews
by Lukas Benedix 15 Apr '13

15 Apr '13

Hi, Is there any written policy about the review-process for Gadgets? For Extensions I found a document, that says an Extension should: get a design review, be internationalized, get a code review and finally get a deployment review. [https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment] I can't find any rules like this for Gadgets, but I see lot's of Gadgets set default in several Wikis. I think Gadgets can be designed badly and have security flaws as well as Extensions… so there shouldn't there exists some review process? best regards, Lukas

5 6

← Newer
1
...
11
12
13
14
15
16
17
...
21
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l April 2013