[Wikitech-l] Technical leadership in Wikimedia

2014-05-18 Thread ENWP Pine
Hi all, your thoughts would be appreciated on 
this. It would be great to get some input from tech-focused contributors. I 
started the thread only on Wikimedia-l to keep the discussion 
consolidated in one place. 

http://lists.wikimedia.org/pipermail/wikimedia-l/2014-May/071811.html

Thanks,

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

[Wikitech-l] Bugzilla Weekly Report

2014-05-18 Thread reporter
MediaWiki Bugzilla Report for May 12, 2014 - May 19, 2014

Status changes this week

Reports changed/set to UNCONFIRMED:  6 
Reports changed/set to NEW:  12
Reports changed/set to ASSIGNED   :  27
Reports changed/set to REOPENED   :  14
Reports changed/set to PATCH_TO_RE:  72
Reports changed/set to RESOLVED   :  210   
Reports changed/set to VERIFIED   :  54

Total reports still open  : 14634 
Total bugs still open : 8801  
Total non-lowest prio. bugs still open: 8549  
Total enhancements still open : 5833  

Reports created this week: 259   

Resolutions for the week:

Reports marked FIXED :  138   
Reports marked DUPLICATE :  20
Reports marked INVALID   :  12
Reports marked WORKSFORME:  28
Reports marked WONTFIX   :  12

Specific Product/Component Resolutions & User Metrics 

Created reports per component

VisualEditor  Editing Tools 13  
  
MediaWiki extensions  WikidataRepo  12  
  
MediaWiki Skin and page rendering   11  
  
Wikimedia General/Unknown   11  
  
VisualEditor  Mobile9   
  

Created reports per product

MediaWiki extensions  80
MediaWiki 50
VisualEditor  48
Wikimedia 32
Wikipedia App 11

Top 5 bug report closers

jrobson [AT] wikimedia.org16
federicoleva [AT] tiscali.it  14
jforrester [AT] wikimedia.org 14
matma.rex [AT] gmail.com  11
aschulz4587 [AT] gmail.com10


Most urgent open issues

Product   | Component | BugID | Priority  | LastChange | Assignee   
  | Summary  
--
Analytics | Wikimetrics   | 63819 | Highest   | 2014-05-15 | 
wikibugs-l[AT]lists. | Worker processes left hanging

MediaWiki | Database  | 32551 | Highest   | 2014-05-14 | 
gdubuc[AT]wikimedia. | Descriptionless files (Missing page_l

MediaWiki | Database  | 63677 | Highest   | 2014-05-18 | 
wikibugs-l[AT]lists. | Update script is failing midway due t

MediaWiki | Email | 63269 | Highest   | 2014-05-16 | 
wikibugs-l[AT]lists. | enotif_body incorrectly assumes helpp

MediaWiki | Skin and page | 63351 | Highest   | 2014-05-16 | 
wikibugs-l[AT]lists. | Document "Typography refresh/update" 

MediaWiki ext | Diff  | 58274 | Highest   | 2014-05-16 | 
wikibugs-l[AT]lists. | Implement an order-aware MapDiffer   

MediaWiki ext | OAuth | 57336 | Highest   | 2014-04-14 | 
wikibugs-l[AT]lists. | Make metawiki the central OAuth wiki 

MediaWiki ext | TimedMediaHan | 64152 | Highest   | 2014-04-22 | 
wikibugs-l[AT]lists. | Fatal error: Call to a member functio

MediaWiki ext | UploadWizard  | 64883 | Highest   | 2014-05-16 | 
rillke[AT]wikipedia. | JPEGs on Commons: Several versions up

MediaWiki ext | UploadWizard  | 65406 | Highest   | 2014-05-18 | 
rillke[AT]wikipedia. | UploadWizard: Flickr uploading broken

MediaWiki ext | WikidataRepo  | 64956 | Highest   | 2014-05-08 | 
wikidata-bugs[AT]lis | Install Entity Suggester on the Wikid

MediaWiki ext | WikidataRepo  | 63224 | Highest   | 2014-05-09 | 
wikidata-bugs[AT]lis | review backend part of entity suggest

MediaWiki ext | WikidataRepo  | 52385 | Highest   | 2014-05-13 | 
wikidata-bugs[AT]lis | Query by one property and one value (

MediaWiki ext | WikidataRepo  | 64600 | Highest   | 2014-05-13 | 
wikidata-bugs[AT]lis | write script that touches every item 

OOjs UI   | General   | 65373 | Highest   | 2014-05-18 | 
krinklemail[AT]gmail | [Regression 1.24wmf5] OOjs UI: Firefo

Pywikibot | General   | 63605 | Highest   | 2014-04-09 | 
devunt[AT]gmail.com  | Ignore expired cookie


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

Re: [Wikitech-l] Reducing botspam on #wikimedia-dev

2014-05-18 Thread Legoktm

On 5/18/14, 7:36 AM, Yuvi Panda wrote:

Hello everyone!

I just merged a change into the new wikibugs that will help reduce
botspam on #wikimedia-dev. wikibugs will no longer report bugs on
#wikimedia-dev that have been reported in other channels, thus
reducing duplication. The previous behavior was that wikibugs will
ping multiple channels - mobile bugs went to both #wikimedia-mobile
and #wikimedia-dev, flow bugs to both #wikimedia-corefeatures and
#wikimedia-dev, etc. Now they only go to the primary channel and
bypass -dev. So mobile bugs will only go to #wikimedia-mobile, and not
to #wikimedia-dev. This also matches the behavior of grrrit-wm.
For Flow/Echo/other -corefeatures projects, we send gerrit patches to 
both -dev and -corefeatures, so I think it would make sense for us to 
still have our bugs going to -dev (or we should change the behavior of 
grrrit-wm).


#mediawiki-feed still gets the full firehose of all changes, if you
are interested in that.

Thanks!


Thanks for doing this :)

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

[Wikitech-l] GSoC and OPW Q&A at the ECT meeting

2014-05-18 Thread Quim Gil
Four acronyms in an email subject! My grandma would be proud of me.  :)

