[Wikitech-l] Fwd: [Wikimedia-l] Wikimania 2016 scholarship applications open

[Quim Gil]

For your information:

"Applications are open until Saturday, January 09 2016 23:59 UTC."

-- Forwarded message --
From: Martin Rulsch 
Date: Tue, Dec 8, 2015 at 10:26 PM
Subject: [Wikimedia-l] Wikimania 2016 scholarship applications open
To: "Wikimania general list (open subscription)" <
wikimani...@lists.wikimedia.org>, Wikimedia Mailing List <
wikimedi...@lists.wikimedia.org>


Thanks again, Dan Garry, for pointing me on this again-ill formatted mail.

Cheers,
Martin

Hi all, Scholarship applications for Wikimania 2016 which is being held in
Esino Lario, Italy on June 22–27, 2016 are now being accepted. Applications
are open until Saturday, January 09 2016 23:59 UTC. Applicants will be able
to apply for a partial or full scholarship. A full scholarship will cover
the cost of an individual's round-trip travel, shared accommodation, and
conference registration fees as arranged by the Wikimedia Foundation. A
partial scholarship will cover conference registration fees and shared
accommodation. Applicants will be rated using a pre-determined selection
process and selection criteria established by the Scholarship Committee and
the Wikimedia Foundation, who will determine which applications are
successful. To learn more about Wikimania 2016 scholarships, please visit:
https://wikimania2016.wikimedia.org/wiki/Scholarships To apply for a
scholarship, fill out the multi-language application form on:
https://scholarships.wikimedia.org/apply It is highly recommended that
applicants review all the material on the Scholarships page and the
associated FAQ ( https://wikimania2016.wikimedia.org/wiki/Scholarships/FAQ
) before submitting an application. If you have any questions, please
contact: wikimania-scholarships at wikimedia.org
 or leave a message at:
https://wikimania2016.wikimedia.org/wiki/Talk:Scholarships Please help us
spread the word! Best regards, for the Scholarship Committee
https://wikimania2016.wikimedia.org/wiki/Scholarship_committee
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,




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

[Wikitech-l] Reading department planning for next quarter

[Moushira Elamrawy]

Hello Everyone,

Hope you are enjoying the approach of the end of the year.  In the last 3
months the reading team has worked on a process for open strategy planning
[0], in order to define priorities, and align tests and products that the
team works on, with broader movement goals.

Given the strategy work, planning for Q3 (the next quarter: Jan - March) is
different; the team is sharing its roadmap for Q3 and Q4 [1], as well as
the actions planned for Q3 [2] early on. Despite of the strategy work and
planning, these documents are still work in progress; adaptations and
changes are likely to take place, given the time frame and tests included.
However, the team is sharing early in order to accommodate feedback.  You
can also add suggestions for Q4 (Apr - Jun), as long as they align with the
roadmap.

This is the first team the team shares its plans early and openly, and
allows room for feedack and suggestions in future planning. We trust that
the open process will help with better engagement and more lessons to learn
on best practices.

Enjoy December!


All the best,
M


[0] https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Testing
[1] https://www.mediawiki.org/wiki/Reading/Roadmap
[2] https://www.mediawiki.org/wiki/Reading/Quarterly_Planning/Q3
[3] https://www.mediawiki.org/wiki/Reading/Quarterly_planning/Q4
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Who owns (or should own) OOjs UI?

[Brad Jorsch (Anomie)]

On Sun, Dec 6, 2015 at 7:30 PM, Bartosz Dziewoński 
wrote:

> On 2015-12-04 18:59, Adam Baso wrote:
>
>> I do wonder though if we've spent much time studying the ease of getting
>> at
>> least some part of oojs-ui split out or making it so that new stuff going
>> forward is part of the oojs-ui family but it's not as monolithich?
>>
>
> Not any more than what is written at <
> https://phabricator.wikimedia.org/T113681#1673158>, as far as I know.
>
> OOjs UI doesn't have a dedicated team (or even a dedicated person)
> supporting it. The changes are mostly driven by whatever the VisualEditor
> or Design teams need, and what they are willing to implement themselves
> (and to a lesser extent, Multimedia team and random people like Brad or
> Florian). This makes it difficult to make any big changes happen.
>

