Wikitech-l February 2015

wikitech-l@lists.wikimedia.org

134 participants
140 discussions

Parser tests failing due to clickable anchors for section headers
by Vivek Ghaisas 20 Feb '15

20 Feb '15

In I562e437e, clickable anchors for section headers were added to the parser's output, which is causing many extensions' tests to fail . I will try to update some of the extensions' tests, but I'm hoping the extension maintainers will update their tests to reflect this change since I don't think I'll be able to update them all as of now. Sincere apologies for the late notification. Regards, polybuildr

2 1

RuboCop is now voting
by Željko Filipin 20 Feb '15

20 Feb '15

Antoine and I have paired on making the RuboCop[0] Jenkins jobs voting. The details are in Phabricator[1] and Gerrit[2]. If you are not familiar with Rubocop, there is some documentation at mediawiki.org[3] and my blog[4]. If a repository is set up to run RuboCop, all you have to do is to execute this is terminal: gem install bundler bundle install bundle exec rubocop If you have any questions, or if you notice any problems, let me know. Željko -- 0: https://github.com/bbatsov/rubocop 1: https://phabricator.wikimedia.org/T84979 2: https://gerrit.wikimedia.org/r/#/c/191861/ 3: https://www.mediawiki.org/wiki/Manual:Coding_conventions/Ruby#RuboCop 4: http://filipin.eu/rubocop/

1 0

Preparing Google Summer of Code 2015 and Outreachy
by Quim Gil 20 Feb '15

20 Feb '15

Today Google Summer of Code 2015 and Outreachy (was FOSS Outreach Program for Women, now open to other groups) have announced their call for organizations. Wikimedia will apply to both programs. The deadlines are February 20 and 17, respectively. THIS IS 7-10 DAYS FROM NOW! We need to update the ideas page, but this time we will do it differently: all project ideas need to be presented as a Phabricator task only (no excerpt in wiki page page is needed). We will use a workboard to track the readiness of project ideas. If you are interested in participating as intern or mentor, follow https://phabricator.wikimedia.org/T921 If you are interested in proposing a project idea, associate your task to https://phabricator.wikimedia.org/tag/possible-tech-projects/ (work-in-progress drafts and other proposals subject to discussion are welcome too) I'm looking for a co-organizer to drive this round. We have a process that works, a motivated pool of mentors, and room for creativity and improvement. Between two people, the job is actually simple, and the rewards are literally priceless (including the possibility to attend the Mentors Summit). Nemo was a great co-organizer of Google Code-in, setting a precedent that we want to consolidate. If you are interested, contact me. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

1 1

(no subject)
by Angela lum neh 19 Feb '15

19 Feb '15

Hello everyone, am Angela. Am happy to be part of this mailing list.

2 1

If you hear about 'hackathon buddies'...
by Quim Gil 19 Feb '15

19 Feb '15

Yesterday we opened the travel request process for Wikimedia Foundation employees in Engineering and Product willing to participate at the Wikimedia Hackathon or Wikimania. There is no public link, but you can follow this task at https://phabricator.wikimedia.org/T89355 In this process, we are asking WMF employees to find a hackathon buddy with the sole requirement of not being another WMF employee. In fact, in the registration for the hackathons we will request the same to all participants. https://www.mediawiki.org/wiki/Hackathons#Pairing_buddies This means that non-WMF contributors might receive a request from a WMF employee to be hackathon buddies. This also means that if you are planning to participate in any of these events (and especially if you plan to request travel sponsorship to Lyon) you will be encouraged to find a buddy as well. It's going to be fun. :) And no worries, we will help making connections to whoever needs that help. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

4 6

OOjs UI 0.8.0 release
by Trevor Parscal 19 Feb '15

19 Feb '15

OOjs UI 0.8.0 has been released today. It will be in MW from 1.25wmf19+. *Breaking changes since last release:* - [BREAKING CHANGE] Make default distribution provide SVG with PNG fallback (Bartosz Dziewoński) We've tagged this as a breaking change, but the only breakage is renaming the stylesheet files. This will only "break" for systems which are responsible for importing the library. This is fixed for MediaWiki and for VisualEditor standalone; no other users should be affected. As part of this change, from MediaWiki 1.25wmf19 onwards, OOjs UI will provide raster icon fallbacks for the vector icons, which we were previously not using. *Deprecations since last major release:* - DEPRECATION: TextInputWidget: Deprecate 'icon' and 'indicator' events (Bartosz Dziewoński) The functionality they expose (user clicking on the icon/indicator) is fundamentally not accessible: the icon/indicator is not focusable (has no tabindex), has no keyboard events, doesn't have a label associated or a tooltip, and has no sensible way of fixing all of this. If something needs to be clickable separately, it should probably be a separate Widget with the appropriate mixins added. - DEPRECATION: ButtonWidget: Rename nofollow config option to noFollow (C. Scott Ananian) We're switching this feature (added just last release) to use consistent camel case. The old `nofollow` property still works for backward compatibility, but it is deprecated and will be removed in the next major release but one. If you have any further questions or need help dealing with deprecations, please let me know. General library documentation is available at mediawiki.org <https://www.mediawiki.org/wiki/OOjs_UI> and generated code-level documentation at doc.mediawiki.org <https://doc.wikimedia.org/oojs-ui/master/#!/api>. - Trevor

