I would prefer to link to docs.openstack.org or the API reference pages with specific links like this: http://api.openstack.org/api-ref-blockstorage-v2.html, http://api.openstack.org/api-ref-compute-v2.html, and so on. The issue I have with linking to the "specs" is that they are likely going to move back into the project repos, and some projects don't even have a "spec" to link to. All projects have a page on api.openstack.org, however. You could also link to api.openstack.org/api-ref.html, which is the main page
Diane ---------------------------------------------- Diane Fleming Software Developer II - US diane.flem...@rackspace.com Cell 512.323.6799 Office 512.874.1260 Skype drfleming0227 Google-plus diane.flem...@gmail.com On 4/27/14 10:12 PM, "Mike Perez" <thin...@gmail.com> wrote: >On 19:19 Sun 27 Apr , Andreas Jaeger wrote: >> So, my proposal would be: >> * Remove WADL links >> * Have PDF links to go http://docs.openstack.org >> * For those current links to the site http://docs.openstack.org: Take >> care that they point either to a current file or get redirected to >> http://docs.openstack.org/index.html > >Andreas, > >Thanks for starting this. As I mentioned, I started this with Cinder [1], >but >I was linking directly to the API spec version with the corresponding >version. >I'm curious on what others think the approach should be here. > >[1] - https://review.openstack.org/#/c/73856/ > >-- >Mike Perez > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev