Re: [Wikitech-l] Medical leave

[Ricordisamoa]

Hi Frances,
no hurry. Rest well and come back stronger!

Il 17/02/2016 02:16, Frances Hocutt ha scritto:

Dear all,

I’m writing to give a heads-up that I expect to be taking medical leave
from today through March 9, due in part to stress caused by the recent
uncertainty and organizational departures. In my absence, my work will be
in the capable hands of Ryan Kaldari and the rest of the Community Tech
team. Any questions you would have directed to me, direct to Ryan.

I hope to return as promptly as circumstance allows.

All the best,
Frances
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l



___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] (no subject)

[Niharika Kohli]

Congratulations, Josephine! :)

On Thu, Feb 18, 2016 at 1:26 AM, Michael Holloway 
wrote:

> Nice work, Josephine!
>
> On Wed, Feb 17, 2016 at 12:43 AM, Josephine Lim 
> wrote:
>
> > Hi all,
> > I've been working on a project to improve the categorization of pictures
> in the Upload to Commons Android app <
> https://phabricator.wikimedia.org/T115101> as part of the Outreachy Dec
> '15 program, which is soon drawing to an end. To summarize, 3 new features
> have been implemented in this app:
> >
> > 1. If a picture with geolocation is uploaded, nearby category
> suggestions are offered (based on the categories of other Commons images
> with similar coordinates)
> >
> > 2. If a picture with no geolocation is uploaded, nearby category
> suggestions are offered based on the user's current location. This is
> optional and only works if enabled in Settings.
> >
> > 3. Category search (when typing in the search field) has been made more
> flexible, whereas previously this was done solely by prefix search. E.g.
> now searching for 'latte' should be able to return 'iced latte'.
> >
> > The latest version of the app is v1.11 and can be downloaded at <
> https://play.google.com/store/apps/details?id=fr.free.nrw.commons>.
> Please feel free to leave feedback or bug reports at <
> https://github.com/nicolas-raoul/apps-android-commons/issues>.
> >
> > I have had an amazing time working on this app as part of the Outreachy
> program, and I greatly appreciate all the support and help that the WMF
> community has given me. :)
> >
> >
> > Cheers!
> >
> >
> > --
> >
> > Regards,
> > Josephine
> >
> > ___
> > Mobile-l mailing list
> > mobil...@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
> >
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Phabricator Update

[Mukunda Modell]

A significant update to https://phabricator.wikimedia.org is coming tonight!

I will be taking Phabricator offline for a short time during the regularly
scheduled maintenance window. This will take place between 01:00 - 03:00
UTC (5:00PM-7:00PM Pacific)

There are a whole lot of new features and bug fixes coming with this
update. Here are some of the most important bug fixes and requests for new
functionality which can will resolved after the update:

   - T84833: When you close an unassigned task as "Resolved" from the
   Comment action, Phabricator thinks you want to claim the task
   
   - T89675: Phabricator avatars should have high definition version for HD
   displays 
   - T119708: setting security to software security bug excluded subscribers
   
   - T89335: Creating private tasks by filling a web form (for AffCom)
   
   - T876: @mentions in descriptions should autocomplete
   
   - T77228: Let non-members watch projects
   
   - T87135: Phabricator should only notify changes to the "Security" field
   if it is indeed changed 
   - T120903: investigate hiding the policy controls for phabricator
   projects. 
   - T91529: Turning the sprint flag on should apply the expected icon and
   color to the project 
   - T115017: For new Phab accounts, link to [[mw:How to report a bug]] at
   the top of task creation form 
   - T91538: Make new tasks within a specific project use a template in
   description field 

For context, there has been some ongoing discussion about potential issues
at https://phabricator.wikimedia.org/conpherence/308/ - further
documentation of the changes and their implications will be published soon.

If you notice any serious issues after the update, please report them in
phabricator or via IRC in the #wikimedia-devtools channel, however, please
wait until the maintenance window is over before reporting any issues -
problems encountered during the maintenance window are to be expected and
reporting them will only serve as a distraction while the upgrade is
underway.