If OOjs UI is the thing that we're supposed to be using in the future for
our UI stuff, it's very concerning that further development is blocked on
T113681 but no one is planning on working on that task or feels ownership
for the thing.

Is someone going to step up to actually own and maintain the thing? Or
should we consider declaring it a failure and figure out a plan to move
away from it, if no one wants to maintain our home-grown JS UI library
anymore?


-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Product Department Office Hour with Wes Moran, Thursday, 10 December

[Sam Klein]

Thanks Rachel, this sounds interesting & seems of broad interest!  Perhaps
worth announcing on some of the larger WP's too?

I've always thought some of these weekly meetings would make interesting
banners for only logged-in users; set at a low % or # of total impressions
to match the amount of participation you'd like to see.  Depends on which
body of users you want to reach.

Warmly,
SJ

On Wed, Dec 9, 2015 at 3:06 PM, Rachel diCerbo 
wrote:

> Hello,
>
> I wanted to send a reminder that office hours with Wes Moran will be in 24
> hours. You can participate by joining the #wikimedia-office channel on
> freenode. The general topic is around product development, so if you have
> questions around process or individual products, please drop by!
>
> Information at meta is here:
> https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
> Timezone information is here:
>
> https://www.timeanddate.com/worldclock/fixedtime.html?hour=20=00=0=10=12=2015
>
> Talk with you tomorrow,
> rachel
>
>
>
>
>
>
> On Thu, Dec 3, 2015 at 8:36 PM, Rachel diCerbo 
> wrote:
>
> > Hi there,
> >
> > The WMF has scheduled an office hour with Wes Moran, VP of Product, for
> > Thursday 10 December, at 20:00 UTC. We can use the time as an informal
> meet
> > and greet, or ask questions about product process, strategy, and
> planning.
> > You can participate in #wikimedia-office on Freenode, and logs will be
> > posted afterwards.
> >
> > You can find the relevant information, including your timezone, here:
> > https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
> >
> > Hope to see you there :)
> > rachel
> >
> >
> > --
> >
> > Rachel diCerbo
> > Director of Community Engagement (Product)
> > Wikimedia Foundation
> > Rdicerb (WMF)
> > 
> @a_rachel
> > 
> >
>
>
>
> --
>
> Rachel diCerbo
> Director of Community Engagement (Product)
> Wikimedia Foundation
> Rdicerb (WMF)  >
> @a_rachel 
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> wikimedi...@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>



-- 
Samuel Klein  @metasj  w:user:sj  +1 617 529 4266
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Who owns (or should own) OOjs UI?

[Brad Jorsch (Anomie)]

On Wed, Dec 9, 2015 at 2:40 PM, Brion Vibber  wrote:

> Unfortunately since the mid-2015 Engineering department reorgs, there is no
> such team...
>

I agree, such a team should be created. I'll be first in line to sign up,
and as part of such a team I'd be happy to help "own" OOjs UI (although I'd
not be comfortable being the lead on owning it).


> If we can't lobby management to (re)create one, we'll have to set up a
> "cross-functional" skunkworks team if we want anything big to get done.
>

IMO a skunkworks team for critical infrastructure would be a sad outcome.


> I would love to be involved, but I'm already stretched thin with
> multimedia-related commitments and probably don't have time to be the main
> point person. But if there's a few others who would like to chip in...
> maybe we can make some decisions and push some code around!
>

Me too, with the API and the AuthManager project. Plus I don't understand
our JS ecosystem well enough to perform the requisite major surgery on OOjs
UI without hand-holding from someone who does know how the packaging should
work.


-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Who owns (or should own) OOjs UI?

[James Forrester]

Short-cut answer to the title question: Me.

On 9 December 2015 at 10:26, Brad Jorsch (Anomie) 
wrote:

> On Sun, Dec 6, 2015 at 7:30 PM, Bartosz Dziewoński 
> wrote:
>
> > On 2015-12-04 18:59, Adam Baso wrote:
> >
> >> I do wonder though if we've spent much time studying the ease of getting
> >> at
> >> least some part of oojs-ui split out or making it so that new stuff
> going
> >> forward is part of the oojs-ui family but it's not as monolithich?
> >
> > Not any more than what is written at <
> > https://phabricator.wikimedia.org/T113681#1673158>, as far as I know.
> >
> > OOjs UI doesn't have a dedicated team (or even a dedicated person)
> > supporting it. The changes are mostly driven by whatever the VisualEditor
> > or Design teams need, and what they are willing to implement themselves
> > (and to a lesser extent, Multimedia team and random people like Brad or
> > Florian). This makes it difficult to make any big changes happen.
> >
>
> If OOjs UI is the thing that we're supposed to be using in the future for
> our UI stuff, it's very concerning that further development is blocked on
> T113681


