>From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014 5:09 PM >On Nov 20, 2014, at 3:40 PM, Sandy Walsh <sandy.wa...@rackspace.com> wrote: >> From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014 3:51 >> PM >>> On Nov 20, 2014, at 8:12 AM, Sandy Walsh <sandy.wa...@rackspace.com> wrote: >>>> The assumptions: >>>> 1. Schema files will be text files. They'll live in their own git repo >>>> (stackforge for now, ideally oslo eventually). >>> Why wouldn’t they live in the repo of the application that generates the >>> notification, like we do with the database schema and APIs defined by those >>> apps? >> >> That would mean downstream consumers (potentially in different languages) >> would need to pull all repos and extract just the schema parts. A separate >> repo would make it more accessible.
>OK, fair. Could we address that by publishing the schemas for an app in a tar >ball using a post merge job? That's something to consider. At first blush it feels a little clunky to pull all projects to extract schemas whenever any of the projects change. But there is something to be said about having the schema files next to the code that going to generate the data. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
