Apps/API: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Goals =
This page contains all of the important details for the '''Marketplace Submission API'''.
* Give developers access to their own data
* Reward trusted accounts with more capabilities


= Brainstorming =
= Elevator Pitch =
* See https://etherpad.mozilla.org/apps-api
The goal of the Marketplace Submission API is to:
* provide individual developers with a way to push single apps to the marketplace.
* provide app workshops with a way to push many apps to the marketplace, on behalf of their customers.


= Examples and Inspiration =
== Overview ==
* http://developer.github.com/v3/
* Prod URL: TBD
* https://dev.twitter.com/docs/api
* Stage URL: TBD
* https://developers.facebook.com/docs/reference/api/
* Code Repo: https://github.com/mozilla/zamboni
* Code: Python / Django
* Dev Team: andym (Marketplace side); zalun (dev ecosystem side)
* IRC Channel: #amo on irc.mozilla.com


= Accessors =
= Meetings =
* [[Apps/API/Search|Search]]
* [https://ecosystem.etherpad.mozilla.org/7 Kickoff meeting], 5/3/2012
* [[Apps/API/Developer_Data|Developer Data]] (keyed or auth)


= Mutators =
= Status =
* [[Apps/API/Submission|Submission]]
Submission API version 1 done on Marketplace side.
* [[Apps/API/Trusted_Submission|Trusted Submission]] (keyed)
 
Current status:
* zalun implementing [https://github.com/mozilla/MarketplaceClientExample client API in Python]
 
 
Previously:
* define necessary API calls and their order of implementation (fwenzel, andym)
** file implementation bugs accordingly (fwenzel)
* implement said API calls (andym)
* document them on MDN (andym + ?)
* implement client API (reference AMO's client API) (zalun)
 
Target time frame:
* 2 weeks for very simple, initial API
 
= Specs / Useful Links =
* andym's brainstorming
** https://etherpad.mozilla.org/apps-api
* morgamic's brainstorming
** Examples and Inspiration
*** http://developer.github.com/v3/
*** https://dev.twitter.com/docs/api
*** https://developers.facebook.com/docs/reference/api/
** Accessors
*** [[Apps/API/Search|Search]]
*** [[Apps/API/Developer_Data|Developer Data]] (keyed or auth)
** Mutators
*** [[Apps/API/Submission|Submission]]
*** [[Apps/API/Trusted_Submission|Trusted Submission]] (keyed)
 
= Bugs =
Bugs are tracked on AMO's Bugzilla product.
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org&component=API File a Bug] in AMO::API. Might want to prefix bug titles with [Apps] or so.
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&component=API&product=addons.mozilla.org Open AMO API bugs]

Latest revision as of 00:12, 28 June 2012

This page contains all of the important details for the Marketplace Submission API.

Elevator Pitch

The goal of the Marketplace Submission API is to:

  • provide individual developers with a way to push single apps to the marketplace.
  • provide app workshops with a way to push many apps to the marketplace, on behalf of their customers.

Overview

  • Prod URL: TBD
  • Stage URL: TBD
  • Code Repo: https://github.com/mozilla/zamboni
  • Code: Python / Django
  • Dev Team: andym (Marketplace side); zalun (dev ecosystem side)
  • IRC Channel: #amo on irc.mozilla.com

Meetings

Status

Submission API version 1 done on Marketplace side.

Current status:


Previously:

  • define necessary API calls and their order of implementation (fwenzel, andym)
    • file implementation bugs accordingly (fwenzel)
  • implement said API calls (andym)
  • document them on MDN (andym + ?)
  • implement client API (reference AMO's client API) (zalun)

Target time frame:

  • 2 weeks for very simple, initial API

Specs / Useful Links

Bugs

Bugs are tracked on AMO's Bugzilla product.