Wikitech-l March 2015

wikitech-l@lists.wikimedia.org

116 participants
90 discussions

Foreign commits create mess in Phabricator
by Petr Kadlec 04 Mar '15

04 Mar '15

Hi, somebody probably already noticed this, but I didn’t see any discussion around, so just to be sure: I have received notifications about commits being assigned to old bugs in Phabricator by epriestley. See for instance T4123 [1] – “epriestley added a commit: Unknown Object (Commit)”. It seems to me the problem is that somehow the Wikimedia instance of Phabricator and the Phabricator instance of Phabricator (erm… the Phacility instance? secure.phabricator.org, I mean) got crossed/synchronized/whatever. Therefore their commit D7601 [2], marked as fixing _their_ bug T4123 [3] somehow modified _our_ bug T4123. [1] It might have been helped by the fact Evan Priestley has the same “epriestley” account at both installations. While adding nonexistent commits makes a bit of a mess, it’s not a huge problem, but some of these commits changed state of the underlying task as well, which is worse. See epriestley’s feed [4]. I guess those would need to be reverted? -- [[cs:User:Mormegil | Petr Kadlec]] [1]: https://phabricator.wikimedia.org/T4123 [2]: https://secure.phabricator.com/D7601 [3]: https://secure.phabricator.com/T4123 [4]: https://phabricator.wikimedia.org/p/epriestley/feed/

3 2

Transfering domain cswp.cz to WMF
by Petr Bena 03 Mar '15

03 Mar '15

Hi, Long time ago I purchased domain cswp.cz in order to use it in same way as enwp.org for czech wikipedia (cswp.org was taken by something). I think that it would be probably better if it was owned and maintained by WMF rather than me, but I don't really know where to ask, neither if ops are actually interested in maintaining it, the script which redirects the page is pretty simple: <?php $uri = $_SERVER['PHP_SELF']; $target = "http://cs.wikipedia.org/wiki"; header ("Location: $target"."$uri"); exit(); I can't really provide any data on usage of this domain, because I never collected any, but if there isn't any long-term plan for global wiki shorteners I think this domain could be used. Thank you

4 3

Phabricator monthly statistics - 2015-01
by communitymetrics＠wikimedia.org 03 Mar '15

03 Mar '15

Hi Community Metrics team, this is your automatic monthly Phabricator statistics mail. Number of accounts created in (2015-01): 305 Number of active users (any activity) in (2015-01): 669 Number of task authors in (2015-01): 401 Number of users who have closed tasks in (2015-01): 199 Number of tasks created in (2015-01): 2584 Number of tasks closed in (2015-01): 1775 Number of tasks in the shell project closed as resolved,fixed in (2015-01): 22 Number of open and stalled tasks in total: 19008 Median age in days of open tasks by priority: Unbreak now: 50 Needs Triage: 132 High: 133 Normal: 417 Low: 691 Needs Volunteer: 531 TODO: Numbers which refer to closed tasks might not be correct, as described in T1003. Yours sincerely, Fab Rick Aytor (via community_metrics.sh on iridium at Sun Feb 1 00:00:05 UTC 2015)

9 13

Fwd: Upcoming GSoC and Outreachy rounds
by Niharika Kohli 03 Mar '15

03 Mar '15

Hello! I am pleased to announce that Wikimedia has been selected as a mentoring organization for the upcoming Google Summer of Code (out of only 137 organizations selected for this round) and Outreachy rounds. Congratulations! We have a phabricator board for possible projects[1] students can work on. Currently, only 7 projects are in the "Featured" column with well-defined project scope and mentors assigned. A lot more are sitting in the "Needs Discussion" and "Missing Mentors" columns, looking forward to your input. Enlisting some of the more discussed projects here: - Gadget Usage Statistics [2] - Out-of-date fact and statistics identification and review [3] - Cross-wiki watchlists [4] - Newsletter Mediawiki Extension [5] Your comments would be greatly appreciated in shaping these ideas into featured projects for the students. If you know of other projects which could be a good fit for a 3 month GSoC/Outreachy round, please feel free to add them to the board. If you think you can mentor one of these projects, please do comment on the ticket indicating so. [1] https://phabricator.wikimedia.org/tag/possible-tech-projects/ [2] https://phabricator.wikimedia.org/T21288 [3] https://phabricator.wikimedia.org/T89416 [4] https://phabricator.wikimedia.org/T5525 [5] https://phabricator.wikimedia.org/T76199 Thank you! Niharika. PS: I am a co-organizer for the upcoming GSoC & Outreachy rounds for Wikimedia, along with Quim. Nice to meet you!

