Wikitech-l October 2014

wikitech-l@lists.wikimedia.org

121 participants
124 discussions

internacionalization for client and server side integrated with handlebars
by Nuria Ruiz 24 Oct '14

24 Oct '14

Hello, Those of you that have deal with client side translation in javascript might appreciate this library recently released from yahoo: http://formatjs.io/github/ Just an FYI Nuria

2 1

OPW 9 Proposal : Pywikibot - Compat to core migration.
by Priyanka Jayaswal 24 Oct '14

24 Oct '14

Hi! I am Priyanka Jayaswal and I am willing to contribute towards Compat to core migration for FOSS Outreach Program for Women - Round 9. I have selected a mentorship project from Project list < https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects> named Pywikibot to resolve it's issue on Compat to core Migration. I have been in contact with mentor John Vandenberg and we have proposed a rough proposal based on our discussions and thoughts. Further information about the project has been provided on the Proposal page: https://upload.wikimedia.org/wikipedia/mediawiki/0/01/ProposalPywikibot-Com… Link for wiki proposal page may be found in : https://www.mediawiki.org/wiki/User:Prianka . We need community's valuable suggestions to improve the proposal, add possible features, and views on the project so that this project can be success. Thanks ! -- *Priyanka Jayaswal* Third Year Undergraduate Student Department of Mathematics Indian Institute of Technology, Kharagpur

3 2

Introducing Math rendering 2.0
by Gabriel Wicke 24 Oct '14

24 Oct '14

