Worked with Bernd on Flow & Echo, showed him the ropes
Looked at Echo test failure, Erik fixed it
Fixed git commit problem
Fixed about half of the JQuery issues, will fix the rest shortly
Then: look at hiring backlog & code review
Worked on pagination on topic & post history, that's in Gerrit
Lots of code review
Working on Echo mentions notification bug
Looked at lots of candidates, approved one to go forward
Fixed a problem with Echo tests that was causing failures
Went to Architecture brainstorming meeting
We had our quarterly review today:
Fixed bug for Beta Labs -- database filling, it's in code review
Updated two patches in code review with -1, they're up for review again
Reviewing interview candidates, more
Cherry-picked all Co-op fixes, they're good to go!
Today: Parsoid/services quarterly review
More interview stuff
Code review Matthias' search work
Change to OfficeWiki config for Sherry
Reviewed VE/Parsoid patch, ready to merge
Updated API docs based on Dev Summit
Enabled Flow on test page for research
Reviewed Qunit mobile test, ready to merge
Community members helped us do our spike for the Echo mentions bugs, much
T87446 -- JQuery error affecting unit tests, filed as unbreak now -- both
VE and Echo. We'll need to fix it.
T75426 -- Comments w diacritics doesn't generate notifications. Important
for Portuguese - put into this sprint.
Issue came up on En.wp yesterday -- someone moved an article page into the
Topic namespace, and couldn't move it back. Matthias wrote a patch; Greg
says okay to deploy it today. We can't currently find the page -- it's
possible that it's been deleted. We''ll have to move it back (even if it's
deleted) to the right namespace -- Matthias will look into it.
Worked on lightncandy issue. Removed flag that was added in 0.18. Submitted
a patch to lightncandy, we'll have to wait for it to be merged to us.
Today: Worked on the moved page to topic namespace issue.
Work on history pagination -- by the end of the day, it'll work on board
history. Next working day, he'll make it work on topic history.
Deployed 2 test pages on Portuguese.
Looked into a Researcher user right that would let us see deleted content.
Today: For Co-op: Configure WMF groups
Lots of meetings & interviews.
O4 - Flow fatal error in feedcontributions in code review, will get merged
into core for next deployment.
Did update on: summarize action should change to "Edit summary". Might need
to knock it back for more work.
Today: code review on Matthias' search code.
Also: review and merge the Co-op bug today (T86612)
Did all the IE8 work, ended up fixing other stuff incl problem with
Reviewed Flow developer applications & tasks
Fixed some Getting Started documentation
Reviewed patch for thank extension so it doesn't keep breaking on mobile.
Debugging reporting content link
Reviewed Flow developer applications & tasks
This morning, shipped ContentHandler to Config, so that's turned on
Today: Lots of meetings & interviews.
After that, update patches with -1s.
Matthias and Pau in SF starting tomorrow!
Worked on reported IE8 bug. Other bugs coming. WIP patch in code review.
Worked on O5 - spike - managing Flow boards outside $wgFlowOccupyPages.
It's going to be a pain.
Matthias' search script is causing problems on Beta, Erik is containing it.
Updating patches for O4 feedcontributions bug, also the Co-op's bug.
I'm looking forward to seeing everybody in SF next week!
---------- Forwarded message ----------
From: "James Hare" <jamesmhare(a)gmail.com>
Date: Jan 13, 2015 2:27 PM
Subject: [Wikimedia-l] Introducing WikiProject X
To: <lgbt(a)lists.wikimedia.org>, <gendergap(a)lists.wikimedia.org>, <
"Partnerships American Cultural North" <glam-us(a)lists.wikimedia.org>
(Standard apology for cross-posting.)
I am pleased to announce a new project, WikiProject X, funded by a
Wikimedia Foundation Individual Engagement Grant. WikiProject X's goal is
to improve the experience of WikiProjects, which are subject-area (or
goal-oriented) collaborative spaces on the English Wikipedia. By making
WikiProjects easier to use and maintain, it will be easier to build
sub-communities of like-minded people, giving editors a sense of community
on a huge and daunting website like Wikipedia. This includes mechanisms for
recruiting new participants and encouraging the creation of safe spaces
where editors, new and experienced alike, can feel like they can
participate in discussions without fear of intimidation or jargon.
The project will begin with some research, both qualitative research in the
form of interviews and case studies, and quantitative research based on
Wikipedia’s database. Our focus will be on WikiProjects that have been
successful in organizing editors, and learning more about what makes them
work. Based on this research, we will develop new tools and interfaces that
make WikiProjects easier to use and easier to maintain. Please note that
this is an opt-in program for WikiProjects; no WikiProject will be required
to make changes.
I would like to invite the community to check out our new page on
(shortcut WP:WPX). There, you can share your experiences with WikiProjects
and sign up to become a pilot tester. Community participation is crucial
for the success of this project, and the more voices we hear, the better.
If you want to sign up for more updates, sign up for our newsletter here: <
Please let me know if you have any questions. I am very much looking
forward to working with everyone on making this project succeed!
Project Manager, WikiProject X
Wikimedia-l mailing list, guidelines at:
ToC is live on Mediawiki now! Feedback thread is here
Patch to core was causing a timestamp problem, worked on that.
Worked on IE8 bug (O3). Turns out there are some more IE8 problems as well,
will fix those too.
Yesterday, worked on Flow=enabled in flowinfo -- in code review.
Spent time on O4 fatal error -- anybody with flow contribs, their contribs
feed doesn't work. Also in code review.
Doing code review on Matthias' code -- timestamps and hovers. Merged one,
there's another coming.
Will work on O5 -- spike about managing Flow boards outside
$wgFlowOccupyPages. Is there a flow-admin page? How do you move or delete a
T67088: O2. No pagination on history pages
Submitted small patch to allow CI to test Flow with other extensions
(finally) merged patch that fixes content diff lengths
Tomorrow: continue history pages pagination
Table of Contents v1 will be out on mediawiki today!
Yesterday: Release readiness review.
Found a couple bugs with ToC, nothing major. Will file them on Phab.
Looked at browser tests. Everything's green except IE8.
Jonathan Morgan reported a problem with how the API handles loading data,
wasn't loading contentmodel. Erik writing a patch that will fix it.
Code review for Matthias' work.
Today: Finish and test patch for Jonathan.
Then O1 and possibly O4.
Yesterday: Put new search on tlow-tests
Restarted Elastic search
Worked on a problem with imports getting stuck in infinite loop,
Special:FlowSearch is now on flow-tests!
Then started working on O2 - No pagination on history pages.
Reviewed Erik's fix on duplicate topic issue -- it was picking up a
different sort order.
Scheduled Flow bot workshop for Dev Summit, Lego will participate
Hygiene patch for Flow event-filing
Merged S' patch for minor browser test fix
Reviewed & merged Getting started patch that's waiting on a change to core.
Follow-up about Getting Started extension
Reviewed ToC stuff, everything is merged except for Erik's last patch. We
can start testing on beta.
Doing a little more work, and merging ToC for release this afternoon.
Reviewing ToC, yesterday and this morning.
Fixed Office Wiki history pages that were throwing fatal errors (T78103).
This happened because the talk page conversion script created the Flow
workflow but didn't create a header. This is a bug from early in the
conversion process that's been fixed, but we had to go back and fix the
ones that happened on Office.
Reviewed some of Matthias' patches.
Today: picking up Sprint O tickets.
Erik will be the release readiness review ranger this week. S says that
some of the tests have been fataling for a while -- he has a writeup of
Jenkins tips that the team says would be helpful.
Emailed Chad and Nik about new search
Sent a patch to Elastica.
Followed up with Anton on the Parsoid unit tests.
Tomorrow: picking up new Sprint O stuff.
(I've been in my new job for 4 hours yet I'm still worrying about Flow
content models. Such loyalty :) )
Good news: if you have the flow-create-board right, and if you're on a wiki
with $wgContentHandlerUseDB set, then add-topic or edit-header creates a
new Flow board. \o/ T76793 is resolved.
However, neither condition is set on enwiki. I added some more blocking
tasks to T78640 <https://phabricator.wikimedia.org/T78640> (Co-op: bot can
create a Flow board for each new mentored editor (tracking)).
Frances, do you have a wiki page explaining what the bot will do?
Are you or ErikB (who comes back from break on Friday) working on T76785
<https://phabricator.wikimedia.org/T76785> (Co-op: get approval for hostbot
to flow-create-board right) ?
I explained the issues to Danny that make T51193
<https://phabricator.wikimedia.org/T51193> (Set $wgContentHandlerUseDB =
true on all WMF wikis) contentious. I moved its blockers to a new T85847
<https://phabricator.wikimedia.org/T85847> (issues with granting the
editcontentmodel right). We'd rather the Co-op bot *not* be tied to big
discussions of changing content models and Flow taking over more talk
pages, but it might get sucked in.
http://etherpad.wikimedia.org/p/editcontentmodel has next steps for
wgContentHandlerUseDB and a draft message about the changes for a Flow tech
lead to eventually send out.
I'm happy to help, but someone else needs to take the reigns rains reins on
=S Page Collaboration team engineer