1 0

VisualEditor weekly triage meetings – 2015-02-25 – minutes
by James Forrester 02 Mar '15

02 Mar '15

Here are the minutes for this week's VisualEditor weekly triage meeting on 2015-02-25. My apologies for their lateness. *Item 1 – Release criteria* The release criteria at https://phabricator.wikimedia.org/project/sprint/profile/1015/ (note new URL) were considered. No changes were proposed. *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/T52036 – Focus highlights for elements using CSS column-count are too tall in Chrome - https://phabricator.wikimedia.org/T70537 – Sometimes page scrolling stops working and in the console getting "Error: offset was inside a handlesOwnChildren node" in Firefox - https://phabricator.wikimedia.org/T73085 – Comments in "unsafe" content locations are not displayed in VisualEditor - https://phabricator.wikimedia.org/T89192 – Including a template/comment/table/gallery/math node in a slug makes the editor completely unresponsive - https://phabricator.wikimedia.org/T89543 – ve.init.mw.ViewPageTarget#transformPage triggers recalculate style due to $.fn.animate - https://phabricator.wikimedia.org/T89943 – Editor freezes after copypasting a reference and trying to insert a references list - https://phabricator.wikimedia.org/T90306 – Cursoring is totally broken in Betalabs with Firefox The fixed tickets represent 81 "story points". There are 813 remaining points in the list of items accepted as of the end of the meeting. … in dependencies: - https://phabricator.wikimedia.org/T52373 – When serializing DOM subtree of <h*> tags, force meta tags (links, categories, etc.) to serialize before / after heading as appropriate - https://phabricator.wikimedia.org/T66171 – Log Parsoid server-side save performance - https://phabricator.wikimedia.org/T75955 – RESTBase / Parsoid integration - https://phabricator.wikimedia.org/T88019 – Transclusion marker meta tags being left behind in some nested extension/transclusion scenarios - https://phabricator.wikimedia.org/T88495 – Unsupported use of multi-cell generating templates within tables - https://phabricator.wikimedia.org/T88660 – Parsoid Cite: Render missing reflists *Item 3 – Review of nominated tickets* Nominated tickets accepted: … as corruption & stability issues: - https://phabricator.wikimedia.org/T49344 – Internal nodes should eventually be in a separate document ("sub-documents") - https://phabricator.wikimedia.org/T90463 – Citoid / citoid integration with VE is emitting data-mw for a template arg that is not compliant with the Parsoid DOMspec - https://phabricator.wikimedia.org/T90478 – Deleting the text inside a bullet/numbered item, heading, other nodes throws error … as performance issues: - https://phabricator.wikimedia.org/T89878 – mediawiki.feedback should use OOjs UI dialog - https://phabricator.wikimedia.org/T90376 – Research incrementally building the CE tree/DOM [accepted as a 'research feasibility' task] - https://phabricator.wikimedia.org/T90374 – Retrieve page HTML directly from RESTbase - https://phabricator.wikimedia.org/T90372 – Send Parsoid API request immediately when user clicks edit - https://phabricator.wikimedia.org/T90304 – Load HTML in parallel with JSON metadata - https://phabricator.wikimedia.org/T90040 – Stash VisualEditor edits using edit stash … as testing issues: - – None this week … as feature issues: - – None this week … as "polish" nice-to-have issues: - https://phabricator.wikimedia.org/T53911 – Scroll to an item when it is selected e.g. when it has been newly inserted - https://phabricator.wikimedia.org/T90622 – Come up with a way of estimating load time and progress along that scale - https://phabricator.wikimedia.org/T64084 – In the template dialog, the boxes for pre-existing, long parameters should be expanded before you click on them in Firefox … as dependencies: - https://phabricator.wikimedia.org/T71950 – Improve nowiki additions to only wrap the string that needs protection - https://phabricator.wikimedia.org/T73006 – Two sets of nowiki tags added; one probably shouldn't have been - https://phabricator.wikimedia.org/T90281 – Improve citoid production service - https://phabricator.wikimedia.org/T88827 – Parsoid should return the full srcset for high DPI devices [polish] … for investigation and re-triage: - https://phabricator.wikimedia.org/T90757 – Adding a template to an article on it.wp means VE gets "frozen" Nominated tickets rejected: - https://phabricator.wikimedia.org/T90299 – Move media to top level icon on toolbar Rejected for now on product grounds, pending resolution of https://phabricator.wikimedia.org/T52227 (Toolbar should collapse items rather than span multiple lines when the window is narrow) and https://phabricator.wikimedia.org/T74159 (Toolbar groups should support sub-groups as items), which will be discussed next meeting. - https://phabricator.wikimedia.org/T56947 – When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too This was both rejected as a Q3 blocker and also declined entirely as a task on which we will ever work; we felt that this approach to the issue added too much complexity and confusion for an infrequent use case, and will become unnecessary once https://phabricator.wikimedia.org/T88337 (Tools should be able to specify a label for their appearance in the context menu ) lands next week. *Item 4 – Other business* The process was very briefly discussed. We considered whether it would be helpful to switch from WebEx to Google Hangouts, which would be simpler for most people to join the call but limited in scope (not an issue so far) and would prevent people being able to call in from a telephone. No final decision was made. Hope this is of interest. Next week's meeting will be at 16:00 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150304T08&p1=224…> ( 08 :00 PST) on Wednesday 4 March; 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

