Analytics/Kraken/Blurbs

From mediawiki.org

Collected snippets we've written about Kraken, to make it easier to talk about it in the future.

2012[edit]

2012 Roadmap[edit]

The Wiki Movement has a chronic need for analytics. We need it to understand our editors, to encourage growth, to engender diversity, to focus our resources, to improve our engineering efforts, and to measure our success. It permeates nearly all our goals, yet our current analytics capabilities are underdeveloped: we lack infrastructure to capture editor, visitor, clickstream, and device data in a way that is easily accessible; our efforts are distributed among different departments; our data is fragmented over different systems and databases; our tools are ad-hoc.

Our overarching vision is to provide a true data services platform: a cluster capable of providing realtime insight into community activity as well as a new view of humanity's knowledge to power applications, mash up into websites, and stream to devices. It must be powerful enough to keep pace with our ample institutional energy, and robust enough to service needs that are as-of-yet hidden from view.

I'm So Sorry I Ever Wrote This[edit]

The Wiki Movement has a chronic need for analytics. We are starved for it. This document describes the resources needed to sate our data-hunger; in addition, it outlines several operational proposals for partially feeding this need, though I suspect we will underestimate how hungry we are until after we get the first byte.

2012 WMF Annual Report[edit]

Our analytics team is building a platform to help the movement and the Foundation study the vast and enigmatic datascape of our projects. The platform aims to provide reliable intelligence in a fraction of the time, accessed via an intuitive self-service interface designed for non-technical users. It's difficult to overstate the potential of a robust data-services platform: the movement has a chronic need for analytics. We need it to understand our editors, to encourage growth, to engender diversity, to focus our resources, to improve our engineering efforts, and to measure our success. The challenge is also great: it must be powerful enough to keep pace with our ample institutional energy, and robust enough to service needs that are as-of-yet hidden from view. We look forward to bringing you new developments in 2013.