As per discussion with @ebuchman.
Should we move this from an issue into some kind of "future-plans" section of the readme in docs?
Docs readme is in flux, so leaving this issue open for now
okay - should be more stable soon then we should merge in
@gamarin2 (cc: @jackzampolin, @zramsay, @ebuchman, @greg-szabo, @alexanderbez, @alessio ) I would change:
SDK API spec โโ> SDK GoDoc with descriptions of pkgs (ToDo)SDK reference doc โโ> SDK GlossarySDK Gaia-lite API: Summary of all Gaia-lite endpoints with their ICS standards, parameters, return values, etc. Preferably in a Swagger file and hosted on the website docsI feel SDK Glossary does not accurately reflect the content. The Reference Doc is more than just a glossary.
SDK API spec โโ> SDK GoDoc with descriptions of pkgs (ToDo)
I very much agree to that - the lack of package-specific docs tends to make life quite tough for a new starter :)
๐@gamarin2 let's stick with SDK Reference then. Can it be Guide instead of Doc ?
I'll open separate issues to track what's needed for each of them. cc: @gamarin2 @jackzampolin
obsolete / replaced by what we just did
Most helpful comment
@gamarin2 (cc: @jackzampolin, @zramsay, @ebuchman, @greg-szabo, @alexanderbez, @alessio ) I would change:
SDK API specโโ>SDK GoDocwith descriptions of pkgs (ToDo)SDK reference docโโ>SDK Glossaryand add
SDK Gaia-lite API: Summary of all Gaia-lite endpoints with their ICS standards, parameters, return values, etc. Preferably in a Swagger file and hosted on the website docs