Terrible instructions for configuring Varnish (4.0)
by Daniel Friesen 01 Mar '15

01 Mar '15

I recently started setting up a server with Varnish and realized that our instructions for configuring Varnish look terrible. Specifically our recommendations for Varnish 4.0. https://www.mediawiki.org/wiki/Manual:Varnish_caching#Configuring_Varnish_4… That said, while I know things look wrong, I'm not enough of a Varnish expert to be confident changing the guide. ## Purging The purge instructions look all wrong. ban() is not equivalent to ban_url() so the invocations look broken. Also the Varnish 4 instructions do purging with a `return (purge);` and omit the vcl_hit and vcl_miss. See: https://www.varnish-cache.org/docs/trunk/users-guide/purging.html ## Gzip The instructions still include Accept-Encoding handling. Varnish now handles gzip natively. >From what I understand without this code Varnish will natively prefer requesting gzipped responses from the server and will handle gunzipping things for clients that don't support it. I believe normalizing "gzip, deflate" -> "gzip,deflate" or just "gzip, deflate" -> "gzip" is also redundant now: https://github.com/varnish/Varnish-Cache/blob/336f2eb8fe1c8f46dbf32a9bad387… ## XFF The instructions include the setting of an X-Forwarded-For header to client.ip as well. This is redundant. Varnish implements XFF natively. And it does it correctly, which is to append to XFF when already present. The guide will end up stripping out information which CheckUser makes use of. ## Redundant and harmful vcl_recv overriding Varnish's default vcl already does stuff like CONNECT piping, Authorization and Cookie passing (and now it also handles the absence of SPDY support). https://github.com/varnish/Varnish-Cache/blob/master/bin/varnishd/builtin.v… However the guide duplicates these things and ends with a `return(hash);` making it so the default vcl is never run. ## If-None-Match Someone is going to have to explain this block to me, because doing it does not make sense to me: if (req.http.If-None-Match) {return(pass);} -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]

2 1

Re: [Wikitech-l] [MediaWiki-l] Autopromote problems
by Alex Monk 01 Mar '15

01 Mar '15

