Thanks for the replies. This is really informative and gives us some ideas
on areas we could highlight. Like I didn't realize the goal of the demos
was to have things in the MDN docs. Since this is part of our success
scenario, we should talk about whether we can be more helpful with this. It
can also help inform our choices for topics of the month.
The chrome experiments angle is interesting as well and something we could
try to leverage more in our messaging!
On Thu, Sep 5, 2013 at 6:42 PM, John Karahalis wrote:
> Comments inline.
> > From: "Majken Connor"
> > To: "For planning and participating in the Dev Derby contest"
> > Sent: Wednesday, August 28, 2013 8:00:16 PM
> > Subject: [Dev Derby] Where the Derby has been
> > Here are the questions from the etherpad. I think this discussion will
> > really be more of an interview with John Karahalis ;)
> > What were the goals of the Dev Derby?
> > - John could you provide any specific goals, like quarterly goals, or
> > mission statements from when the project was launched?
> Quoting Les from another thread:
> "As I understood it, the original goal of Dev Derby was to get more
> content in the Demo Studio. And, the goal of Demo Studio was to have
> working demos of web tech. From there, we've long planned to work
> references to the best demos into MDN documentation. So, ideally, it's
> meant to be a virtuous cycle: Docs -> Dev Derby -> Demo Studio -> Docs ->
> (repeat). But, I can't say that we've ever effectively closed that loop."
> My unofficial mission statement has been this: Help creative web
> developers learn, challenge themselves, and get their names out there while
> pushing the web forward. The platform itself has changed very little since
> the contest began, so quarterly goals usually focused on participation
> numbers -- X number of contributors before December, etc. Getting more
> entries on the Demo Studio than on Chrome Experiments was a goal from the
> time the project began until we all accomplished it in March.
> > Why was it under MDN?
> > - This might be answered by the goals, but was MDN just a sort of best
> > place for it at the time, or did it bring specific attention to parts of
> > MDN?
> See quote from Les above.
> > What were its successes?
> > - Again will relate back to the goals, but we already have some answers
> > the etherpad, like it brought attention to MDN (do we have any relevant
> > stats?) and that some people were even hired after submitting to the
> > contest!
> The Demo Studio surpassed Chrome Experiments in number of entries. This is
> especially important because Chrome Experiments implied (successfully among
> both developers and users) that Chrome is needed to make the most of the
> web today. Surpassing it highlighted the importance (and possibility) of
> building amazing experiences for users everywhere, regardless of browser.
> Most Demo Studio entries were submitted through the Dev Derby contest, so
> we can say with confidence that this would not have happened without the
> The biggest success of the Dev Derby, in my opinion, is that it had a
> profound impact on contributors. People who knew nothing about particular
> web technologies would study up on them, challenge themselves, and
> routinely win first place in contests focused on those technologies. It was
> > ["What was involved in running the Derby?" was also in this section but I
> > will split this one into its own discussion]
> Outlined here. Sounds minor, but even just keeping the lights on can
> require a good deal of work... at least the way we were running the contest
> in the past.
> > Please add your own sub-questions on these topics, or follow-ups on the
> > answers already given!
> > _______________________________________________
> > community-devderby mailing list
> > email@example.com
> > https://lists.mozilla.org/listinfo/community-devderby
> community-devderby mailing list