Editor Engagement Features Plan (E2) - Q3 2013 - EE

Liam Wyatt

31 Jan 31 Jan

6:23 p.m.

More of a naming-clarification question than one about your work-plans... But could you clarify the difference between the "E2: Editor Engagement Features" team and the "E3: editor engagement experiments" team http://www.mediawiki.org/wiki/E3 Is it the same thing with a new name? Is it the "next step" for when things "graduate from the E3 team up to level E2 and, presumably then go into production at E1? -Liam wittylama.com Peace, love & metadata On 1 February 2013 13:04, Fabrice Florin <fflorin(a)wikimedia.org> wrote:

...

Hi folks, Based on our discussions over the past few weeks, here is a quick overview of our plans for the Editor Engagement Features team (E2) in this quarter (January-March 2013). http://www.mediawiki.org/wiki/Editor_Engagement/2013_strategy_planning_(Fea… Our team's overall goal for 2012-2013 is to help reverse Wikipedia's editor decline by building features that can recruit new editors and retain existing editors. To that end, we are working on these key quarterly milestones for January-March 2013: Echo (Notifications): • Expand first beta version on MediaWiki.org, with better features for new editors • Deploy a limited release of Echo on the English Wikipedia by the end of the quarter Flow (Messaging): • Create a design spec and product plan for user-to-user messaging on talk pages • Discuss designs and plans with the community through a variety of channels Article Feedback v5: • Complete and test final features, code refactoring and database cluster • Prepare for deployment on multiple sites, once approved by their communities Our strategy planning page includes roadmaps and timelines for each of these projects, for discussion purposes. Please note that goals beyond this quarter are approximate and subject to change, as our plans get periodically adjusted. Our current plans are also outlined in these slides: http://www.mediawiki.org/wiki/File:E2_Planning_-_Q3_2013.pdf Please let us know if you have any questions, comments or suggestions about our plans for the current quarter, which are now well under way. We expect to conduct another planning update next quarter, based on discussions with our teams and communities. All the best, Fabrice _______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

Reply

Steven Walling

6:39 p.m.

On Thu, Jan 31, 2013 at 6:23 PM, Liam Wyatt <liamwyatt(a)gmail.com> wrote:

...

More of a naming-clarification question than one about your work-plans... But could you clarify the difference between the "E2: Editor Engagement Features" team and the "E3: editor engagement experiments" team http://www.mediawiki.org/wiki/E3 Is it the same thing with a new name? Is it the "next step" for when things "graduate from the E3 team up to level E2 and, presumably then go into production at E1? -Liam

Oliver's description is correct. We're two separate features development teams, which focus on different approaches to editor engagement. We collaborate on some projects, but there isn't a process where we experiment to find what works, then hand it off to E2 or someone else to build permanently. When we find something worth making permanent, we generally do that ourselves. I kind of like the way Terry puts it: E2 builds the levers. E3 figures out how to pull them. An example might be Echo, the new notifications system. E2 is building out that platform, and regardless of details we know that we want a modern notifications system to replace that damn yellow messages bar, including a way for developers on other teams and in the community to trigger a notification. The E3 approach to "pulling that lever" might be to test the effectiveness of particular notifications at driving editing activity. -- Steven Walling https://wikimediafoundation.org/

Reply

Liam Wyatt

6:54 p.m.

Thanks for the fast (and many) responses. Does this mean that the visual editor team should be called "E1: Editing"? ;-) wittylama.com Peace, love & metadata On 1 February 2013 13:41, Fabrice Florin <fflorin(a)wikimedia.org> wrote:

...

Hi Liam, Thanks for your good question, and sorry for not making this more clear at the outset :) We have two different teams working on editor engagement, code-named E2 (Features) and E3 (Experiments). The E2 team focuses on developing large features that typically require months to build, while the E3 team focuses on more rapid experiments that can improve the experience of new good faith contributors. Here are examples of what each team is working on, as summarized in our annual plan for 2012-13: E2: Editor Engagement Features • Develop a more responsive and engaging user experience. • Implement scaleable notifications system for user-relevant events • Create new user-to-user messaging system. E3: Editor Engagement Experiments • Support editor engagement work with rapid experimentation, and directly prioritize the most successful experiments. • Conduct a range of product and community experiments designed to directly increase new editor engagement and retention. You can read more about this fiscal year's plans for each teams in our Engineering goals for 2012-13: http://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Reversing… Note that this plan was written a year ago, so some of the specific objectives have since been adjusted. Hence this quarterly planning process, where we readjust our goals to reflect recent developments. I hope this helps. We're happy to provide more clarifications, as needed. Be well, Fabrice On Jan 31, 2013, at 6:23 PM, Liam Wyatt wrote: More of a naming-clarification question than one about your work-plans... But could you clarify the difference between the "E2: Editor Engagement Features" team and the "E3: editor engagement experiments" team http://www.mediawiki.org/wiki/E3 Is it the same thing with a new name? Is it the "next step" for when things "graduate from the E3 team up to level E2 and, presumably then go into production at E1? -Liam wittylama.com Peace, love & metadata On 1 February 2013 13:04, Fabrice Florin <fflorin(a)wikimedia.org> wrote:

Hi folks, Based on our discussions over the past few weeks, here is a quick overview of our plans for the Editor Engagement Features team (E2) in this quarter (January-March 2013). http://www.mediawiki.org/wiki/Editor_Engagement/2013_strategy_planning_(Fea… Our team's overall goal for 2012-2013 is to help reverse Wikipedia's editor decline by building features that can recruit new editors and retain existing editors. To that end, we are working on these key quarterly milestones for January-March 2013: Echo (Notifications): • Expand first beta version on MediaWiki.org, with better features for new editors • Deploy a limited release of Echo on the English Wikipedia by the end of the quarter Flow (Messaging): • Create a design spec and product plan for user-to-user messaging on talk pages • Discuss designs and plans with the community through a variety of channels Article Feedback v5: • Complete and test final features, code refactoring and database cluster • Prepare for deployment on multiple sites, once approved by their communities Our strategy planning page includes roadmaps and timelines for each of these projects, for discussion purposes. Please note that goals beyond this quarter are approximate and subject to change, as our plans get periodically adjusted. Our current plans are also outlined in these slides: http://www.mediawiki.org/wiki/File:E2_Planning_-_Q3_2013.pdf Please let us know if you have any questions, comments or suggestions about our plans for the current quarter, which are now well under way. We expect to conduct another planning update next quarter, based on discussions with our teams and communities. All the best, Fabrice _______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

_______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee _______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) Donate to keep Wikipedia free: https://donate.wikimedia.org/ _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

Reply

Fabrice Florin

6:57 p.m.

Hehe ;) I think it would be very cool if the VE team was renamed E1, but I'm not sure if they would be up for that. I guess the E1 slot remains open for now … Cheers, -f On Jan 31, 2013, at 6:54 PM, Liam Wyatt wrote:

...

Thanks for the fast (and many) responses. Does this mean that the visual editor team should be called "E1: Editing"? ;-) wittylama.com Peace, love & metadata On 1 February 2013 13:41, Fabrice Florin <fflorin(a)wikimedia.org> wrote: Hi Liam, Thanks for your good question, and sorry for not making this more clear at the outset :) We have two different teams working on editor engagement, code-named E2 (Features) and E3 (Experiments). The E2 team focuses on developing large features that typically require months to build, while the E3 team focuses on more rapid experiments that can improve the experience of new good faith contributors. Here are examples of what each team is working on, as summarized in our annual plan for 2012-13: E2: Editor Engagement Features • Develop a more responsive and engaging user experience. • Implement scaleable notifications system for user-relevant events • Create new user-to-user messaging system. E3: Editor Engagement Experiments • Support editor engagement work with rapid experimentation, and directly prioritize the most successful experiments. • Conduct a range of product and community experiments designed to directly increase new editor engagement and retention. You can read more about this fiscal year's plans for each teams in our Engineering goals for 2012-13: http://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Reversing… Note that this plan was written a year ago, so some of the specific objectives have since been adjusted. Hence this quarterly planning process, where we readjust our goals to reflect recent developments. I hope this helps. We're happy to provide more clarifications, as needed. Be well, Fabrice On Jan 31, 2013, at 6:23 PM, Liam Wyatt wrote:

More of a naming-clarification question than one about your work-plans... But could you clarify the difference between the "E2: Editor Engagement Features" team and the "E3: editor engagement experiments" team http://www.mediawiki.org/wiki/E3 Is it the same thing with a new name? Is it the "next step" for when things "graduate from the E3 team up to level E2 and, presumably then go into production at E1? -Liam wittylama.com Peace, love & metadata On 1 February 2013 13:04, Fabrice Florin <fflorin(a)wikimedia.org> wrote: Hi folks, Based on our discussions over the past few weeks, here is a quick overview of our plans for the Editor Engagement Features team (E2) in this quarter (January-March 2013). http://www.mediawiki.org/wiki/Editor_Engagement/2013_strategy_planning_(Fea… Our team's overall goal for 2012-2013 is to help reverse Wikipedia's editor decline by building features that can recruit new editors and retain existing editors. To that end, we are working on these key quarterly milestones for January-March 2013: Echo (Notifications): • Expand first beta version on MediaWiki.org, with better features for new editors • Deploy a limited release of Echo on the English Wikipedia by the end of the quarter Flow (Messaging): • Create a design spec and product plan for user-to-user messaging on talk pages • Discuss designs and plans with the community through a variety of channels Article Feedback v5: • Complete and test final features, code refactoring and database cluster • Prepare for deployment on multiple sites, once approved by their communities Our strategy planning page includes roadmaps and timelines for each of these projects, for discussion purposes. Please note that goals beyond this quarter are approximate and subject to change, as our plans get periodically adjusted. Our current plans are also outlined in these slides: http://www.mediawiki.org/wiki/File:E2_Planning_-_Q3_2013.pdf Please let us know if you have any questions, comments or suggestions about our plans for the current quarter, which are now well under way. We expect to conduct another planning update next quarter, based on discussions with our teams and communities. All the best, Fabrice _______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

