Wikitech-l July 2014

wikitech-l@lists.wikimedia.org

144 participants
151 discussions

MediaWiki now supports PBKDF2 and Bcrypt
by Tyler Romeo 28 Jul '14

28 Jul '14

Hi everybody, I was on the brink of celebrating the one-year anniversary of a patch I submitted being open, but today it was finally merged! https://gerrit.wikimedia.org/r/77645 The old User::comparePasswords() and User::crypt() functions have been replaced with a new password hashing API. This means MediaWiki now natively supports Bcrypt and PBKDF2 as replacement password hashing algorithms. Furthermore, the system allows seamless transitioning, meaning users’ password hashes will be updated automatically the next time they log in. This means that MD5 is almost out the door, which is a big win (a follow up patch, https://gerrit.wikimedia.org/r/149658, changes the default to PBKDF2, which would mean any wiki that upgrades to 1.24 would automatically switch away from MD5). I’d like to thank Aaron Schulz, Chris Steipp, Krinkle, and many others who helped get this through. -- Tyler Romeo 0x405D34A7C86B42DF

3 3

MediaWiki third-party release managers
by Greg Grossmeier 28 Jul '14

28 Jul '14

I am pleased to announce (after far too long of a delay, my apologies), that Mark Hershberger and Markus Glaser will take on the task of managing the third-party releases of MediaWiki for another year. Congrats Mark and Markus! I'd like to explicitly thank the International Consortium team for their proposal. The choice was indeed a hard one to make and I'm glad we had the second proposal to add context and perspective to Mark's and Markus's. There will be a few changes to this work this coming year, mostly in terms of transparency. Mark and Markus have agreed to conduct quarterly reviews for their work and the output of those meetings will be publicly shared. That means you'll (soon) be able to see the quarterly goals and their progress. Also, we hope to see more collaboration between Mark and Markus and the wider community in the supportive work; the work that everyone can help with to make the releases as good as they can be. We'll be monitoring this collaboration in review process over the course of the year and we currently plan to call out collaboration goals in next year's call for proposals. I look forward to another year of working with Mark and Markus! Best, Greg -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

1 0

MediaWiki Language Extension Bundle 2014.07 release
by Kartik Mistry 28 Jul '14

28 Jul '14

Hello all, I would like to announce the release of MediaWiki Language Extension Bundle 2014.07. This bundle is compatible with MediaWiki 1.23.x and MediaWiki 1.22.x releases. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.07.tar… * sha256sum: 8af5c001db9375bf8dfd16495c7a88fc8dc9b4fe281b1048f6bea6c490bc4a9d Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n * Report bugs to: https://bugzilla.wikimedia.org * Talk with us at: #mediawiki-i18n @ Freenode Release notes for each extension are below. -- Kartik Mistry == Babel, CleanChanges and LocalisationUpdate == * Only localisation updates == CLDR == * Localisation updates. * Updated to CLDR 25 and fixed rebuild script. * Added Simple English translation to Persian. == Translate == === Noteworthy changes === * Bug 67921: Store translatable page translation units in variable form to improve translation memory suggestions. * Display source language for the pages in Special:Translate * Fixed ElasticSearchTTMServer to not return matches for single word messages only. * Changes in Special:PageMigration: ** Bug 66162: Simplistic alignment based on h2 headers. ** Bug 65942: Split headers from other wiki text in translation units. ** Added script for preparing the page for Translation. == UniversalLanguageSelector == === Noteworthy changes === * Stopped using deprecated jquery.json module, this will make ULS slightly smaller. * Added support for Rutul language. === Input Methods === * Added Ludic (lud) transliteration layout. * Added Tibetian (bo) EWTS layout. -- Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_ {kartikm, 0x1f1f}.wordpress.com

1 0

What does a hackathon cost?
by Maarten Dammers 28 Jul '14

28 Jul '14

Hi everyone, Different chapters are looking into organizing next years hackathon. One of the recurring questions is how much it costs to organize such an event. To make it easier to answer this question we published the budget of the Amsterdam hackathon at https://www.mediawiki.org/wiki/Amsterdam_Hackathon_2013/Budget . I believe it's the intention to also publish the budget of this year (Zürich) and 2012 (Berlin). That should give quite a complete overview. One note of warning: You might have different costs than we had. Take for example the internet and wireless: We didn't spend any money on that. Maarten

2 1

New RfC: server-side Javascript error logging
by Gergo Tisza 28 Jul '14

28 Jul '14

Hi all, frontend development is greatly hindered by not having logs of errors that happen in production. If there is a mistake in a PHP file, it is usually quickly caught after deployment when a large number of exceptions show up in the error log. If the mistake is in a JS file, it can take a long time until the error is reported and reproduced; especially so if it only happens under exotic conditions. Many sites solve this issue by setting up an error handler in Javascript which reports any errors that occurred to a logging server. I tried to make a laundry list of things that need to be done or considered if we want to set up such logging for Wikimedia sites and/or MediaWiki in general; I put it up as a draft RfC at [1]. I would appreciate feedback on whether this is plausible or worthwhile. [1] https://www.mediawiki.org/wiki/Requests_for_comment/Server-side_Javascript_…

4 3

Welcoming Joel Sahleen to the Language Engineering team
by Alolita Sharma 28 Jul '14

28 Jul '14

Hi Everyone, Please join me in welcoming Joel Sahleen as software engineer in the Language Engineering team. Joel joins us from Adobe where he has been a globalization engineer for the past 5 years. He developed the internationalization and localization system for PHP components used in the Adobe Marketing Cloud. He also helped build a continuous integration system for localization that currently supports many different products, programming languages and file formats. Prior to becoming a techie and taking the job at Adobe, Joel did a long stint as a Teaching Fellow in the Departments of East Asian Languages and Literatures and Religious Studies at Stanford University. Joel taught courses on Early Chinese Language, Thought, History and Culture and developed course materials used for Advanced Classical Chinese. Joel is very interested in the development of collaborative, online, multilingual texts and is looking forward to advance platform support for languages, scripts, encodings and formats in the Wikimedia universe. In Joel’s own words - “My main reason for wanting to join the WMF is that I believe in its mission. I believe providing access to knowledge is one of the best things you can do to help a person live up to his or her full potential, and as the world becomes more interconnected and interdependent, I believe it is essential that the pursuit of knowledge becomes more community-driven and accessible to everyone. Language engineering is key to making this collaborative effort possible and I am glad to be joining a team and an organization that is actively working to make the world a better place.” I couldn’t agree with him more. Joel lives right outside Salt Lake City, Utah with his wife, two boys, nephew and two dogs. He enjoys traveling, writing, painting and most of all - learning new things. He can be reached on email at jsahleen at wikimedia.org and on our irc channels including #mediawiki, #wikimedia-dev and #mediawiki-i18n. He will also be at Wikimania so feel free to say hello! Joel - I am excited to have you on the language engineering team :-) Welcome! - Alolita Alolita Sharma आलोलिता शर्मा Director of Engineering Internationalization & Localization Wikimedia Foundation

2 1

Pywikibot bug triage
by Amir Ladsgroup 28 Jul '14

28 Jul '14

Hello, There will be the next round of bug triage <https://www.mediawiki.org/wiki/Bug_management/How_to_triage> for pywikibot in July 24th - 27th in #pywikibot channel. We will focus on prioritizing and categorizing bugs listed here. <https://bugzilla.wikimedia.org/buglist.cgi?product=Pywikibot&resolution=---…> <https://bugzilla.wikimedia.org/buglist.cgi?product=Pywikibot&resolution=---…> I hope to see you there. Best <https://bugzilla.wikimedia.org/buglist.cgi?product=Pywikibot&resolution=---…> -- Amir

1 2

Bugzilla Weekly Report
by reporter＠zirconium.wikimedia.org 27 Jul '14

27 Jul '14

1 0

Re: [Wikitech-l] [Wikitech-ambassadors] wikis using badges
by Ricordisamoa 26 Jul '14

26 Jul '14

Il 17/07/2014 16:43, Lydia Pintscher ha scritto: > Hey :) > > Wikidata will soon be able to also maintain article badges like "good > article" and "featured article". I am very happy that we won't use {{Link FA}} anymore, but I'm very skeptical about storing that information on Wikidata. As I previously wrote on the bug page, the page quality rank does not actually pertain to sitelinks. I renew my proposal of an extension to store a quality rank of a page on the client wiki itself, in a structured format that would also be made available to sister projects and to the Wikibase repository. Keeping them on Wikidata would increase redundancy with the client sites, and surely some bots would have to periodically update badges on the repo. Even if I noticed your hard work on badges, I strongly believe that they shouldn't be used for FA/GAs.

1 0

Feedback for mediawiki api development course on codecademy.
by Diwanshi Pandey 25 Jul '14

25 Jul '14

Hello everyone, I am Diwanshi Pandey, an OPW intern. I'd like to have your feedback on the course I have created on codecademy for mediawiki api with help of my mentor Yuri Astrakhan. A little insight: The course is about parsing and querying mediawiki api. Initially we created one course which included 44 exercises but according to codecademy's guidelines their course are for beginners and should have maximum 30 exercises in one course. So we did a split up into two courses: One is Introduction to Wikipedia API<http://www.codecademy.com/courses/web-beginner-en-vj9nh/0/1>and other is Wikipedia:Query API <http://www.codecademy.com/courses/web-beginner-en-yd3lp/0/1>. Also due to api security and restrictions we couldn't implement tutorial on "editing wiki pages through api call" from a non wiki site yet. We are waiting till we find a good and easy way to demo that. Feedback may include: * Are the exercises easy to understand for novice users/developers? * Are changes needed in the look of exercises? * Are there any exercises which need not to be implemented or in too depth? * Any other thing? Thanks, -- *Regards,* *Diwanshi Pandey*

4 8

← Newer
1
2
3
4
5
6
7
...
16
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 July 2014