Submitted to OpenSym 2018. Should hear back in late April.
Fri, May 18
Tue, May 15
Apr 25 2018
Apr 23 2018
Submitted for review. Should hear back on first round reviews by June 16th.
Apr 20 2018
Apr 12 2018
Thanks @Aklapper, it does. One reasonably quick option for the VE team might be to copy/paste the task description above (and the link to the slide deck) to a page on MW.org. I could even do that myself, if I knew where they wanted to put it and if I knew that the description was still accurate.
@Jdforrester-WMF @Whatamidoing-WMF is the rationale for the "Save"-->"Publish" decision documented anywhere on wiki? I KEEP hearing from editors during interviews and talkpage discussions that this is confusing and that they have problems with it. I'd like to be able to point them to a description of the design rationale--they don't have to agree with the rationale, but at least they should be able to see that WMF has based the decision on research rather than whim.
Here's another example, from today. I want to challenge the assignment of 'low' priority to this bug. I encounter this error more than half of the time when I edit in Firefox. I'm disabling the 2017 WTE until it's fixed; it basically prevents me from using the feature in my chosen browser, and it's not an edge case. @TBolliger can you give me a sense of why this is being de-prioritized?
Apr 11 2018
Apr 2 2018
@Sek2016 I think that since there will only be a few tables on the page (max 3?), you shouldn't need to create an in-page nave menu. Instead, you might consider providing a preview of the first N rows of each table (3? 5?) and then a "view all" button that would expand the entire table in-context, like an accordion menu.
Your redesign makes sense to me, @Sek2016. I like how you reduced the size of the metrics. I like how you present more information about the purpose of the dashboard in several distinct sections below the login prompt. Enclosing the login prompt section is logical, since that's the primary call to action on the screen so we really want users to focus on that.
Mar 23 2018
Mar 22 2018
I needed to document this in a Phab ticket for quarterly planning purposes. If a ticket for this task already exists, we can a) merge this one in or b) re-scope this one so that it just describes my specific activities related to this project.
Latest update: didn't submit to ICWSM 2018; new plan is to perform 2-3 more interviews and submit to CSCW 2018.
Mar 20 2018
Mar 15 2018
Mar 14 2018
Mar 13 2018
@leila CDP:SD status has been updated.
Mar 9 2018
Mar 6 2018
Added SRE-Access-Requests. Removed myself as assignee now that next steps are (I assume) from Ops, but not sure who to re-assign to.
Mar 5 2018
Feb 28 2018
Feb 26 2018
Feb 23 2018
Thanks, @Deskana. I'll do that. Also, FWIW this occurred for me repeatedly on Chrome (Version 64.0.3282.167 (Official Build) (64-bit)) yesterday as well. However, I use a lot of the same extensions across Chrome and Firefox, because I switch frequently. So next time it crops up, I'll try disabling the extensions or using a fresh profile and see if I can duplicate it there.
For my part, it sounds like the new mediawiki_history tables & other data lake resources cover most of the cross-wiki join use cases I might have. So I don't object to moving to a multi-instance solution.
Feb 22 2018
Feb 21 2018
Feb 15 2018
Feb 13 2018
I don't know if there is a static site generator for the Research Landing page, @Jan_Dittrich. But I know next to nothing about web development. I do know that all the content was manually added to flat HTML pages, even navigation menu items. See the development repository for history and relevant files. Any generators, compilers, or other tools used in the Landing Page are shared with the Wikimedia UI Style Guide, so perhaps @Volker_E can inform us.