https://wiki.mozilla.org/api.php?action=feedcontributions&user=Robnyman&feedformat=atomMozillaWiki - User contributions [en]2024-03-28T11:53:31ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Technical_Evangelism&diff=999952Engagement/Developer Engagement/Technical Evangelism2014-07-24T08:57:42Z<p>Robnyman: /* Communication Channels */</p>
<hr />
<div><section begin=summary />{{TeamSummary<br />
|teamtitle=Technical Evangelism<br />
|teampagelocation=Engagement/Developer_Engagement/Technical_Evangelism<br />
|teamlead=Mark Coggins<br />
|mailinglist= [https://lists.mozilla.org/listinfo/evangelism evangelism@lists.mozilla.org]<br />
|description=Mozilla's Technology Evangelism group engages with developers and the broader web community to:<br />
*Share the Mozilla mission of openness, innovation and opportunity on the web <br />
*Encourage adoption of open web standards and open standards-based technology created by Mozilla and others in support of our mission<br />
*Provide developer enablement resources<br />
*Collect and champion developer feedback on Mozilla initiatives and technology<br />
*Understand competing initiatives and technology from for-profit players<br />
}}<section end=summary /><br />
<br />
== Communication Channels ==<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Name''' <br />
| style="background:#EFEFEF;" | '''Description''' <br />
| style="background:#EFEFEF;" | '''Location''' <br />
| style="background:#EFEFEF;" | '''Notes'''<br />
|-<br />
|Hacks Blog<br />
|Information about open web technology of interest to developers.<br />
|[https://hacks.mozilla.org/ hacks.mozilla.org]<br />
|[[Engagement/Developer Engagement/Hacks blog|Editorial guidelines and calendar]] <br />
|-<br />
|Hacks YouTube Video Channel<br />
|Videos of talks, demonstrations and how-tos.<br />
|[http://www.youtube.com/user/mozhacks/ Mozhacks on YouTube]<br />
|<br />
|-<br />
|Hacks on Twitter<br />
|Tweets about open web technology.<br />
|[https://twitter.com/mozhacks/ @mozhacks]<br />
|<br />
|-<br />
|Mozilla Apps Dev on Twitter<br />
|Tweets for open web app developers from Mozilla's Developer Relations team.<br />
|[https://twitter.com/mozappsdev @mozappsdev]<br />
|<br />
|-<br />
|Firefox Apps & Hacks<br />
|A (more-or-less) monthly newsletter for developers focused on Firefox OS, Firefox Marketplace, the Open Web Apps ecosystem<br />
|Subscribe [https://hacks.mozilla.org/newsletter here].<br />
|<br />
|-<br />
|Evangelism discussion group<br />
|Public discussion group about Mozilla evangelism activities<br />
|[https://lists.mozilla.org/listinfo/evangelism evangelism@lists.mozilla.org]<br />
|<br />
|-<br />
|Feedback channel on UserVoice<br />
|Feedback channel for ideas for the Developer Tools in Firefox<br />
|[http://mzl.la/devtools http://mzl.la/devtools]<br />
|<br />
|-<br />
|Stack Overflow<br />
|Sponsored tags by Mozilla on Stack Overflow<br />
|[http://stackoverflow.com/r/mozilla http://stackoverflow.com/r/mozilla]<br />
|<br />
|}<br />
<br />
== Team: Role & Focus ==<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Name''' <br />
| style="background:#EFEFEF;" | '''Role''' <br />
| style="background:#EFEFEF;" | '''Q3 Focus'''<br />
|-<br />
|[https://mozillians.org/en-US/u/mcoggins/ Mark Coggins]<br />
|Team lead.<br />
|Plan and lead execution of the Firefox OS developer engagement initiative.<br />
|-<br />
|[https://mozillians.org/en-US/u/fharper/ Frédéric Harper]<br />
|Firefox OS Evangelist. Work his magic to help Firefox OS developers to be successful.<br />
|Recruit developers--and their apps--to the Firefox OS platform.<br />
|-<br />
|[https://mozillians.org/en-US/u/cheilmann/ Christian Heilmann]<br />
|Principal Developer Evangelist. Making the world love HTML5 and the open web as much as I do. Helping Mozilla folk to speak to developers.<br />
|Train and recruit volunteer evangelists and speakers, update speaker reps materials and represent Tech Evan on the developer event committee.<br />
|-<br />
|[https://mozillians.org/en-US/u/havi/ Havi Hoffman]<br />
|Content wrangler. Creating developer content, planning developer events and moving information across time and space.<br />
|Strategy for Firefox OS Apps Workshops and "Phones for App" program. Increase participation on Transifex Apps [https://www.transifex.com/organization/mozilla-tech-evangelism/ Localization Project].<br />
|-<br />
|[https://mozillians.org/en-US/u/robert/ Robert Nyman]<br />
|Technical Evangelist. Editor of Mozilla Hacks.<br />
|Increase readership of Hacks Blog. Capture developer feedback through User Voice.<br />
|-<br />
|[https://mozillians.org/en-US/u/jweathersby/ Jason Weathersby]<br />
|Firefox OS Evangelist.<br />
|Recruit developers--and their apps--to the Firefox OS platform.<br />
|}<br />
<br />
== Key Q3 Goals ==<br />
* Enable acceptance of 900 new Firefox OS apps in the Marketplace from independent developers (aka "long tail developers"), 195 of which were created by developers with whom we have a direct relationship.<br />
* Complete full plan for recruiting, training and rewarding volunteer evangelists and speakers.<br />
<br />
== Key Initiatives ==<br />
* [[Engagement/Developer_Engagement/Technical_Evangelism/Get_Involved|Volunteer Evangelists and Speakers]]<br />
* [http://stackoverflow.com/r/mozilla Mozilla on StackOverflow]<br />
* [[Engagement/Developer_Engagement/FirefoxOS-porting-training|Firefox OS App Migration Workshops]]<br />
* [[ReMo/SOPs/AppDaysInABox|App Days in a Box]]<br />
* [https://mozhacks.wufoo.com/forms/apps-on-a-flame/ Phones for Apps Program]<br />
* [https://www.transifex.com/organization/mozilla-tech-evangelism/ Firefox OS App Localization on Transifex]<br />
* [https://ffdevtools.uservoice.com/ Developer feedback through User Voice]<br />
<br />
== Events ==<br />
<br />
* [https://developer.mozilla.org/en-US/events Where is Mozilla schedule]<br />
* [https://bugzilla.mozilla.org/form.dev-engagement-event Event Sponsorship Bugzilla Form]</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog&diff=967840Engagement/Developer Engagement/Hacks blog2014-04-23T07:58:27Z<p>Robnyman: /* General focus/topics */</p>
<hr />
<div>==What Mozilla Hacks is - our vision==<br />
<br />
Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be one of the key resources for people developing for the Open Web, talking about both news and in-depth descriptions of technologies and features. We will cover both development tips and tricks in general, but also look at features in Mozilla's products from a technical perspective - to show our approach and line of thinking, and hopefully inspire other companies to implement what we have.<br />
<br />
Mozilla Hacks is, just like [https://developer.mozilla.org/ MDN (Mozilla Developer Network)], a web browser agnostic resource, focused on the Open Web and sharing knowledge with all web developers out there.<br />
<br />
Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We aim to have original content. If we find an interesting blog post, we might highlight it, but always with our own take.<br />
<br />
Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more.<br />
<br />
==Goals==<br />
<br />
Mozilla Hacks aims to be one of the key web sites people will turn to for unbiased and expert knowledge about developing. Our intent is to have at least three descriptive articles per week, explaining a feature or technology. <br />
<br />
==Writers/contributors==<br />
<br />
Members of the Developer Engagement Team are writing for Mozilla Hacks, but any other Mozillian is also welcome to contribute! If you know something interesting that would be great to share with the readers of Mozilla Hacks, please let us know! We can be reached at mozhacks [at] mozilla [dot] com. When it comes to personal branding, we hope that the exposure you will get - both as an author and in the Mozilla context - will be good motivation for deciding to write for Mozilla Hacks!<br />
And if you have the technical expertise, but aren't sure about the writing, we'd be more than happy to help put together an article together with you.<br />
<br />
We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed.<br />
<br />
We would also like to feature guest posts from prominent people within the web business. There are so many talented people out there, and we would love to highlight and share your knowledge!<br />
<br />
==Author responsibility==<br />
<br />
We can't stress enough that Mozilla Hacks is not a billboard or announcement channel. It is there for us to have a dialog with developers out there, to hear their opinions, give them clarifications and for them to voice their takes on what we say. A blog post author is responsible for moderating and replying to comments. Not every comment needs a reply, but questions and similar should be addressed. People take the time to read and to comment, and they deserve the respect to have that communication. Also be aware that comments can be quoted in press, direct questions from journalists and similar, so please reach out to Mozilla press if you want/need to verify your statement.<br />
<br />
It is also a long term base for a good relations with developers based on mutual respect and communication.<br />
<br />
==Behavior guidelines==<br />
<br />
Mozilla Hacks is a place based on mutual respect and understanding, and the way we address each other is supposed to reflect that. We expect anyone writing or commenting to use proper laguage and refrain from insulting other people. We reserve the right to remove anything that doesn't qualify as decent behavior towards other people.<br />
<br />
==Publishing posts==<br />
<br />
Blog posts should be added to the Mozilla Hacks blog calendar in good time before - it now resides internally in Zimbra. E-mail mozhacks [at] mozilla [dot] com for access, to have an overview of what is being planned.<br />
Everything that is to be published needs to be approved before, by Robert Nyman, Christian Heilmann or Stormy Peters - or Developer Engagement otherwise if they aren't reachable (see contact information above). We would like at least a few days notice before posting, to read through it and ensure it is both on topic and phrased in a way suitable for Mozilla Hacks.<br />
<br />
We generally refrain from posts on Fridays, US time, since then the rest of the world have moved into weekend, meaning that we won't be available to reply to comments or handle any other feedback<br />
<br />
==Writing for Mozilla Hacks==<br />
<br />
When it comes to more detailed questions on how to format content for a blog post, which plugins are supported and more, read more in the [https://wiki.mozilla.org/Engagement/Developer_Engagement/Hacks_blog/Writing Writing for Mozilla Hacks] guidelines.<br />
<br />
==Metrics==<br />
<br />
We are currently using Google Analytics, and monthly metrics reports are sent internally.<br />
<br />
==General focus/topics==<br />
<br />
These are general topics and areas we will cover<br />
<br />
* Open Web<br />
* HTML5<br />
* Firefox OS<br />
* Web APIs<br />
* Mozilla Products (engineer perspective)<br />
* Use cases<br />
** Evaluations and guides to HTML5 Apps & games<br />
* News in the web development world - short links, attention bits and more<br />
<br />
==Organization and Contact==<br />
<br />
Editor: Robert Nyman (robert@)<br />
<br />
Team:<br />
* Christian Heilmann (cheilmann@)<br />
* Janet Swisher (jswisher@)<br />
* Eric "Sheppy" Shepherd (eshepherd@)<br />
<br />
All e-mail addresses can be reached at @mozilla.com. Please contact any of the people above or mozhacks [at] mozilla [dot] com if you have any questions.</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog&diff=967835Engagement/Developer Engagement/Hacks blog2014-04-23T07:46:42Z<p>Robnyman: /* Metrics */</p>
<hr />
<div>==What Mozilla Hacks is - our vision==<br />
<br />
Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be one of the key resources for people developing for the Open Web, talking about both news and in-depth descriptions of technologies and features. We will cover both development tips and tricks in general, but also look at features in Mozilla's products from a technical perspective - to show our approach and line of thinking, and hopefully inspire other companies to implement what we have.<br />
<br />
Mozilla Hacks is, just like [https://developer.mozilla.org/ MDN (Mozilla Developer Network)], a web browser agnostic resource, focused on the Open Web and sharing knowledge with all web developers out there.<br />
<br />
Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We aim to have original content. If we find an interesting blog post, we might highlight it, but always with our own take.<br />
<br />
Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more.<br />
<br />
==Goals==<br />
<br />
Mozilla Hacks aims to be one of the key web sites people will turn to for unbiased and expert knowledge about developing. Our intent is to have at least three descriptive articles per week, explaining a feature or technology. <br />
<br />
==Writers/contributors==<br />
<br />
Members of the Developer Engagement Team are writing for Mozilla Hacks, but any other Mozillian is also welcome to contribute! If you know something interesting that would be great to share with the readers of Mozilla Hacks, please let us know! We can be reached at mozhacks [at] mozilla [dot] com. When it comes to personal branding, we hope that the exposure you will get - both as an author and in the Mozilla context - will be good motivation for deciding to write for Mozilla Hacks!<br />
And if you have the technical expertise, but aren't sure about the writing, we'd be more than happy to help put together an article together with you.<br />
<br />
We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed.<br />
<br />
We would also like to feature guest posts from prominent people within the web business. There are so many talented people out there, and we would love to highlight and share your knowledge!<br />
<br />
==Author responsibility==<br />
<br />
We can't stress enough that Mozilla Hacks is not a billboard or announcement channel. It is there for us to have a dialog with developers out there, to hear their opinions, give them clarifications and for them to voice their takes on what we say. A blog post author is responsible for moderating and replying to comments. Not every comment needs a reply, but questions and similar should be addressed. People take the time to read and to comment, and they deserve the respect to have that communication. Also be aware that comments can be quoted in press, direct questions from journalists and similar, so please reach out to Mozilla press if you want/need to verify your statement.<br />
<br />
It is also a long term base for a good relations with developers based on mutual respect and communication.<br />
<br />
==Behavior guidelines==<br />
<br />
Mozilla Hacks is a place based on mutual respect and understanding, and the way we address each other is supposed to reflect that. We expect anyone writing or commenting to use proper laguage and refrain from insulting other people. We reserve the right to remove anything that doesn't qualify as decent behavior towards other people.<br />
<br />
==Publishing posts==<br />
<br />
Blog posts should be added to the Mozilla Hacks blog calendar in good time before - it now resides internally in Zimbra. E-mail mozhacks [at] mozilla [dot] com for access, to have an overview of what is being planned.<br />
Everything that is to be published needs to be approved before, by Robert Nyman, Christian Heilmann or Stormy Peters - or Developer Engagement otherwise if they aren't reachable (see contact information above). We would like at least a few days notice before posting, to read through it and ensure it is both on topic and phrased in a way suitable for Mozilla Hacks.<br />
<br />
We generally refrain from posts on Fridays, US time, since then the rest of the world have moved into weekend, meaning that we won't be available to reply to comments or handle any other feedback<br />
<br />
==Writing for Mozilla Hacks==<br />
<br />
When it comes to more detailed questions on how to format content for a blog post, which plugins are supported and more, read more in the [https://wiki.mozilla.org/Engagement/Developer_Engagement/Hacks_blog/Writing Writing for Mozilla Hacks] guidelines.<br />
<br />
==Metrics==<br />
<br />
We are currently using Google Analytics, and monthly metrics reports are sent internally.<br />
<br />
==General focus/topics==<br />
<br />
These are general topics and areas we will cover<br />
<br />
* Open Web<br />
* HTML5<br />
* Firefox OS<br />
* Web APIs<br />
* Mozilla Products (engineer perspective) - Bleeding Edge Firefox etc<br />
* Recurring posts:<br />
** Hacks Weekly<br />
** Bi-weekly State of games<br />
** Monthly - most interesting posts on Mozilla Hacks<br />
** Monthly: Dev Derby winners<br />
** Monthly: Interview with most recent Derby winner (unless the winner doesn't want to)<br />
** Web Developer Toolbox: introductions to tools and libraries<br />
** Wiki Wednesday<br />
** State of the Docs<br />
* Use cases<br />
** Evaluations and guides to HTML5 Apps & games<br />
* News in the web development world - short links, attention bits and more<br />
* News related to MDN: doc sprints, etc.<br />
<br />
==Organization and Contact==<br />
<br />
Editor: Robert Nyman (robert@)<br />
<br />
Team:<br />
* Christian Heilmann (cheilmann@)<br />
* Janet Swisher (jswisher@)<br />
* Eric "Sheppy" Shepherd (eshepherd@)<br />
<br />
All e-mail addresses can be reached at @mozilla.com. Please contact any of the people above or mozhacks [at] mozilla [dot] com if you have any questions.</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=938168Engagement/Developer Engagement/Hacks blog/Writing2014-02-24T20:00:18Z<p>Robnyman: /* Installed Plug-ins */</p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com). Once the initial draft has been received, it will be added to the Mozilla Hacks blog and iterated on there, with revision and reviewer support.<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Mozilla Hacks author account==<br />
<br />
The Editor of Mozilla Hacks will set you up with an account. Make sure to have a bio ready and that your e-mail address is connected to a [https://en.gravatar.com/ Gravatar]. Additionally, please inform the Editor about potential website URLs, Twitter, Facebook and Google+ accounts you want to show with your profile.<br />
<br />
==Embedding media and https==<br />
<br />
The width of the content on Mozilla Hacks is 500 pixels. Make sure that images, embedded videos etc are adapted to that. If you want to add images to your post, please [https://hacks.mozilla.org/wp-admin/media-new.php upload them to Mozilla Hacks] and then reference their URL with an &lt;img&gt; element.<br />
<br />
<b>Note:</b> Mozilla Hacks is being served as https so if you embed anything, it has to support https as well, due to [https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ Mixed Content Blocking]. For instance, at the time of writing (April 26th 2013), YouTube and GitHub embeds supports https, Vimeo and jsFiddle doesn't.<br />
<br />
==Using code samples in your post==<br />
<br />
When you write code samples in your post, make sure to wrap code blocks spanning over multiple lines with <tt>&lt;pre&gt;</tt> elements. As described above, we use the GeSHI support to generate color highlighting for your code.<br />
To enable that, just use the <tt>lang</tt> attribute on the <tt>&lt;pre&gt;</tt> element, like this:<br />
<br />
<pre>&lt;pre lang="javascript"&gt;<br />
var URL = "https://hacks.mozilla.org/";<br />
&lt;/pre&gt;</pre><br />
<br />
For code formatting within text/paragraphs, wrap them with <tt>&lt;code&gt;</tt> elements:<br />
<br />
<pre>This is some text about the <code>canvas</code> element</pre><br />
<br />
<br />
Note:<br />
<br />
* Do <b>not</b> use &lt;code&gt; elements in code blocks wrapped with the <tt>&lt;pre&gt;</tt> element<br />
* Do <b>not</b> escape HTML entities like <, > and & with &amp;lt;, &amp;gt; and &amp;amp; in those code blocks<br />
<br />
Another option is also embedding gists or similar. Note: it has to support https (see above).<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=909695Engagement/Developer Engagement/Mozilla Developer Program2014-01-29T10:19:43Z<p>Robnyman: /* Activities */</p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|DONE: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|DONE: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program membership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
=== II. Membership offerings ===<br />
<br />
==== Dependencies ====<br />
<br />
* MDN Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Developer Profiles on on MDN<br />
|Robert Nyman, Luke Crouch<br />
|Ongoing: <br />
|-<br />
| Badges on MDN<br />
|Robert Nyman, Luke Crouch, Christie Koehler <br />
|Ongoing:<br />
|-<br />
| Localization offer for translating Apps<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
* Identity team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil Clouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil Clouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=909692Engagement/Developer Engagement/Mozilla Developer Program2014-01-29T10:18:48Z<p>Robnyman: /* Dependencies */</p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|DONE: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|DONE: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program membership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
=== II. Membership offerings ===<br />
<br />
==== Dependencies ====<br />
<br />
* MDN Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Developer Profiles on on MDN<br />
|Robert Nyman, Luke Crouch<br />
|Ongoing: <br />
|-<br />
| Badges on MDN<br />
|Robert Nyman, Luke Crouch, Christie Koehler <br />
|Ongoing:<br />
|-<br />
| Localization offer for translating Apps<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
* Identity team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=909689Engagement/Developer Engagement/Mozilla Developer Program2014-01-29T10:17:56Z<p>Robnyman: /* II. Enable one account for all developer facing web sites */</p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|DONE: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|DONE: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program membership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
=== II. Membership offerings ===<br />
<br />
==== Dependencies ====<br />
<br />
* MDN Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Developer Profiles on on MDN<br />
|Robert Nyman, Luke Crouch<br />
|Ongoing: <br />
|-<br />
| Badges on MDN<br />
|Robert Nyman, Luke Crouch, Christie Koehler <br />
|Ongoing:<br />
|-<br />
| Localization offer for translating Apps<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=909687Engagement/Developer Engagement/Mozilla Developer Program2014-01-29T10:16:59Z<p>Robnyman: /* Activities */</p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|DONE: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|DONE: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program membership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Developer Profiles on on MDN<br />
|Robert Nyman, Luke Crouch<br />
|Ongoing: <br />
|-<br />
| Badges on MDN<br />
|Robert Nyman, Luke Crouch, Christie Koehler <br />
|Ongoing:<br />
|-<br />
| Localization offer for translating Apps<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=909685Engagement/Developer Engagement/Mozilla Developer Program2014-01-29T10:16:01Z<p>Robnyman: /* Activities */</p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|DONE: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|DONE: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program membership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Developer Profiles on on MDN<br />
|Robert Nyman, Luke Crouch<br />
|Ongoing: <br />
|-<br />
| Badges on MDN<br />
|Robert Nyman, Luke Crouch<br />
|Ongoing:<br />
|-<br />
| Localization offer for translating Apps<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=909680Engagement/Developer Engagement/Mozilla Developer Program2014-01-29T10:11:53Z<p>Robnyman: /* Activities */</p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|DONE: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|DONE: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program membership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|DONE: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for constructive information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog&diff=807652Engagement/Developer Engagement/Hacks blog2013-12-19T22:40:29Z<p>Robnyman: </p>
<hr />
<div>==What Mozilla Hacks is - our vision==<br />
<br />
Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be one of the key resources for people developing for the Open Web, talking about both news and in-depth descriptions of technologies and features. We will cover both development tips and tricks in general, but also look at features in Mozilla's products from a technical perspective - to show our approach and line of thinking, and hopefully inspire other companies to implement what we have.<br />
<br />
Mozilla Hacks is, just like [https://developer.mozilla.org/ MDN (Mozilla Developer Network)], a web browser agnostic resource, focused on the Open Web and sharing knowledge with all web developers out there.<br />
<br />
Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We aim to have original content. If we find an interesting blog post, we might highlight it, but always with our own take.<br />
<br />
Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more.<br />
<br />
==Goals==<br />
<br />
Mozilla Hacks aims to be one of the key web sites people will turn to for unbiased and expert knowledge about developing. Our intent is to have at least three descriptive articles per week, explaining a feature or technology. <br />
<br />
==Writers/contributors==<br />
<br />
Members of the Developer Engagement Team are writing for Mozilla Hacks, but any other Mozillian is also welcome to contribute! If you know something interesting that would be great to share with the readers of Mozilla Hacks, please let us know! We can be reached at mozhacks [at] mozilla [dot] com. When it comes to personal branding, we hope that the exposure you will get - both as an author and in the Mozilla context - will be good motivation for deciding to write for Mozilla Hacks!<br />
And if you have the technical expertise, but aren't sure about the writing, we'd be more than happy to help put together an article together with you.<br />
<br />
We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed.<br />
<br />
We would also like to feature guest posts from prominent people within the web business. There are so many talented people out there, and we would love to highlight and share your knowledge!<br />
<br />
==Author responsibility==<br />
<br />
We can't stress enough that Mozilla Hacks is not a billboard or announcement channel. It is there for us to have a dialog with developers out there, to hear their opinions, give them clarifications and for them to voice their takes on what we say. A blog post author is responsible for moderating and replying to comments. Not every comment needs a reply, but questions and similar should be addressed. People take the time to read and to comment, and they deserve the respect to have that communication. Also be aware that comments can be quoted in press, direct questions from jouranlists and similar, so please reach out to Mozilla press if you want/need to verify your statement.<br />
<br />
It is also a long term base for a good relations with developers based on mutual respect and communication.<br />
<br />
==Behavior guidelines==<br />
<br />
Mozilla Hacks is a place based on mutual respect and understanding, and the way we address each other is supposed to reflect that. We expect anyone writing or commenting to use proper laguage and refrain from insulting other people. We reserve the right to remove anything that doesn't qualify as decent behavior towards other people.<br />
<br />
==Publishing posts==<br />
<br />
Blog posts should be added to the Mozilla Hacks blog calendar in good time before - it now resides internally in Zimbra. E-mail mozhacks [at] mozilla [dot] com for access, to have an overview of what is being planned.<br />
Everything that is to be published needs to be approved before, by Robert Nyman, Christian Heilmann or Stormy Peters - or Developer Engagement otherwise if they aren't reachable (see contact information above). We would like at least a few days notice before posting, to read through it and ensure it is both on topic and phrased in a way suitable for Mozilla Hacks.<br />
<br />
We generally refrain from posts on Fridays, US time, since then the rest of the world have moved into weekend, meaning that we won't be available to reply to comments or handle any other feedback<br />
<br />
==Writing for Mozilla Hacks==<br />
<br />
When it comes to more detailed questions on how to format content for a blog post, which plugins are supported and more, read more in the [https://wiki.mozilla.org/Engagement/Developer_Engagement/Hacks_blog/Writing Writing for Mozilla Hacks] guidelines.<br />
<br />
==Metrics==<br />
<br />
We are currently using Google Analytics, and biweekly metrics reports are sent internally.<br />
<br />
==General focus/topics==<br />
<br />
These are general topics and areas we will cover<br />
<br />
* Open Web<br />
* HTML5<br />
* Firefox OS<br />
* Web APIs<br />
* Mozilla Products (engineer perspective) - Bleeding Edge Firefox etc<br />
* Recurring posts:<br />
** Hacks Weekly<br />
** Bi-weekly State of games<br />
** Monthly - most interesting posts on Mozilla Hacks<br />
** Monthly: Dev Derby winners<br />
** Monthly: Interview with most recent Derby winner (unless the winner doesn't want to)<br />
** Web Developer Toolbox: introductions to tools and libraries<br />
** Wiki Wednesday<br />
** State of the Docs<br />
* Use cases<br />
** Evaluations and guides to HTML5 Apps & games<br />
* News in the web development world - short links, attention bits and more<br />
* News related to MDN: doc sprints, etc.<br />
<br />
==Organization and Contact==<br />
<br />
Editor: Robert Nyman (robert@)<br />
<br />
Team:<br />
* Christian Heilmann (cheilmann@)<br />
* Janet Swisher (jswisher@)<br />
* Eric "Sheppy" Shepherd (eshepherd@)<br />
<br />
All e-mail addresses can be reached at @mozilla.com. Please contact any of the people above or mozhacks [at] mozilla [dot] com if you have any questions.</div>Robnymanhttps://wiki.mozilla.org/index.php?title=MDN/Development&diff=788570MDN/Development2013-12-12T21:27:46Z<p>Robnyman: /* Proposed Projects */</p>
<hr />
<div>The MDN site is under active development and is constantly evolving. In addition to the paid engineering, writing and product teams, the MDN community contributes feature requests, helps prioritize work and contributes code to the platform. <br />
<br />
=Development Process=<br />
In March of 2013, the MDN development team switched from using Agile to a continuous deployment process using Kanban. <br />
* [https://wiki.mozilla.org/MDN/Development/drivers Work Prioritization process] - MDN-drivers<br />
* Overview of the MDN Kanban-based development [[/Process|process]]<br />
* [[/Plans|Archive]] of Agile development sprints<br />
<br />
==Following development in real time==<br />
<br />
If you want to stay in the loop on a bug or a set of bugs, be sure to add yourself to the "cc" list. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are automatically pushed to the dev server every 5 minutes:<br />
<br />
https://developer-dev.allizom.org/<br />
<br />
The dev team pushes commits to stage and production servers when the code is ready. You can see which commits are on the stage & production servers here:<br />
<br />
http://mzl.la/mdn_whats_deployed<br />
<br />
Commits also often include numbers of bugs that you can visit to see relevant discussions.<br />
<br />
=Platform=<br />
<br />
*[https://github.com/mozilla/kuma Kuma on github]<br />
* [https://developer.mozilla.org/Project:en/Getting_started_with_Kuma Getting started with Kuma]<br />
* [https://developer.mozilla.org/Project:en/Introduction_to_KumaScript Introduction to KumaScript]<br />
* [[MDN/Development/Contribute/Development|Contributing to development]]<br />
* [[MDN/Development/Contribute/Design|Contributing to design]]<br />
<br />
=Roadmap/Status=<br />
*[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtB4DXCweXv2dHNqUXZTdFJmaXY1a1hwT2IyYTR4NUE#gid=0 MDN 2013 Roadmap]<br />
* Notes from our January 2013 [https://etherpad.mozilla.org/MDN-Austin-2013 planning meeting in Austin]<br />
* Notes from our August 2012 [https://etherpad.mozilla.org/MDN-Toronto-2012 planning meeting in Toronto]<br />
<br />
<br />
For notifications about changes to the MDN, please subscribe to our [http://bit.ly/mdn-dev-rss-released feed of released changes]. For more technical information about a change, click through from that feed entry to the Bugzilla ticket the entry is associated with. You can also follow our [https://github.com/mozilla/kuma/commits/master.atom feed of all source code commits] or watch this page for an [https://developer.mozilla.org/en-US/docs/Project:Changelog overview of commits pushed to production].<br />
<br />
All of these resources provide essentially the same information, just in slightly different formats.<br />
<br />
=Projects=<br />
==Current Projects==<br />
====[[/Redesign|MDN Redesign]]====<br />
*Large project aimed at rebranding & redesigning MDN to better serve developers as users and contributors.<br />
<br />
====Localization dashboard====<br />
*The [[MDN/Development/Localization dashboard|localization dashboard]] will make it easier for our localization teams to do their work.<br />
<br />
==Proposed Projects==<br />
<br />
====Badges====<br />
*Proposal for [https://wiki.mozilla.org/MDN/Development/Badges Badges] on MDN, being managed by Florian<br />
<br />
====Metrics====<br />
*Proposal for [[MDN/Development/Metrics|Metrics]] on MDN, being managed by [[User:Groovecoder|groovecoder]]<br />
<br />
====Product versioning====<br />
*Proposal to support [[MDN/Development/Product_Versioning|product versioning]], proposed by Will<br />
<br />
====[[/GitHub_Integration|GitHub Integration]]====<br />
*Proposal for what GitHub integration might look like.<br />
<br />
====Git backend for wiki====<br />
*Proposal for [[MDN/Development/GitBackend|migrating to Git as the data backend for the wiki]], proposed by [[User:LesOrchard|lorchard]]<br />
<br />
====Page building blocks====<br />
*Proposed [[MDN/Development/BuildingBlocks|building blocks]] for the page templates and building blocks project requirement.<br />
<br />
====Improving compatibility tables====<br />
*Proposal to improve MDN's [[MDN/Development/CompatibilityTables|compatibility tables]], proposed by [[User:Jeremie|Jeremie]] and Daniel Buchner<br />
<br />
====Accessibility Review====<br />
* will kickoff in 2014<br />
<br />
====Mobile/Tablet & Offline Experience for MDN====<br />
* will kickoff in 2014<br />
<br />
====Mozilla Hacks Localization====<br />
*Proposal for [[MDN/Development/HacksLocalization|Mozilla Hacks Localization]], being managed by [[User:Robnyman|Robert Nyman]]<br />
<br />
==Completed Projects==<br />
<br />
====Google Summer of Code====<br />
*The Mozilla Developer Network team will be hosting a Google Summer of Code this summer. The project will center around building a Localization Dashboard to track localization status and help localizers find articles that need to be updated. <br />
*For more information, please see our [[/Google_Summer_of_Code_2013|Google Summer of Code 2013]] page.<br />
<br />
=Subpages=<br />
This is a list of all subpages of this page.<br />
{{Subpagelist}}<br />
<br />
== Contact ==<br />
* [[MDN/Development/Team|The team]]<br />
* For regular updates about development status, please join [https://lists.mozilla.org/options/dev-mdn our mailing list].<br />
<br />
__NOTOC__</div>Robnymanhttps://wiki.mozilla.org/index.php?title=MDN/Development&diff=788567MDN/Development2013-12-12T21:26:37Z<p>Robnyman: /* Proposed Projects */</p>
<hr />
<div>The MDN site is under active development and is constantly evolving. In addition to the paid engineering, writing and product teams, the MDN community contributes feature requests, helps prioritize work and contributes code to the platform. <br />
<br />
=Development Process=<br />
In March of 2013, the MDN development team switched from using Agile to a continuous deployment process using Kanban. <br />
* [https://wiki.mozilla.org/MDN/Development/drivers Work Prioritization process] - MDN-drivers<br />
* Overview of the MDN Kanban-based development [[/Process|process]]<br />
* [[/Plans|Archive]] of Agile development sprints<br />
<br />
==Following development in real time==<br />
<br />
If you want to stay in the loop on a bug or a set of bugs, be sure to add yourself to the "cc" list. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are automatically pushed to the dev server every 5 minutes:<br />
<br />
https://developer-dev.allizom.org/<br />
<br />
The dev team pushes commits to stage and production servers when the code is ready. You can see which commits are on the stage & production servers here:<br />
<br />
http://mzl.la/mdn_whats_deployed<br />
<br />
Commits also often include numbers of bugs that you can visit to see relevant discussions.<br />
<br />
=Platform=<br />
<br />
*[https://github.com/mozilla/kuma Kuma on github]<br />
* [https://developer.mozilla.org/Project:en/Getting_started_with_Kuma Getting started with Kuma]<br />
* [https://developer.mozilla.org/Project:en/Introduction_to_KumaScript Introduction to KumaScript]<br />
* [[MDN/Development/Contribute/Development|Contributing to development]]<br />
* [[MDN/Development/Contribute/Design|Contributing to design]]<br />
<br />
=Roadmap/Status=<br />
*[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtB4DXCweXv2dHNqUXZTdFJmaXY1a1hwT2IyYTR4NUE#gid=0 MDN 2013 Roadmap]<br />
* Notes from our January 2013 [https://etherpad.mozilla.org/MDN-Austin-2013 planning meeting in Austin]<br />
* Notes from our August 2012 [https://etherpad.mozilla.org/MDN-Toronto-2012 planning meeting in Toronto]<br />
<br />
<br />
For notifications about changes to the MDN, please subscribe to our [http://bit.ly/mdn-dev-rss-released feed of released changes]. For more technical information about a change, click through from that feed entry to the Bugzilla ticket the entry is associated with. You can also follow our [https://github.com/mozilla/kuma/commits/master.atom feed of all source code commits] or watch this page for an [https://developer.mozilla.org/en-US/docs/Project:Changelog overview of commits pushed to production].<br />
<br />
All of these resources provide essentially the same information, just in slightly different formats.<br />
<br />
=Projects=<br />
==Current Projects==<br />
====[[/Redesign|MDN Redesign]]====<br />
*Large project aimed at rebranding & redesigning MDN to better serve developers as users and contributors.<br />
<br />
====Localization dashboard====<br />
*The [[MDN/Development/Localization dashboard|localization dashboard]] will make it easier for our localization teams to do their work.<br />
<br />
==Proposed Projects==<br />
<br />
====Badges====<br />
*Proposal for [https://wiki.mozilla.org/MDN/Development/Badges Badges] on MDN, being managed by Florian<br />
<br />
====Metrics====<br />
*Proposal for [[MDN/Development/Metrics|Metrics]] on MDN, being managed by [[User:Groovecoder|groovecoder]]<br />
<br />
====Product versioning====<br />
*Proposal to support [[MDN/Development/Product_Versioning|product versioning]], proposed by Will<br />
<br />
====[[/GitHub_Integration|GitHub Integration]]====<br />
*Proposal for what GitHub integration might look like.<br />
<br />
====Git backend for wiki====<br />
*Proposal for [[MDN/Development/GitBackend|migrating to Git as the data backend for the wiki]], proposed by [[User:LesOrchard|lorchard]]<br />
<br />
====Page building blocks====<br />
*Proposed [[MDN/Development/BuildingBlocks|building blocks]] for the page templates and building blocks project requirement.<br />
<br />
====Improving compatibility tables====<br />
*Proposal to improve MDN's [[MDN/Development/CompatibilityTables|compatibility tables]], proposed by [[User:Jeremie|Jeremie]] and Daniel Buchner<br />
<br />
====Accessibility Review====<br />
* will kickoff in 2014<br />
<br />
====Mobile/Tablet & Offline Experience for MDN====<br />
* will kickoff in 2014<br />
<br />
====Mozilla Hacks Localization====<br />
*Proposal for [[MDN/Development/Metrics|HacksLocalization]], being managed by [[User:Robnyman|Robert Nyman]]<br />
<br />
https://wiki.mozilla.org/MDN/Development/HacksLocalization<br />
<br />
==Completed Projects==<br />
<br />
====Google Summer of Code====<br />
*The Mozilla Developer Network team will be hosting a Google Summer of Code this summer. The project will center around building a Localization Dashboard to track localization status and help localizers find articles that need to be updated. <br />
*For more information, please see our [[/Google_Summer_of_Code_2013|Google Summer of Code 2013]] page.<br />
<br />
=Subpages=<br />
This is a list of all subpages of this page.<br />
{{Subpagelist}}<br />
<br />
== Contact ==<br />
* [[MDN/Development/Team|The team]]<br />
* For regular updates about development status, please join [https://lists.mozilla.org/options/dev-mdn our mailing list].<br />
<br />
__NOTOC__</div>Robnymanhttps://wiki.mozilla.org/index.php?title=MDN/Projects/Development/Hacks_Localization&diff=788565MDN/Projects/Development/Hacks Localization2013-12-12T21:24:32Z<p>Robnyman: /* Project statement */</p>
<hr />
<div>'''Note: This is a first draft Dec 12 2013'''<br />
<br />
== Project statement ==<br />
Offer [http://hacks.mozilla.org/ Mozilla Hacks] in a number of different languages. Currently, almost one third of the visitors are from North America, and together, North America and Europe have about 72% of all the visitors. Meaning, the possibilities are endless when it comes to places like South America and Asia, where English knowledge isn't as strong.<br />
<br />
By localizing Mozilla Hacks - and we have lots of communities interested in doing the actual translations - we'll be able to reach a much wider and more disperse audience. Offering a product in many languages has also been a key driving factor for Firefox, and has given us a lot of goodwill and following, and I see this as an extension to that.<br />
<br />
Measuring the size of the opportunity and the impact of the project would easily be seen in more unique visitors to Mozilla Hacks overall, with the new addition stemming from more countries with more non-native English speakers.<br />
<br />
It is also a great opportunity to foster and increase our localization community.<br />
<br />
== Implementation resources ==<br />
# Develop our own WordPress L10N plugin that would be secure and hopefully portable to other blogs. Previous investigation showed the available plugins to have security issues and were not approved by Security Assurance. <br />
# Build completely separate instances of a blog and host the localized template and content at a different URL. Not very elegant, but it works.<br />
# Have localized content as separate duplicate blog posts but keep an en-US base template for the header and footer.<br />
<br />
(1 is preferable, 2 would be too much maintenance, and 3 is doable as a second option)<br />
<br />
== Next Steps ==<br />
* Feedback / more ideas</div>Robnymanhttps://wiki.mozilla.org/index.php?title=MDN/Projects/Development/Hacks_Localization&diff=788564MDN/Projects/Development/Hacks Localization2013-12-12T21:24:18Z<p>Robnyman: Created page with "'''Note: This is a first draft Dec 12 2013''' == Project statement == Offer [http://hacks.mozilla.org/ Mozilla Hacks]in a number of different languages. Currently, almost one..."</p>
<hr />
<div>'''Note: This is a first draft Dec 12 2013'''<br />
<br />
== Project statement ==<br />
Offer [http://hacks.mozilla.org/ Mozilla Hacks]in a number of different languages. Currently, almost one third of the visitors are from North America, and together, North America and Europe have about 72% of all the visitors. Meaning, the possibilities are endless when it comes to places like South America and Asia, where English knowledge isn't as strong.<br />
<br />
By localizing Mozilla Hacks - and we have lots of communities interested in doing the actual translations - we'll be able to reach a much wider and more disperse audience. Offering a product in many languages has also been a key driving factor for Firefox, and has given us a lot of goodwill and following, and I see this as an extension to that.<br />
<br />
Measuring the size of the opportunity and the impact of the project would easily be seen in more unique visitors to Mozilla Hacks overall, with the new addition stemming from more countries with more non-native English speakers.<br />
<br />
It is also a great opportunity to foster and increase our localization community.<br />
<br />
== Implementation resources ==<br />
# Develop our own WordPress L10N plugin that would be secure and hopefully portable to other blogs. Previous investigation showed the available plugins to have security issues and were not approved by Security Assurance. <br />
# Build completely separate instances of a blog and host the localized template and content at a different URL. Not very elegant, but it works.<br />
# Have localized content as separate duplicate blog posts but keep an en-US base template for the header and footer.<br />
<br />
(1 is preferable, 2 would be too much maintenance, and 3 is doable as a second option)<br />
<br />
== Next Steps ==<br />
* Feedback / more ideas</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=779728Engagement/Developer Engagement/Mozilla Developer Program2013-12-03T18:51:08Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for constructive information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=779724Engagement/Developer Engagement/Mozilla Developer Program2013-12-03T18:50:10Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in Q&A and forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Q&A, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, Q&A interaction and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in Q&A initiatives<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching Q&A on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate Q&A in the MDN Content Zone. Offer search capabilities and listing latest questions through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Meetings&diff=779546Engagement/Developer Engagement/Meetings2013-12-03T15:34:37Z<p>Robnyman: /* Meeting Notes */</p>
<hr />
<div>= Mozilla Developer Program Weekly Meetings =<br />
<br />
==Meeting Details==<br />
*Every Tuesday @ 9:00am Pacific Time (16:00 UTC through November 6) <br />
*IRC: irc.mozilla.org #devrel<br />
<br />
==Meeting Notes==<br />
* [https://etherpad.mozilla.org/devengage-2013-12-03 Dec 3, 2013]<br />
* [https://devengage.etherpad.mozilla.org/devengage-2013-10-22 Oct 22, 2013]<br />
* [https://devengage.etherpad.mozilla.org/26 Oct 15, 2013]<br />
* [https://devengage.etherpad.mozilla.org/22 Oct 1, 2013]<br />
* [https://devengage.etherpad.mozilla.org/21 Sept 24, 2013]<br />
* [https://devengage.etherpad.mozilla.org/19 Sept 17, 2013]<br />
<subpages kidsonly="yes" sort="desc" /></div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Meetings&diff=778996Engagement/Developer Engagement/Meetings2013-12-02T18:46:35Z<p>Robnyman: /* Meeting Notes */</p>
<hr />
<div>= Mozilla Developer Program Weekly Meetings =<br />
<br />
==Meeting Details==<br />
*Every Tuesday @ 9:00am Pacific Time (16:00 UTC through November 6) <br />
*IRC: irc.mozilla.org #devrel<br />
<br />
==Meeting Notes==<br />
* [https://devengage.etherpad.mozilla.org/devengage-2013-12-03 Dec 3, 2013]<br />
* [https://devengage.etherpad.mozilla.org/devengage-2013-10-22 Oct 22, 2013]<br />
* [https://devengage.etherpad.mozilla.org/26 Oct 15, 2013]<br />
* [https://devengage.etherpad.mozilla.org/22 Oct 1, 2013]<br />
* [https://devengage.etherpad.mozilla.org/21 Sept 24, 2013]<br />
* [https://devengage.etherpad.mozilla.org/19 Sept 17, 2013]<br />
<subpages kidsonly="yes" sort="desc" /></div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Engagement-Offsite-2014-January&diff=774226Engagement/Engagement-Offsite-2014-January2013-11-25T18:15:12Z<p>Robnyman: </p>
<hr />
<div>=All Engagement Offsite, January 2014=<br />
<br />
==Location & Dates==<br />
<br />
* Bay Area - place TBD<br />
* Dates: 01/13-17 (Monday and Friday being travel days)<br />
<br />
==Agenda==<br />
*Here's a link to the [https://etherpad.mozilla.org/Engagement-Offsite-2014] Etherpad for adding session proposals and agenda topics for the working days<br />
<br />
==Travel Info==<br />
Your name in the following table is considered an RSVP.<br />
*Please add a number next to your first and last names, arrival and departure dates and any dietary restrictions. <br />
We will use this document to make hotel reservation for the offsite (check in on Monday - check out on Friday). <br />
* For airline tickets and any additional hotel days, please book through Egencia.<br />
<br />
==Travel Details==<br />
{| class="fullwidth-table" <br />
! Full Name || Arrival and Departure Dates || Dietary restrictions<br />
|-<br />
| 1. William Reynolds || 01/13-17 || Paleo (no grains, gluten, dairy or soy)<br />
|- <br />
| 2. Luciana Vianna || 01/13-17 || None<br />
|- <br />
| 3. Grace Jimenez || 01/13-17 || None<br />
|- <br />
| 4. Pete Scanlon || 01/13-17 || Vegetarian <br />
|- <br />
| 5. Jean Collings || 01/13-17 || None<br />
|- <br />
| 6. Kristin Baird || 01/13-16 || None <br />
|-<br />
| 7. Ibai Garcia || 01/13-17 || None <br />
|-<br />
| 8. Jessilyn Davis || 01/13-17 || Vegetarian <br />
|- <br />
| 9. Karolina Shaw || 01/11-16 (11-13 in SF) || No grains (rice, pasta, wheat, oats)<br />
|- <br />
|10. Roland Tanglao || 01/13-17 || None<br />
|-<br />
|11. John Bernard || 01/13-16 || None<br />
|-<br />
|12. Kadir Topal || 01/13-17 || Vegetarian<br />
|-<br />
|13. Chris Heilmann || 01/11-18 || Paleo<br />
|-<br />
|14. Jesse Montano || 01/14-17 || None<br />
|-<br />
|15. Katherine Naszradi || 01/14-17 || None<br />
|-<br />
|16. Mike Manning || 01/13-17 || None<br />
|-<br />
|17. Carmen Collins || 01/13-16 || Gluten Free<br />
|-<br />
|18. Michael Kelly || 01/13-17 || I like hot chocolate!<br />
|-<br />
|19. Ali Spivak || 01/13-17 (local) || Gluten Free<br />
|-<br />
|20. Dan Horner || 01/13-17 || Paleo<br />
|-<br />
|21. Laura Forrest || 01/13-17 || Paleo<br />
|-<br />
|22. Shannon Prior || 01/13-17 || None<br />
|-<br />
|23. Matej Novak || 01/12–18 || None<br />
|-<br />
|24. Chelsea Novak || 01/12–18 || Severe Peanut Allergy<br />
|-<br />
|25. Michelle Luna || 01/13-17 || None<br />
|-<br />
|26. Havi Hoffman || 01/14-17 || None <br />
|-<br />
|27. Frédéric Harper || 01/11-18 || None <br />
|-<br />
|28. Giorgos Logiotatidis || 01/12-18 || None <br />
|-<br />
|29. Alex Gibson || 01/12-18 || None <br />
|-<br />
|30. Gen Kanai || 01/13-17 || None<br />
|-<br />
|31. Jessica Osorio || 01/13-17 || None<br />
|-<br />
|32. Lee Tom || 01/13-15 || None<br />
|-<br />
|33. Angelina Fabbro || 01/13-17 || Lactose intolerant<br />
|-}<br />
|34. Sakina Groth || 01/13-17 || Vegetarian<br />
|-}<br />
|35. Michael Ellis || 01/13-17 || None<br />
|-}<br />
|36. Marcia Zikan || 01/13-17 || None<br />
|-}<br />
|37. Josh Mize || 01/13-17 || No mammals<br />
|-}<br />
|38. Benjamin Sternthal || 01/13-17 || None<br />
|-}<br />
|39. Chris More || 01/13-17 || None<br />
|-}<br />
|40. Jennifer Bertsch || 01/13-17 || None<br />
|-}<br />
|41. Mike Alexis || 01/13-17 || No red meat; no eggs<br />
|-}<br />
|42. Florian Scholz || 01/12-24 (17-24 in SF) || None<br />
|-}<br />
|43. John Slater || 01/14-17 || None<br />
|-}<br />
|44. Chris Mills || 01/13-22 (17-22 in SF), arriving 2pm on the 13th || None<br />
|-}<br />
|45. Hermina Condei || 01/13-17 || None<br />
|-}<br />
|46. Michael Verdi || 01/12-18 || Vegan<br />
|-}<br />
|47. Brian King || 01/12-18 || None<br />
|-}<br />
|48. Holly Habstritt Gaal || 01/13-17 || None<br />
|-}<br />
|49. Madalina Ana || 01/13-18 || None<br />
|-}<br />
|50. Barry Munsterteiger || 01/13-17 || None<br />
|-}<br />
|51. Robert Nyman || 01/13-18 || None</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=764862Engagement/Developer Engagement/Mozilla Developer Program2013-11-19T00:44:08Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Apps & Marketplace ====<br />
<br />
* Apps & (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=764861Engagement/Developer Engagement/Mozilla Developer Program2013-11-19T00:43:01Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
==== Firefox Marketplace ====<br />
<br />
* Firefox Marketplace (Bill Walker, Fred Wenzel)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=764153Engagement/Developer Engagement/Mozilla Developer Program2013-11-18T11:47:12Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Partnerships (Universities, Code for America etc)<br />
|Robert Nyman, Bill Walker, Fred Wenzel<br />
|Idea phase.<br />
|-<br />
| Local data offerings<br />
|Robert Nyman, Market Research<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762052Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T12:28:16Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch. However, a stronger public push and marketing efforts belong to phase 2 (see below).<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|-<br />
| External push for the Developer Program, with associated marketing activities.<br />
|Sakina Groth, Robert Nyman, Stormy Peters<br />
|Idea phase.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762051Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T12:20:17Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism<br />
* MDN<br />
* Market research<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762050Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T12:18:46Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* <br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762048Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T12:17:05Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
== Components ==<br />
<br />
The Mozilla Developer Program consists of (subject to change over time):<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* <br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaiel, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaiel, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
| Establishing feedback channels for constructive information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Not started.<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762046Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T12:15:41Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
== Components ==<br />
<br />
In its first incarnation, the Mozilla Developer Program consists of:<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallel with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targeting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* <br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaiel, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaiel, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
| Establishing feedback channels for constructive information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Not started.<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762039Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T12:14:02Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
== Components ==<br />
<br />
In its first incarnation, the Mozilla Developer Program consists of:<br />
<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Content Zone on MDN]<br />
* Developer blog - [http://hacks.mozilla.org/ Mozilla Hacks]<br />
* [http://stackoverflow.com/r/mozilla Forums, on Stack Overflow]<br />
* Newsletter<br />
* MDN account<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallell with moving into new phases, e.g. membership, forums and more.<br />
<br />
Initially, the main initial group we're targetting is mobile developers who are developing for the mobile web as the first target, and help them with support, information and more about Firefox OS and the Open Web on mobile in general. This means developers who are:<br />
<br />
* Porting apps to HTML5<br />
* Building partial native/hybrid apps through PhoneGap and similar solutions<br />
* Offering the full mobile web experience, through Firefox OS or responsive HTML5 web sites<br />
<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
| Establishing feedback channels for cinstructite information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Planned.<br />
|}<br />
<br />
=== III. Broadening the offering ===<br />
<br />
==== Dependencies ====<br />
<br />
* <br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Q1 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaiel, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaiel, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
| Establishing feedback channels for constructive information and data gathering, and a good two-way communication with developers. Preferably per product/area, e.g. Developer Tools, WebAPIs.<br />
|Robert Nyman<br />
|Not started.<br />
|-<br />
| Acknowledgement for contributions, i.e. badges.<br />
|Robert Nyman, Christie Koehler<br />
|Idea phase.<br />
|-<br />
| Information about consumer needs (“I need an app for that”)<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Evaluating events for Developer Program members<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
| Help & rewards. Where a developer/localizer could, as a token of appreciation, get a support ticket with an engineer.<br />
|Robert Nyman<br />
|Idea phase.<br />
|-<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762022Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T11:09:15Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallell with moving into new phases, e.g. membership, forums and more.<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762021Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T11:08:26Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates.<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallell with moving into new phases, e.g. membership, forums and more.<br />
<br />
Explanations of the categories of activities used in each phase are shown below in the [[#Category Definitions | Category Definitions]] section.<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762020Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T11:07:49Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates..<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallell with moving into new phases, e.g. membership, forums and more.<br />
<br />
Explanations of the categories of activities used in each phase are shown below in the [[#Category Definitions | Category Definitions]] section.<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762019Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T11:03:44Z<p>Robnyman: </p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates..<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies<br />
<br />
== Audience ==<br />
<br />
====By Developer Type====<br />
<br />
*'''HTML5 Developers:''' <br />
**HTML5 Game Developers <br />
*'''Mobile App Developers:''' iPhone & Android app developers with an interesting in porting apps and learning the web<br />
*'''Web Developers:''' General web developers unfamiliar with HTML5 specifics/or mobile app UX who can be encouraged to build quality apps and more<br />
<br />
== Strategy ==<br />
<br />
* Unifying content and developer-focused offerings in a Content Zone on MDN<br />
* Engaging directly in forums with developers<br />
* Offering a membership, for free<br />
* Newsletter subscription<br />
* Evaluating data and features that will help developers choosing the web<br />
<br />
<br />
== Participants & Stakeholders ==<br />
<br />
==== Developer Engagement Team (Stormy Peters) ====<br />
<br />
* Technical Evangelism team (Mark Coggins) <br />
* Mozilla Developer Network (MDN) team (Ali Spivak) <br />
* Developer Program (Robert Nyman) <br />
* Engineering (Luke Crouch) <br />
* Contributors from the Global Mozilla community<br />
**Localizers<br />
**Speakers, community leaders and evangelism reps<br />
<br />
==== Developer Tools ====<br />
<br />
* Developer Tools (Dave Camp, Jeff Griffiths)<br />
<br />
<br />
== Activities by Phase ==<br />
<br />
The idea is to describe the activities and roadmap for the Developer Program by phase. It also means that started phases will most likely continue running while in parallell with moving into new phases, e.g. membership, forums and more.<br />
<br />
Explanations of the categories of activities used in each phase are shown below in the [[#Category Definitions | Category Definitions]] section.<br />
<br />
=== I. Create the Developer Program ===<br />
<br />
==== Dependencies ====<br />
<br />
* Technical Evangelism participation in forums<br />
* MDN engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* Started<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Creating content in a Content Zone on MDN<br />
|Robert Nyman, Chris Mills<br />
|Ongoing: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program Developer Program on MDN], [https://bugzilla.mozilla.org/show_bug.cgi?id=918127 Bug 918127]<br />
|-<br />
| Launching forums on Stack Overflow. Three tags sponsored by Mozilla: firefox, firefox-os, html5-apps. Manning by Firefox OS Evangelists, community members and any Mozillian<br />
|Robert Nyman, Mark Coggins<br />
|Launched: [http://stackoverflow.com/r/mozilla Mozilla's landing page on Stack Overflow]<br />
|-<br />
| Integrate forums in the MDN Content Zone. Offer search capabilities and listing latest forum posts through the [http://api.stackoverflow.com/ Stack Exchange API] <br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932705 Bug 932705]<br />
|-<br />
| Offer a Developer Program memvership. Initially this will be a MDN account - long-term plan is one account for all developer phasing web sites (see phase 2 below)<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707]<br />
|-<br />
| Include latest Mozilla Hacks posts in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932717 Bug 932717]<br />
|-<br />
| Offering a newsletter<br />
|Robert Nyman, Havi Hoffman<br />
|Newsletter exists. Rebranding a matter of publich launch ([https://bugzilla.mozilla.org/show_bug.cgi?id=932716 Bug 932716]).<br />
|-<br />
| Newsletter opt-in/sign-up as part of registering/editing a MDN account<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932707 Bug 932707], [https://bugzilla.mozilla.org/show_bug.cgi?id=936123 Bug 936123]<br />
|-<br />
| Integrate Where is Mozilla? in the Content Zone<br />
|Luke Crouch, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=935712 Bug 935712]<br />
|-<br />
| Soft launch the Developer Program. The idea is to have above activities in place, and publicly available, by early December, to coincide with the MDN redesign launch.<br />
|Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=932711 Bug 932711]<br />
|-}<br />
<br />
<br />
=== II. Enable one account for all developer facing web sites ===<br />
<br />
==== Dependencies ====<br />
<br />
* Identity team<br />
* MDN Engineering team<br />
* Marketplace & AMO Engineering team<br />
<br />
==== Anticipated Start Time ====<br />
<br />
* January 2014<br />
<br />
==== Activities ====<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background:#EFEFEF;" | '''Activity''' <br />
| style="background:#EFEFEF;" | '''Owner''' <br />
| style="background:#EFEFEF;" | '''Date/Link to Details'''<br />
|-<br />
| Single sign-on for MDN, Marketplace and AMO<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
| One central place for account administration. This could be owned by the Identity team, with possible site-specific preference to complement that.<br />
|Lloyd Hilaeil, Luke Crouch, Wil CLouser, Robert Nyman<br />
|Ongoing: [https://bugzilla.mozilla.org/show_bug.cgi?id=933031 Bug 933031]<br />
|-<br />
<br />
|-}</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=762011Engagement/Developer Engagement/Mozilla Developer Program2013-11-15T10:26:15Z<p>Robnyman: /* Mozilla Developer Program (MDP) */</p>
<hr />
<div>=Mozilla Developer Program (MDP)=<br />
<br />
<br />
'''Owners''': Robert Nyman, Stormy Peters<br />
<br />
'''Status''': Living document, subject to on-going revision and status updates..<br />
<br />
'''Feedback''': If you have good ideas and would like to contribute to the Developer Program and its activities, or you believe that your team should involved in a certain part, please feel free to reach out directly to Robert: robert [at] mozilla [dot] com<br />
<br />
== Goals ==<br />
<br />
<blockquote>''Enable, inspire and collaborate to make the Web the primary platform used to create experiences across all connected devices.''</blockquote><br />
<br />
The Mozilla Developer Program (MDP) is aimed at building long-term relationships with developers, to include and introduce them in what we do and act as a complement specifically to our Evangelism, MDN and the Firefox Marketplace. It is about tying together our developer facing efforts, and it also exists to continue the work for the Mozilla mission, inspiring people to use open standards no matter which platform they work on. <br />
<br />
We want to help introduce developers to open web technologies, inspire them to contribute and help them out with their endeavours. The idea is also to cater to developers looking for something to sign up for and belong to, which is especially important in the mobile world.<br />
<br />
In the short to medium term, we seek to:<br />
<br />
* Set a base number of features<br />
* Identify developer needs<br />
* Work iteratively in bringing features and possibilities to developers to help them choose Open Web technologies</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Meetings/2013-09-10&diff=705213Engagement/Developer Engagement/Meetings/2013-09-102013-09-09T19:52:46Z<p>Robnyman: /* Actions */</p>
<hr />
<div>* Tuesday, September 10, 2013 @ 9:00am Pacific Time (16:00 UTC through November 6)<br />
<br />
= Agenda =<br />
Add your agenda items here before hand. Add links to more information or background whenever possible.<br />
<br />
* Intros<br />
* News<br />
* Upcoming developer events <br />
<br />
= Actions =<br />
* ACTION: sole to write a post on web audio and the audiomonkey patch polyfill [DONE]<br />
* ACTION: Ali Spivak to work with teams to figure out metrics around awareness and linking. <br />
* ACTION: Maire Reavy to schedule a follow up with the people interested in helping with WebRTC. Email her if interested.<br />
* ACTION: Stormy to write up Developer Program description DONE (Need to move to wiki.)<br />
* ACTION: Daniel Buchner to send out forum requirements and include Mark Coggins in StackOverflow conversations<br />
* ACTION: Bill Maggs to create developer program roadmap<br />
<br />
= Notes =<br />
<br />
= IRC Log =</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=695547Engagement/Developer Engagement/Hacks blog/Writing2013-08-16T12:59:53Z<p>Robnyman: /* Using code samples in your post */</p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com). Once the initial draft has been received, it will be added to the Mozilla Hacks blog and iterated on there, with revision and reviewer support.<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Mozilla Hacks author account==<br />
<br />
The Editor of Mozilla Hacks will set you up with an account. Make sure to have a bio ready and that your e-mail address is connected to a [https://en.gravatar.com/ Gravatar]. Additionally, please inform the Editor about potential website URLs, Twitter, Facebook and Google+ accounts you want to show with your profile.<br />
<br />
==Embedding media and https==<br />
<br />
The width of the content on Mozilla Hacks is 500 pixels. Make sure that images, embedded videos etc are adapted to that. If you want to add images to your post, please [https://hacks.mozilla.org/wp-admin/media-new.php upload them to Mozilla Hacks] and then reference their URL with an &lt;img&gt; element.<br />
<br />
<b>Note:</b> Mozilla Hacks is being served as https so if you embed anything, it has to support https as well, due to [https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ Mixed Content Blocking]. For instance, at the time of writing (April 26th 2013), YouTube and GitHub embeds supports https, Vimeo and jsFiddle doesn't.<br />
<br />
==Using code samples in your post==<br />
<br />
When you write code samples in your post, make sure to wrap code blocks spanning over multiple lines with <tt>&lt;pre&gt;</tt> elements. As described above, we use the GeSHI support to generate color highlighting for your code.<br />
To enable that, just use the <tt>lang</tt> attribute on the <tt>&lt;pre&gt;</tt> element, like this:<br />
<br />
<pre>&lt;pre lang="javascript"&gt;<br />
var URL = "https://hacks.mozilla.org/";<br />
&lt;/pre&gt;</pre><br />
<br />
For code formatting within text/paragraphs, wrap them with <tt>&lt;code&gt;</tt> elements:<br />
<br />
<pre>This is some text about the <code>canvas</code> element</pre><br />
<br />
<br />
Note:<br />
<br />
* Do <b>not</b> use &lt;code&gt; elements in code blocks wrapped with the <tt>&lt;pre&gt;</tt> element<br />
* Do <b>not</b> escape HTML entities like <, > and & with &amp;lt;, &amp;gt; and &amp;amp; in those code blocks<br />
<br />
Another option is also embedding gists or similar. Note: it has to support https (see above).<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Mozilla_Developer_Program&diff=668708Engagement/Developer Engagement/Mozilla Developer Program2013-06-19T22:00:07Z<p>Robnyman: Created page with "=Mozilla Developer Program (MDP)="</p>
<hr />
<div>=Mozilla Developer Program (MDP)=</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog&diff=649765Engagement/Developer Engagement/Hacks blog2013-04-26T10:23:45Z<p>Robnyman: /* Metrics */</p>
<hr />
<div>==What Mozilla Hacks is - our vision==<br />
<br />
Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be one of the key resources for people developing for the Open Web, talking about both news and in-depth descriptions of technologies and features. We will cover both development tips and tricks in general, but also look at features in Mozilla's products from a technical perspective - to show our approach and line of thinking, and hopefully inspire other companies to implement what we have.<br />
<br />
Mozilla Hacks is, just like [https://developer.mozilla.org/ MDN (Mozilla Developer Network)], a web browser agnostic resource, focused on the Open Web and sharing knowledge with all web developers out there.<br />
<br />
Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We aim to have original content. If we find an interesting blog post, we might highlight it, but always with our own take.<br />
<br />
Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more.<br />
<br />
==Goals==<br />
<br />
Mozilla Hacks aims to be one of the key web sites people will turn to for unbiased and expert knowledge about developing. Our intent is to have at least three descriptive articles per week, explaining a feature or technology. <br />
<br />
We also aim to grow the audience by a 100% within the next year (September 2012 > September 2013).<br />
<br />
==Writers/contributors==<br />
<br />
Members of the Developer Engagement Team are writing for Mozilla Hacks, but any other Mozillian is also welcome to contribute! If you know something interesting that would be great to share with the readers of Mozilla Hacks, please let us know! We can be reached at mozhacks [at] mozilla [dot] com. When it comes to personal branding, we hope that the exposure you will get - both as an author and in the Mozilla context - will be good motivation for deciding to write for Mozilla Hacks!<br />
And if you have the technical expertise, but aren't sure about the writing, we'd be more than happy to help put together an article together with you.<br />
<br />
We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed.<br />
<br />
We would also like to feature guest posts from prominent people within the web business. There are so many talented people out there, and we would love to highlight and share your knowledge!<br />
<br />
==Author responsibility==<br />
<br />
We can't stress enough that Mozilla Hacks is not a billboard or announcement channel. It is there for us to have a dialog with developers out there, to hear their opinions, give them clarifications and for them to voice their takes on what we say. A blog post author is responsible for moderating and replying to comments. Not every comment needs a reply, but questions and similar should be addressed. People take the time to read and to comment, and they deserve the respect to have that communication. Also be aware that comments can be quoted in press, direct questions from jouranlists and similar, so please reach out to Mozilla press if you want/need to verify your statement.<br />
<br />
It is also a long term base for a good relations with developers based on mutual respect and communication.<br />
<br />
==Behavior guidelines==<br />
<br />
Mozilla Hacks is a place based on mutual respect and understanding, and the way we address each other is supposed to reflect that. We expect anyone writing or commenting to use proper laguage and refrain from insulting other people. We reserve the right to remove anything that doesn't qualify as decent behavior towards other people.<br />
<br />
==Publishing posts==<br />
<br />
Blog posts should be added to the Mozilla Hacks blog calendar in good time before - it now resides internally in Zimbra. E-mail mozhacks [at] mozilla [dot] com for access, to have an overview of what is being planned.<br />
Everything that is to be published needs to be approved before, by Robert Nyman, Christian Heilmann or Stormy Peters - or Developer Engagement otherwise if they aren't reachable (see contact information above). We would like at least a few days notice before posting, to read through it and ensure it is both on topic and phrased in a way suitable for Mozilla Hacks.<br />
<br />
We generally refrain from posts on Fridays, US time, since then the rest of the world have moved into weekend, meaning that we won't be available to reply to comments or handle any other feedback<br />
<br />
==Writing for Mozilla Hacks==<br />
<br />
When it comes to more detailed questions on how to format content for a blog post, which plugins are supported and more, read more in the [https://wiki.mozilla.org/Engagement/Developer_Engagement/Hacks_blog/Writing Writing for Mozilla Hacks] guidelines.<br />
<br />
==Metrics==<br />
<br />
We are currently using Google Analytics, and biweekly metrics reports are sent internally.<br />
<br />
==General focus/topics==<br />
<br />
These are general topics and areas we will cover<br />
<br />
* Open Web<br />
* HTML5<br />
* Firefox OS<br />
* Web APIs<br />
* Mozilla Products (engineer perspective) - Bleeding Edge Firefox etc<br />
* Recurring posts:<br />
** Hacks Weekly<br />
** Bi-weekly State of games<br />
** Monthly - most interesting posts on Mozilla Hacks<br />
** Monthly: Dev Derby winners<br />
** Monthly: Interview with most recent Derby winner (unless the winner doesn't want to)<br />
** Web Developer Toolbox: introductions to tools and libraries<br />
** Wiki Wednesday<br />
** State of the Docs<br />
* Use cases<br />
** Evaluations and guides to HTML5 Apps & games<br />
* News in the web development world - short links, attention bits and more<br />
* News related to MDN: doc sprints, etc.<br />
<br />
==Organization and Contact==<br />
<br />
Editor: Robert Nyman (robert@)<br />
<br />
Team:<br />
* Christian Heilmann (cheilmann@)<br />
* Janet Swisher (jswisher@)<br />
* Eric "Sheppy" Shepherd (eshepherd@)<br />
<br />
All e-mail addresses can be reached at @mozilla.com. Please contact any of the people above or mozhacks [at] mozilla [dot] com if you have any questions.</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog&diff=649764Engagement/Developer Engagement/Hacks blog2013-04-26T10:23:04Z<p>Robnyman: /* Organization and Contact */</p>
<hr />
<div>==What Mozilla Hacks is - our vision==<br />
<br />
Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be one of the key resources for people developing for the Open Web, talking about both news and in-depth descriptions of technologies and features. We will cover both development tips and tricks in general, but also look at features in Mozilla's products from a technical perspective - to show our approach and line of thinking, and hopefully inspire other companies to implement what we have.<br />
<br />
Mozilla Hacks is, just like [https://developer.mozilla.org/ MDN (Mozilla Developer Network)], a web browser agnostic resource, focused on the Open Web and sharing knowledge with all web developers out there.<br />
<br />
Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We aim to have original content. If we find an interesting blog post, we might highlight it, but always with our own take.<br />
<br />
Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more.<br />
<br />
==Goals==<br />
<br />
Mozilla Hacks aims to be one of the key web sites people will turn to for unbiased and expert knowledge about developing. Our intent is to have at least three descriptive articles per week, explaining a feature or technology. <br />
<br />
We also aim to grow the audience by a 100% within the next year (September 2012 > September 2013).<br />
<br />
==Writers/contributors==<br />
<br />
Members of the Developer Engagement Team are writing for Mozilla Hacks, but any other Mozillian is also welcome to contribute! If you know something interesting that would be great to share with the readers of Mozilla Hacks, please let us know! We can be reached at mozhacks [at] mozilla [dot] com. When it comes to personal branding, we hope that the exposure you will get - both as an author and in the Mozilla context - will be good motivation for deciding to write for Mozilla Hacks!<br />
And if you have the technical expertise, but aren't sure about the writing, we'd be more than happy to help put together an article together with you.<br />
<br />
We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed.<br />
<br />
We would also like to feature guest posts from prominent people within the web business. There are so many talented people out there, and we would love to highlight and share your knowledge!<br />
<br />
==Author responsibility==<br />
<br />
We can't stress enough that Mozilla Hacks is not a billboard or announcement channel. It is there for us to have a dialog with developers out there, to hear their opinions, give them clarifications and for them to voice their takes on what we say. A blog post author is responsible for moderating and replying to comments. Not every comment needs a reply, but questions and similar should be addressed. People take the time to read and to comment, and they deserve the respect to have that communication. Also be aware that comments can be quoted in press, direct questions from jouranlists and similar, so please reach out to Mozilla press if you want/need to verify your statement.<br />
<br />
It is also a long term base for a good relations with developers based on mutual respect and communication.<br />
<br />
==Behavior guidelines==<br />
<br />
Mozilla Hacks is a place based on mutual respect and understanding, and the way we address each other is supposed to reflect that. We expect anyone writing or commenting to use proper laguage and refrain from insulting other people. We reserve the right to remove anything that doesn't qualify as decent behavior towards other people.<br />
<br />
==Publishing posts==<br />
<br />
Blog posts should be added to the Mozilla Hacks blog calendar in good time before - it now resides internally in Zimbra. E-mail mozhacks [at] mozilla [dot] com for access, to have an overview of what is being planned.<br />
Everything that is to be published needs to be approved before, by Robert Nyman, Christian Heilmann or Stormy Peters - or Developer Engagement otherwise if they aren't reachable (see contact information above). We would like at least a few days notice before posting, to read through it and ensure it is both on topic and phrased in a way suitable for Mozilla Hacks.<br />
<br />
We generally refrain from posts on Fridays, US time, since then the rest of the world have moved into weekend, meaning that we won't be available to reply to comments or handle any other feedback<br />
<br />
==Writing for Mozilla Hacks==<br />
<br />
When it comes to more detailed questions on how to format content for a blog post, which plugins are supported and more, read more in the [https://wiki.mozilla.org/Engagement/Developer_Engagement/Hacks_blog/Writing Writing for Mozilla Hacks] guidelines.<br />
<br />
==Metrics==<br />
<br />
We are currently using WebTrends for statistics, and are evaluating using Google Analytics. The idea is to be able to share how we are moving along, and also internally report on a weekly basis on popularity and interest.<br />
<br />
==General focus/topics==<br />
<br />
These are general topics and areas we will cover<br />
<br />
* Open Web<br />
* HTML5<br />
* Firefox OS<br />
* Web APIs<br />
* Mozilla Products (engineer perspective) - Bleeding Edge Firefox etc<br />
* Recurring posts:<br />
** Hacks Weekly<br />
** Bi-weekly State of games<br />
** Monthly - most interesting posts on Mozilla Hacks<br />
** Monthly: Dev Derby winners<br />
** Monthly: Interview with most recent Derby winner (unless the winner doesn't want to)<br />
** Web Developer Toolbox: introductions to tools and libraries<br />
** Wiki Wednesday<br />
** State of the Docs<br />
* Use cases<br />
** Evaluations and guides to HTML5 Apps & games<br />
* News in the web development world - short links, attention bits and more<br />
* News related to MDN: doc sprints, etc.<br />
<br />
==Organization and Contact==<br />
<br />
Editor: Robert Nyman (robert@)<br />
<br />
Team:<br />
* Christian Heilmann (cheilmann@)<br />
* Janet Swisher (jswisher@)<br />
* Eric "Sheppy" Shepherd (eshepherd@)<br />
<br />
All e-mail addresses can be reached at @mozilla.com. Please contact any of the people above or mozhacks [at] mozilla [dot] com if you have any questions.</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=649763Engagement/Developer Engagement/Hacks blog/Writing2013-04-26T10:20:42Z<p>Robnyman: </p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com). Once the initial draft has been received, it will be added to the Mozilla Hacks blog and iterated on there, with revision and reviewer support.<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Mozilla Hacks author account==<br />
<br />
The Editor of Mozilla Hacks will set you up with an account. Make sure to have a bio ready and that your e-mail address is connected to a [https://en.gravatar.com/ Gravatar]. Additionally, please inform the Editor about potential website URLs, Twitter, Facebook and Google+ accounts you want to show with your profile.<br />
<br />
==Embedding media and https==<br />
<br />
The width of the content on Mozilla Hacks is 500 pixels. Make sure that images, embedded videos etc are adapted to that. If you want to add images to your post, please [https://hacks.mozilla.org/wp-admin/media-new.php upload them to Mozilla Hacks] and then reference their URL with an &lt;img&gt; element.<br />
<br />
<b>Note:</b> Mozilla Hacks is being served as https so if you embed anything, it has to support https as well, due to [https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ Mixed Content Blocking]. For instance, at the time of writing (April 26th 2013), YouTube and GitHub embeds supports https, Vimeo and jsFiddle doesn't.<br />
<br />
==Using code samples in your post==<br />
<br />
When you write code samples in your post, make sure to wrap them with <tt>&lt;pre&gt;</tt> elements. As described above, we use the GeSHI support to generate color highlighting for your code.<br />
To enable that, just use the <tt>lang</tt> attribute on the <tt>&lt;pre&gt;</tt> element, like this:<br />
<br />
<pre><code>&lt;pre lang="javascript"&gt;<br />
var URL = "https://hacks.mozilla.org/";<br />
&lt;/pre&gt;</code></pre><br />
<br />
Note:<br />
<br />
* Do <b>not</b> use &lt;code&gt; elements<br />
* Do <b>not</b> escape HTML entities like <, > and & with &amp;lt;, &amp;gt; and &amp;amp;<br />
<br />
Another option is also embedding gists or similar. Note: it has to support https (see above).<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=649761Engagement/Developer Engagement/Hacks blog/Writing2013-04-26T10:16:23Z<p>Robnyman: </p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com). Once the initial draft has been received, it will be added to the Mozilal Hacks blog and iterated on there, with revision and reviewer support.<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Embedding media and https==<br />
<br />
The width of the content on Mozilla Hacks is 500 pixels. Make sure that images, embedded videos etc are adapted to that. If you want to add images to your post, please [https://hacks.mozilla.org/wp-admin/media-new.php upload them to Mozilla Hacks] and then reference their URL with an &lt;img&gt; element.<br />
<br />
<b>Note:</b> Mozilla Hacks is being served as https so if you embed anything, it has to support https as well, due to [https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ Mixed Content Blocking]. For instance, at the time of writing (April 26th 2013), YouTube and GitHub embeds supports https, Vimeo and jsFiddle doesn't.<br />
<br />
==Using code samples in your post==<br />
<br />
When you write code samples in your post, make sure to wrap them with <tt>&lt;pre&gt;</tt> elements. As described above, we use the GeSHI support to generate color highlighting for your code.<br />
To enable that, just use the <tt>lang</tt> attribute on the <tt>&lt;pre&gt;</tt> element, like this:<br />
<br />
<pre><code>&lt;pre lang="javascript"&gt;<br />
var URL = "https://hacks.mozilla.org/";<br />
&lt;/pre&gt;</code></pre><br />
<br />
Note:<br />
<br />
* Do <b>not</b> use &lt;code&gt; elements<br />
* Do <b>not</b> escape HTML entities like <, > and & with &amp;lt;, &amp;gt; and &amp;amp;<br />
<br />
Another option is also embedding gists or similar. Note: it has to support https (see above).<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=649760Engagement/Developer Engagement/Hacks blog/Writing2013-04-26T10:15:26Z<p>Robnyman: </p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com).<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Embedding media and https==<br />
<br />
The width of the content on Mozilla Hacks is 500 pixels. Make sure that images, embedded videos etc are adapted to that. If you want to add images to your post, please [https://hacks.mozilla.org/wp-admin/media-new.php upload them to Mozilla Hacks] and then reference their URL with an &lt;img&gt; element.<br />
<br />
<b>Note:</b> Mozilla Hacks is being served as https so if you embed anything, it has to support https as well, due to [https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ Mixed Content Blocking]. For instance, at the time of writing (April 26th 2013), YouTube and GitHub embeds supports https, Vimeo and jsFiddle doesn't.<br />
<br />
==Using code samples in your post==<br />
<br />
When you write code samples in your post, make sure to wrap them with <tt>&lt;pre&gt;</tt> elements. As described above, we use the GeSHI support to generate color highlighting for your code.<br />
To enable that, just use the <tt>lang</tt> attribute on the <tt>&lt;pre&gt;</tt> element, like this:<br />
<br />
<pre><code>&lt;pre lang="javascript"&gt;<br />
var URL = "https://hacks.mozilla.org/";<br />
&lt;/pre&gt;</code></pre><br />
<br />
Note:<br />
<br />
* Do <b>not</b> use &lt;code&gt; elements<br />
* Do <b>not</b> escape HTML entities like <, > and & with &amp;lt;, &amp;gt; and &amp;amp;<br />
<br />
Another option is also embedding gists or similar. Note: it has to support https (see above).<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=649758Engagement/Developer Engagement/Hacks blog/Writing2013-04-26T10:15:12Z<p>Robnyman: </p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com).<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Content width==<br />
<br />
<br />
<br />
==Embedding media and https==<br />
<br />
The width of the content on Mozilla Hacks is 500 pixels. Make sure that images, embedded videos etc are adapted to that. If you want to add images to your post, please [https://hacks.mozilla.org/wp-admin/media-new.php upload them to Mozilla Hacks] and then reference their URL with an &lt;img&gt; element.<br />
<br />
<b>Note:</b> Mozilla Hacks is being served as https so if you embed anything, it has to support https as well, due to [https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ Mixed Content Blocking]. For instance, at the time of writing (April 26th 2013), YouTube and GitHub embeds supports https, Vimeo and jsFiddle doesn't.<br />
<br />
==Using code samples in your post==<br />
<br />
When you write code samples in your post, make sure to wrap them with <tt>&lt;pre&gt;</tt> elements. As described above, we use the GeSHI support to generate color highlighting for your code.<br />
To enable that, just use the <tt>lang</tt> attribute on the <tt>&lt;pre&gt;</tt> element, like this:<br />
<br />
<pre><code>&lt;pre lang="javascript"&gt;<br />
var URL = "https://hacks.mozilla.org/";<br />
&lt;/pre&gt;</code></pre><br />
<br />
Note:<br />
<br />
* Do <b>not</b> use &lt;code&gt; elements<br />
* Do <b>not</b> escape HTML entities like <, > and & with &amp;lt;, &amp;gt; and &amp;amp;<br />
<br />
Another option is also embedding gists or similar. Note: it has to support https (see above).<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=649747Engagement/Developer Engagement/Hacks blog/Writing2013-04-26T10:05:38Z<p>Robnyman: /* Using code samples in your post */</p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com).<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers<br />
<br />
==Using code samples in your post==<br />
<br />
When you write code samples in your post, make sure to wrap them with <tt>&lt;pre&gt;</tt> elements. As described above, we use the GeSHI support to generate color highlighting for your code.<br />
To enable that, just use the <tt>lang</tt> attribute on the <tt>&lt;pre&gt;</tt> element, like this:<br />
<br />
<pre><code>&lt;pre lang="javascript"&gt;<br />
var URL = "https://hacks.mozilla.org/";<br />
&lt;/pre&gt;</code></pre><br />
<br />
Note:<br />
<br />
* Do <b>not</b> use &lt;code&gt; elements<br />
* Do <b>not</b> escape HTML entities like <, > and & with &amp;lt;, &amp;gt; and &amp;amp;</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=649745Engagement/Developer Engagement/Hacks blog/Writing2013-04-26T09:53:46Z<p>Robnyman: /* Installed Plug-ins */</p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com).<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with [http://qbnz.com/highlighter/ GeSHi]: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers<br />
<br />
==Using privileged elements==<br />
By default in WordPress, only users with Administrator privileges can post &lt;audio&gt;, &lt;video&gt;, or &lt;iframe&gt; elements. If non-admin users try to publish posts containing these elements, the elements are stripped out. On Hacks, we now use the [http://wordpress.org/extend/plugins/simple-embed-code/other_notes/ Artiss Code Embed] plug-in to enable non-admin users to publish privileged elements. <br />
<br />
To use this plug-in:<br />
<br />
# While in the '''Edit Post''' view, click '''Screen Options''', under the WordPress toolbar. The screen options panel expands. <br />
# Select the '''Custom Fields''' checkbox. You only need to do this once. After you have used custom fields, they will be displayed for you by default.<br />
# In the '''Custom Fields''' section of the page, under "Add New Custom Field", click '''Enter new'''.<br />
# Under '''Name''', type "CODE" and any identifier of your choice, so that "CODE" is the prefix of your identifier. For example "CODEfoobar".<br />
# Under '''Value''', type the code for privileged element, including any attributes, exactly as you would type it in an HTML page.<br />
# Click '''Add Custom Field'''.<br />
# In the body of your post, wherever you want the privileged element to appear, type the identifier you defined as a custom field, surrounded by "%" characters. For example "%CODEfoobar%". <br />
# Preview or publish the post as you normally would. The value of the custom field is substituted into your post.<br />
<br />
You can reuse a custom field that was defined on another post. Use the '''Code Embed > Search''' item in the side navigation to find existing fields for Code Embed.</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Hacks_blog/Writing&diff=492269Engagement/Developer Engagement/Hacks blog/Writing2012-12-05T20:54:04Z<p>Robnyman: /* Write in HTML! */</p>
<hr />
<div>=Writing for Mozilla Hacks=<br />
This page contains useful information for people posting on the [http://hacks.mozilla.org Hacks blog].<br />
<br />
==Writing in plain text, Markdown or HTML==<br />
<br />
If you are writing a draft in whatever environment you prefer: write it in plain text, Markdown or HTML and send to the Editor of Mozilla Hacks (mozhacks [at] mozilla [dot] com).<br />
<br />
If you write directly in Mozilla Hacks' Wordpress instance: The WYSIWYG editor in WordPress produces very bad HTML, which reflects poorly on our expertise if people view the source of posts. So, please don't use it. There's even a profile setting, "Disable the visual editor when writing". If this wasn't set by whoever created your account, please go in and change your own profile, so you don't accidentally use the visual editor.<br />
<br />
==Sharing code==<br />
When you write a blog post that contains code, please consider adding that code to the [https://github.com/mozilla/mozhacks/ Mozilla Hacks repository on GitHub]. That way, people can read, fork and easily work on that code themselves!<br />
<br />
==Installed Plug-ins==<br />
The following plug-ins are installed on Hacks:<br />
* [http://akismet.com/ Akismet]: spam filter<br />
* [http://www.artiss.co.uk/code-embed Artiss Code Embed]: allows embedding privileged code in posts<br />
* [http://wordpress.org/extend/plugins/co-authors-plus/ Co-Authors Plus]: allows multiple authors to be assigned to a post<br />
* FC Pagination: Show numbered pagination instead of "Next page" and "Previous Page" (by Craig Cook)<br />
* [http://flagrantdisregard.com/footnotes-plugin FD Footnotes]: supports footnotes<br />
* [http://www.prelovac.com/vladimir/wordpress-plugins/seo-smart-links SEO Smart Links]: helps SEO through auto-generation of links<br />
* [http://txfx.net/code/wordpress/subscribe-to-comments/ Subscribe to comments]: lets users subscribe to comments<br />
* [http://www.piepalace.ca/blog/projects/time-release Time Release]: queues posts to publish after inactivity<br />
* [http://crowdfavorite.com/wordpress/plugins/twitter-tools/ Twitter Tools]: supports auto-tweeting articles<br />
* [https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA]: integrates reCAPTCHA with WordPress<br />
* [http://wordpress.org/extend/plugins/wp-syntax/ WP-Syntax]: Syntax highlighting with GeSHi: use &lt;pre lang="LANGUAGE_NAME" line="1"&gt; to highlight for LANGUAGE_NAME, with line numbers<br />
<br />
==Using privileged elements==<br />
By default in WordPress, only users with Administrator privileges can post &lt;audio&gt;, &lt;video&gt;, or &lt;iframe&gt; elements. If non-admin users try to publish posts containing these elements, the elements are stripped out. On Hacks, we now use the [http://wordpress.org/extend/plugins/simple-embed-code/other_notes/ Artiss Code Embed] plug-in to enable non-admin users to publish privileged elements. <br />
<br />
To use this plug-in:<br />
<br />
# While in the '''Edit Post''' view, click '''Screen Options''', under the WordPress toolbar. The screen options panel expands. <br />
# Select the '''Custom Fields''' checkbox. You only need to do this once. After you have used custom fields, they will be displayed for you by default.<br />
# In the '''Custom Fields''' section of the page, under "Add New Custom Field", click '''Enter new'''.<br />
# Under '''Name''', type "CODE" and any identifier of your choice, so that "CODE" is the prefix of your identifier. For example "CODEfoobar".<br />
# Under '''Value''', type the code for privileged element, including any attributes, exactly as you would type it in an HTML page.<br />
# Click '''Add Custom Field'''.<br />
# In the body of your post, wherever you want the privileged element to appear, type the identifier you defined as a custom field, surrounded by "%" characters. For example "%CODEfoobar%". <br />
# Preview or publish the post as you normally would. The value of the custom field is substituted into your post.<br />
<br />
You can reuse a custom field that was defined on another post. Use the '''Code Embed > Search''' item in the side navigation to find existing fields for Code Embed.</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/FirefoxOS-porting-training&diff=489425Engagement/Developer Engagement/FirefoxOS-porting-training2012-11-21T23:01:59Z<p>Robnyman: /* 11:15 - 12:15 Presentation: Web APIS */</p>
<hr />
<div>= Porting apps to Firefox OS training outline =<br />
<br />
This is a training outline for the invite-only events around porting HTML5 apps for Firefox OS to be held in Mountain View on 4-5 January, 2013 and London on 18-19 January.<br />
<br />
== Before the Event: Prerequisites ==<br />
<br />
Briefing e-mail to attendees with:<br />
* Goals<br />
* Agenda<br />
* What to bring<br />
* How to set up development environment<br />
* Pointers to other resources<br />
<br />
== Day 1: Setting the stage and sharing knowledge ==<br />
<br />
=== 09:00 Breakfast and networking ===<br />
<br />
=== 09:30 Introduction ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing the agenda of the event<br />
* Explanation of facilities - getting people connected, ensuring power<br />
* Who are you, optionally what app are you building<br />
<br />
=== 10:15 - 11:15 Presentation: Firefox OS ===<br />
<br />
==== Speaker: B2G Engineer (Philikon, Andreas, Jonas, Detrich (for referrals)) ====<br />
<br />
* Quick introduction to the architecture of the Firefox OS, why we do it and where to find information and help. <br />
* Introduction of the communication channels in case you need information after the event<br />
* How to get your hands on Firefox OS<br />
** Building it yourself <br />
** Emulation / r2d2b2g<br />
** Introduction of test devices and how to test on Firefox OS (keys, handling)<br />
** How to get apps onto device<br />
<br />
=== 11:15 - 12:15 Presentation: Web APIs ===<br />
<br />
==== Speaker: Technology Evangelist (Robert Nyman) ====<br />
<br />
* Overview of all the Web APIs supported in Firefox OS<br />
* MozApps API overview<br />
* Demo code, examples of how to get them to work<br />
* Where and how to file bugs<br />
<br />
=== 12:15 - 13:00 Lunch (either provided or getting people out to hunt squirrels) ===<br />
<br />
=== 13:00 - 13:45 Presentation: What makes a good Firefox OS app ===<br />
<br />
==== Speaker: Technical Evangelist or Gaia Engineer (Michal B., Built-in app engineer, Josh Carpenter, Vivien, Dale Harvey) ====<br />
<br />
* Explanation of the must haves of a good Firefox OS app:<br />
** Device specific handling (touch vs. mouse)<br />
** Offline capability, atomic updates and quick first load experience<br />
** Full screen <br />
** Good UI patterns (lists, panels, visual feedback, fingers not covering important parts)<br />
** Performance Tips & Tricks<br />
** Guided tour of built-in app<br />
** Detailed information on the manifest format<br />
<br />
=== 13:45 - 14:45 Presentation: Infrastructure ===<br />
<br />
==== Speaker: Marketplace Engineer or Product Lead (Potch, Justin Scott, Wil Clauser) ====<br />
<br />
* Explanation of the Firefox marketplace and how to submit apps<br />
* Detailed explanation and demo of how an app submission works<br />
* Introduction to payment systems <br />
* Updating your apps in the future<br />
* Introduction to the idea of findable apps on the web<br />
<br />
=== 14:45 - 15:45 Presentation: Pitfalls and helpers ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing gotchas of HTML5 app development (broken AppCache issues)<br />
* Introducing helper libraries and tools to use (Lawnchair for local storage, Gecko-friendly libraries (Modernizr))<br />
* Other helpers: AppCache generator, etc.<br />
<br />
=== 15:45 - 16:00 break ===<br />
<br />
=== 16:00 - 17:00 Problem Round Table ===<br />
<br />
==== Speakers: experts from earlier in the day ====<br />
<br />
* Talk about what problems you've experienced or anticipate and discuss workarounds <br />
<br />
=== 17:00- 18:30 Workshop: Installing development environments and getting to know Firefox OS ===<br />
<br />
==== Speakers: Technology Evangelists ====<br />
<br />
* Helping all the people who came to install their dev environment, distribute phones and show how to test on them<br />
<br />
=== 18:30 - 19:00 Group organisation - partnering Mozilla people with teams and planning the next day activities in groups ===<br />
<br />
=== 19:00 Dinner and merriments ===<br />
<br />
== Day 2: Pencils down, roll up sleeves ==<br />
<br />
=== 09:00 Breakfast and networking ===<br />
<br />
=== 10:00 Introduction === <br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing the agenda of today<br />
* Explanation of facilities - who is where, how to get what<br />
<br />
=== 10:30 - 13:00 Group work ===<br />
<br />
=== 13:00 Lunch ===<br />
<br />
=== 14:00 - 16:00 Group work === <br />
<br />
=== 16:00 - 17:00 Results and findings presentations ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Quick presentations by each team about what they achieved and where they got stuck<br />
* Presentation of ways to work around issues encountered<br />
* Target date for submission; prize for meeting target<br />
<br />
=== 17:00 - 17:30 Keep in contact presentation ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Explanation of the ongoing ways to contact the team and get help<br />
* Explanation on how to contribute to B2G and Web APIs<br />
* Introduction of other schemes planned for developers<br />
* Go-to resources for issue resolution<br />
<br />
=== 17:30 Off to the pub/food ===</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/FirefoxOS-porting-training&diff=489424Engagement/Developer Engagement/FirefoxOS-porting-training2012-11-21T23:01:31Z<p>Robnyman: /* Before the Event: Prerequisites */</p>
<hr />
<div>= Porting apps to Firefox OS training outline =<br />
<br />
This is a training outline for the invite-only events around porting HTML5 apps for Firefox OS to be held in Mountain View on 4-5 January, 2013 and London on 18-19 January.<br />
<br />
== Before the Event: Prerequisites ==<br />
<br />
Briefing e-mail to attendees with:<br />
* Goals<br />
* Agenda<br />
* What to bring<br />
* How to set up development environment<br />
* Pointers to other resources<br />
<br />
== Day 1: Setting the stage and sharing knowledge ==<br />
<br />
=== 09:00 Breakfast and networking ===<br />
<br />
=== 09:30 Introduction ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing the agenda of the event<br />
* Explanation of facilities - getting people connected, ensuring power<br />
* Who are you, optionally what app are you building<br />
<br />
=== 10:15 - 11:15 Presentation: Firefox OS ===<br />
<br />
==== Speaker: B2G Engineer (Philikon, Andreas, Jonas, Detrich (for referrals)) ====<br />
<br />
* Quick introduction to the architecture of the Firefox OS, why we do it and where to find information and help. <br />
* Introduction of the communication channels in case you need information after the event<br />
* How to get your hands on Firefox OS<br />
** Building it yourself <br />
** Emulation / r2d2b2g<br />
** Introduction of test devices and how to test on Firefox OS (keys, handling)<br />
** How to get apps onto device<br />
<br />
=== 11:15 - 12:15 Presentation: Web APIS ===<br />
<br />
==== Speaker: Technology Evangelist (Robert Nyman) ====<br />
<br />
* Overview of all the Web APIs supported in Firefox OS<br />
* MozApps API overview<br />
* Demo code, examples of how to get them to work<br />
* Where and how to file bugs<br />
<br />
=== 12:15 - 13:00 Lunch (either provided or getting people out to hunt squirrels) ===<br />
<br />
=== 13:00 - 13:45 Presentation: What makes a good Firefox OS app ===<br />
<br />
==== Speaker: Technical Evangelist or Gaia Engineer (Michal B., Built-in app engineer, Josh Carpenter, Vivien, Dale Harvey) ====<br />
<br />
* Explanation of the must haves of a good Firefox OS app:<br />
** Device specific handling (touch vs. mouse)<br />
** Offline capability, atomic updates and quick first load experience<br />
** Full screen <br />
** Good UI patterns (lists, panels, visual feedback, fingers not covering important parts)<br />
** Performance Tips & Tricks<br />
** Guided tour of built-in app<br />
** Detailed information on the manifest format<br />
<br />
=== 13:45 - 14:45 Presentation: Infrastructure ===<br />
<br />
==== Speaker: Marketplace Engineer or Product Lead (Potch, Justin Scott, Wil Clauser) ====<br />
<br />
* Explanation of the Firefox marketplace and how to submit apps<br />
* Detailed explanation and demo of how an app submission works<br />
* Introduction to payment systems <br />
* Updating your apps in the future<br />
* Introduction to the idea of findable apps on the web<br />
<br />
=== 14:45 - 15:45 Presentation: Pitfalls and helpers ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing gotchas of HTML5 app development (broken AppCache issues)<br />
* Introducing helper libraries and tools to use (Lawnchair for local storage, Gecko-friendly libraries (Modernizr))<br />
* Other helpers: AppCache generator, etc.<br />
<br />
=== 15:45 - 16:00 break ===<br />
<br />
=== 16:00 - 17:00 Problem Round Table ===<br />
<br />
==== Speakers: experts from earlier in the day ====<br />
<br />
* Talk about what problems you've experienced or anticipate and discuss workarounds <br />
<br />
=== 17:00- 18:30 Workshop: Installing development environments and getting to know Firefox OS ===<br />
<br />
==== Speakers: Technology Evangelists ====<br />
<br />
* Helping all the people who came to install their dev environment, distribute phones and show how to test on them<br />
<br />
=== 18:30 - 19:00 Group organisation - partnering Mozilla people with teams and planning the next day activities in groups ===<br />
<br />
=== 19:00 Dinner and merriments ===<br />
<br />
== Day 2: Pencils down, roll up sleeves ==<br />
<br />
=== 09:00 Breakfast and networking ===<br />
<br />
=== 10:00 Introduction === <br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing the agenda of today<br />
* Explanation of facilities - who is where, how to get what<br />
<br />
=== 10:30 - 13:00 Group work ===<br />
<br />
=== 13:00 Lunch ===<br />
<br />
=== 14:00 - 16:00 Group work === <br />
<br />
=== 16:00 - 17:00 Results and findings presentations ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Quick presentations by each team about what they achieved and where they got stuck<br />
* Presentation of ways to work around issues encountered<br />
* Target date for submission; prize for meeting target<br />
<br />
=== 17:00 - 17:30 Keep in contact presentation ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Explanation of the ongoing ways to contact the team and get help<br />
* Explanation on how to contribute to B2G and Web APIs<br />
* Introduction of other schemes planned for developers<br />
* Go-to resources for issue resolution<br />
<br />
=== 17:30 Off to the pub/food ===</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/FirefoxOS-porting-training&diff=489405Engagement/Developer Engagement/FirefoxOS-porting-training2012-11-21T22:11:39Z<p>Robnyman: /* Speaker: Technology Evangelist */</p>
<hr />
<div>= Porting apps to Firefox OS training outline =<br />
<br />
This is a training outline for the invite-only events around porting HTML5 apps for Firefox OS to be held in Mountain View on 4-5 January, 2013 and London on 18-19 January.<br />
<br />
== Before the Event: Prerequisites ==<br />
<br />
Briefing e-mail to attendees with:<br />
* Goals<br />
* Agenda<br />
* What to bring<br />
* How to set up development environment<br />
* Pointers to other resrouces<br />
<br />
== Day 1: Setting the stage and sharing knowledge ==<br />
<br />
=== 09:00 Breakfast and networking ===<br />
<br />
=== 09:30 Introduction ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing the agenda of the event<br />
* Explanation of facilities - getting people connected, ensuring power<br />
* Who are you, optionally what app are you building<br />
<br />
=== 10:15 - 11:15 Presentation: Firefox OS ===<br />
<br />
==== Speaker: B2G Engineer (Philikon, Andreas, Jonas, Detrich (for referrals)) ====<br />
<br />
* Quick introduction to the architecture of the Firefox OS, why we do it and where to find information and help. <br />
* Introduction of the communication channels in case you need information after the event<br />
* How to get your hands on Firefox OS<br />
** Building it yourself <br />
** Emulation / r2d2b2g<br />
** Introduction of test devices and how to test on Firefox OS (keys, handling)<br />
** How to get apps onto device<br />
<br />
=== 11:15 - 12:15 Presentation: Web APIS ===<br />
<br />
==== Speaker: Technology Evangelist (Robert Nyman) ====<br />
<br />
* Overview of all the Web APIs supported in Firefox OS<br />
* MozApps API overview<br />
* Demo code, examples of how to get them to work<br />
* Where and how to file bugs<br />
<br />
=== 12:15 - 13:00 Lunch (either provided or getting people out to hunt squirrels) ===<br />
<br />
=== 13:00 - 13:45 Presentation: What makes a good Firefox OS app ===<br />
<br />
==== Speaker: Technical Evangelist or Gaia Engineer (Michal B., Built-in app engineer, Josh Carpenter, Vivien, Dale Harvey) ====<br />
<br />
* Explanation of the must haves of a good Firefox OS app:<br />
** Device specific handling (touch vs. mouse)<br />
** Offline capability, atomic updates and quick first load experience<br />
** Full screen <br />
** Good UI patterns (lists, panels, visual feedback, fingers not covering important parts)<br />
** Performance Tips & Tricks<br />
** Guided tour of built-in app<br />
** Detailed information on the manifest format<br />
<br />
=== 13:45 - 14:45 Presentation: Infrastructure ===<br />
<br />
==== Speaker: Marketplace Engineer or Product Lead (Potch, Justin Scott, Wil Clauser) ====<br />
<br />
* Explanation of the Firefox marketplace and how to submit apps<br />
* Detailed explanation and demo of how an app submission works<br />
* Introduction to payment systems <br />
* Updating your apps in the future<br />
* Introduction to the idea of findable apps on the web<br />
<br />
=== 14:45 - 15:45 Presentation: Pitfalls and helpers ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing gotchas of HTML5 app development (broken AppCache issues)<br />
* Introducing helper libraries and tools to use (Lawnchair for local storage, Gecko-friendly libraries (Modernizr))<br />
* Other helpers: AppCache generator, etc.<br />
<br />
=== 15:45 - 16:00 break ===<br />
<br />
=== 16:00 - 17:00 Problem Round Table ===<br />
<br />
==== Speakers: experts from earlier in the day ====<br />
<br />
* Talk about what problems you've experienced or anticipate and discuss workarounds <br />
<br />
=== 17:00- 18:30 Workshop: Installing development environments and getting to know Firefox OS ===<br />
<br />
==== Speakers: Technology Evangelists ====<br />
<br />
* Helping all the people who came to install their dev environment, distribute phones and show how to test on them<br />
<br />
=== 18:30 - 19:00 Group organisation - partnering Mozilla people with teams and planning the next day activities in groups ===<br />
<br />
=== 19:00 Dinner and merriments ===<br />
<br />
== Day 2: Pencils down, roll up sleeves ==<br />
<br />
=== 09:00 Breakfast and networking ===<br />
<br />
=== 10:00 Introduction === <br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Introducing the agenda of today<br />
* Explanation of facilities - who is where, how to get what<br />
<br />
=== 10:30 - 13:00 Group work ===<br />
<br />
=== 13:00 Lunch ===<br />
<br />
=== 14:00 - 16:00 Group work === <br />
<br />
=== 16:00 - 17:00 Results and findings presentations ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Quick presentations by each team about what they achieved and where they got stuck<br />
* Presentation of ways to work around issues encountered<br />
* Target date for submission; prize for meeting target<br />
<br />
=== 17:00 - 17:30 Keep in contact presentation ===<br />
<br />
==== Speaker: Technology Evangelist ====<br />
<br />
* Explanation of the ongoing ways to contact the team and get help<br />
* Explanation on how to contribute to B2G and Web APIs<br />
* Introduction of other schemes planned for developers<br />
* Go-to resources for issue resolution<br />
<br />
=== 17:30 Off to the pub/food ===</div>Robnymanhttps://wiki.mozilla.org/index.php?title=Talk:Engagement/Developer_Engagement/FirefoxOSAppsv2&diff=476457Talk:Engagement/Developer Engagement/FirefoxOSAppsv22012-10-04T11:05:00Z<p>Robnyman: </p>
<hr />
<div>Please provide feedback on the Firefox OS Apps & Marketplace Developer Engagement plan here by clicking the "Edit" link above. Be sure to save the page before you exit. Even though the history function shows editor names, we suggest you use this format:<br />
<br />
Name: Comment<br />
<br />
Thank you.<br />
<br />
--------------------------------<br />
<br />
Havi: here are the proposed uber-categories - <br />
*Content<br />
*Events <br />
*Tools<br />
*Support<br />
*Contests & Incentives<br />
<br />
<span style="color:red">Added "Feedback Collection" and then bucketed all the activities accordingly. (Some were a bit of a force fit, but I think that's okay.) Also provided a table at end of doc to describe the categories.</span><br />
<br />
---------------------------------<br />
Stormy: <br />
<br />
Great job pulling all the information/plans into one place and making sense of it!<br />
In particular, I really like the phases approach.<br />
<br />
Goals: <br />
* I like Ali's specific to the audience goal suggestions<br />
* I don't think the goals should be so specific to the Brazil launch; I think we should just say "initial launch" <span style="color:red">addressed</span><br />
* "vital ecosystem" -> "vital developer ecosystem" <span style="color:red">addressed</span><br />
* Do we want to populate the marketplace or get individual developers to populate the marketplace? <span style="color:red">addressed</span><br />
* The first goal "generate enthusiasm ..." is important but not measurable. (Some of Ali's suggestions might provide some measurement.) <span style="color:red">In the short term, recognized this as more of a vision statement and suggested the other bullets as the specific goals/metrics for the plan.</span><br />
<br />
Strategy:<br />
* I think we could tighten this up and include more of what we are doing. <span style="color:red">addressed</span><br />
* We should mention contents/incentives/big developer party <span style="color:red">addressed</span><br />
<br />
Participants & Stakeholders:<br />
* Just an FYI, I don't think all the evangelism reps are on engagement-developers. There's a separate list for evangelist reps. <span style="color:red">addressed</span><br />
* Why are their tools under Marketplace & Apps and tools under developer experience/developer tools? Do Ali/Kevin have a document some where that describes how they are working together/merging plans? <span style="color:red">clarified players; Ali has a line item regarding MDN/DevHub rationalization, and see her remark below</span><br />
* What about Lisa Brewster? <span style="color:red">addressed</span><br />
<br />
Raise Developer Awareness:<br />
* quality app says done, is that in a form we can disseminate as part of our outreach? <span style="color:red">This is baked into Lisa Brewster's guidelines, which will be published. Do we need more?</span><br />
<br />
Enable App Prototyping:<br />
* Sync developer tools, MDN and DevHub <span style="color:red">added tools</span><br />
* Brazil support community has "Continue" as the owner <span style="color:red">addressed</span><br />
* Feedback capture: we need a good way to give feedback (not on games but in general) <span style="color:red">suggested weekly report</span><br />
* Joe has been working on a sample app <span style="color:red">addressed</span><br />
* Close the time frames or change the title to be "start time frame" <span style="color:red">addressed</span><br />
<br />
--------------------------------<br />
<br />
Ali: here are some of my thoughts on goals & strategies...<br />
<br />
Goals - I'd like to see something less defined by what we (Mozilla) want and more developer-centric. <br />
<br />
Could we possibly add something along the lines of providing a certain percentage of new apps developers training or assistance with their apps. Or a goal around providing developers with an audience (I guess I'm getting at the thought that we are focused too much on looking at what we want, as opposed to what we are doing for developers to help them help the web).<br />
<br />
Ideas for goals for target demographics: <br />
*Number of existing (platform, marketplace, type) apps moved to FFOS/Marketplace<br />
*Provide (# or %) of general web developers with training on apps & related technologies<br />
*Get (x)% of developers who participate in an event, training, etc to submit an app<br />
*Number of existing mobile apps ported (could be by platform, type, etc)<br />
*Get a specific number or percentage of Mozilla community members submit an app (provide support / training for this)<br />
*Train a certain number of people in (x) market(s) how to make apps<br />
<br />
Christian and I were chatting about this, and he added some ideas as well. Specifically:<br />
*Chrome HTML5 apps developers could be a target demographic for porting over apps<br />
*It would be smart to do some fact finding in existing web app communities (i.e. Chrome) and get their feedback about what they are missing that we could provide, and develop goals around that...<br />
<br />
Similar thoughts with the strategy, I'd like to see more about how we can help people upskill to creating apps, or helping developers (recruiting isn't very helpful if they don't have or gain the skills to develop apps). Having the regional communities do training assumes they have the skills needed, which may not be the case (most of our community members in ReMo are Firefox contributors).<br />
<br />
<span style="color:red">In the short term, punted on goal rejigging. I was struggling with the concern that we would be adding a false precision, but let's discuss further face to face. I see the value and the desire to make the goals more developer-facing. Did add several action items around Chrome developer demographic.</span><br />
--------------------------------<br />
ali: <br />
re:<br />
Do Ali/Kevin have a document some where that describes how they are working together/merging plans? <br />
I'll be working on this next week and will post a link to it...<br />
--------------------------------<br />
Rob: Overall, I'm happy with the goals and strategies. I just have a few things I want to clarify and some bits to make everyone aware of that might prove useful.<br />
<br />
* Should another primary goal be to educate and evangelise the 'why' behind Open Web Apps?<br />
** This might be assumed in a larger goal but I want to make sure we focus on the reasons why this is happening as well as getting bums on seats in the Marketplace<br />
* It's worth pointing out that we have Mozilla-produced tools like Emscripten for converting native apps to JavaScript<br />
** Right now, this converts from C++ though there are other tools around that convert from C#<br />
** I'm not sure if anything exists to convert from Obj-C (iPhone) though<br />
* One strategy that we could explore is reaching out to tool developers so we can change things from the top-down<br />
** This is something that we're exploring with game engines and game-creation tools<br />
** I think it will be easier to get apps if developers don't need to change their process aside from adding a new target or re-exporting from their existing tool<br />
** I believe we'll have a battle on our hands if we try and convince all developers to take a manual approach to this, unless we do a very good job explaining the 'why' (they should care) and prove that the apps will work cross-platform (which they don't, atm – meaning devs will need to manually change things at some point in the future)<br />
<br />
I'm not exactly sure where to put all those but they're my general thoughts so far.<br />
<br />
--------------------------------<br />
Robert: Thanks for putting this together!<br />
Some feedback:<br />
<br />
* There seems to be a gap between existing HTML5 APP Developers and Web Developers described as "General web developers unfamiliar with HTML5 specifics". I think we have a LOT of HTML5-knowing web developers out there, but they don't have an existing app. "All" they need is information about APIs etc needed for creating an app.<br />
* Incentive. Even while we know it's good for the Open Web, why would developers use it? E.g. what's the projected user base, markets, backwards compatibility, monetization options.<br />
* Platforms. This document is very Firefox OS-centric, for obvious reasons, but I think we need to cover desktop in general.<br />
** Rendering engine. To my knowledge, the APIs etc will only work in Gecko (Firefox). Then we're "just" another Chrome Store and it will be hard to convince developers</div>Robnyman