Two bugs ready to backport:
-- Lock topic reason appears twice in hidden topic titlebar (I-102)
-- Repeated topics showing up in scroll (I-103)
*Erik*:
Worked on patch for duplicated topics I-103 -- it was related to Hide
changes. Matthias fixed a bug and passed it through, ready to deploy today.
Submitted several patches (about recent changes?) into one.
Today: "No formatting defined for notification" error -- it's been on the
back burner, should look at it again today.
*Matt*:
Talked to mobile team about the ToC work. Didn't hear anything from mobile
web, Dan G said
Looks on app -- Flow doesn't work properly. Filed bugs about False title --
clicking links talke you to web.
Submitted a patch for HHVM.
Figured out Cirrus Search -- filed bug about case sensitive titles.
Submitted patch to remove new level of directory tray.
Reviewed last patch in the chain for I-102.
Today: start with RTL bug. Danny will bring some more bugs in from the
backlog if they're needed.
*Matthias*:
Noticed we have php unit tests intermittently failing. Spent time looking
into it -- tried to trigger unit tests, and couldn't. Will look into it
more tomorrow. Assume it's an issue with Jenkins that we don't have to
worry about, but it might be related to cache refactors.
Then will resume search work tomorrow.
*Shahyar*:
Yesterday had hailstorm-related power outage.
Today: A few patches to update.
Putting up patch for H-8 -- add hide etc to board history. Will put up a
patch and add that to the
*Matt*:
Yesterday, walked through the code with Erik to get more familiar.
Worked on mw-ui patch for anchors and mw-ui bugs. It's in review, hoping
for Shahyar or Jon to look at it.
*Erik*:
Yesterday - worked with Matt.
Did code review on Shahyar's stuff.
Worked on fatal exception bug.
I-102 is still in code review
Highest priority: I-103 (repeating topics showing up on boards) -- needs to
get backported before the bug goes to enwiki and frwiki.
*Matthias*:
Worked on cache after some feedback from Erik.
Worked on Cirrus Search.
Tomorrow -- Code review, unless I-103 still needs work.
Shahyar missed the meeting today; he sent an email.
*Matt*:
Had a meeting about logging event-tracking. Experimenting with SendBeacon,
to see what kind of browser support there is.
*Matthias*:
Working on Flow search -- some refactoring patches for Cirrus Search. Nik
sent an email reply today -- they'll meet this week.
S says: We're still figuring out design for Search. We might use a version
of the existing special page for no-JS.
There's still a couple days more of refactoring for Cirrus.
*Erik*:
Fri -- Fixed I-102 regression, lock topic reason appears twice in titlebar.
It's in code review. He'll change the order of patches today.
Danny says -- it would be good for that to get backported on Tues deploy,
so that the bug doesn't go out to Frwiki this week.
Danny's also concerned about I-103 -- repeated topics showing up in load
more. Erik will look at it, and we'll try to backport 102 & 103.
I-1 (Hide topic updates) is waiting for Shahyar's H-8 - OOJS integration
for history pages.
*Shahyar*:
Patches up for mobile font size bug, H-99 (topic pages should always show
uncollapsed)
H-8 -- Add hide/delete/suppress to history. Patches to integrate OOJS are
up for code review. We should look through it, and then once we agree on
how we want to go forward with it, we'll show it to Trevor/Roan/Timo.
Matt wants to understand the integration more -- they'll talk about it
later today.
Minutes and slides from Wednesday's quarterly review meeting of the
Foundation's Core features (Flow) team are now available at
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
.
On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)wikimedia.org> wrote:
> Hi folks,
>
> to increase accountability and create more opportunities for course
> corrections and resourcing adjustments as necessary, Sue's asked me
> and Howie Fung to set up a quarterly project evaluation process,
> starting with our highest priority initiatives. These are, according
> to Sue's narrowing focus recommendations which were approved by the
> Board [1]:
>
> - Visual Editor
> - Mobile (mobile contributions + Wikipedia Zero)
> - Editor Engagement (also known as the E2 and E3 teams)
> - Funds Dissemination Committe and expanded grant-making capacity
>
> I'm proposing the following initial schedule:
>
> January:
> - Editor Engagement Experiments
>
> February:
> - Visual Editor
> - Mobile (Contribs + Zero)
>
> March:
> - Editor Engagement Features (Echo, Flow projects)
> - Funds Dissemination Committee
>
> We’ll try doing this on the same day or adjacent to the monthly
> metrics meetings [2], since the team(s) will give a presentation on
> their recent progress, which will help set some context that would
> otherwise need to be covered in the quarterly review itself. This will
> also create open opportunities for feedback and questions.
>
> My goal is to do this in a manner where even though the quarterly
> review meetings themselves are internal, the outcomes are captured as
> meeting minutes and shared publicly, which is why I'm starting this
> discussion on a public list as well. I've created a wiki page here
> which we can use to discuss the concept further:
>
> https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…
>
> The internal review will, at minimum, include:
>
> Sue Gardner
> myself
> Howie Fung
> Team members and relevant director(s)
> Designated minute-taker
>
> So for example, for Visual Editor, the review team would be the Visual
> Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker.
>
> I imagine the structure of the review roughly as follows, with a
> duration of about 2 1/2 hours divided into 25-30 minute blocks:
>
> - Brief team intro and recap of team's activities through the quarter,
> compared with goals
> - Drill into goals and targets: Did we achieve what we said we would?
> - Review of challenges, blockers and successes
> - Discussion of proposed changes (e.g. resourcing, targets) and other
> action items
> - Buffer time, debriefing
>
> Once again, the primary purpose of these reviews is to create improved
> structures for internal accountability, escalation points in cases
> where serious changes are necessary, and transparency to the world.
>
> In addition to these priority initiatives, my recommendation would be
> to conduct quarterly reviews for any activity that requires more than
> a set amount of resources (people/dollars). These additional reviews
> may however be conducted in a more lightweight manner and internally
> to the departments. We’re slowly getting into that habit in
> engineering.
>
> As we pilot this process, the format of the high priority reviews can
> help inform and support reviews across the organization.
>
> Feedback and questions are appreciated.
>
> All best,
> Erik
>
> [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus
> [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Foundation
>
> Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
>
> _______________________________________________
> Wikimedia-l mailing list
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
--
Tilman Bayer
Senior Operations Analyst (Movement Communications)
Wikimedia Foundation
IRC (Freenode): HaeB
VE team,
VisualEditor is now enabled on talk pages on Meta, and I had a good
experience with it until I tried to find a way to insert my signature. It
turns out that VE does not support signatures. I have raised the priority
of https://bugzilla.wikimedia.org/show_bug.cgi?id=51154 to high, and would
appreciate seeing a fix for this ASAP and/or disabling VE on talk pages
until this is fixed. I feel that it makes little sense to have VE enabled
on talk pages without the ability to add signatures.
As I discussed with James F., I am considering starting an RfC on English
Wikipedia about re-enabling VE. This signature problem is an issue that I
feel definitely should be fixed before an RfC gets underway. (:
Thanks,
Pine
I had to miss the Flow standup due to an EventLogging meeting.
Yesterday, I participated in Monthly Metrics, and did a mixture of
Growth and Flow work yesterday. On the Flow side, this included
looking at/filing some Flow/Echo bugs.
At the EventLogging meeting, we decided to put an experimental method
that uses sendBeacon (http://www.w3.org/TR/beacon/), into EventLogging,
then do an experiment in WikimediaEvents to log the same data with the
current logging method and the sendBeacon-based method.
Matt Flaschen
*Erik*:
I-1: Hide updates -- getting close, but needs to take the duplicate reason
out of the edit summary. We're not going to do a swat deploy today -- it's
not an important enough bug to justify a Friday deployment. We'll do it on
Monday.
Also: Discovered yesterday that we've never written any API level tests for
Flow, because there are a few bugs in the way. Erik is clearing that up so
we can get those tests working.
More work to be done on the "root post" fatal exceptions bug.
*Shahyar*:
Working on bug - Mobile: Font size and line spacing is too small.
After that: integrating OOJS, to make H-8 possible (add moderation actions
to board history).
S would like Shahyar to look at the bug about not collapsing topics on
topic pages.
There's a new card for the modal (I-7) -- re-enable click-out closing, and
use EventEmitter to prevent closing if content was inserted into form. This
should go into the backlog.
Matt's out for Yom Kippur, Matthias is out for Friday evening.
The new HIde is being deployed to Mediawiki this morning! Hide now actually
hides the topic from the board, so you can take vandalism/spam off the
page, as you can with wikitext. A hidden topic is accessible through
history and contributions.
*Matt*:
Reviewed one of Chris' browser test changes. Had to do some fiddling. It
works now, merged it.
*Matthias*:
Worked on Fatal exception (didn't load root post) -- it's in code review.
Will work on search tomorrow. Not merging this to master yet.
*Erik*:
Yesterday - Chris McM found that new topic notifications were taking longer
than 5 sec, failing browser tests. Looking into what's happening. The
Flowify process seems to be slow -- it's sending info to core just to come
back.
We'll make a Trello card for performance. Erik will be doing more work on
this.
Fixing the duplication of the moderation reason in the topic header.
Also working on the varnish cache for anons -- right now anons aren't
getting the new page when someone hides/unhides a topic. The cache is
busted when somebody makes a change to the page (posting a new topic or
message), but we need to fix it.
Shahyar MIA today.
Matt Flaschen is joining the Flow team -- welcome, Matt! He's finishing up
his last sprint with the Growth team, and transitioning to Flow.
*Matthias*:
Backend test for Flow search is up now on flow-tests -- it works! Very
exciting.
Today: Code review, moving patches through.
Looking at the issue that required running Erik's purge script this
weekend. Not sure what's happening. Erik says it's something being written
to cache and not database. But thought we'd already wrapped things in
transactions. If the database transaction failed, they would get an error
in their browser. Matthias has added a patch which makes failures go to log
pages.
*Shahyar*:
Do a run through code review -- lots need review.
H-8: Add (hide) to history pages -- it will be done this sprint. S says:
make sure we don't launch broken JS.
*Erik*:
Echo bugs -- Russians changed their signature, and it broke Echo. Echo is a
mess -- it uses regular expressions to find timestamp, and another to find
the link. Working on a patch to use a regular expression to find the whole
double bracket expression, and then pass that through to the title class.
That will need some testing, so we don't break mentions. Bartosz wrote some
extra tests for Russian names, which is helpful.
Also: Jared's request that Thank gets an Undo instead of a Confirm.
Back-end is easy to do, but we need some UX details. This is going to go to
backlog, we need to figure out priority of this. Matt will help with the
analytics part.
Hi,
so I noticed last week that the Flow builds were getting deprecation
warnings from the test framework saying "Locating textareas with
'#text_field' is deprecated. Please, use '#textarea' method instead."
I don't like being deprecated, but upon updating the test, to my surprise,
the page_object gem could no longer see the element.
I filed an upstream bug for this:
https://github.com/cheezy/page-object/issues/248
In the meantime, let's keep using the text_field locator as long as it
keeps working for us.
-Chris