DeveloperExperience: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 13: Line 13:


* Getting Started Resources
* Getting Started Resources
** [[/Mozilla-App-SDK|Mozilla App SDK]]
** '''[[/Mozilla-App-SDK|Mozilla App SDK]]'''
*** Product Owner: dbuchner
*** Product Owner: dbuchner
*** Engineering Owner: fwenzel
*** Engineering Owner: fwenzel
Line 19: Line 19:
*** What's next: prototyping to figure out the best path to implement the widgets
*** What's next: prototyping to figure out the best path to implement the widgets
** Documentation
** Documentation
*** {{ok|}} DevHub
*** {{ok|}} '''DevHub''' (needs a link)
**** Product Owner: dbuchner
**** Product Owner: dbuchner
**** Engineering Owner: fwenzel
**** Engineering Owner: fwenzel
**** Status: v1 launched on staging
**** Status: v1 launched on staging
**** What's next:  
**** What's next:  
*** [[Apps/DesignGuide|Design Guidelines]]
*** '''[[Apps/DesignGuide|Design Guidelines]]'''
**** Product Owner: dbuchner
**** Product Owner: dbuchner
**** Engineering Owner: fwenzel
**** Engineering Owner: fwenzel
**** Status: initial version on staging
**** Status: initial version on staging
**** What's next:
**** What's next:
*** Existing Websites/Apps to Firefox Apps Docs
*** '''Existing Websites/Apps to Firefox Apps Docs'''
**** Product Owner: dbuchner
**** Product Owner: dbuchner
**** What's next: determine if there's something underway, figure out what needs to happen
**** What's next: determine if there's something underway, figure out what needs to happen
*** Improved Firefox for Devs resource on MDN
*** '''Improved Firefox for Devs resource on MDN'''
**** Product Owner: kdangoor
**** Product Owner: kdangoor
**** Status: there's a bug on file
**** Status: there's a bug on file
**** What's next: more detail, and should there be a link to DevHub from MDN front page?
**** What's next: more detail, and should there be a link to DevHub from MDN front page?
** How to get a phone?
** '''How to get a phone?'''
*** Product Owner: kdangoor (tracking down real owner)
*** Product Owner: kdangoor (tracking down real owner)
*** What's next: talking to people to find plans
*** What's next: talking to people to find plans
* Developer Tools
* Developer Tools
** {{risk|}} [[DevTools/Features/ToolsWindow|Tools Window]] (Useful for remoting)
** {{risk|}} '''[[DevTools/Features/ToolsWindow|Tools Window]]''' (Useful for remoting)
*** Product Owner: kdangoor
*** Product Owner: kdangoor
*** Engineering Owner: jwalker
*** Engineering Owner: jwalker
Line 46: Line 46:
*** Product Owner: kdangoor
*** Product Owner: kdangoor
*** Engineering Owner: rcampbell
*** Engineering Owner: rcampbell
** Short Term Add-on Builder Support
** '''Short Term Add-on Builder Support'''
*** Product Owner: jgriffiths/dbuchner
*** Product Owner: jgriffiths/dbuchner
*** Engineering Owner: fwenzel?
*** Engineering Owner: fwenzel?
*** What's next: see {{bug|671835}}
*** What's next: see {{bug|671835}}
** {{ok|}} [[DevTools/Features/SourceMap|JavaScript Source Maps]]
** {{ok|}} '''[[DevTools/Features/SourceMap|JavaScript Source Maps]]'''
*** Product Owner: kdangoor
*** Product Owner: kdangoor
*** Engineering Owner: rcampbell
*** Engineering Owner: rcampbell
* Firefox OS Developer Support
* '''Firefox OS Developer Support'''
** Product Owner: kdangoor
** Product Owner: kdangoor
** What's next: rekindle the earlier thread, check on ownership
** What's next: rekindle the earlier thread, check on ownership

Revision as of 15:50, 31 August 2012

Developer Experience

Mozilla aims to make the web work better for developers, enabling them to produce ever better applications and sites. The Developer Experience product team works to find the ways in which Mozilla can best help developers do more. Kevin Dangoor has produced a 5 minute video introducing the idea.

The Developer Experience product team is:

  • Kevin Dangoor
  • Daniel Buchner

In Progress

  • Getting Started Resources
    • Mozilla App SDK
      • Product Owner: dbuchner
      • Engineering Owner: fwenzel
      • Status: Initial document and meeting to discuss
      • What's next: prototyping to figure out the best path to implement the widgets
    • Documentation
      • [ON TRACK] DevHub (needs a link)
        • Product Owner: dbuchner
        • Engineering Owner: fwenzel
        • Status: v1 launched on staging
        • What's next:
      • Design Guidelines
        • Product Owner: dbuchner
        • Engineering Owner: fwenzel
        • Status: initial version on staging
        • What's next:
      • Existing Websites/Apps to Firefox Apps Docs
        • Product Owner: dbuchner
        • What's next: determine if there's something underway, figure out what needs to happen
      • Improved Firefox for Devs resource on MDN
        • Product Owner: kdangoor
        • Status: there's a bug on file
        • What's next: more detail, and should there be a link to DevHub from MDN front page?
    • How to get a phone?
      • Product Owner: kdangoor (tracking down real owner)
      • What's next: talking to people to find plans
  • Developer Tools
    • [AT RISK] Tools Window (Useful for remoting)
      • Product Owner: kdangoor
      • Engineering Owner: jwalker
    • [ON TRACK] Remote Web Console (needlink)
      • Product Owner: kdangoor
      • Engineering Owner: rcampbell
    • Short Term Add-on Builder Support
      • Product Owner: jgriffiths/dbuchner
      • Engineering Owner: fwenzel?
      • What's next: see bug 671835
    • [ON TRACK] JavaScript Source Maps
      • Product Owner: kdangoor
      • Engineering Owner: rcampbell
  • Firefox OS Developer Support
    • Product Owner: kdangoor
    • What's next: rekindle the earlier thread, check on ownership

Coming Up

  • Developer Tools

Plans

A developer experience roadmap is currently being revised.

Kilimanjaro People

This is a collection of notes about people who are involved in developer-related aspects of the Kilimanjaro project.

  • Documentation
    • The Developer Ecosystem team, led by Fred Wenzel, are working on creating tutorials/tracks to guide developers through App creation
    • Janet Swisher is working on content strategy for Apps developers
  • Apps Marketplace partners
    • These are the service providers that developers use that will push Apps to the Marketplace on behalf of the developers
    • Ron Piovesan does a lot of the initial contact with these partners
    • Kev Needham's group helps support the partners if they are having trouble with the store or other issues
    • Fred Wenzel's group can help engineers with the APIs and system integration
  • Libraries
    • James Burke has worked on Apps-related libraries
    • Kumar McMillan and Andy McKay have worked on payments
  • Apps Marketplace development
    • Wil Clousner's team is developing the Marketplace
  • Evangelism
    • Joe Stagner is leading on developer evangelism for Apps
    • Havi is doing the go-to-market plans

Developer Experience Go-To People

  • Product Managers: Kevin Dangoor, Daniel Buchner
  • Developer Tools Engineering: Dave Camp
  • Apps Ecosystem Web Development: Fred Wenzel
  • Developer PR: Paul Jarratt
  • UX: Brian Dils
  • Market Research: John Jensen