Confirmed users
142
edits
Community:SummerOfCode15:Brainstorming: Difference between revisions
Community:SummerOfCode15:Brainstorming (view source)
Revision as of 15:15, 4 February 2015
, 4 February 2015added link to swagger
(Added a gsoc for release engineering) |
(added link to swagger) |
||
| Line 324: | Line 324: | ||
|- | |- | ||
| Define, test, and publish json hyperschemas for all release engineering APIs | | Define, test, and publish json hyperschemas for all release engineering APIs | ||
| We have several APIs (e.g. clobberer, buildapi, mozpool, modern mapper, slaveapi, ...) but have no central standardised way of defining them, publishing them, documenting them, or sharing them. A cool project would be to use json hyperschema (see e.g. https://brandur.org/elegant-apis) to define all our apis, and have a framework for auto testing them, auto-documenting them, even potentially auto-generating client libraries for them e.g. in python, and auto-publishing the schemas to a central location for reference. | | We have several APIs (e.g. clobberer, buildapi, mozpool, modern mapper, slaveapi, ...) but have no central standardised way of defining them, publishing them, documenting them, or sharing them. A cool project would be to use json hyperschema (see e.g. https://brandur.org/elegant-apis) to define all our apis, and have a framework for auto testing them, auto-documenting them, even potentially auto-generating client libraries for them e.g. in python, and auto-publishing the schemas to a central location for reference. Another interesting option might be using http://swagger.io/. | ||
| json, json hyperschema, solid programming skills, enthusiasm, code generation, web interface design | | json, json hyperschema, solid programming skills, enthusiasm, code generation, web interface design | ||
| [mailto:pmoore@mozilla.com Pete Moore] | | [mailto:pmoore@mozilla.com Pete Moore] | ||