The amount of times I've viewed a photo on Wikipedia and thought wow
and wanted to thank the contributor for putting it there for me to
Also it always seemed strange to me that I couldn't thank someone for
creating a page...
On Sun, Sep 21, 2014 at 1:49 PM, Jon Robson <jdlrobson(a)gmail.com> wrote:
> The amount of times I've viewed a photo on Wikipedia and thought wow and
> wanted to thank the contributor for putting it there for me to see.
> Also it always seemed strange to me that I couldn't thank someone for
> creating a page.
> On 12 Sep 2014 15:50, "Matthew Flaschen" <mflaschen(a)wikimedia.org> wrote:
>> On 09/12/2014 02:28 PM, James Salsman wrote:
>>> How many estimated days of developer work is the "major can of worms" of
>>> delivering thank notifications only, in a new way, to IPs? As cans of
>>> worms go, I'm pretty sure it would not be on the major end of the scale,
>>> if an experienced developer actually quantified it.
>> I doubt we would make a whole new backend just for anon recipients of
>> Thanks. That leaves only two possibilities:
>> * Have Echo support anonymous recipients
>> (https://bugzilla.wikimedia.org/show_bug.cgi?id=56828). Apparently Wikihow
>> has code for this, and there is a WIP patch, but Wikihow doesn't have the
>> exact same infrastructure as us.
>> * Use an existing backend, probably user talk pages (or maybe Flow user
>> talk pages, assuming anon talk pages are eventually converted over to this)
>> Matt Flaschen
>> EE mailing list
Shahyar, Juliusz, Trevor, Roan and I met to discuss using oojs inside
the mobile and Flow projects.
The following 3 patches kicks off moving MobileFrontend's class model
towards that of oojs - many thanks for Roan for doing most of the
On the long term we'd look to swap out the Class.js and
eventemitter.js files in MobileFrontend for oojs, but this is going to
be tricky and require some care, possibly mixing both oojs and
MobileFrontend's class code in the repository at the same time. e.g.
longterm. The MobileFrontend core development team will need to work
out how best to manage this transition.
modules with element management per the currently-accepted use of
OOjs, it is unclear how we may go about integrating with OOjs fully.
However, some potential use cases have been identified as candidates
for implementing OOjs on an interim basis, primarily by abstracting
some current FlowBoardComponent workflows, such as those which handle
(re-)rendering of existing and new content fetched from the API.
There's an ugly bug on En.WP today -- there's some broken JS on Topic
pages, so the reply field doesn't open properly, and you can't click the
buttons. Erik is going to deploy a fix for this as soon as we can.
I-3 (change page title to Topic name on Board name) -- has a patch ready to
Found and fixed a fatal error yesterday
Today -- fixing the en.wp bug, then something from the Sprint I column
G-11 (new modal dialog) -- the version on ee-flow needs a little more work.
Clicking outside automatically closes the modal, even if you've typed in
the dialog. Fix for this: Disable clicking outside the modal for now. At
some point in the near future, we'll drop in OOJS and integrate the events.
Also: the modal looks weird with the X and Check in the top corners -- that
design is only used for multi-step dialogs. Taking them out for this modal.
Forwarding. Please take this opportunity to ask questions!
---------- Forwarded message ----------
From: "Siko Bouterse" <sbouterse(a)wikimedia.org>
Date: Sep 18, 2014 3:30 PM
Subject: [Wikimedia-l] Upcoming help sessions for drafting Individual
Engagement Grant proposals
As we announced earlier this month, September is the month to apply for
an Individual Engagement Grant. The deadline to submit a proposal is
To help you turn your ideas and projects into successful proposals, we’re
hosting a few IdeaLab Proposal Clinics in Hangouts and IRC this month.
The first one took place on September 16. Newcomers had a chance to talk to
current and past grantees, as well as WMF Grantmaking staff, to workshop
ideas and strengthen their proposals.
If you have an idea you would like to submit, but feel unsure about how to
draft or finalize your proposal, join a session! There are three events
left before the deadline:
* IRC office hours in #wikimedia-office - Sept 23, 1600 UTC (Tuesday)
* Hangout - Sept 25, 1700 UTC (Thursday) 
* Hangout - Sept 28, 1700 UTC (Sunday) 
Join us next week to discuss your ideas, and bring any questions you have
IdeaLab Clinic II. Join via Hangout:
 IdeaLab Clinic III. Join via Hangout:
Head of Individual Grants
Wikimedia Foundation, Inc.
*Imagine a world in which every single human being can freely share in the
sum of all knowledge. *
*Donate <https://donate.wikimedia.org> or click the "edit" button today,
and help us make it a reality!*
Wikimedia-l mailing list, guidelines at:
Regression patches -- most of the regressions we found yesterday will be
fixed in today's release.
Working on search tomorrow -- he'll be talking to Nik and Chad next week.
Shahyar worked on a regression ticket, Erik finished it up
Spent a lot of time arguing with people about whether to merge stuff into
core. But at least people showed up to comment. :) So apparently this is
the way to get people to comment on your stuff -- just merge it. S points
out that probably the best day to do that is Monday, rather than right
before the release. We have learned many things.
S couldn't get the dialog patch up on eeflow yesterday -- try again today.
Watchlist star refactoring -- Shahyar was getting an exception from browser
test. Fixed it this morning, it's working again. He needs to rebase it off
Today -- working on H-8 (add the ability to put hide / delete / suppress
functions on history & other non-board pages)
Fixed up lots of the regressions -- some Danny identified, and some Erik
found along the way.
The only one that still needs to go through -- dismissing new topic
notifications by going to the board. We still need to work on this some
Danny will have to do another pass checking everything out at the release,
and we'll see what else needs fixing. We've patched up a lot -- there will
be some more bugs to squash, but we're getting close. :)
There were some regressions found today on ee-flow -- we should fix them,
and merge the fixes for tomorrow's release if they're not risky. We can
propose them today and get +2.
H-99 (Locked and hidden pages should be uncollapsed on the topic pages)
H-106 (Wikilinks in subpage boards are incorrect)
Submitted WIP patch for Special:Flowify.
X-15 -- Jon had feedback on watchlist stars to make the hack slightly less
hacky. We need to get that code reviewed and on eeflow as soon as we can.
Now working on search. Back-end stuff is fully functional. Need some
Modal -- now in code review!
Should write unit tests for modal event handling
Today: Look at regressions on ee-flow and merge them for tomorrow's release
Several front end engineers, designers, and others got together again
to update on their progress to standardize icons across projects
today. This was a follow to the previous conversation on 8/27 .
Big take aways:
* Monte iterating and almost completing his SVG->Font python scripts
* Trevor & Bartosz finalizing an npm module for customizing SVG generation
* Jon needing additional support from Sam to move forward on mw ui icon markup
Notes from the discussion can be found on etherpad 
Follow up items:
* Finish up SVG2FONT2SVG script (hopefully done in a week) (Monte)
** Create manifest for padding and other small options (Trevor)
* Review Trevor's SVG/PNG generation (Everyone present once its out)
* Followup with Sam for standard icon html mark-up (Matt)
* Schedule team discussion follow up (Tomasz)
Please update as necessary if you attended and I've forgotten or
 - https://lists.wikimedia.org/pipermail/mobile-l/2014-August/007922.html
 - http://etherpad.wikimedia.org/p/IconStandardization
