Right now, in order to submit a diff, [[Git/Workflow]] suggests that you
get a Gerrit account before you clone. How do we enable much more casual
committers? I want experienced developers to be able to randomly fork
and request pulls without having to get an account. If the answer is
"for now, link to your fork in a Bugzilla comment and mark it 'patch'
'need-review'," that's adequate (because we let people get Bugzilla
accounts without waiting for a gatekeeper), but if there's a better way
I'd like to know it so I can update docs.
Also asked at
Volunteer Development Coordinator
During the triage yesterday, we sorted out the bugs marked as 1.19
regressions and scheduled them to be fixed before the roll outs on Monday
or Wednesday. Anyone who is interested in the results of the triage
should check the etherpad: http://etherpad.wikimedia.org/119triage
Today, a 1.19 regression with ProofreadPage was reported. Since we
didn't discuss this one yesterday, I'm going to post it here.
Side-by-side functionality broken in Chrome and possibly some Internet
Following the update to 1.19wmf1 English Wikisource has a break in
the side by side viewing of text and image. This basically prevents
all use of affected browsers from this functionality.
Mark A. Hershberger
can someone give me an idea, how I can determine a uploaded file's real path, when I only have the filename? I have written some code but there could also be a API call available.
Weberhofer GmbH, Austria, Vienna
Before the March 3rd migration of MediaWiki core + WMF-deployed
extensions to git, we want all MediaWiki developers to feel comfortable
with Git, git-review, and Gerrit. So I'm scheduling the first in some
one-hour interactive training sessions where you can learn the new
MediaWiki development workflow.
I can lead a couple of these on Monday and Tuesday, 27 and 28 February.
If you're interested, please mark down times that you're available in
I intend on running these sessions via Google+ Hangout (you don't have
to enable your webcam or audio) so you'll see my screen as I show you
the steps. If you prefer not to use G+, then please let me know and I'll
separately schedule some IRC trainings, or find another screensharing
While it's nice if you can come to a training, I aim to also make sure
comprehensive documentation is at
by sometime this Friday. And then, after I've gotten the ball rolling,
I hope other new experts will take the lead and start teaching.
Volunteer Development Coordinator
What: 1.19 bug triage
When: Friday, February, 21:00UTC
Time zone conversion: http://hexm.de/f2
Where: #wikimedia-dev on freenode
if you don't have an IRC client
We've found and fixed some really nasty bugs during the deployment of
MediaWiki 1.19 to some smaller wikis.
Right now, Bugzilla shows about 13 bugs that need to be fixed. You can
see these on the linked etherpad. Ideally, we'd get these all fixed
before our next deployment on Monday.
If you want to help, join us on IRC at the time above in #wikimedia-dev.
Mark A. Hershberger
Off the really great success of Wikipedia V1.0 for Android
(http://bit.ly/xvoPrR ) and its impressive roll out
(http://bit.ly/A5mva7) the mobile team is now moving full speed with
V1.1. We've already released an alpha and a beta, and today are
putting out another beta release.
For those that just want to get started you can download the new build
With V1.1 we've added :
- Integration with QuickSearch in Android
- Open Wikipedia links from other apps in the Wikipedia App (URL Intents)
- OpenStreetMaps replaced Google Maps for nearby view (using MapQuest tiles)
- Added Did You Mean? to search results
- Moved to jQuery off Zepto (mostly)
- Touching co-ordinates inside articles shows map overlay
- Full text search
- Added 'Clear History'
- Added 'Clear Saved Pages'
- Localized a few messages that were missing
- Enable app to be saved to SD card
- Major code-refactor, still needs more love :)
- Improved tablet experience
- Move to using Hogan.js for templating
- Fixed a lot of tiny bugs!
Since the last beta we've specifically done work on:
- Android 4.0 fixes for the Map
- Map usability fixes
- Fixes nearby me issues in non-english locales
- About page now lists contributors
Up-to-date changes can now be found at
We're targeting our betas as mostly feature complete and reasonably
stable, but in no way
100% bug free. We need you to tell us where the app is crashing,
misbehaving, and in general providing a poor user experience. Expect
that across our alpha, beta, release candidate cycle your
feedback can significantly alter the features that we've added.
Test this extensively and file bugs under
Hammer on these builds mercilessly so that we can get all the kinks
out before our next major market release.
Key points to test for this version
* Test the quick search box integration. Tap the 'G' to show all of
your data providers. Tap the config icon at the top right of the new
window. Scroll to the bottom of the 'Searchable items' menu and check
'Wikipedia' . Search for 'San Francisco' and/or any other term. Try
the same with multiple languages. You may have to turn off Web
searches until you train your phone to surface Wikipedia results more
* Open the native web browser. Load google.com. Search for 'San
Francisco'. Tap the result that points to our mobile site. The app
should pop up an intent menu. Choose 'Wikipedia' as the default app.
* Switch your phone to a language that is written Right to Left. Use
the application as you normally would, and report anything that is not
what you would expect. We now have nascent RTL UI support, and need
all the testing we can possibly get
* Tap near by in the App. Navigate around the map and select whatever
pins you might see. Tap a pin to go to the article detail page
* Search for 'Mumbai' in the App search bar. Go to the article. Scroll
to the bottom of the info box. Tap the GPS coordinate. You should then
see a map with geographically related articles
* Search for 'Charile Sava' in the App search bar. Note that no
relevant match shows up. Tap the magnifying glass to the a full text
search and note that 'Ann curtis' comes up
* Search for 'San Francisko' . Note that the app catches the
misspelling and offers up 'San Francisco' as a spelling correction.
Tap the spelling correction to go to the article
* In the app tap menu, history, and top right X button to clear your
* In the app tap menu, saved pages, and top right X button to clear
your saved pages
* Starting from the home screen tap menu, manage apps, scroll to
'Wikipedia'. Tap move to USB storage.
* All of our test cases from V1.0 - http://bit.ly/vpbhQe
* .. and whatever else you may want try out
Since the last beta, we've specifically fixed bugs related to non
english languages and Nearby Me feature, and fixes for Android 4.0.
Specific testing on those issues would be great!
General Feedback @
(edit away) .
There are bound to be bugs but don't think that someone will file them
for you. If you don't file it then chances are that we won't know it's
an issue. If you're not sure of whether it's a bug or not, then come
join us on #wikimedia-mobile (freenode) and we'll sort it out.
P.S. For more frequent announcements and discussions, please join the
mobile-l mailing list
Yuvi Panda T
This mail refers to E:RSS version 2.01 as in r112315 .
- begin of Namespace handling and ATOM feed handling
- E:RSS is compatible with E:WikiArticleFeeds RSS, ATOM feeds
- handles basic HTML layout tags in feed items
If you think you are an XML expert, please feel free to improve the parser
with the goal to betterparse ATOM feeds, rdf: ...
A non-representative list of RSS and ATOM feeds for testing is
When _viewing_ this page please take into account that that page is
by an outdated version of E:RSS on MediaWiki.
When making your own tests then set
$wgRSSCacheCompare=1; // to avoid caching effects and
$wgRSSFetchTimeout=15; // to bear with slow RSS sources
and always action=purge your wiki test page/s when experimenting.
TechOps is happy to announce Christian Aistleitner has joined us as a
Christian, who is based in Linz, Austria, will work towards hardening the
XML dump infrastructure.
Though he just completed his PhD in 2011, he has been doing programming
since his teenage years., and started working in 2001. His career revolves
around free software integration, making software maintainable, and
tracking down and fixing the ever hiding bugs.
He is a self-confessed code reading junkie, feeding on twisted, obscure
code. And this passion for the obscure is not limited to programming
languages, but also translates to spoken languages, as he is keen on
Finally, when not working or at home, you can often find Christian in
playgrounds where there are swing and see-saws.
Please join me in welcoming Chris and you can reach him on IRC (his nick is