Post-Summit Project Proposal: MaaS: MDN as a Startup

[Luke Crouch]

MDN is following Florian's lead for codifying Summit ideas into project
proposals:

1. Create a project page on wiki.moz [1]
2. Start a corresponding thread on mdn-drivers [2]

My post-Summit project idea is a KPI Metrics Dashboard to help us
operate MDN like a Lean Startup. A fuller write-up for the why, what,
and how are in this blog post:

http://groovecoder.com/2013/10/08/maas-mdn-as-a-startup/

Comment on the blog post and/or reply to mdn-drivers to join the feedback.

Thanks,
-L

[1] https://wiki.mozilla.org/MDN/Development/Summit_Feedback
[2] https://groups.google.com/forum/#!forum/mozilla.mdn.drivers

[Ali Spivak]

if we can link to them off of the MDN Development page, that would be swell.

https://wiki.mozilla.org/MDN/Development and put the link and description in the "Proposed Projects" section



ali spivak
408-859-8260
asp...@mozilla.com

_______________________________________________
engagement-developers mailing list
engagement...@lists.mozilla.org
https://lists.mozilla.org/listinfo/engagement-developers

[Thierry Régagnon]

I think this a great idea. :)

I was talking with Jean-Yves during the Summit that I would love as a contributor to access more metrics about MDN.
Jean-Yves told me that the localization dashboard should have many metrics to help translators in their work. To choose which article to translate or improve.

Like Luke, I feel we should start defining engagement KPIs for MDN, and use them to drive enhancements on the project.

Have A/B tests already been done on MDN?

Luke Crouch <lcr...@mozilla.com> a écrit :

>MDN is following Florian's lead for codifying Summit ideas into project
>proposals:
>
>1. Create a project page on wiki.moz [1]
>2. Start a corresponding thread on mdn-drivers [2]
>
>My post-Summit project idea is a KPI Metrics Dashboard to help us
>operate MDN like a Lean Startup. A fuller write-up for the why, what,
>and how are in this blog post:
>
>http://groovecoder.com/2013/10/08/maas-mdn-as-a-startup/
>
>Comment on the blog post and/or reply to mdn-drivers to join the feedback.
>
>Thanks,
>-L
>
>[1] https://wiki.mozilla.org/MDN/Development/Summit_Feedback
>[2] https://groups.google.com/forum/#!forum/mozilla.mdn.drivers
>_______________________________________________

>dev-mdc mailing list
>dev...@lists.mozilla.org
>https://lists.mozilla.org/listinfo/dev-mdc

[Luke Crouch]

Yeah, we have the tooling (i.e., optimizely.com) to do simple A/B tests
and we've done a few. Going forward I'd love to trim our project ideas
down to the Minimum Viable Experiment to test our hypotheses before we
go all-in on a feature or change.

E.g., we want section editing because we think it will increase edits,
but it's a big engineering effort to do it. Can we fake it a bit by
restoring section edit *buttons* that link to the full edit page with
some js to jump the textarea down to the right section?

If that's smaller and easier to implement, we can measure the impact on
# of edits. If it's worth the effort, we make a full robust
section-editing feature. If not, we experiment with something else
and/or move on to another project.

-L