​"Further development" is not blocked​ on this task. A few things that some
people want to do are. Please do not exaggerate for effect to try to get
your way. I'm sorry that we disagree as to whether your patch belongs in
the library in its current form.


> but no one is planning on working on that task or feels ownership
> for the thing.
>

​The value-add of doing that accrues to the people currently not using
OOUI.​ The work is, and has always been, a group effort by engineers,
designers and product people making our front-end architecture more sane
and consistent. Responsibility for change lies with those that want it and
can justify the time, mostly. This is the same model as used for most
shared things around MediaWiki. The passion, care and effort from volunteer
and staff developers that goes into improving the library as people extend
its use to more places is great. I'd love for there to be dedicated
engineers to support the use of OOUI, but however.


> Is someone going to step up to actually own and maintain the thing?


​I am, and remain, the product owner responsible since 2012.​ The plan was
to transfer the product/design side of it entirely to Volker, but we've not
formally 'handed over the keys' yet. It doesn't appear that there's a
particular rush, given the lack of movement to re-do how skins in MediaWiki
work, as had been the ambition in 2013.

​[Trim the rest.]

​J.
-- 
James D. Forrester
Lead Product Manager, Editing
Wikimedia Foundation, Inc.

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

Re: [Wikitech-l] Tech Talk: Secure Coding For MediaWiki Developers: December 09

[Chris Steipp]

Just a reminder this is starting in one hour!

On Thu, Dec 3, 2015 at 1:54 PM, Rachel Farrand 
wrote:

> Please join for the following tech talk:
>
> *Tech Talk**:* Secure Coding For MediaWiki Developers
> *Presenter:* Darian Patrick
> *Date:* December 09, 2015
> *Time: *23:00 UTC
> <
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Secure+Coding+For+MediaWiki+Developers=20151209T2330=1440=1
> >
> Link to live YouTube stream 
> *IRC channel for questions/discussion:* #wikimedia-office
> Google+ page
> <
> https://plus.google.com/u/0/b/103470172168784626509/events/cv74aqvumuu4k4cflh0gcfcv33g
> >,
> another
> place for questions
>
> *Summary: *This talk will present material to aid MediaWiki developers in
> secure programming practices. The talk will draw on information from
> https://www.mediawiki.org/wiki/Security_for_developers, the CWE-25 (
> https://cwe.mitre.org/top25/), other resources, in an attempt to elucidate
> topics pertinent to core and extension developers.
> ___
> 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] Product Department Office Hour with Wes Moran, Thursday, 10 December

[Rachel diCerbo]

Hello,

I wanted to send a reminder that office hours with Wes Moran will be in 24
hours. You can participate by joining the #wikimedia-office channel on
freenode. The general topic is around product development, so if you have
questions around process or individual products, please drop by!

Information at meta is here:
https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
Timezone information is here:
https://www.timeanddate.com/worldclock/fixedtime.html?hour=20=00=0=10=12=2015

Talk with you tomorrow,
rachel






On Thu, Dec 3, 2015 at 8:36 PM, Rachel diCerbo 
wrote:

> Hi there,
>
> The WMF has scheduled an office hour with Wes Moran, VP of Product, for
> Thursday 10 December, at 20:00 UTC. We can use the time as an informal meet
> and greet, or ask questions about product process, strategy, and planning.
> You can participate in #wikimedia-office on Freenode, and logs will be
> posted afterwards.
>
> You can find the relevant information, including your timezone, here:
> https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
>
> Hope to see you there :)
> rachel
>
>
> --
>
> Rachel diCerbo
> Director of Community Engagement (Product)
> Wikimedia Foundation
> Rdicerb (WMF)
> @a_rachel
> 
>



-- 

Rachel diCerbo
Director of Community Engagement (Product)
Wikimedia Foundation
Rdicerb (WMF) 
@a_rachel 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Who owns (or should own) OOjs UI?

