Engagement/Developer Engagement/AddonSDK: Difference between revisions

Jump to navigation Jump to search
no edit summary
(dump from the related google doc)
 
No edit summary
Line 3: Line 3:
The plan to raise awareness of the Add-on SDK is a relatively straightforward set of complimentary initiatives in support activity, blogging, other social media, developer events and direct contact with key add-ons groups. One particular focus for these activities should be that they all produce data that can be easily accessed and compared.
The plan to raise awareness of the Add-on SDK is a relatively straightforward set of complimentary initiatives in support activity, blogging, other social media, developer events and direct contact with key add-ons groups. One particular focus for these activities should be that they all produce data that can be easily accessed and compared.


Support Activity
== Support Activity ==


People ask questions about the SDK in a few different places, but the top three seem to be ( in order of frequency ):
People ask questions about the SDK in a few different places, but the top three seem to be ( in order of frequency ):


  * the Jetpack google group
* the Jetpack google group
  * the SDK forum on AMO
* the SDK forum on AMO
  * Stack Overflow
* Stack Overflow
 
A goal here is to strike the delicate balance of being able to ensure that user questions get answered correctly, and not dominating what would otherwise be a natural, organic discussion. This concern is more targeted at interactions on the mailing list and SOF than the forums, as the forums are generally not monitored otherwise. Currently myself, Will and Wes are doing a decent job of this, but an interesting goal to hit would be that we a) continue to identify places on the internet where the SDK is discussed, and b) we attempt a 'zero unanswered questions' policy, particularly for the forum.
A goal here is to strike the delicate balance of being able to ensure that user questions get answered correctly, and not dominating what would otherwise be a natural, organic discussion. This concern is more targeted at interactions on the mailing list and SOF than the forums, as the forums are generally not monitored otherwise. Currently myself, Will and Wes are doing a decent job of this, but an interesting goal to hit would be that we a) continue to identify places on the internet where the SDK is discussed, and b) we attempt a 'zero unanswered questions' policy, particularly for the forum.


A possible long-term goal might be to take the route of MDN wrt forums:
A possible long-term goal might be to take the route of MDN wrt forums:


https://developer.mozilla.org/en-US/discussion
https://developer.mozilla.org/en-US/discussion


It's worth noting on that page that MDN points Addons development discussion to the AMO forums.
It's worth noting on that page that MDN points Addons development discussion to the AMO forums.


 
== Blogging ==
 
Blogging


Weekly blog posts on add ons.mozilla.org involving SDK-related content. The intent here is to pick up on the efforts Will has already started and dramatically increase the number of posts about the SDK on the AMO blog.
Weekly blog posts on add ons.mozilla.org involving SDK-related content. The intent here is to pick up on the efforts Will has already started and dramatically increase the number of posts about the SDK on the AMO blog.
Line 30: Line 27:




Future plans:
== Future plans ==


   * whenever a new API lands on the SDK development branch, we should create a blog post about it, including runnable examples hosted on builder.
   * whenever a new API lands on the SDK development branch, we should create a blog post about it, including runnable examples hosted on builder.
Confirmed users
1,100

edits

Navigation menu