After a month of community onboarding, Google Summer of Code and FOSS
Outreach Program for Women interns will start their work officially
tomorrow, Monday 19.

The Engineering Community team will devote its monthly IRC meeting to
answer any questions from interns and mentors and to discuss any related
topics.

Tuesday 20 at 16:00 UTC at #wikimedia-office
https://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings/2014-05-20

If you want to discuss other community topics, please add them to the
schedule. See you there!


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Reducing botspam on #wikimedia-dev

2014-05-18 Thread K. Peachey
tbh -dev (or somewhere else) should be the master channel for bz output.


On 19 May 2014 00:36, Yuvi Panda  wrote:

> Hello everyone!
>
> I just merged a change into the new wikibugs that will help reduce
> botspam on #wikimedia-dev. wikibugs will no longer report bugs on
> #wikimedia-dev that have been reported in other channels, thus
> reducing duplication. The previous behavior was that wikibugs will
> ping multiple channels - mobile bugs went to both #wikimedia-mobile
> and #wikimedia-dev, flow bugs to both #wikimedia-corefeatures and
> #wikimedia-dev, etc. Now they only go to the primary channel and
> bypass -dev. So mobile bugs will only go to #wikimedia-mobile, and not
> to #wikimedia-dev. This also matches the behavior of grrrit-wm.
>
> #mediawiki-feed still gets the full firehose of all changes, if you
> are interested in that.
>
> Thanks!
>
> --
> Yuvi Panda T
> http://yuvi.in/blog
>
> ___
> 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] Deployments of new, radically different default features

2014-05-18 Thread Rainer Rillke
Sun May 18 00:20:10 UTC 2014 Brian Wolff bawolff at gmail.com  wrote:

> I do think there are probably better ways to handle notification of
> new features. Perhaps a pop up the first time new feature is activated
> explaining the feature and how to disable it. I'm not really sure.

Yeah, that would be cool: I am tool "x", I do "y" and you can disable me
pressing button "z". Let button "z" be a prominent element of the UI for
the time of testing at large scale.
This way, we can get rid of some of the banners, thus reducing the risk
for ~-blindness and some of the trouble. VE has something similar now,
if I recall correctly (though the disable-me-button is missing).

-- Rillke

---
I also like MMV as a visitor; but it doesn't fit into any
administrator's workflow at Commons most of the time. Perhaps you also
want to make it easier for anyone to report issues? Other sites have
heavy libraries allowing users to pick the trouble-maker, or take a
screenshot and cutting it, ...

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

Re: [Wikitech-l] Reducing botspam on #wikimedia-dev

2014-05-18 Thread Yuvi Panda
I also see that there is room for more cleanup. The Growth and
Analytics teams should move out of -dev :D Perhaps ops too?


-- 
Yuvi Panda T
http://yuvi.in/blog

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

Re: [Wikitech-l] Reducing botspam on #wikimedia-dev

2014-05-18 Thread Merlijn van Deen
On 18 May 2014 19:58, Nick Wilson (Quiddity)  wrote:

> Current setup details are at
> https://github.com/valhallasw/pywikibugs/blob/master/channels.py
> docs are linked at
> https://www.mediawiki.org/wiki/wikibugs
>
>
Recently I moved the repo to Gerrit, but I forgot to update the
documentation. The new URL is:

https://github.com/wikimedia/labs-tools-pywikibugs/blob/master/channels.py

(or via https://git.wikimedia.org/summary/?r=labs/tools/pywikibugs.git )

which is now also reflected in the documentation.

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

Re: [Wikitech-l] Reducing botspam on #wikimedia-dev

2014-05-18 Thread Nick Wilson (Quiddity)
On Sun, May 18, 2014 at 7:36 AM, Yuvi Panda  wrote:

> Hello everyone!
>
> I just merged a change into the new wikibugs that will help reduce
> botspam on #wikimedia-dev. wikibugs will no longer report bugs on
> #wikimedia-dev that have been reported in other channels, thus
> reducing duplication. The previous behavior was that wikibugs will
> ping multiple channels - mobile bugs went to both #wikimedia-mobile
> and #wikimedia-dev, flow bugs to both #wikimedia-corefeatures and
> #wikimedia-dev, etc. Now they only go to the primary channel and
> bypass -dev. So mobile bugs will only go to #wikimedia-mobile, and not
> to #wikimedia-dev. This also matches the behavior of grrrit-wm.
>
> #mediawiki-feed still gets the full firehose of all changes, if you
> are interested in that.
>
> Thanks!
>
> --
> Yuvi Panda T
> http://yuvi.in/blog
>


Woohoo! Thank you, Yuvi. :)

Note:
Current setup details are at
https://github.com/valhallasw/pywikibugs/blob/master/channels.py
docs are linked at
https://www.mediawiki.org/wiki/wikibugs
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Reducing botspam on #wikimedia-dev

2014-05-18 Thread Prateek Saxena
Thanks Yuvi! I was just about to put it on ignore :\

—prtksxna

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

[Wikitech-l] Reducing botspam on #wikimedia-dev

2014-05-18 Thread Yuvi Panda
Hello everyone!

I just merged a change into the new wikibugs that will help reduce
botspam on #wikimedia-dev. wikibugs will no longer report bugs on
#wikimedia-dev that have been reported in other channels, thus
reducing duplication. The previous behavior was that wikibugs will
ping multiple channels - mobile bugs went to both #wikimedia-mobile
and #wikimedia-dev, flow bugs to both #wikimedia-corefeatures and
#wikimedia-dev, etc. Now they only go to the primary channel and
bypass -dev. So mobile bugs will only go to #wikimedia-mobile, and not
to #wikimedia-dev. This also matches the behavior of grrrit-wm.

#mediawiki-feed still gets the full firehose of all changes, if you
are interested in that.

Thanks!

-- 
Yuvi Panda T
http://yuvi.in/blog

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

Re: [Wikitech-l] Transcluding non-text content as HTML on wikitext pages

2014-05-18 Thread Gabriel Wicke
On 05/18/2014 02:28 AM, Subramanya Sastry wrote:
> However, in his previous message, Gabriel indicated that
> a property in the JSON/XML response structure might work better for
> multi-part responses.

The difference between wrapper and property is actually that using inline
wrappers in the returned wikitext would force us to escape similar wrappers
from normal template content to avoid opening a gaping XSS hole.

A separate property in the JSON/XML structure avoids the need for escaping
(and associated security risks if not done thoroughly), and should be
relatively straightforward to implement and consume.

Gabriel

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