You're welcome. I wonder how APCOND_ISIP and APCOND_IPINRANGE were expected to work, and if we should deprecate/remove them. On 28 February 2015 at 23:17, John Horne <john.horne(a)plymouth.ac.uk> wrote: > On Sat, 2015-02-28 at 03:27 +0000, Alex Monk wrote: > > (CCing wikitech-l) > > On 28 February 2015 at 01:04, John Horne <john.horne(a)plymouth.ac.uk> > wrote: > > > > > > $wgAutopromote['sysop'] = array(APCOND_ISIP, '141.163.4.11'); > > > > > Wait, what? MediaWiki supports that?! You should not do that. > > > Yes, MW allowed me to do this, but reading your reply I can see why it > is not something we want to do. It also explains why the 'user list' > page seemed to allocate everyone to the administrators group. > > We have now changed things a bit in that the 'editor' permissions have > been pushed into the 'user' group (most were there anyway). > > We also removed any other 'autopromote' settings. By logging in using > the default login mechanism, and with the initially created account, I > could then set my own account to be administrator and bureaucrat. After > that everything looked fine. > > However, we are intending to use the Shibboleth extension (as forked on > github) as the main login mechanism. When we reapplied this, my groups > were gone again! It seems the extension has a bug in that it removes a > users groups, but never adds them back again. I have corrected this, and > submitted a patch upstream. > > So now we are happy. We have Shibboleth login working fine, and the > users groups are as they should be and remain so upon login/logout. We > are now not using autopromote at all. > > > > Many thanks for your reply, > > John. > > -- > ---------------------------------------------------- > John Horne Tel: +44 (0)1752 587287 > Plymouth University, UK > > > _______________________________________________ > MediaWiki-l mailing list > To unsubscribe, go to: > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l >

1 0

Line break in php
by Thomas Mulhall 01 Mar '15

01 Mar '15

Hi how can I do line breaks in php because I am trying to do line breaks for global in github.com/paladox/Metrolook/blob/test/MetrolookTemplate.php

2 1

Tech Talk: What's New with MediaWiki-Vagrant?: Simple Use Cases and Beyond: November 25
by Rachel Farrand 01 Mar '15

01 Mar '15

Please join us for the following tech talk: *Tech Talk**:* What's New with MediaWiki-Vagrant?: Simple Use Cases and Beyond *Presenter:* Bryan Davis & Dan Duvall *Date:* November 25th *Time:* 1830 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?msg=What%27s+New+with+…> Link to live YouTube stream <http://www.youtube.com/watch?v=I66xR-fq2O8> *IRC channel for questions/discussion:* #wikimedia-office Google+ page <http://www.youtube.com/watch?v=I66xR-fq2O8>, another place for questions *Talk description:*We'll start off by giving a brief refresher on how MW-Vagrant works and how it differs from stock Vagrant. Next, we'll showcase some of the newest and most useful features of MWV such as multi-wiki support, SSH/HTTP sharing, Labs integration, advanced customization using Hiera and local roles. Finally, we'd like to show how MWV can be useful in test-driven development by demonstrating how to run unit and browser tests. The last 15 minutes will be reserved for Q/A. == Outline (WIP) == * (10 minutes) What is Vagrant, MediaWiki-Vagrant, Puppet (dan + bryan) * (15 minutes) Local customizations (bryan) * (15 minutes) Running unit tests and browser tests under MW-V (dan) * (5 minutes) Vagrant sharing (it's awesomesauce!!!) (bryan) * (15 minutes) Q & A

3 6

Phabricator monthly statistics - 2015-02
by communitymetrics＠wikimedia.org 01 Mar '15

01 Mar '15

Hi Community Metrics team, this is your automatic monthly Phabricator statistics mail. Number of accounts created in (2015-02): 317 Number of active users (any activity) in (2015-02): 733 Number of task authors in (2015-02): 422 Number of users who have closed tasks in (2015-02): 216 Number of tasks created in (2015-02): 2952 Number of tasks closed in (2015-02): 2092 Number of tasks in the shell project closed as resolved,fixed in (2015-02): 10 Number of open and stalled tasks in total: 19967 Median age in days of open tasks by priority: Unbreak now: 17 Needs Triage: 122 High: 104 Normal: 394 Low: 675 Needs Volunteer: 522 TODO: Numbers which refer to closed tasks might not be correct, as described in T1003. Yours sincerely, Fab Rick Aytor (via community_metrics.sh on iridium at Sun Mar 1 00:00:04 UTC 2015)

1 0

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