Wikitech-l December 2013

wikitech-l@lists.wikimedia.org

125 participants
119 discussions

OAuth Devlopment Training
by Chris Steipp 21 Dec '13

21 Dec '13

Hi all, For any developers who have been thinking about connecting their application to MediaWiki, but haven't gotten around to diving in, I'm going to have a short training/workshop session next week. I'll give a brief intro to using the version of OAuth that we're running, and walk through some quick demos in php and go. After that, I'm happy to walk any developer through getting their app connected, if anyone is struggling with a particular issue. It will be Wed, Dec 18th at 11am PST (1900 UTC). Please let me know if you're interested. We'll probably use a hangout for the session, but if that's not an option for anyone we can use a voice call and etherpad. Either way I'll probably send out invites individually.

5 6

Suggested process for determining topics at the Architecture Summit
by Diederik van Liere 21 Dec '13

21 Dec '13

Hola, We wanted to update you with our proposal on how we are thinking on how to create a program for the Architecture Summit coming January. We started grouping the RFC's from https://www.mediawiki.org/wiki/RFC into clusters at https://www.mediawiki.org/wiki/Architecture_Summit_2014/RFC_Clusters. This clustering is neither perfect nor complete and we would like to ask your help with finetuning the clustering. The idea is that a cluster contains RFC's that belong to each other -- this means if we discuss RFC A and therefore RFC B needs to be discussed as well then those two RFC's should be in the same cluster. Clusters should also be small, probably not more than 3 or 4 RFC's per cluster. Sometimes RFC's in the same cluster will offer alternative suggested implementations, sometimes, RFC's are closely related because they pursue a similar goal. Currently, we have one big cluster called 'General Mediawiki Functionality' and this list definitely needs to be broken up in smaller clusters. The 'Misc' cluster can probably also broken up in smaller clusters. Once we have nailed down the clusters of RFC's then we will run a strawpoll to gauge interest for the different clusters. The strawpoll will inform our decision which clusters should be discussed at the Architecture Summit. We want to launch this strawpoll at the latest on January 2nd, 2014. Summary: 1) Help us finalize the clustering of RFC's on https://www.mediawiki.org/wiki/Architecture_Summit_2014/RFC_Clusters 2) Participate in the strawpoll once it goes live (probably January 2nd), separate email will follow. If you have any questions, thoughts, suggestions, remarks, etc, etc please let us know! Best, Diederik

1 0

Deployment highlights - week of December 23rd
by Greg Grossmeier 21 Dec '13

21 Dec '13

Hello and welcome to the special holiday edition of the deployment highlights email. == Week of Dec 23rd == ZERO DEPLOYS https://wikitech.wikimedia.org/wiki/Deployments#Week_of_December_23 == Week of Dec 30th == This week will be a partial deploy week (no deploys on Tuesday or Wednesday, Dec 31st and Jan 1st, respectively): https://wikitech.wikimedia.org/wiki/Deployments#Week_of_December_30 As such, the MediaWiki update that normally happens on Tuesday that week will instead occur on Monday (the 30th). See the MediaWiki schedule at https://www.mediawiki.org/wiki/MediaWiki_1.23/Roadmap#Schedule_for_the_depl… The other notable deployment the week of the 30th is the disablement of the pt.wikipedia.org 'emergency captcha'. See: https://bugzilla.wikimedia.org/show_bug.cgi?id=49860 for all of the details, especially: https://bugzilla.wikimedia.org/show_bug.cgi?id=49860#c75 (comment 75, by Erik Moeller). Thanks, and as always, have a good weekend, Greg -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

1 0

wikitech/labs outage
by Daniel Zahn 20 Dec '13

20 Dec '13

Hi all, we had an outage of Wikitech and Labsconsole / Labs. Apache on virt0 was broken. It was reported by S Page on IRC, the symptons were wikitech and labsconsole being down via HTTP(S) but pingable. We also had Icinga monitoring telling us about it. I went to virt0 and saw Apache running, shortly after restarted it and that fixed the issue. The root cause i found to be a bug in Phusion Passenger module that is used on virt0, as opposed to cluster Apache. from /usr/lib/phusion_passenger/passenger-spawn-server:61 *** Exception Errno::EPIPE in Passenger RequestHandler (Broken pipe) (process 23592): I made a copy of the full log and for now it is on virt0 in /root/apache2_error_log_20131219.log if you would like to see it all. So far i just blame https://www.phusionpassenger.com/ respectively libapache2-mod-passenger and didn't take any further action. I did tell the labs IRC channel but did not post on labs-l. Daniel -- Daniel Zahn <dzahn(a)wikimedia.org> Operations Engineer

1 0

jCanvas module
by Alex Brollo 19 Dec '13

19 Dec '13

I'm playing a little bit with HTML5 features; I see that thare's a jStorage module, but i didn't found jCanvas module. Is there some interest about? Alex

1 0

Draft for Bugzilla etiquette guidelines
by Andre Klapper 19 Dec '13

19 Dec '13

Heya everybody, based on a discussion on the teampractices@ mailing list ([1],[2]) I have published an initial draft for potential Bugzilla etiquette guidelines. It tries to explain workflows and "helpful behavior" in Bugzilla, as things work slightly different than on wikipages (not only on a technical level): https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette I welcome your comments on the Talk/Discussion page! Cheers, andre [1] http://lists.wikimedia.org/pipermail/teampractices/2013-November/000112.html [2] http://lists.wikimedia.org/pipermail/teampractices/2013-November/000158.html -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

3 4

RFC deadline this Friday, December 20
by Rob Lanphier 19 Dec '13

19 Dec '13