Sprint H ends tomorrow.
Code review today, merged a lot of patches. Found a problem with Shahyar's
We talked about how to handle the watch star in Vector and Monobook. The
current patch is a hack, and may cause problems down the line, but we need
to have the tooltip that explains what subscribing to a board means. We're
almost certain to change something about this in the near-ish future, so
this won't be dropped and forgotten.
The new watch star patch should fix the problems with the star on Monobook
(X-7 and X-8).
Working on fixes for the Hide modal, to center it and make it look like a
real modal dialog (G-11). This involves H-9: allow external elements to be
related to a Flow component.
The patches work, but it's breaking some other elements. He'll fix that
Yesterday, mostly H-5 -- When a topic is locked, take out all reply links.
It's in code review.
Danny asked him to look at H-99 -- it's a change that Jon worked on and
released, to always keep moderated threads uncollapsed on topic pages.
So I think by now, most of us have experienced the positive impact of the
Thanks tool (https://www.mediawiki.org/wiki/Extension:Thanks) on our wikis.
I'd like to hear thoughts about adding the function to more places. Thanks
currently visible on...
- Page histories
I'd like to propose that anywhere that I can undo or rollback an edit, I
should be able to thank someone. If that location provides me enough
information to revert an edit, surely it provides me enough context to show
gratitude as well. With that proposal in mind, some suggestions of new
A slightly expanded scope might also include all public logs (move, delete,
patrol, etc.). This is requested already at
https://bugzilla.wikimedia.org/show_bug.cgi?id=58485 but may be harder to
Script to delete old notifications is done, needs testing on eeflow or
betalabs to make sure we have the cron job to run the job queue.
Once that's done, we can release putting unread messages in chronological
H-2 -- email notifications -- it works, should go in code review.
Benny's last day -- S says that he's cleared for takeoff.
G-102 -- "no formatting defined for notification" error -- there's a patch
so we get more information on this.
There's a bunch of patches in code review.
X-12: Monobook -- Watch star tooltip.
S is talking to Shahyar about setting up a brown-bag on "think mobile
first", to make sure we know all the guidelines.
Yesterday -- swat deploy to release Echo fixes. (Thank you!)
Today -- getting into the code review list.
Shahyar can't log in...
There's a patch for the Hide modal dialog on Monobook, which we were hoping
to backport yesterday. S will check with Shahyar to see the status.
The remaining issues are for Monobook -- Erik talked to Chris McMahon about
running browser tests for a user with Monobook as the skin.