1 0

VisualEditor weekly triage meetings – 2015-02-18 – minutes
by James Forrester 19 Feb '15

19 Feb '15

Here are the minutes for this week's VisualEditor weekly triage meeting on 2015-02-18. *Item 1 – Release criteria* The release criteria at https://phabricator.wikimedia.org/project/sprint/profile/1015/ (note new URL) were considered. It was proposed and agreed that the wording for "Qualitative UX testing" be changed from "Most users" to a specific number of 75%, and similarly in "Meets specified performance benchmarks", that "reasonable" was changed to a specific number of 150%. These changes have been made. *Item 2 – Review of fixed tickets since last week* These accepted items were fixed and so will be released in this week's production release unless otherwise noted. … in VisualEditor: - https://phabricator.wikimedia.org/T88650 – Support data-mw.body.id for reference contents - https://phabricator.wikimedia.org/T88148 – class="wikitable wikitable" corrupted to class="wikitable" - https://phabricator.wikimedia.org/T87161 – Default to not performing sanity checks - https://phabricator.wikimedia.org/T86401 – Cutting and pasting a paragraph causes (only) the last inline template to be replaced by HTML - https://phabricator.wikimedia.org/T74929 – Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox [*fixed in our IME work in January*] - https://phabricator.wikimedia.org/T74398 – Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode - https://phabricator.wikimedia.org/T67873 – Cannot go to the next line of an article after inserting a special character in a block slug and "TypeError: Inserted data is trying to close the root node (at index 0)" appears [*fixed earlier*] - https://phabricator.wikimedia.org/T65462 – Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome [*fixed in our IME work in January*] - https://phabricator.wikimedia.org/T61748 – Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari [*fixed in our IME work in January*] The fixed tickets represent 83 "story points". There are 1020 remaining points in the list of items accepted as of the end of the meeting. … in dependencies: - https://phabricator.wikimedia.org/T88660 – Parsoid Cite: Render missing reflists - https://phabricator.wikimedia.org/T88019 – Transclusion marker meta tags being left behind in some nested extension/transclusion scenarios - https://phabricator.wikimedia.org/T85870 – Parsoid performance analysis - https://phabricator.wikimedia.org/T75955 – RESTBase / Parsoid integration - waiting for parsoid deploy - https://phabricator.wikimedia.org/T69787 – Investigate remaining rtselser errors in parserTest runs *Item 3 – Review of nominated tickets* Nominated tickets accepted: … as corruption & stability issues: - https://phabricator.wikimedia.org/T89192 – [Regression wmf-16] Including a template/comment/table/gallery/math node in a slug makes the editor completely unresponsive - https://phabricator.wikimedia.org/T89309 – [Regression wmf-17] Safari - cannot click in any check-box … as performance issues: - https://phabricator.wikimedia.org/T89543 – ve.init.mw.ViewPageTarget.transformPage triggers recalculate style due to $.fn.animate - https://phabricator.wikimedia.org/T89423 – Massive recalculate style triggered by OO.ui.Widget.setDisabled - https://phabricator.wikimedia.org/T89536 – Instrument (i.e., track) additional progress markers for VE load - https://phabricator.wikimedia.org/T89735 – VisualEditor is emitting event "timing.ve.behavior.firstTransaction.undefined" … as testing issues: - https://phabricator.wikimedia.org/T89075 – Investigate Chrome disconnect failures when running MediaWiki tests on labs slaves … as feature issues: - https://phabricator.wikimedia.org/T88152 – Cite: 'Autofill from URL' initially shows Basic as a type for inserted citation in context menu, then corrects when re-selected - https://phabricator.wikimedia.org/T89352 – Make slugs keyboard accessible again - https://phabricator.wikimedia.org/T76398 – External link interface for link dialogue [high risk area; accepted with provision that we will likely have to modify work based on user testing] - https://phabriactor.wikimedia.org/T76397 – Search interface for link dialogue [ high technological risk area; accepted with lower priority, to be re-assessed later ] - https://phabricator.wikimedia.org/T52036 – Focus highlights for elements using CSS column-count are too tall in Chrome [accepted as a "polish" issue] - https://phabricator.wikimedia.org/T73085 – Comments in "unsafe" content locations are not displayed [accepted as a lower-priority issue; needs technological investigation for feasibility] … as dependencies: - https://phabricator.wikimedia.org/T89788 – Report on the central tendency for length of pages which are edited for VisualEditor performance benchmarking … for investigation and re-triage: - – None this week Nominated tickets rejected: - https://phabricator.wikimedia.org/T89074 – Create a guided tour for VisualEditor using Getting Started tooltips Rejected for now based on product concerns raised about targeting the right user groups and in the right way, and technological risk/feasibility about bringing in new systems into contact with VisualEditor. Likely to be re-cast and re-nominated next week. - https://phabricator.wikimedia.org/T89072 – Change Welcome dialogue content to more helpful message to new users based on the GuidedTour Rejected as dependent on the above ticket. *Item 4 – Other business* The process was very briefly discussed, without suggestion of changes. Hope this is of interest. Next week's meeting will be at 00 <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150225T16&p1=224…> :00 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150225T16&p1=224…> ( 16 :00 PST) on Wednesday 25 February; hope to see many of you there. Joining instructions are on mw:Talk:VisualEditor/Portal <https://www.mediawiki.org/wiki/Talk:VisualEditor/Portal#How_to_join_the_tri…> . We'll send a reminder before the meeting. Yours, -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester

1 0

Html.php line 269
by Petr Bena 19 Feb '15

19 Feb '15

Can someone explain the point of these lines to me? https://github.com/wikimedia/mediawiki/blob/master/includes/Html.php#L269 If these tags are optional, they can be there, so why remove them? If you remove them, you should probably also care about them in closeElement() so that mediawiki doesn't produce html which has only ending tags for html and head. It seems that on WMF installation we don't use anyway as there is head tag. So why is it there? What purpose does it server?

6 10

Scrum of Scrums notes, 2015-02-18
by Dan Andreescu 18 Feb '15

18 Feb '15

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-02-18

1 0

[Reminder] [x-post] Language Engineering IRC Office Hour on 18 February 2015 (Wednesday) at 1300 UTC
by Runa Bhattacharjee 18 Feb '15

18 Feb '15

Hello, A quick reminder about Language Engineering team's monthly IRC office hour thats happening later today at 1300 UTC on #wikimedia-office. Please see below for the original announcement, local time, and agenda. We will post logs on metawiki[1] after the event. Thanks Runa [1] https://meta.wikimedia.org/wiki/IRC_office_hours#Office_hour_logs ---------- Forwarded message ---------- From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org> Date: Fri, Feb 13, 2015 at 7:47 PM Subject: [x-post] Language Engineering IRC Office Hour on 18 February 2015 (Wednesday) at 1300 UTC To: MediaWiki internationalisation <mediawiki-i18n(a)lists.wikimedia.org>, Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, "Wikimedia & GLAM collaboration [Public]" <glam(a)lists.wikimedia.org> [X-posted announcement] Hello, The next monthly IRC office hour of the WMF Language Engineering team will be on February 18, 2015 (Wednesday) at 1300 UTC on #wikimedia-office. Please note that for this instance the session has been set to a much earlier hour. We will be taking questions and discussing about our ongoing projects, particularly the recent activation of Content Translation as a beta feature on several Wikipedias[1]. We’d love to hear comments, suggestions and any feedback that will help us make this tool better. Please see below to check local time and event details. Logs from our earlier office hours are available at: https://meta.wikimedia.org/wiki/Category:Language_Engineering Thanks Runa [1] http://blog.wikimedia.org/2015/01/20/try-content-translation/ Monthly IRC Office Hour: ================== # Date: February 18, 2015 (Wednesday) # Time: 1300 UTC (Check local time: http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150218T1300) # IRC channel: #wikimedia-office # Agenda: 1. Ongoing projects - Content Translation beta feature 2. Q & A (Questions can be sent to me ahead of the event) -- Language Engineering - Outreach and QA Coordinator Wikimedia Foundation -- Language Engineering - Outreach and QA Coordinator Wikimedia Foundation

1 0

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

Jump to page:

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 February 2015