{"action":"created","issue":{"url":"https://api.github.com/repos/getavalon/core/issues/280","repository_url":"https://api.github.com/repos/getavalon/core","labels_url":"https://api.github.com/repos/getavalon/core/issues/280/labels{/name}","comments_url":"https://api.github.com/repos/getavalon/core/issues/280/comments","events_url":"https://api.github.com/repos/getavalon/core/issues/280/events","html_url":"https://github.com/getavalon/core/issues/280","id":260273236,"number":280,"title":"Ftrack integration","user":{"login":"mkolar","id":3333008,"avatar_url":"https://avatars2.githubusercontent.com/u/3333008?v=4","gravatar_id":"","url":"https://api.github.com/users/mkolar","html_url":"https://github.com/mkolar","followers_url":"https://api.github.com/users/mkolar/followers","following_url":"https://api.github.com/users/mkolar/following{/other_user}","gists_url":"https://api.github.com/users/mkolar/gists{/gist_id}","starred_url":"https://api.github.com/users/mkolar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mkolar/subscriptions","organizations_url":"https://api.github.com/users/mkolar/orgs","repos_url":"https://api.github.com/users/mkolar/repos","events_url":"https://api.github.com/users/mkolar/events{/privacy}","received_events_url":"https://api.github.com/users/mkolar/received_events","type":"User","site_admin":false},"labels":[{"id":623246299,"url":"https://api.github.com/repos/getavalon/core/labels/epic","name":"epic","color":"5319e7","default":false},{"id":522384519,"url":"https://api.github.com/repos/getavalon/core/labels/feature","name":"feature","color":"bfd4f2","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2017-09-25T13:17:05Z","updated_at":"2017-09-27T13:48:55Z","closed_at":null,"author_association":"NONE","body":"# Goal\r\n\r\nImplement a system which would enable connection between ftrack and avalon. \r\n\r\n# Motivation\r\n\r\nFtrack has been struggling for quite some time with writing good usable pipeline tools. Even though they've implemented pyblish in the latest publishing tools, the development is taking very long time, and it doesn't seem to be looking at the pipeline in all it's complexity as avalon is. However joining avalon's data management and ftrack production tracking capabilities would I believe create extremely strong tool. The same goes for shotgun where it would provide alternative to their very robust pipeline toolkit, but that's for another issue.\r\n\r\n# Implementation\r\n\r\nTo make this happen there are certainly many smaller and bigger tasks to be done, but we can start break them down here and slowly make issues for each of them as we go along. This is where I would start\r\n\r\n- define what should be the relationship between avalon and ftrack database (what data needs to live in both, or in just one of them)\r\n- map terms between the two systems, to make sure we're not mixing up vocabulary when talking about the two\r\n- get launcher/environment setup API up an running to be able to use ftrack actions instead of the avalon default launcher\r\n- create ftrack action that mirrors objects into avalon database. This can eventually be automated with ftrack event script that listens to new objects being created in ftrack and creates them in avalon too. \r\n\r\nThis would be sufficient for a start. It's fairly one way (ftrack to avalon), but that's more than enough to get the ball rolling.\r\n\r\nThe first major question is. Are there any relevant concepts in place already that need to be evaluated and considered, or are we looking the such setup from scratch? "},"comment":{"url":"https://api.github.com/repos/getavalon/core/issues/comments/332526701","html_url":"https://github.com/getavalon/core/issues/280#issuecomment-332526701","issue_url":"https://api.github.com/repos/getavalon/core/issues/280","id":332526701,"user":{"login":"tokejepsen","id":1860085,"avatar_url":"https://avatars0.githubusercontent.com/u/1860085?v=4","gravatar_id":"","url":"https://api.github.com/users/tokejepsen","html_url":"https://github.com/tokejepsen","followers_url":"https://api.github.com/users/tokejepsen/followers","following_url":"https://api.github.com/users/tokejepsen/following{/other_user}","gists_url":"https://api.github.com/users/tokejepsen/gists{/gist_id}","starred_url":"https://api.github.com/users/tokejepsen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tokejepsen/subscriptions","organizations_url":"https://api.github.com/users/tokejepsen/orgs","repos_url":"https://api.github.com/users/tokejepsen/repos","events_url":"https://api.github.com/users/tokejepsen/events{/privacy}","received_events_url":"https://api.github.com/users/tokejepsen/received_events","type":"User","site_admin":false},"created_at":"2017-09-27T13:48:55Z","updated_at":"2017-09-27T13:48:55Z","author_association":"NONE","body":"> There'll be pros/cons to each approach\r\n\r\nWould you get best of both worlds, by utilizing both?\r\n\r\nWith \"Auto Syncing\" you get assets that haven't need launched, but there is change of the syncing not working.\r\nWith \"Launch Syncing\" you get assets that have already been worked on, but offline you couldn't launch any other.\r\n\r\nAlso what happens if Ftrack is down, and a publish is made? Would you need to republish to propagate to Ftrack, or would we rely on auto syncing or manually Avalon push tools for pushing to Ftrack?"}}
{"actor":{"display_login":"tokejepsen"}}