---------- Forwarded message ----------
WikiConference USA 2015 will be held *October 9–11* at the U.S. National
Archives in Washington, D.C.
Registration and scholarship applications are open. Session proposals may
I've been trying to encourage a certain structure to our weekly IRC
meetings, by means of some brief statements in the meeting and by
talking to people afterwards about what I was trying to achieve. But
this approach has led to frustration and miscommunication. I think
it's about time I wrote my thoughts out in full for everyone.
What I want is pretty modest and achievable.
I want to have a brief wrap-up period, lasting 5-10 minutes at the end
of the meeting, where the regular flow of discussion is suspended, and
we instead focus on helping the RFC author and other implementors, by
producing action items, meeting summary notes, and if possible, RFC
resolution (acceptance or rejection).
At the end of this wrap-up period, the #endmeeting command will be
given. Then you are free to continue your discussions unlogged,
without expecting all relevant parties to remain in attendance.
We are all engineers, and we love thinking about hard problems and
clever solutions. That is why it is important that discussion be
suspended. Otherwise, it is too difficult to focus on the meeting goals.
-- Tim Starling
Two security patches are being merged (Jenkins is processing now for the
Flow one, TextExtracts already merged) for TextExtracts and Flow:
It is recommended to upgrade to these if possible. There is a possible
vulnerability if you are running both TextExtracts and Flow (may nor may
not affect other extensions with TextExtracts):
TLDR: Performance audit of the mobile site, please help & chime in
The Reading web team is focusing on performance of the site in one of
goal <https://phabricator.wikimedia.org/T104432>s, specially the mobile
version to improve the experience of all our users on the least powerful
As part of such goal we've (Baha & Jon) conducted an initial performance
audit of the mobile site, where we've discovered a few interesting facts,
mostly regarding how images are loading and how they are not cached.
We encourage you to read up the phab task
https://phabricator.wikimedia.org/T105365#1477762 and if it is of your
interest try and help us understand the highest impact areas where we'll be
able to improve the performance of the site, and technical problems you can
foresee in performance profiles of it.
Thanks a lot,
Hi Community Metrics team,
this is your automatic monthly Phabricator statistics mail.
Number of accounts created in (2015-07): 264
Number of active users (any activity) in (2015-07): 797
Number of task authors in (2015-07): 454
Number of users who have closed tasks in (2015-07): 256
Number of projects which had at least one task moved from one column
to another on their workboard in (2015-07): 182
Number of tasks created in (2015-07): 3233
Number of tasks closed in (2015-07): 2576
Number of open and stalled tasks in total: 24477
Median age in days of open tasks by priority:
Unbreak now: 39
Needs Triage: 92
Needs Volunteer: 535
(How long tasks have been open, not how long they have had that priority)
TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.
Fab Rick Aytor
(via community_metrics.sh on iridium at Sat Aug 1 00:00:07 UTC 2015)