Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
1. https://www.mediawiki.org/wiki/Product 2. https://www.mediawiki.org/wiki/Community_Engagement_(Product) 3. https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs 4. https://metrics.wmflabs.org/ 5. https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation 6. https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe... 7. https://meta.wikimedia.org/wiki/Growth 8. https://www.mediawiki.org/wiki/Mobile_web_projects 9. https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote:
Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Thanks Aaron -- well said.
We are collaborating with the growth team on task suggestions which is one of the first areas where we see our data being used to drive feature development. We have some ideas in this area but our activities have been focused on measurement and comprehension.
-Toby
On Thu, Aug 14, 2014 at 7:07 AM, Aaron Halfaker ahalfaker@wikimedia.org wrote:
Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
- https://www.mediawiki.org/wiki/Product
- https://www.mediawiki.org/wiki/Community_Engagement_(Product)
https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs 4. https://metrics.wmflabs.org/ 5. https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation 6. https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe... 7. https://meta.wikimedia.org/wiki/Growth 8. https://www.mediawiki.org/wiki/Mobile_web_projects 9. https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote:
Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Pine – in fact (as I am sure you know, as you post frequently there) you can reach most Product people involved in the design of editor engagement features/experiments via ee@lists.wikimedia.org.
On Aug 14, 2014, at 7:10 AM, Toby Negrin tnegrin@wikimedia.org wrote:
Thanks Aaron -- well said.
We are collaborating with the growth team on task suggestions which is one of the first areas where we see our data being used to drive feature development. We have some ideas in this area but our activities have been focused on measurement and comprehension.
-Toby
On Thu, Aug 14, 2014 at 7:07 AM, Aaron Halfaker ahalfaker@wikimedia.org wrote: Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
- https://www.mediawiki.org/wiki/Product
- https://www.mediawiki.org/wiki/Community_Engagement_(Product)
- https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs
- https://metrics.wmflabs.org/
- https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation
- https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe...
- https://meta.wikimedia.org/wiki/Growth
- https://www.mediawiki.org/wiki/Mobile_web_projects
- https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote: Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
bah! I forgot about that list!
On Thu, Aug 14, 2014 at 3:15 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:
Pine – in fact (as I am sure you know, as you post frequently there) you can reach most Product people involved in the design of editor engagement features/experiments via ee@lists.wikimedia.org.
On Aug 14, 2014, at 7:10 AM, Toby Negrin tnegrin@wikimedia.org wrote:
Thanks Aaron -- well said.
We are collaborating with the growth team on task suggestions which is one of the first areas where we see our data being used to drive feature development. We have some ideas in this area but our activities have been focused on measurement and comprehension.
-Toby
On Thu, Aug 14, 2014 at 7:07 AM, Aaron Halfaker ahalfaker@wikimedia.org wrote:
Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
- https://www.mediawiki.org/wiki/Product
- https://www.mediawiki.org/wiki/Community_Engagement_(Product)
https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs 4. https://metrics.wmflabs.org/ 5. https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation 6. https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe... 7. https://meta.wikimedia.org/wiki/Growth 8. https://www.mediawiki.org/wiki/Mobile_web_projects 9. https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote:
Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Thanks all. My question was more about tools than features which is why I asked here.
Pine On Aug 14, 2014 7:19 AM, "Aaron Halfaker" ahalfaker@wikimedia.org wrote:
bah! I forgot about that list!
On Thu, Aug 14, 2014 at 3:15 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:
Pine – in fact (as I am sure you know, as you post frequently there) you can reach most Product people involved in the design of editor engagement features/experiments via ee@lists.wikimedia.org.
On Aug 14, 2014, at 7:10 AM, Toby Negrin tnegrin@wikimedia.org wrote:
Thanks Aaron -- well said.
We are collaborating with the growth team on task suggestions which is one of the first areas where we see our data being used to drive feature development. We have some ideas in this area but our activities have been focused on measurement and comprehension.
-Toby
On Thu, Aug 14, 2014 at 7:07 AM, Aaron Halfaker ahalfaker@wikimedia.org wrote:
Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
- https://www.mediawiki.org/wiki/Product
- https://www.mediawiki.org/wiki/Community_Engagement_(Product)
https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs 4. https://metrics.wmflabs.org/ 5. https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation 6. https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe... 7. https://meta.wikimedia.org/wiki/Growth 8. https://www.mediawiki.org/wiki/Mobile_web_projects 9. https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote:
Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Pine, can you help me understand the difference between tools and features?
Could you be referring to things like Snuggle[1], my academic/volunteer work to improve editor engagement on-wiki? If so, I wouldn't refer to that as something that's been "developed by Analytics".
1. https://snuggle-en.wmflabs.org/
-Aaron
On Thu, Aug 14, 2014 at 7:45 PM, Pine W wiki.pine@gmail.com wrote:
Thanks all. My question was more about tools than features which is why I asked here.
Pine On Aug 14, 2014 7:19 AM, "Aaron Halfaker" ahalfaker@wikimedia.org wrote:
bah! I forgot about that list!
On Thu, Aug 14, 2014 at 3:15 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:
Pine – in fact (as I am sure you know, as you post frequently there) you can reach most Product people involved in the design of editor engagement features/experiments via ee@lists.wikimedia.org.
On Aug 14, 2014, at 7:10 AM, Toby Negrin tnegrin@wikimedia.org wrote:
Thanks Aaron -- well said.
We are collaborating with the growth team on task suggestions which is one of the first areas where we see our data being used to drive feature development. We have some ideas in this area but our activities have been focused on measurement and comprehension.
-Toby
On Thu, Aug 14, 2014 at 7:07 AM, Aaron Halfaker <ahalfaker@wikimedia.org
wrote:
Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
- https://www.mediawiki.org/wiki/Product
- https://www.mediawiki.org/wiki/Community_Engagement_(Product)
https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs 4. https://metrics.wmflabs.org/ 5. https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation 6. https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe... 7. https://meta.wikimedia.org/wiki/Growth 8. https://www.mediawiki.org/wiki/Mobile_web_projects 9. https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote:
Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
I was thinking of tools in the sense of software developed by Analytics for use by the EE teams when they measure the effectiveness of their work or look for new opportunities. EEVS appears to be a good example of what I had in mind as a tool. Your Snuggle project is something I would consider to be more like a feature because it is intended for use by end users.
In other words, "tools" are used by devs and PMs to develop and evaluate their products and opportunities for end-user engagement, and "features" are used by end users. That is my arbitrary way of differentiating types of software. Can you think of better terminology?
Pine On Aug 15, 2014 2:42 AM, "Aaron Halfaker" ahalfaker@wikimedia.org wrote:
Pine, can you help me understand the difference between tools and features?
Could you be referring to things like Snuggle[1], my academic/volunteer work to improve editor engagement on-wiki? If so, I wouldn't refer to that as something that's been "developed by Analytics".
-Aaron
On Thu, Aug 14, 2014 at 7:45 PM, Pine W wiki.pine@gmail.com wrote:
Thanks all. My question was more about tools than features which is why I asked here.
Pine On Aug 14, 2014 7:19 AM, "Aaron Halfaker" ahalfaker@wikimedia.org wrote:
bah! I forgot about that list!
On Thu, Aug 14, 2014 at 3:15 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:
Pine – in fact (as I am sure you know, as you post frequently there) you can reach most Product people involved in the design of editor engagement features/experiments via ee@lists.wikimedia.org.
On Aug 14, 2014, at 7:10 AM, Toby Negrin tnegrin@wikimedia.org wrote:
Thanks Aaron -- well said.
We are collaborating with the growth team on task suggestions which is one of the first areas where we see our data being used to drive feature development. We have some ideas in this area but our activities have been focused on measurement and comprehension.
-Toby
On Thu, Aug 14, 2014 at 7:07 AM, Aaron Halfaker < ahalfaker@wikimedia.org> wrote:
Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
- https://www.mediawiki.org/wiki/Product
- https://www.mediawiki.org/wiki/Community_Engagement_(Product)
https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs 4. https://metrics.wmflabs.org/ 5. https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation 6. https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe... 7. https://meta.wikimedia.org/wiki/Growth 8. https://www.mediawiki.org/wiki/Mobile_web_projects 9. https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote:
Hi Analytics team,
I'm curious, which tools developed by Analytics have contributed notably to editor engagement successes?
Pine
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
I guess the point of confusion, and the distinction I'd make, is instead being clearer around "contributing to editor engagement successes".
On 15 August 2014 21:45, Pine W wiki.pine@gmail.com wrote:
I was thinking of tools in the sense of software developed by Analytics for use by the EE teams when they measure the effectiveness of their work or look for new opportunities. EEVS appears to be a good example of what I had in mind as a tool. Your Snuggle project is something I would consider to be more like a feature because it is intended for use by end users.
In other words, "tools" are used by devs and PMs to develop and evaluate their products and opportunities for end-user engagement, and "features" are used by end users. That is my arbitrary way of differentiating types of software. Can you think of better terminology?
Pine On Aug 15, 2014 2:42 AM, "Aaron Halfaker" ahalfaker@wikimedia.org wrote:
Pine, can you help me understand the difference between tools and features?
Could you be referring to things like Snuggle[1], my academic/volunteer work to improve editor engagement on-wiki? If so, I wouldn't refer to that as something that's been "developed by Analytics".
-Aaron
On Thu, Aug 14, 2014 at 7:45 PM, Pine W wiki.pine@gmail.com wrote:
Thanks all. My question was more about tools than features which is why I asked here.
Pine On Aug 14, 2014 7:19 AM, "Aaron Halfaker" ahalfaker@wikimedia.org wrote:
bah! I forgot about that list!
On Thu, Aug 14, 2014 at 3:15 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:
Pine – in fact (as I am sure you know, as you post frequently there) you can reach most Product people involved in the design of editor engagement features/experiments via ee@lists.wikimedia.org.
On Aug 14, 2014, at 7:10 AM, Toby Negrin tnegrin@wikimedia.org wrote:
Thanks Aaron -- well said.
We are collaborating with the growth team on task suggestions which is one of the first areas where we see our data being used to drive feature development. We have some ideas in this area but our activities have been focused on measurement and comprehension.
-Toby
On Thu, Aug 14, 2014 at 7:07 AM, Aaron Halfaker < ahalfaker@wikimedia.org> wrote:
Hey Pine,
We don't deploy software that affects the user experience on Wikimedia projects, so it is hard to identify any direct effect on editor engagement that we've had. The Product teams[1] develop user-facing features. It doesn't look like they have a public facing mailing list, but the community engagement team (for product)[2] does. You can contact them at cep@lists.wikimedia.org.
In analytics, we develop new measures of editor engagement (among other things)[3] and deploy those measures for public use. For example, see WikiMetrics[4]. We also support the product teams by helping them identify which features are likely to have a positive impact with background analysis (e.g. [5]) and by running experiments to help product teams iterate toward feature designs that maximize positive impact (e.g. [6]). Right now, we provide direct support of the Growth[7] and Mobile[8] product teams, but we also consult with other teams at the WMF and engage with "community outreach efforts" (e.g. [9]) in our (not so copious) free time.
- https://www.mediawiki.org/wiki/Product
- https://www.mediawiki.org/wiki/Community_Engagement_(Product)
https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs 4. https://metrics.wmflabs.org/ 5. https://meta.wikimedia.org/wiki/Research:Wikipedia_article_creation 6. https://meta.wikimedia.org/wiki/Research:Asking_anonymous_editors_to_registe... 7. https://meta.wikimedia.org/wiki/Growth 8. https://www.mediawiki.org/wiki/Mobile_web_projects 9. https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
-Aaron
On Thu, Aug 14, 2014 at 2:11 AM, Pine W wiki.pine@gmail.com wrote:
> Hi Analytics team, > > I'm curious, which tools developed by Analytics have contributed > notably to editor engagement successes? > > Pine > > _______________________________________________ > Analytics mailing list > Analytics@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/analytics > >
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics