Hi, speaking of Echo, I hope the plan is to have full Echo functionality with Flow from launch day if not before. Echo is widely used by the community, and it's one of my favorite features from the past few years.
Thanks (:
Pine
We have 4 3/4 engineers, even with SF office closed for Veterans Day on Nov 11 we should achieve great things.
Obviously the board TOC is highest priority. Shahyar will have a version of J2b "Opening the ToC dropdown" by Friday. flow-tests is running the gerrit patches for a fixed header that shows the current topic title.Pau Giner is in SF starting Monday and we will use his every waking hour :) for TOC review and search UX design.We will have a meeting to triage Flow & Echo bugs soon.
Other themes for the sprint are
* analytics (usage queries and event logging)
* Flow on all officewiki talk pages
* convert LQT pages to Flow
On analytics, we met with Dan Andreescu who's already set up a lot of infrastructure \o/ We have a web site http://flow-reportcard.wmflabs.org/# and patches in process that will let us commit queries to a limn-flow-data repository that will generate dashboard graphs. More in https://www.mediawiki.org/wiki/Flow/Analytics
Rather than do a hacky conversion of officewiki's 10 LQT pages, we'd like all the features of LQT->Flow conversion implemented so the script is ready to (eventually) run on the other 12 LQT wikis, some with thousands of LQT pages . One feature we have to defer is programmatically enabling Flow on a converted LQT page; doing that properly by changing content format to 'flow-board' is a separate task that requires on $wgContentHandlerUseDB = true, which is blocked by security bug 70901.Team <3--=S Page Features engineer
_______________________________________________
EE mailing list
EE@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ee