[Brad Jorsch (Anomie)]

On Wed, Dec 9, 2015 at 3:40 PM, James Forrester 
wrote:

> Short-cut answer to the title question: Me.
>

I'm glad to hear that you are accepting responsibility for OOjs UI
development! Do you have a timeline on a fix for T113681, or a page that
indicates what higher-priority development you and your team are working on
in the near future?


> > If OOjs UI is the thing that we're supposed to be using in the future for
> > our UI stuff, it's very concerning that further development is blocked on
> > T113681
>
> ​"Further development" is not blocked​ on this task. A few things that some
> people want to do are.


Let's not chop logic here. If "a few things that some people want to do"
cannot be done due to T113681, then T113681 is indeed blocking some further
development even if other further development isn't blocked. This email
thread isn't even about
T113681 specifically, it's about that there are no development resources
for fixing things in OOjs UI unless someone is willing to do it as a
skunkworks project, and OOjs UI isn't yet a finished product where we might
be able to justify that.

I'm disappointed that you don't think that the fact that "some things
people want to do" are blocked and no development resources are available
to remedy the situation is cause for concern. When the situation was
brought up in today's Scrum of Scrums, the consensus was that it is indeed
concerning.


> Please do not exaggerate for effect to try to get your way. I'm sorry that
> we disagree as to whether your patch belongs in the library in its current
> form.
>

Since you brought it up, let's look at my patch. There are two concrete
blockers that have been raised on my patch. Neither of them actually have
to do with the form of the patch itself.

The long-standing blocker has been disagreement over how the widget can be
internationalized in the context of OOjs UI: The Language and translatewiki
faction wants OOjs UI developers to integrate cldrjs, while the OOjs UI
developers are unwilling to make any decision as to whether cldrjs is the
way to go or translatewiki will just have to deal with providing
translations for month and weekday names as they do for everything else.
The closest we have to a decision is really a cop-out: "shove it into
MediaWiki even though it doesn't belong there, because MediaWiki already
happens to have most of the needed i18n strings and we can't make any
decision here".

In last week's Scrum of Scrums, you brought up T113681 as a new blocker:
OOjs UI is already too large, so we can't add new stuff until someone
reworks it to be able to load individual components. MatmaRex then stated
that no one owns or maintains OOjs UI to the extent that we can expect T113681
to be solved any time soon, which brought the lack of maintainership in
OOjs UI into clear view.

MatmaRex also raised some other objections (disagreement with Design's
design, non-use of moment.js despite moment.js not gaining us anything,
doubt that anyone actually needs  despite evidence
to the contrary), but no one else has agreed with those and he hasn't
deigned to respond to attempts at further discussion in Gerrit.

If you have objections to the actual form of my patch, as opposed to lack
of a willingness to make any decision on the i18n issue or any progress on
the form of OOjs UI as a whole, you should raise them in Gerrit instead of
continuing to sit on them. Although I wonder why you haven't done so
already.


-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Procedural updates to the RFC process (Re: Objections to PHP 5.5 version requirement)

[Legoktm]

Hi,

On 12/02/2015 09:52 PM, Rob Lanphier wrote:
> We also discussed having some sort of minimum discussion time on
> wikitech-l prior to having the decision-oriented RFC meeting.  That
> seems sensible, with the caveat that we discussed: we should ask that
> those proposing RFCs announce their intention on wikitech-l, directing
> the conversation toward the Phab ticket associated with the RFC.  The
> Phab ticket should be the "discussion of record", whereas wikitech-l
> can be "announcement of record" (torturing the "newspaper of record"
> metaphor[2])

This has always been part of the RfC process[1] (steps 4-5), I think it
would be a good idea to enforce that all steps of the process have been
followed first before scheduling a meeting and making a decision.

[1]
https://www.mediawiki.org/wiki/Requests_for_comment/Process#Making_a_proposal

-- Legoktm

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

[Wikitech-l] Community Tech: November report

[Danny Horn]

Hi everyone, here's what the Community Tech team's been up to lately.

* Community Wishlist Survey: we've been running this survey to identify the
most important features and fixes to work on in 2016; you might have heard
about it because we've been spamming mailing lists and village pumps. If
you haven't checked it out yet -- the voting phase ends on Monday, please
come and vote for the proposals you want to support! There are a lot of
proposals, and many of them are awesome.
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