Dear Wikipedians, We'd like to announce a major update of the Math (rendering) extension. For registered Wikipedia users, we have introduced a new math rendering mode using MathML, a markup language for mathematical formulae. Since MathML is not supported in all browsers [1], we have also added a fall-back mode using scalable vector graphics (SVG). Both modes offer crisp rendering at any resolution, which is a major advantage over the current image-based default. We'll also be able to make our math more accessible by improving screenreader and magnification support. We encourage you to enable the MathML mode in your Appearance preferences. As an example, the URL for this section on the English Wikipedia is: https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rendering For editors, there are also two new optional features: 1) You can set the "id" attribute to create math tags that can be referenced. For example, the following math tag <math id="MassEnergyEquivalence"> E=mc^2 </math> can be referenced by the wikitext [[#MassEnergyEquivalence|mass energy equivalence]] This is true regardless of the rendering mode used. 2) In addition, there is the attribute "display" with the possible values "block" or "inline". This attribute can be used to control the layout of the math tag with regard to centering and size of the operators. See https://www.mediawiki.org/wiki/Extension:Math/Displaystyle for a full description, of this feature. Your feedback is very welcome. Please report bugs in Bugzilla against the Math extension, or post on the talk page here: https://www.mediawiki.org/wiki/Extension_talk:Math All this is brought to you by Moritz Schubotz and Frédéric Wang (both volunteers) in collaboration with Gabriel Wicke, C. Scott Ananian, Alexandros Kosiaris and Roan Kattouw from the Wikimedia Foundation. We also owe a big thanks to Peter Krautzberger and Davide P. Cervone of MathJax for the server-side math rendering backend. Best, Gabriel Wicke (GWicke) and Moritz Schubotz (Physikerwelt) [1]: Currently MathML is supported by Firefox & other Gecko-based browsers, and accessibility tools like Apple's VoiceOver. There is also partial support in WebKit.

3 2

Looking for project status updates
by Pine W 23 Oct '14

23 Oct '14

Hi Terry (or anyone who knows the answers), It's been awhile since I've noticed a status update from the Growth that team through the EE list or this list. The Meta page implies that the Growth team disbanded on October 3. Is that true, and if so, does WMF still have a single person leading tech-based growth initiatives? Also, who is PMming Winter? It would be helpful to have a unified high-level overview of the status, relationships, plans, strategic goals, and contacts for projects like: VE Winter Flow Citoid MV SUL Growth HHVM Mobile web Mobile apps etc. Thanks (: Pine

5 6

Open issues for next MediaWiki maintenance releases
by Markus Glaser 23 Oct '14

23 Oct '14

Hello everyone, next week on October, 29th, there will be another set of security and maintenance releases for MediaWiki. There are still some unresolved bugs and changes that are wating to be +2'ed. So if you feel like improving MediaWiki tarball releases in the upcoming days, you could have a look at these lists: Open bugs for MW 1.23: https://bugzilla.wikimedia.org/buglist.cgi?action=wrap&list_id=331203&produ… Fixes that need to be backported: https://bugzilla.wikimedia.org/buglist.cgi?f1=flagtypes.name&list_id=331206… Changes in Gerrit that are waiting to be merged: https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/core+branc… Thanks for your help! Markus (mglaser) Wiki Release Team

1 0

Now you can submit / claim Engineering Community tasks
by Quim Gil 23 Oct '14

23 Oct '14

Following the activity of the Engineering Community team has never been simple, not even for ourselves. Proposing Engineering Community tasks effectively was even more complex. Here is an attempt to change this: https://phabricator.wikimedia.org/tag/engineering-community/ Since the beginning of this month, we are using Phabricator to organize the Engineering Community team work. https://phabricator.wikimedia.org/tag/ect-october-2014/board/ You can watch, comment, and get involved. You can also submit and claim tasks. What should we be working on next month? How can we facilitate more tech community work done by more people? See you there. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

3 5

Re: [Wikitech-l] [Wikimedia-l] Quarterly reviews of high priority WMF initiatives
by Tilman Bayer 23 Oct '14

23 Oct '14

Minutes and slides from the recent quarterly review meeting of the Foundation's MediaWiki Core team can now be found at https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Quarterly_revi… . On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)wikimedia.org> wrote: > Hi folks, > > to increase accountability and create more opportunities for course > corrections and resourcing adjustments as necessary, Sue's asked me > and Howie Fung to set up a quarterly project evaluation process, > starting with our highest priority initiatives. These are, according > to Sue's narrowing focus recommendations which were approved by the > Board [1]: > > - Visual Editor > - Mobile (mobile contributions + Wikipedia Zero) > - Editor Engagement (also known as the E2 and E3 teams) > - Funds Dissemination Committe and expanded grant-making capacity > > I'm proposing the following initial schedule: > > January: > - Editor Engagement Experiments > > February: > - Visual Editor > - Mobile (Contribs + Zero) > > March: > - Editor Engagement Features (Echo, Flow projects) > - Funds Dissemination Committee > > We’ll try doing this on the same day or adjacent to the monthly > metrics meetings [2], since the team(s) will give a presentation on > their recent progress, which will help set some context that would > otherwise need to be covered in the quarterly review itself. This will > also create open opportunities for feedback and questions. > > My goal is to do this in a manner where even though the quarterly > review meetings themselves are internal, the outcomes are captured as > meeting minutes and shared publicly, which is why I'm starting this > discussion on a public list as well. I've created a wiki page here > which we can use to discuss the concept further: > > https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r… > > The internal review will, at minimum, include: > > Sue Gardner > myself > Howie Fung > Team members and relevant director(s) > Designated minute-taker > > So for example, for Visual Editor, the review team would be the Visual > Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker. > > I imagine the structure of the review roughly as follows, with a > duration of about 2 1/2 hours divided into 25-30 minute blocks: > > - Brief team intro and recap of team's activities through the quarter, > compared with goals > - Drill into goals and targets: Did we achieve what we said we would? > - Review of challenges, blockers and successes > - Discussion of proposed changes (e.g. resourcing, targets) and other > action items > - Buffer time, debriefing > > Once again, the primary purpose of these reviews is to create improved > structures for internal accountability, escalation points in cases > where serious changes are necessary, and transparency to the world. > > In addition to these priority initiatives, my recommendation would be > to conduct quarterly reviews for any activity that requires more than > a set amount of resources (people/dollars). These additional reviews > may however be conducted in a more lightweight manner and internally > to the departments. We’re slowly getting into that habit in > engineering. > > As we pilot this process, the format of the high priority reviews can > help inform and support reviews across the organization. > > Feedback and questions are appreciated. > > All best, > Erik > > [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus > [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings > -- > Erik Möller > VP of Engineering and Product Development, Wikimedia Foundation > > Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate > > _______________________________________________ > Wikimedia-l mailing list > Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Tilman Bayer Senior Operations Analyst (Movement Communications) Wikimedia Foundation IRC (Freenode): HaeB

1 0

MediaWiki Architecture Committee updates
by Brion Vibber 22 Oct '14

22 Oct '14

Hey all -- Announcement time! The MediaWiki Architecture Committee has added two members by provisional internal consensus: * Roan Kattouw, Wikimedia Foundation (visual editor & core) * Daniel Kinzler, Wikimedia Deutschland Roan and Daniel are familiar faces with longtime contributions to MediaWiki. They will be helping with relevant RfC reviews and approvals, and giving advice and ideas as we continue to spin up work in the Arch Committee. These are in addition to the original three members: * Mark Bergsma, Wikimedia Foundation (ops) * Tim Starling, Wikimedia Foundation (core) * Brion Vibber, Wikimedia Foundation (mobile) We plan to have a more formal process for maintenance of the committee membership ready for approval at the MediaWiki Dev Summit in January[1], as well as a more fleshed-out roadmap of what we want the committee to accomplish. Other Arch Committee news: * In the meantime we're concentrating on picking up MediaWiki RfCs to make sure they don't go stale. Last week, Brion and Tim picked up the RfC for styling in templates[2] with an eye to do clean scoping of the styles for security and cleanliness purposes. * We've been chatting with Trevor's Front-end Standardization Group about some other RfC topics such as picking an HTML templating engine for ResourceLoader modules[3]. Jon Robson from Mobile Web has started on a changeset[4] integrating some of the interfaces from the Mantle extension, starting with a basic HTML loader and with plans to include JS-side (and later PHP-side) Handlebars-compatible template compilers. This is still a work in progress as I understand. Both of these RfC pages need to be updated for current status. Also I totally understand that using the term "template" for both MediaWiki markup templates and HTML UI templates is confusing! * This week's RfC checkup meeting happening real soon now -- 21:00 UTC / 2pm Pacific Time -- in #wikimedia-office so come by and say hello! Until next time.... arch on! [1] http://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015 [2] http://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templat… [3] http://www.mediawiki.org/wiki/Requests_for_comment/HTML_templating_library [4] https://gerrit.wikimedia.org/r/#/c/165952/ and friends -- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org)

4 3

Meet-up at WMF: Exploratory Testing for Complex Software, Oct 22 2014
by Arthur Richards 22 Oct '14

22 Oct '14

On Wednesday, October 22, 2014 the Quality Assurance Group and Team Practices Group hope you will join us for a meet-up at the WMF entitled 'Exploratory Testing for Complex Software; Lessons from Cloud Foundry' with special guest speaker Elisabeth Hendrickson [1]. We will be discussing testing in agile iterative software development, and in particular exploratory testing <https://en.wikipedia.org/wiki/Exploratory_testing> [0]. This will be a lively and enlightening conversation, aimed at everyone concerned about the overall quality of software - even those who do not necessarily contribute code. *When*: Wednesday, October 22, 2014, 6:00pm - 8:30pm (for WMF folks there is a calendar event on the Engineering calendar) *Where*: Wikimedia Foundation 6th Floor, collab space 149 New Montgomery St. San Francisco, CA (Accessible for remote participation via Hangouts on Air; link TBA) *From the meet-up invite <http://www.meetup.com/wikimedia-tech/events/207856222/>*[2]: In modern software development organizations, the days are gone when separate, independent Quality Assurance departments test software only after it is finished. Iterative development and agile methods mean that software is constantly being created, tested, released, marketed, and used in short, tight cycles. An important testing approach in such an environment is called Exploratory Testing, and the Wikimedia Foundation has made significant investments to support Exploratory Testing for its software development projects. Elisabeth Hendrickson is "test obsessed". She was an early adopter and vocal proponent of all aspects of agile software testing. She has been particularly instrumental in encouraging and defining the practice of Exploratory Testing. Elisabeth's 2013 book "Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing" is the standard reference on the subject. Join us in the Wikimedia Foundation collaboration space to hear Elisabeth discuss her experience doing software testing for complex projects, with particular examples of Exploratory Testing from her current work as Director of Quality Engineering for Cloud Foundry. This talk is for everyone involved in the overall quality of software, and it will be of particular interest to Project Managers, Product Managers, and those working with software development projects who do not necessarily contribute code directly to the projects. [0] https://en.wikipedia.org/wiki/Exploratory_testing [1] Elisabeth Hendrickson is a tester, developer, and Agile enabler. She wrote her first line of code in 1980, and almost immediately found her first bug. In 2010 she won the prestigious Gordon Pask Award from the Agile Alliance. She is best known for her Google Tech Talk on Agile Testing as well as her wildly popular Test Heuristics Cheatsheet. In 2003, she learned how to do Agile for real from Pivotal Labs while working as a tester on one of their projects. In 2012 she decided it was time to take up permanent residence in the Pivotal offices, where she is the Director of Quality Engineering for Cloud Foundry, Pivotal's Open Source Platform as a Service (PaaS). [2] http://www.meetup.com/wikimedia-tech/events/207856222/ -- Arthur Richards Team Practices Manager [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

4 6

Tech Talk: Design Research in Product Development: Oct 22
by Rachel Farrand 22 Oct '14

22 Oct '14

Please join us for the following tech talk: *Tech Talk**:* Design Research in Product Development *Presenter:* Abbey Ripstra, Design & Usability Research Analyst on The UX team at the Wikimedia Foundation *Date:* October 22 *Time:* 1900 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Desig…> Link to live YouTube stream <http://www.youtube.com/watch?v=jYMTzzosUIw> *IRC channel for questions:* #wikimedia-office Google+ page <https://plus.google.com/u/0/b/103470172168784626509/events/caiiagf75bvddr09…>, another place for questions Talk description: The value of design research in product development is being recognized more frequently these days. This talk will quickly describe the innovation process, and how, when and why design research fits into the different parts of the innovation process. For most of the talk, Abbey will focus in on the product development part of innovation and describe how, when and why to best utilize the various methodologies of design research toward building intuitive, easy to use products that meet the needs of users. Abbey will also talk about, and want to collaborate on, the best ways to integrate design research, specifically, into product development at Wikimedia Foundation.

2 5

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

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 October 2014