Engagement/Developer Engagement/Meetings/2013-07-16

From MozillaWiki
Jump to: navigation, search
  • Tuesday, July 16, 2013 @ 9:00am Pacific Time (16:00 UTC through November 6)

Agenda

Add your agenda items here before hand. Add links to more information or background whenever possible.

Actions

  • ACTION: sole to write a post on web audio and the audiomonkey patch polyfill
  • ACTION: chrismills to help with demo for WebRTC
  • ACTION: Ali Spivak to work with teams to figure out metrics around awareness and linking.
  • ACTION: Maire Reavy to schedule a follow up with the people interested in helping with WebRTC. Email her if interested.

Notes

  • Purpose of the meeting:
    • a place where we can discuss our developer efforts across Mozilla and coordinate and align on goals and efforts
    • IRC only meeting
  • Intros - we introduced everyone as it was the first meeting
    • jezdez and chris mills joined the developer engagement team!
    • Mark Coggins, I manage the technical evangelism group at Mozilla
    • Luke Crouch, MDN site development
    • Ali Spivak, MDN Product Manager
    • John Karahalis, project manager for MDN
    • Janet Swisher, community manager for developer docs and technical evangelism
    • Jannis Leidel, web developer at MDN
    • Randell Jesup. webrtc tech lead.
    • I'm Eric Shepherd, the developer documention lead. Basically I try to organize the docs community into producing coherent docs about the tech side of Mozilla and the Open Web.
    • Les Orchard, MDN dev
    • Paul McLanahan, www.mozilla.org developer
    • Maire Reavy, I am the engineering manager for WebRTC and am involved in several other media (audio/video) projects
    • Stormy Peters, Developer Engagement & Websites - enabling others
    • Robert Nyman, Technical Evangelist, runs the Hacks blog
    • Soledad Penades, Developer at dev ecosystem
    • Daniel Buchner, product manager
    • David Walsh, MDN dev
  • News
    • Simulator 4 released!
    • elastic search
    • MDN & WebMaker
      • we've been doing MDN doc sprints on a regular basis for a couple of years, now
      • alispivak and jms are working with Laura H and Michelle T from WebMaker to develop a new kind of event that combines an WebMaker techniques with an MDN sprint, more of a learning event
      • We're planning to prototype this at the OHM festival in the Netherlands at the end of July https://ohm2013.org/site/
      • We're also talking about iterating on it at Tech4Africa (http://tech4africa.com/event/tech4africa-the-annual-conference/)
      • Will also try out with JSFoo in India.
    • WebRTC
      • There was a webrtc expo a few weeks ago. we had 2 developers go (jib and tim terriberry) and andreas gave one of the keynotes. These expos happen about every 6 months, it'd be great if we could have more a presence at the next one and even more importantly, encourage more webrtc devs to use firefox.
      • webrtc on desktop is no longer behind a pref
      • DataChannels will let developers do a bunch of innovative stuff
      • we had some /unbelievable/ entries to our getUserMedia Dev Derby (with judging from mreavy and jesup -- thanks again!). Winners will be announced on Hacks on Thursday.
      • many people use only the webkit prefix, so the demos don't work on Firefox
      • We believe we have parity (and then some in areas like audio recording and DataChannels) so if there is stuff that devs want that firefox doesn't do, that would be a great list to capture and prioritize.
      • ACTION: sole to write a post on web audio and the audiomonkey patch polyfill
      • ACTION: chrismills to help with demo for WebRTC
    • Cross Organizational Developer Goals
      • Given the Mozilla mission, how do we make sure we are successful with how it relates to developers? ("Our mission is to promote openness, innovation & opportunity on the Web.")
        • What would we look at to say "Mozilla's mission succeeded with developers!"?
        • Which projects? What metrics? Thoughts?
      • Brainstorming:
        • one measurement is that web sites/apps don't work in just one web browser
        • Best chance is to solve problem issues for devs, like offline, data sync, caching, IndexedDB, etc
        • goals and success metrics around community participation/contribution & have tools to measure them
        • How do we map product project goals? Persona is important for an open web that respects people's privacy. And the Persona team has a goal to get x number of website using persona. Would the developer perspective on that be the same?
        • Tools is huge too
        • cross compatible open web apps...
        • WebAPI/Platform should be involved
        • getting more specific about measuring success, a year from now, how will we know if Mozilla has successfully engaged web developers to help in our mission? How will the world be measurable different? Either the world in general or the impact that our projects have had.
        • we have apps that work across web platform envs, apps that have real meat, with advanced APIs
        • X apps using the API after it has been in 2 or more browsers for 2 quarters
        • active participants in the developer program, MDN community. I think we need a session at the offsite (jumping ahead on the agenda) to define key metrics (e.g. what does active mean as far as contribution) and how to measure
        • getting active feedback on our content, from demos to blogs to tweets to documentation.
        • getting other vendors interesting in implementing the standards for open web apps would be a huge metric, but slow to implement
        • how many conference slide decks or blog posts recommend MDN or other Mozilla developer-facing properties -- somehow measuring and improving that number.
        • mention and links to developer content from outside sources could be a measurement, inbound links
        • ACTION: Ali Spivak to work with teams to figure out metrics around awareness and linking.
        • For measuring success with mozilla, look at how many of these actively developed products work with Mozilla
        • For WebRTC, making sure sites using the technology work with Firefox.
  • Other updates
    • We have a bunch of developer facing roles open!
      • Developer program manager, project manager, product marketing manager, product manager ....
      • In spite of all the "managers" in the title - these roles do lots of real work! :) And are all very technical. Please spread the word.
    • MDN redesign
      • there is a link to the wiki page for the redesign in the agenda
      • MDN is being redesigned/rebranded to provide a single visual identity & brand for developers. Part of that is pulling together developer-facing websites and programs under a revamped Mozilla Developer Network. we are gathering disperate dev content and sites under one dev umbrella/
      • there is an email thread in process about the schedule for the design work - I guess the creative team forgot to account for some vacation time, so there is likely going to be an impact
      • ACTION: Maire Reavy to schedule a follow up with the people interested in helping with WebRTC. Email her if interested.
    • Events
      • the main thing to know is we track all the events mozilla participates in here: https://developer.mozilla.org/en-US/events
      • You can see the ones that are coming up and, if you are going to one that isn't listed, please let Robyn Chau know
    • Offsite agenda and goals
    • Dbuc raises awareness of this issue being discussed on the MDN drivers list https://groups.google.com/forum/#!topic/mozilla.mdn.drivers/PRXZo2gc4PA

IRC Log

File:Devrel-irc-transcript-mtg-13-07-16.odt

Retrieved from "https://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Meetings/2013-07-16&oldid=683222"