* Gadgets 2.0: A new Gadget Manager has been in the works for a long time,
to replace Mediawiki:Gadgets-definition as the interface for managing
gadgets on a wiki. Community Tech is helping to complete the feature -- in
November, we created new Gadget and Gadget_definition namespaces and
content models, and we're currently working on the Gadget Manager itself.
For more info: https://www.mediawiki.org/wiki/Gadgets_2.0 and
https://phabricator.wikimedia.org/T31272.

* GadgetUsage: We made some improvements to the Special:GadgetUsage report,
filtering out removed gadgets and adding a recently active users count. You
can see the improved report at
https://www.mediawiki.org/wiki/Special:GadgetUsage, and it'll roll out to
more projects next week.

* Citation bot: We've been working on getting Citation bot into shape;
check out https://phabricator.wikimedia.org/T108412 for more.

In December, we've got more work coming up on Gadget Manager, Citation bot
and storing WikiProject article assessment metadata. Plus come and vote in
the Wishlist Survey so that we have interesting things to work on in
January. Thank you and good night.

DannyH (WMF)
Community Tech



(cross-posted to Wikimedia-l, Wikitech-l and WMF staff lists, sorry for the
duplication)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wmfall] Community Tech: November report

[Ryan Kaldari]

Also, we should mention that most of the work for Gadgets 2.0 was
originally done by Timo and Kunal and they have been a huge help getting us
up to speed on it. We should have a demo up on Labs soon for people to play
with.

On Wed, Dec 9, 2015 at 5:10 PM, Danny Horn  wrote:

> Hi everyone, here's what the Community Tech team's been up to lately.
>
> * Community Wishlist Survey: we've been running this survey to identify
> the most important features and fixes to work on in 2016; you might have
> heard about it because we've been spamming mailing lists and village pumps.
> If you haven't checked it out yet -- the voting phase ends on Monday,
> please come and vote for the proposals you want to support! There are a lot
> of proposals, and many of them are awesome.
> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey
>
> * Gadgets 2.0: A new Gadget Manager has been in the works for a long time,
> to replace Mediawiki:Gadgets-definition as the interface for managing
> gadgets on a wiki. Community Tech is helping to complete the feature -- in
> November, we created new Gadget and Gadget_definition namespaces and
> content models, and we're currently working on the Gadget Manager itself.
> For more info: https://www.mediawiki.org/wiki/Gadgets_2.0 and
> https://phabricator.wikimedia.org/T31272.
>
> * GadgetUsage: We made some improvements to the Special:GadgetUsage
> report, filtering out removed gadgets and adding a recently active users
> count. You can see the improved report at
> https://www.mediawiki.org/wiki/Special:GadgetUsage, and it'll roll out to
> more projects next week.
>
> * Citation bot: We've been working on getting Citation bot into shape;
> check out https://phabricator.wikimedia.org/T108412 for more.
>
> In December, we've got more work coming up on Gadget Manager, Citation bot
> and storing WikiProject article assessment metadata. Plus come and vote in
> the Wishlist Survey so that we have interesting things to work on in
> January. Thank you and good night.
>
> DannyH (WMF)
> Community Tech
>
>
>
> (cross-posted to Wikimedia-l, Wikitech-l and WMF staff lists, sorry for
> the duplication)
>
> ___
> Wmfall mailing list
> wmf...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] ExtensionDistributor download statistics (try #2)

[Legoktm]

Hi,

Thanks to some awesome work by Addshore, ExtensionDistributor download
stats are now sent to graphite, and aggregated in a pretty dashboard[1],
which is filterable by branch and extension. (Note: the ordering is
sorted by max and not total, that's a known bug[2].)

The top 15 extensions and skins over the past 30 days are also shown on
Special:ExtensionDistributor[3] and Special:SkinDistributor[4].

[1]
https://grafana.wikimedia.org/dashboard/db/extension-distributor-downloads
[2] https://phabricator.wikimedia.org/T120337
[3] https://www.mediawiki.org/wiki/Special:ExtensionDistributor
[4] https://www.mediawiki.org/wiki/Special:SkinDistributor

-- Legoktm

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

[Wikitech-l] 2015-12-09 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-12-09


= 2015-12-09 =

== Reading ==

=== Android ===
* 2.1.135-beta-2015-12-03 published to beta only.
* 2.1.136-* release candidate to be published as beta soon.
** Only bug fixes and polish since v2.1.135.
** New Wikipedia Maps promotion from beta to prod to appear in this release.
** Final planned release of 2015.

=== iOS ===
* Doing regression testing before wider, public beta distribution of
Wikipedia 5.0.0
* Considering Mobile Content Service integration (perhaps as a beta
experiment) as Q3 "reach" goal
** (
https://www.mediawiki.org/wiki/Reading/Quarterly_Planning/Q3#iOS_Goals_.28not_all_committed.29)

=== Mobile Content Service ===
* 10% of Android Beta App users use the RB based service for link previews
(page summary) + page content

=== Reading Infrastructure ===
* We're concerned that oojs-ui is what we're supposedly wanting to move UI
stuff to, but oojs-ui is apparently unowned and development is blocked on
T113681 with no one planning to work on it (and people are being encouraged
to shove stuff into mw.widgets to hack around that block).
** ApiSandbox is now theoretically blocked on Brad finding time to apply
said hack, since we've determined oojs-ui isn't getting new functionality
any time soon..

== Technology ==

=== Security ===
* Reviews: ArticlePlacement (waiting for wikidata), Thumbor in progress,
RevisionJumper this week
* Secure Code training today, 3:30pm PST -
https://lists.wikimedia.org/pipermail/wikitech-l/2015-December/084213.html
* Need help: T118769 (Ops, someone who can help with vcl)
* Goals: 2FA for wiki accounts, and possibly changes to Javascript
permisions (T120889, T120886) . Input welcome.
**
https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Goals_201516#Q3_.28Jan-Mar_2016.29

=== Technical Operations ===
* Blocking: none
* Blocked by: none
* Updates:
* Migration from OpenDJ to OpenLDAP successful. Some minor wake from
the migration, solved today
* ops get their yuvikeys one by one
* moving on with scaling alerting monitoring
* drafting Q3 goals

=== Services ===
* Actively working with RelEng on Scap3
:* Current goal: set up AQS in beta
* RESTBase v0.9.0 released
:* many config style changes
:* Analytics - need to coordinate next deploy (config changes)
:* move RESTBase to service::node -
https://gerrit.wikimedia.org/r/#/c/257898/
* EventBus
:* extension emitting events now in Beta, after tests moving to prod (next
week)
:* need security review
:* HTTP proxy service work continues (Analytics)
:* working on change propagation
* CXServer move to service-runner
:* let's schedule the actual merge/deploy, Kartik, Alex
* Goals for next Q: https://phabricator.wikimedia.org/T118868
:* finalisation tomorrow
:* if you have JobRunner jobs, we'd like to talk to you about moving them
to the EventBus

== Release Engineering ==
* *Blocking*: (none)
* *Blocked by*: (none)
* *Updates*:
** Scap3 refactoring and tech debt cleanup
*** https://phabricator.wikimedia.org/project/view/1449/
*** Deployed AQS in Beta Cluster
*** Moving on to support Mathoid
*** One Q3 goal is to support MediaWiki deployments
** Rolling responsibility of cutting MediaWiki branches
*** Bear with noobs

== Discovery ==
* Portal A/B test launched
* Completion suggesters beta feature deployed soon
* Working on Q3 goals
* No blocking/blockers

=== Maps/Graphs ===
* interactive graphs are on the train -
https://test.wikipedia.org/wiki/DynamicGraph
* Do not perform image quality reduction for any zero partners, or it may
corrupt image URLs
* Will push kartographer extension to beta cluster


== Fundraising Tech ==
* Tiny, conservative fixes to Central Notice and payments-wiki
* Bunch of new visualizations for the internal fundraising dashboard
* Dealing with interesting behaviors of the new CiviCRM verison
** Actually upstreaming a bunch of fixes!
* Watching donation streams and error logs
* More testing of backup credit card processor
* Gathering stats on donatewiki clicks
** Will replace 3rd-party email performance tracking, which has been
redirecting users through weird-looking domains

==Community Tech==
* Wrapping up Wishlist Survey
* Working on Gadgets 2.0
* PageAssessments extension - need some help figuring out job/database
scalability

== Editing ==

=== Parsing ===
* Discovered use of "wikitext as a database" page (
https://ur.wikipedia.org/wiki/%D9%86%D8%A7%D9%85_%D9%85%D9%82%D8%A7%D9%85%D8%A7%D8%AA_%DA%A9%DB%92
)
that was being updated multiple times a minute by bots
** Let to a 80% and higher load on the Parsoid cluster over the last 4-6
hours because the DOM is larger than what Parsoid can reliably handle.
** Filed https://phabricator.wikimedia.org/T120972: Introduce configurable
wt2html/html2wt to deal with this; On the RESTBase end, there is
https://phabricator.wikimedia.org/T120971 (Blacklist automatic updates for
especially expensive pages)
___
Wikitech-l mailing list

Re: [Wikitech-l] Improving CAPTCHA friendliness for humans, and increasing CAPTCHA difficulty for bots

[Pine W]

Hi, just checking to see if CAPTCHA improvements are likely anytime in the
near future. I notice that
https://phabricator.wikimedia.org/project/board/225/ shows nothing under
"Awaiting code review". Is anyone working on this? If not, what kind of
nudge would be necessary to get some resources devoted to CAPTCHA
improvements?

Thanks,
Pine

On Tue, Aug 25, 2015 at 6:48 PM, Brian Wolff  wrote:

> On 8/25/15, Dan Garry  wrote:
> > On 19 August 2015 at 23:06, Matthew Flaschen 
> > wrote:
> >>
> >> I agree this is an important issue.  It just isn't resourced right now
> by
> >> the WMF, as far as I know.
> >>
> >
> > Indeed. There have been numerous discussions about the captcha on this
> > mailing list over the past few years, but no progress because this issue
> > just isn't being worked on by anyone.
> >
> > Dan
> >
>
> Well there's that, but its also because its very unclear what "we"
> actually want and how we would get there.
>
> Make captchas not suck, well a great goal, is not an action plan in itself.
>
> --
> -bawolff
>
> ___
> 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] Who owns (or should own) OOjs UI?

[Brion Vibber]

OOjs UI is used as a core component of MediaWiki's user interfaces,
including heavy use in WMF-sponsored initiatives such as VE and Flow and
slowly increasing use within core; as such it should probably be maintained
by the MediaWiki Core team at Wikimedia Foundation.

Unfortunately since the mid-2015 Engineering department reorgs, there is no
such team... If we can't lobby management to (re)create one, we'll have to
set up a "cross-functional" skunkworks team if we want anything big to get
done.


I would love to be involved, but I'm already stretched thin with
multimedia-related commitments and probably don't have time to be the main
point person. But if there's a few others who would like to chip in...
maybe we can make some decisions and push some code around!

-- brion

On Wed, Dec 9, 2015 at 10:26 AM, Brad Jorsch (Anomie)  wrote:

> On Sun, Dec 6, 2015 at 7:30 PM, Bartosz Dziewoński 
> wrote:
>
> > On 2015-12-04 18:59, Adam Baso wrote:
> >
> >> I do wonder though if we've spent much time studying the ease of getting
> >> at
> >> least some part of oojs-ui split out or making it so that new stuff
> going
> >> forward is part of the oojs-ui family but it's not as monolithich?
> >>
> >
> > Not any more than what is written at <
> > https://phabricator.wikimedia.org/T113681#1673158>, as far as I know.
> >
> > OOjs UI doesn't have a dedicated team (or even a dedicated person)
> > supporting it. The changes are mostly driven by whatever the VisualEditor
> > or Design teams need, and what they are willing to implement themselves
> > (and to a lesser extent, Multimedia team and random people like Brad or
> > Florian). This makes it difficult to make any big changes happen.
> >
>
> If OOjs UI is the thing that we're supposed to be using in the future for
> our UI stuff, it's very concerning that further development is blocked on
> T113681 but no one is planning on working on that task or feels ownership
> for the thing.
>
> Is someone going to step up to actually own and maintain the thing? Or
> should we consider declaring it a failure and figure out a plan to move
> away from it, if no one wants to maintain our home-grown JS UI library
> anymore?
>
>
> --
> Brad Jorsch (Anomie)
> Senior Software Engineer
> Wikimedia Foundation
> ___
> 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