Hi everyone, Everything I said below still stands, except now there are only two days, so please make the most of them. Don't make me break out the caps lock. I'll do it. :-) Thanks Rob ---------- Forwarded message ---------- From: Rob Lanphier <robla(a)wikimedia.org> Date: Wed, Dec 11, 2013 at 12:41 PM Subject: RFC deadline approaching for Arch Summit: December 20 To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Hi everyone, We're just over a week away from the Friday, December 20 deadline for RFCs as items to consider at the Architecture Summit.[1] That's not a hard and fast rule (we've never done this before), but we should definitely have a reasonable amount of time between the point an RFC is proposed and being discussed at the Architecture Summit. Ideally, we'll have taken care of everything that's reasonable to take care of via mailing list/IRC/other online meeting, and really be down the things that require face-to-face time to accomplish. It's my hope that we're not just nibbling at the edges, but that we're actually going to talk about things that will substantially modernize our architecture and reduce our technical debt. I believe there are RFCs in the list and in the works that do that, but I also know there are areas we've discussed informally in the past that we've never set to writing. Many of the RFCs cover important areas of incremental improvement, but not all of the changes we need to make have such small increments. Anyway, RFC submission page is here: https://www.mediawiki.org/wiki/Requests_for_comment Rob [1] https://www.mediawiki.org/wiki/Architecture_Summit_2014

3 2

Wikipedia mobile app rewrite early test builds available
by Brion Vibber 19 Dec '13

19 Dec '13

As folks may be aware, over in the Wikimedia Mobile Apps team we're starting a refresh of the Wikipedia mobile apps for Android and iOS, which have not been updated in a while and are now wayyy behind the mobile web in features and UI awesomeness. The new apps are using native UI around the content web view, which lets us integrate with the system better than the old PhoneGap-based HTML app, and provide long-desired features like pinch-to-zoom in the article view. Our first 2-week work sprint is finishing up, and builds of current state are available: * Android: http://dumps.wikimedia.org/android/apps-android-wikipedia-dev-sprint1.apk * iOS: on testflightapp.com (email notifications sent to our recently trimmed beta list) Both versions are pretty bare-bones, so don't be surprised by missing icons, toolbar buttons that don't work, or incomplete design. :) This first feature sprint concentrated on getting search & basic content loading working. You can type into the search box, the search results include thumbnails, and you can select a search result to load the article. You can also click on internal links in both iOS and Android versions, though they get a little flaky from there out. :) Back/forward is not yet implemented on iOS; back works on Android but there's no forward. Note also the pretty animation when following links on Android -- neat! Next sprint's release should look more polished, as we'll have some more navigation working, and the first sprint stuff prettied up to better match design: https://upload.wikimedia.org/wikipedia/commons/c/c8/Search-overlay-01.png For in-progress design & UX ideas for the new app, see https://www.mediawiki.org/wiki/Wikipedia_App_Design Note that you may or may not need to manually uninstall the old app if it's present first. If you want to try the iOS version and aren't on the beta list you'll have to build it yourself on a Mac with XCode 5, and then you can only install it on your device if you are a registered iOS developer (thank Apple's restrictions on third-party app installations!): $ git clone https://gerrit.wikimedia.org/r/apps/ios/wikipediaapps-ios-wikipedia (Unfortunately we cannot add new people to the iOS beta list until Apple clears out old entries from our 100-max device database, either at the end of the calendar year or in February when our membership rolls over. Yeah, I'm serious...) And of course you can build the Android version too, and run it with no restrictions: $ git clone https://gerrit.wikimedia.org/r/apps/android/wikipediaapps-android-wikipedia Note that there's separate work going to revitalize the Wikipedia app for Firefox OS, which will remain HTML5-based as that's how native Firefox apps work! That's being spearheaded by the Wikimedia Mobile Partnerships & Wikipedia Zero team. -- brion

5 6

Jenkins tests queue should proceed faster
by Antoine Musso 19 Dec '13

19 Dec '13

Hello, Gerrit changes are processed by a daemon known as Zuul which triggers Jenkins jobs and report back to Gerrit as the infamous jenkins-bot. Since I upgraded Zuul in May 2013, the jobs were not processed as fast as we would have wanted. There were issues on Jenkins side, faulty configuration on the server but we eventually reached some acceptable state. Still. During busy hours (Europe evening, SF morning) with the l10n bot submitting half a thousand of changes, we would have to wait up to half an hour to get a test report. I spent most of the night debugging and reproducing that issue on my computer then went to bed. A few minutes ago, I have deployed a change that would make Zuul process changes way faster. The change is ridiculously small since it is just about commenting two lines: https://gerrit.wikimedia.org/r/102465 It basically prevents Zuul from updating builds descriptions pages in Jenkins until all builds have been completed. Since updating a build description takes roughly 500ms, that is saving a ton of waiting time. Thanks a ton to at least Ori, Timo, Qchris, RobH, manybubles and basically everyone around using the CI platform in one way or another. I have monitored the upgrade for the last few minutes in production and that works as expected. The rollback plan is: Revert https://gerrit.wikimedia.org/r/102465 Merge revert on gallium: - cd /usr/local/src/zuul - git pull - as root: * http_proxy=. python setup.py install * /etc/init.d/zuul restart I don't think that it is needed though. Will monitor again tonight during the real peak hour. For reference the bug is https://bugzilla.wikimedia.org/48025 which I believe is now properly fixed. Merry Christmas. -- Antoine "hashar" Musso

2 1

Lowering limitation of the score extension
by Mathieu Stumpf 18 Dec '13

18 Dec '13

Hello, I would like to use the score extension to generate guitar chords diagrams, but writing something like <score> \fret-diagram #"s:0.75;6-x;5-x;4-o;3-2;2-3;1-2;" </score> I get this message error: Processing `.../file.ly' Parsing... .../file.ly:12:0: error: unknown escaped string: `\fret' \fret-diagram #"s:0.75;6-x;5-x;4-o;3-2;2-3;1-2;" .../file.ly:12:0: error: syntax error, unexpected STRING \fret-diagram #"s:0.75;6-x;5-x;4-o;3-2;2-3;1-2;" .../file.ly:21:24: error: syntax error, unexpected '}' }error: failed files: ".../file.ly" exited with status: 1 The code works just fine when I compile it with my local lilypond. That functionality would be really interesting, since with a little scribunto module, it would allow to generate chords diagram on the fly, and even a chord book. Also I would like to make even more with colored diagrams showing a set of interval on the neck. It would be fine if the mediawiki environnement would allow this. kind regards

2 2

← Newer
1
2
3
4
5
6
7
8
...
12
Older →

2026

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 December 2013