Thanks for your patience!
Mukunda Modell
Phabricator Release Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Tech Talk: Automated citations in Wikipedia: Citoid and the technology behind it: February 29th

[Rachel Farrand]

Please join for the following tech talk:

*Tech Talk**:* Automated citations in Wikipedia: Citoid and the technology
behind it
*Presenter:* Sebastian Karcher (Syracuse University, Zotero)
*Date:* February 29th, 2016
*Time: *20:00 UTC

*Length:* 1 hour
Link to live YouTube stream 
*IRC channel for questions/discussion:* #wikimedia-office

*Summary: *The talk provides a very brief introduction to Marielle Volz's
Citoid, the tool providing Wikipedia's new automated citations.I then focus
on the technology underlying Citoid, Zotero translators, and discuss how
interested users/developers can help improve that functionality to better
serve the Wikipedia community.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RFC: Defining a policy for REST API result format versioning / negotiation

[Gabriel Wicke]

The IRC discussion just finished, thanks to everybody who
participated! You can read a full log on the task [1]. Here is a short
summary:

== Question 1: How to request a specific response format ==

Overall there was a slight preference for using the Accept header over
query strings for format negotiation. It was noted that support for
query strings can be added additionally at a later point.

== Question 2: What to do if no format was specified ==

The main question in the discussion was whether strong encouragement
will be enough to persuade clients to explicitly specify a format
version. A common concern was that clients without explicit version in
the request won't pay attention to announcements either, and will only
find out when things break.

There was consensus for starting with strong encouragement and quick
default changes. If most clients continue to omit explicit versions in
their requests, then we can reconsider *forcing* clients to supply a
version.

== Next steps ==

The Architecture Committee will officially decide this matter based on
the discussion at next Wednesday's meeting.

Gabriel

[1]: https://phabricator.wikimedia.org/T124365#2036959

On Mon, Feb 15, 2016 at 7:41 PM, Gabriel Wicke  wrote:
> We will discuss options for REST API response format versioning and
> -negotiation in Wednesday's RFC meeting:
>
> Topic: https://phabricator.wikimedia.org/T124365
> Time: Wednesday 22:00 UTC (2pm PST)
> Location: #wikimedia-office IRC channel
>
> This RFC will then enter its one-week Final Comment Period, after
> which the Architecture Committee will decide based on the discussion.
>
> I'm looking forward to your input on the task or IRC.
>
> Gabriel
>
> On Thu, Jan 21, 2016 at 4:29 PM, Gabriel Wicke  wrote:
>> Hi,
>>
>> we are considering a policy for REST API end point result format
>> versioning and negotiation. The background and considerations are
>> spelled out in a task and mw.org page:
>>
>> https://phabricator.wikimedia.org/T124365
>> https://www.mediawiki.org/wiki/Talk:API_versioning
>>
>> Based on the discussion so far, have come up with the following
>> candidate solution:
>>
>> 1) Clearly advise clients to explicitly request the expected mime type
>> with an Accept header. Support older mime types (with on-the-fly
>> transformations) until usage has fallen below a very low percentage,
>> with an explicit sunset announcement.
>>
>> 2) Always return the latest content type if no explicit Accept header
>> was specified.
>>
>> We are interested in hearing your thoughts on this.
>>
>> Once we have reached rough consensus on the way forward, we intend to
>> apply the newly minted policy to an evolution of the Parsoid HTML
>> format, which will move the data-mw attribute to a separate metadata
>> blob.
>>
>> Gabriel Wicke
>
>
>
> --
> Gabriel Wicke
> Principal Engineer, Wikimedia Foundation



-- 
Gabriel Wicke
Principal Engineer, Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] (no subject)

[Michael Holloway]

Nice work, Josephine!

On Wed, Feb 17, 2016 at 12:43 AM, Josephine Lim 
wrote:

> Hi all,
> I've been working on a project to improve the categorization of pictures in 
> the Upload to Commons Android app  
> as part of the Outreachy Dec '15 program, which is soon drawing to an end. To 
> summarize, 3 new features have been implemented in this app:
>
> 1. If a picture with geolocation is uploaded, nearby category suggestions are 
> offered (based on the categories of other Commons images with similar 
> coordinates)
>
> 2. If a picture with no geolocation is uploaded, nearby category suggestions 
> are offered based on the user's current location. This is optional and only 
> works if enabled in Settings.
>
> 3. Category search (when typing in the search field) has been made more 
> flexible, whereas previously this was done solely by prefix search. E.g. now 
> searching for 'latte' should be able to return 'iced latte'.
>
> The latest version of the app is v1.11 and can be downloaded at 
> . Please 
> feel free to leave feedback or bug reports at 
> .
>
> I have had an amazing time working on this app as part of the Outreachy 
> program, and I greatly appreciate all the support and help that the WMF 
> community has given me. :)
>
>
> Cheers!
>
>
> --
>
> Regards,
> Josephine
>
> ___
> Mobile-l mailing list
> mobil...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] 2016-02-17 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-02-17

= 2016-02-17 =

== Technology ==

=== Analytics ===
* '''*Blocking'''*:
** Discovery with a pageview API bug: T127034, Dan is working on it right
now
** Multimedia with dumps parsing asks: T126808, T126809, Analytics will
triage hopefully soon (within one or two weeks, but backlog is huge)
* '''*Blocked'''*
** Services (known) because we need to refactor / move AQS (Analytics Query
Service) out of the restbase repo
* '''*Updates*'''*:*
** Same as last time, nothing new is ongoing

   -

=== Architecture ===
[No update.]

=== Performance ===
[No update.]

=== Release Engineering ===
* '''*Blocking'''*:
** Nothing new
* '''*Blocked'''*:
** Looking for review on Phabricator ops/puppet role cleanup. See
https://phabricator.wikimedia.org/T125851
** Looking for a merge from Ops on scap3 provider changes. See
https://phabricator.wikimedia.org/T127215
* '''*Updates*'''*:*
** See wmf.14 group1 deployment blockers
https://phabricator.wikimedia.org/T125597
*** Save latency regression
** Progress on JS-based end-to-end (browser) tests in core. See
https://gerrit.wikimedia.org/r/#/c/256404/

=== Research ===
* '''*Blocking'''*:
** Nothing
* '''*Blocked'''*:
** ORES still blocked on Ops. See https://phabricator.wikimedia.org/T106867
* '''*Updates*'''*:*
** Reader survey test went live 16 Feb in 16:00-17:00 PST SWAT time (5:100K
sampling): for QA purposes
** Reader survey at full rate will go out 17 Feb 8:00-9:00 PST, for less
than 2 weeks, at a 1:500 sampling rate:
https://meta.wikimedia.org/wiki/Research:Characterizing_Wikipedia_Reader_Behaviour

=== Security ===
* '''*Blocking'''*:
** Nice to have: https://phabricator.wikimedia.org/T125382 (Maps)
* '''*Blocked'''*:
** None.
* '''*Updates*'''*:*
** 2FA for wikis progressing
** Security patches

=== Services ===
* '''*Blocking'''*:
** Nobody
* '''*Blocked'''*:
** Separate AQS off of RESTBase - https://phabricator.wikimedia.org/T126294
*** need to schedule a time with Analytics Ops for the move
** Mathoid - SVG to PNG support
*** librsvg(-dev) for Jessie
* '''*Updates*'''*:*
** RESTBase: dropping listing URIs (/pagr/html/ , ...)
** Cassandra multi-instance work _still_ undergoing

=== Technical Operations ===
* '''*Blocking'''*:
**  ORES moving into production, finally hardware is in place
* '''*Blocked'''*:
** Nothing
* '''*Updates*'''*:*
** Ongoing discussions/work about the switchover goal
** Moved with LE cxserver to jessie and node 4.2

