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:
Name: Comment
Thank you.
Havi: here are the proposed uber-categories -
- Content
- Events
- Tools
- Support
- Contests & Incentives
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.
Stormy:
Great job pulling all the information/plans into one place and making sense of it! In particular, I really like the phases approach.
Goals:
- I like Ali's specific to the audience goal suggestions
- I don't think the goals should be so specific to the Brazil launch; I think we should just say "initial launch" addressed
- "vital ecosystem" -> "vital developer ecosystem" addressed
- Do we want to populate the marketplace or get individual developers to populate the marketplace? addressed
- The first goal "generate enthusiasm ..." is important but not measurable. (Some of Ali's suggestions might provide some measurement.) 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.
Strategy:
- I think we could tighten this up and include more of what we are doing. addressed
- We should mention contents/incentives/big developer party addressed
Participants & Stakeholders:
- Just an FYI, I don't think all the evangelism reps are on engagement-developers. There's a separate list for evangelist reps. addressed
- 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? clarified players; Ali has a line item regarding MDN/DevHub rationalization, and see her remark below
- What about Lisa Brewster? addressed
Raise Developer Awareness:
- quality app says done, is that in a form we can disseminate as part of our outreach? This is baked into Lisa Brewster's guidelines, which will be published. Do we need more?
Enable App Prototyping:
- Sync developer tools, MDN and DevHub added tools
- Brazil support community has "Continue" as the owner addressed
- Feedback capture: we need a good way to give feedback (not on games but in general) suggested weekly report
- Joe has been working on a sample app addressed
- Close the time frames or change the title to be "start time frame" addressed
Ali: here are some of my thoughts on goals & strategies...
Goals - I'd like to see something less defined by what we (Mozilla) want and more developer-centric.
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).
Ideas for goals for target demographics:
- Number of existing (platform, marketplace, type) apps moved to FFOS/Marketplace
- Provide (# or %) of general web developers with training on apps & related technologies
- Get (x)% of developers who participate in an event, training, etc to submit an app
- Number of existing mobile apps ported (could be by platform, type, etc)
- Get a specific number or percentage of Mozilla community members submit an app (provide support / training for this)
- Train a certain number of people in (x) market(s) how to make apps
Christian and I were chatting about this, and he added some ideas as well. Specifically:
- Chrome HTML5 apps developers could be a target demographic for porting over apps
- 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...
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).
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.
ali: re: Do Ali/Kevin have a document some where that describes how they are working together/merging plans? I'll be working on this next week and will post a link to it...