Change Details

==Background== After the much anticipated [1] Pageview API is finally real and running, we are reaching out to you - people who need this data. Whether you build tools or research this fascinating movement of ours, we want to know where you think we should go next, both in the short term and the long term. Now that we have a clear, solid infrastructure to both compute and serve data, our limits are only privacy, security, and budget. So come, join the discussion in the comments on this task. Help us know what data you need next. ==Problem== We (team Analytics) have too much data to safely release everything. We need to know what use cases people have and which is the most important or common use case, so we can prioritize. The more data we release, the harder it gets to keep it safe from de-anonymization attacks. So finding out exactly what's important is crucial. ==Goal== At the end of The Mediawiki Developer Summit, we want consensus on what data the community and WMF want to be able to query for. ==More Information== * **Status of Discussion**: Brainstorming, gathering short and long term requirements * **Background Information**: [1] and basically, any data requests ever made on analytics-l * **Related Tasks** All tasks related to the pageview API are tagged {slug} in the title, but this discussion goes beyond the Pageview API [1] https://phabricator.wikimedia.org/T44259

==Background== After the much anticipated [1] Pageview API is finally real and running, we are reaching out to you - people who need this data. Whether you build tools or research this fascinating movement of ours, we want to know where you think we should go next, both in the short term and the long term. Now that we have a clear, solid infrastructure to both compute and serve data, our limits are only privacy, security, and budget. So come, join the discussion in the comments on this task. Help us know what data you need next. ==Problem== We (team Analytics) have too much data to safely release everything. We need to know what use cases people have and which is the most important or common use case, so we can prioritize. The more data we release, the harder it gets to keep it safe from de-anonymization attacks. So finding out exactly what's important is crucial. ==Goal== At the end of The Mediawiki Developer Summit, we want consensus on what data the community and WMF want to be able to query for. This task can still serve as the landing place to gather requirements for the pageview API. But its purpose for the MWDS has expanded to talking about the Event Bus and data flows in general. See this comment for detail: T112956#1903466 ==More Information== * **Status of Discussion**: Brainstorming, gathering short and long term requirements * **Background Information**: [1] and basically, any data requests ever made on analytics-l * **Related Tasks** All tasks related to the pageview API are tagged {slug} in the title, but this discussion goes beyond the Pageview API [1] https://phabricator.wikimedia.org/T44259

==Background== After the much anticipated [1] Pageview API is finally real and running, we are reaching out to you - people who need this data. Whether you build tools or research this fascinating movement of ours, we want to know where you think we should go next, both in the short term and the long term. Now that we have a clear, solid infrastructure to both compute and serve data, our limits are only privacy, security, and budget. So come, join the discussion in the comments on this task. Help us know what data you need next. ==Problem== We (team Analytics) have too much data to safely release everything. We need to know what use cases people have and which is the most important or common use case, so we can prioritize. The more data we release, the harder it gets to keep it safe from de-anonymization attacks. So finding out exactly what's important is crucial. ==Goal== At the end of The Mediawiki Developer Summit, we want consensus on what data the community and WMF want to be able to query for. This task can still serve as the landing place to gather requirements for the pageview API. But its purpose for the MWDS has expanded to talking about the Event Bus and data flows in general. See this comment for detail: T112956#1903466 ==More Information== * **Status of Discussion**: Brainstorming, gathering short and long term requirements * **Background Information**: [1] and basically, any data requests ever made on analytics-l * **Related Tasks** All tasks related to the pageview API are tagged {slug} in the title, but this discussion goes beyond the Pageview API [1] https://phabricator.wikimedia.org/T44259