== Product ==
=== Community Tech ===
* '''*Blocking'''*:
** Nothing
* '''*Blocked'''*:
** Gadgets 2.0 - blocked on ResourceLoader cache invalidation issue
(Performance team) - https://gerrit.wikimedia.org/r/#/c/269901/
* '''*Updates*'''*:*
** PageAssessments

=== Discovery ===
; '''*Blocking'''*:
** none
; '''*Blocked'''*:
** none
; '''*Updates*'''*:*
** Building more analytics about user satisfaction in completion
** TextCat merged, A/B tests to follow
** WDQS Blazegraph 2.0 work still in progress, getting there
** Discussing adding caching layer, for ops attention:
https://phabricator.wikimedia.org/T126730
** Discussing QuickSurvey with ops

 Maps & Graphs 
*; '''Updates'''*
* Kartographer (maps) launched on beta cluster, getting ready to enable it
on Wikivoyage
** VE has been helping, thanks Ed Sanders
* Graphs can support WDQS, but might need caching (N.B. Operations)
* Created a page-views graph - can be placed on a talk page to show
corresponding view for the past N days.
https://en.wikipedia.org/wiki/Template:Graph:PageViews

*; '''Blockers'''*
* Security: need SVG sanitization lib review (Security) -
https://phabricator.wikimedia.org/T125382
** Note that Performance were thinking of shipping sanitised user-provided
SVGs to clients (instead of server-rendered PNGs), which would also need
this functionality.
*** Are we sanitizing SVG on upload/download?  Or do we always convert them
in a sanbox env to PNG?
 RIght now in production we always convert in a sandbox to PNG for
normal page views, and (?) don't sanitise at all for download of the
original SVG (on file pages).
 We sanitize on upload, mostly show PNG's in articles. Raw svg's are
served from upload.wm.o (untrusted domain)

=== Editing ===
 Collaboration 
* '''*Blocking'''*:
** Dry run patch for external store migration is merged.  Now we need to
set External Store up on Beta, then test the dry run patch there:
https://phabricator.wikimedia.org/T119567
* '''*Blocked'''*:
** Flow dump generation on dumps.wikimedia.org:
https://phabricator.wikimedia.org/T119511
* '''*Updates*'''*:*
** Human-readable name patch is almost done:
https://phabricator.wikimedia.org/T121936
** Will be enabling cross-wiki notifications on first set of wikis soon (
https://gerrit.wikimedia.org/r/#/c/265413/)

 Language 
* '''*Blocking'''*:
** Apertium packages?
* '''*Blocked'''*:
** None.
* '''*Updates*'''*:*
** cxserver migrated to Jessie with help of Alex

 Multimedia 
* '''*Blocking'''*:
** None
* 

Re: [Wikitech-l] 1.27.0-wmf.14 on hold

[Chad]

On Tue, Feb 16, 2016 at 12:23 PM Antoine Musso  wrote:

> Le 16/02/2016 18:20, Chad a écrit :
> > Hi all,
> >
> > Holding deploy now
> > There is a bug with save times
> > See this task for more[0]
> >
> > -Chad
>
> Note: the branch has been cut already on Feb 16th around 15:00 UTC.
>
>
Update: we deployed to testwiki yesterday, mainly so we could populate
the l10n caches for the new branch.

We're still holding back wmf.14 from the remaining wikis while the problem
is investigated.

-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Medical leave

[Derk-Jan Hartman]

Take care Frances !

> Hopefully the situations will improve soon / by then. (really needs to...)

I couldn't agree more with that statement...


DJ

On Wed, Feb 17, 2016 at 8:51 AM, aude  wrote:

> On Wed, Feb 17, 2016 at 2:16 AM, Frances Hocutt 
> wrote:
>
> > Dear all,
> >
> > I’m writing to give a heads-up that I expect to be taking medical leave
> > from today through March 9, due in part to stress caused by the recent
> > uncertainty and organizational departures. In my absence, my work will be
> > in the capable hands of Ryan Kaldari and the rest of the Community Tech
> > team. Any questions you would have directed to me, direct to Ryan.
> >
>
> :(
>
> Please take care.  Look forward to see you around again in March.
> Hopefully the situations will improve soon / by then. (really needs to...)
>
> Cheers,
> Katie
>
>
> >
> > I hope to return as promptly as circumstance allows.
> >
> > All the best,
> > Frances
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
> --
> @wikidata
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Medical leave

[Luis Villa]

Sorry to hear this; Frances, you're an under-appreciated buffer for many
people and processes at the Foundation. Take care of yourself, please.

Luis

On Tue, Feb 16, 2016 at 11:52 PM aude  wrote:

> On Wed, Feb 17, 2016 at 2:16 AM, Frances Hocutt 
> wrote:
>
> > Dear all,
> >
> > I’m writing to give a heads-up that I expect to be taking medical leave
> > from today through March 9, due in part to stress caused by the recent
> > uncertainty and organizational departures. In my absence, my work will be
> > in the capable hands of Ryan Kaldari and the rest of the Community Tech
> > team. Any questions you would have directed to me, direct to Ryan.
> >
>
> :(
>
> Please take care.  Look forward to see you around again in March.
> Hopefully the situations will improve soon / by then. (really needs to...)
>
> Cheers,
> Katie
>
>
> >
> > I hope to return as promptly as circumstance allows.
> >
> > All the best,
> > Frances
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
> --
> @wikidata
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] Update on Upload to Commons Android App project

[Bahodir Mansurov]

Thank you! I use regularly use this app and improvements are always  
welcome.


On Wed, 17 Feb 2016 00:48:53 -0500, Josephine Lim  
 wrote:



Hi all,
I've been working on a project to improve the categorization of
pictures in the Upload to Commons Android app
 as part of the Outreachy
Dec '15 program, which is soon drawing to an end. To summarize, 3 new
features have been implemented in this app:

1. If a picture with geolocation is uploaded, nearby category
suggestions are offered (based on the categories of other Commons
images with similar coordinates)

2. If a picture with no geolocation is uploaded, nearby category
suggestions are offered based on the user's current location. This is
optional and only works if enabled in Settings.

3. Category search (when typing in the search field) has been made
more flexible, whereas previously this was done solely by prefix
search. E.g. now searching for 'latte' should be able to return 'iced
latte'.

The latest version of the app is v1.11 and can be downloaded at
.
Please feel free to leave feedback or bug reports at
.

I have had an amazing time working on this app as part of the
Outreachy program, and I greatly appreciate all the support and help
that the WMF community has given me. :)


Cheers!





--
Baha

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Mass migration to new syntax - PRO or CON?

[Legoktm]

On 02/16/2016 01:52 PM, Legoktm wrote:
> On 02/12/2016 07:27 AM, Daniel Kinzler wrote:
>> Please give a quick PRO or CON response as a basis for discussion.
> 
> No one has responded in a few days, and the current count is 13-5-2, so
> I'm going to find a time to do the mass migration when there aren't that
> many people making core changes and do this today or tomorrow.

{{done}}.

-- Legoktm

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] MediaWiki-Codesniffer 0.6.0 released and [arrays, like, this]

[Legoktm]

Hello!

MediaWiki-Codesniffer 0.6.0 has been released, here's what's changed:
* Add Generic.Arrays.DisallowLongArraySyntax to ruleset, autofix this
repo (Kunal Mehta)
* Add sniff to detect consecutive empty lines in a file (Vivek Ghaisas)
* Disable Generic.Functions.CallTimePassByReference.NotAllowed (Kunal Mehta)
* Update squizlabs/php_codesniffer to 2.5.1 (Paladox)

Notably, this release now requires []-style arrays, as well as PHP 5.5.9
or higher to run.

To help automatically migrate, you can use the "phpcbf" tool. I
recommend setting up a "composer fix" command (for example [1]). Running
just "composer fix" will try to auto-fix every file in the repo, while
"composer fix filename" will just check that filename.

[1] https://gerrit.wikimedia.org/r/#/c/271220/

Thanks,
-- Legoktm


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l