_______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) Donate to keep Wikipedia free: https://donate.wikimedia.org/ _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

_______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) Donate to keep Wikipedia free: https://donate.wikimedia.org/

Reply

Oliver Keyes

6:48 a.m.

Well, keep that confusion on the QT and DL or HC will have us on KP, OK? On 1 February 2013 14:41, Guerillero Wikipedia < guerillero.wikipedia(a)gmail.com> wrote:

...

Your code names never cease to confuse me. --Tom (Guerillero) On Thu, Jan 31, 2013 at 9:57 PM, Fabrice Florin <fflorin(a)wikimedia.org>wrote;wrote:

Hehe ;) I think it would be very cool if the VE team was renamed E1, but I'm not sure if they would be up for that. I guess the E1 slot remains open for now … Cheers, -f On Jan 31, 2013, at 6:54 PM, Liam Wyatt wrote: Thanks for the fast (and many) responses. Does this mean that the visual editor team should be called "E1: Editing"? ;-) wittylama.com Peace, love & metadata On 1 February 2013 13:41, Fabrice Florin <fflorin(a)wikimedia.org> wrote:

Hi Liam, Thanks for your good question, and sorry for not making this more clear at the outset :) We have two different teams working on editor engagement, code-named E2 (Features) and E3 (Experiments). The E2 team focuses on developing large features that typically require months to build, while the E3 team focuses on more rapid experiments that can improve the experience of new good faith contributors. Here are examples of what each team is working on, as summarized in our annual plan for 2012-13: E2: Editor Engagement Features • Develop a more responsive and engaging user experience. • Implement scaleable notifications system for user-relevant events • Create new user-to-user messaging system. E3: Editor Engagement Experiments • Support editor engagement work with rapid experimentation, and directly prioritize the most successful experiments. • Conduct a range of product and community experiments designed to directly increase new editor engagement and retention. You can read more about this fiscal year's plans for each teams in our Engineering goals for 2012-13: http://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Reversing… Note that this plan was written a year ago, so some of the specific objectives have since been adjusted. Hence this quarterly planning process, where we readjust our goals to reflect recent developments. I hope this helps. We're happy to provide more clarifications, as needed. Be well, Fabrice On Jan 31, 2013, at 6:23 PM, Liam Wyatt wrote: More of a naming-clarification question than one about your work-plans... But could you clarify the difference between the "E2: Editor Engagement Features" team and the "E3: editor engagement experiments" team http://www.mediawiki.org/wiki/E3 Is it the same thing with a new name? Is it the "next step" for when things "graduate from the E3 team up to level E2 and, presumably then go into production at E1? -Liam wittylama.com Peace, love & metadata On 1 February 2013 13:04, Fabrice Florin <fflorin(a)wikimedia.org> wrote:

Hi folks, Based on our discussions over the past few weeks, here is a quick overview of our plans for the Editor Engagement Features team (E2) in this quarter (January-March 2013). http://www.mediawiki.org/wiki/Editor_Engagement/2013_strategy_planning_(Fea… Our team's overall goal for 2012-2013 is to help reverse Wikipedia's editor decline by building features that can recruit new editors and retain existing editors. To that end, we are working on these key quarterly milestones for January-March 2013: Echo (Notifications): • Expand first beta version on MediaWiki.org, with better features for new editors • Deploy a limited release of Echo on the English Wikipedia by the end of the quarter Flow (Messaging): • Create a design spec and product plan for user-to-user messaging on talk pages • Discuss designs and plans with the community through a variety of channels Article Feedback v5: • Complete and test final features, code refactoring and database cluster • Prepare for deployment on multiple sites, once approved by their communities Our strategy planning page includes roadmaps and timelines for each of these projects, for discussion purposes. Please note that goals beyond this quarter are approximate and subject to change, as our plans get periodically adjusted. Our current plans are also outlined in these slides: http://www.mediawiki.org/wiki/File:E2_Planning_-_Q3_2013.pdf Please let us know if you have any questions, comments or suggestions about our plans for the current quarter, which are now well under way. We expect to conduct another planning update next quarter, based on discussions with our teams and communities. All the best, Fabrice _______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

_______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee _______________________________ Fabrice Florin Product Manager, Editor Engagement Wikimedia Foundation http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) Donate to keep Wikipedia free: https://donate.wikimedia.org/ _______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

_______________________________________________ EE mailing list EE(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

-- Oliver Keyes Community Liaison, Product Development Wikimedia Foundation

Reply