{"action":"opened","issue":{"url":"https://api.github.com/repos/ga4gh/server/issues/876","labels_url":"https://api.github.com/repos/ga4gh/server/issues/876/labels{/name}","comments_url":"https://api.github.com/repos/ga4gh/server/issues/876/comments","events_url":"https://api.github.com/repos/ga4gh/server/issues/876/events","html_url":"https://github.com/ga4gh/server/issues/876","id":128815046,"number":876,"title":"Proto definitions not within ga4gh package","user":{"login":"jeromekelleher","id":2664569,"avatar_url":"https://avatars.githubusercontent.com/u/2664569?v=3","gravatar_id":"","url":"https://api.github.com/users/jeromekelleher","html_url":"https://github.com/jeromekelleher","followers_url":"https://api.github.com/users/jeromekelleher/followers","following_url":"https://api.github.com/users/jeromekelleher/following{/other_user}","gists_url":"https://api.github.com/users/jeromekelleher/gists{/gist_id}","starred_url":"https://api.github.com/users/jeromekelleher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeromekelleher/subscriptions","organizations_url":"https://api.github.com/users/jeromekelleher/orgs","repos_url":"https://api.github.com/users/jeromekelleher/repos","events_url":"https://api.github.com/users/jeromekelleher/events{/privacy}","received_events_url":"https://api.github.com/users/jeromekelleher/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ga4gh/server/labels/Protobuf","name":"Protobuf","color":"f7c6c7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-26T13:07:06Z","updated_at":"2016-01-26T13:07:06Z","closed_at":null,"body":"Currently, the protobuf schema definitions live in the ``proto`` directory. While this works well for development, there are potential issues with packaging. For example, when we create a distribution package, we will need to install two Python package ``ga4gh`` and ``proto``. This will create potential conflicts with existing packages. In any case, keeping source code required for the ga4gh package in an external namespace is confusing and untidy.\r\n\r\nWe should seek to move all the proto definitions to within the ga4gh directory, so that all code is encapsulated within the ``ga4gh`` package. This requires schema updates. Comments from @palfrey in #799:\r\n >>So, would it be possible to have the proto stuff contained in the ga4gh package?\r\n\r\n> Yes, but not without changes to schemas. They all specify the package path as starting \"proto\", and this cascades down to their dependencies, so it would have to change there as well. I had a quick go at it, and here's the experimental set of changes that would do that https://github.com/lshift/ga4gh-schemas/compare/proto3...lshift:proto3-ga4gh?expand=1"}}