Google SageTV vs Open SageTV

[Ian Davies]

I see that on Open SageTV is a fork of Google SageTV on Github. Is there any difference between the two?

Thanks,

Ian.

[Fuzzy]

what 'Open SageTV' do you refer to?

[stuckless]

OpenSageTV (https://github.com/OpenSageTV), is GitHub "org" for open source related projects around SageTV and SageTV components. So, the Android MiniClient lives there, there is a fork of SageTV, there is a fork of mplayer there (used by the PC placeshifter), etc. Normally this stuff would live with "SageTV" but SageTV is a google owned and you can't be a member of those projects unless you are a google employee.

Currently all builds for SageTV come from the main "sagetv" repo, but, I contemplated doing builds against a fork, in OpenSageTV, because it's much easier to manage builds when you have direct commit access to a repo. I haven't done that yet, but it may happen at some point.

[Ian Davies]

Originally Posted by stuckless

OpenSageTV (https://github.com/OpenSageTV), is GitHub "org" for open source related projects around SageTV and SageTV components. So, the Android MiniClient lives there, there is a fork of SageTV, there is a fork of mplayer there (used by the PC placeshifter), etc. Normally this stuff would live with "SageTV" but SageTV is a google owned and you can't be a member of those projects unless you are a google employee.

Currently all builds for SageTV come from the main "sagetv" repo, but, I contemplated doing builds against a fork, in OpenSageTV, because it's much easier to manage builds when you have direct commit access to a repo. I haven't done that yet, but it may happen at some point.

Thanks for the explanation, stuckless. So, all the changes that the non-Google employees make are against the OpenSageTV repo and someone from Google then commits these to the main Google SageTV repo. So effectively the projects are the same. Is that the case? Or, are only Google employees working on SageTV? I'm just curious how it works.

[EnterNoEscape]

Originally Posted by Ian Davies

Thanks for the explanation, stuckless. So, all the changes that the non-Google employees make are against the OpenSageTV repo and someone from Google then commits these to the main Google SageTV repo. So effectively the projects are the same. Is that the case? Or, are only Google employees working on SageTV? I'm just curious how it works.

Developers outside of Google digitally sign a contributor license agreement (CLA). After that is done, they submit pull requests from their own forked copy of the SageTV repository to the Google SageTV repository on GitHub. A continuous integrator (CI) compiles the entire Linux part of SageTV with the pull request changes and displays an error if it doesn't compile. If it fails, you need to fix your code. Then usually Narflex goes over the changes and might make suggestions or indicate things that must be changed/fixed for various reasons. After he is ok with the request, he merges it into the Google repository.

[Ian Davies]

Originally Posted by EnterNoEscape

Developers outside of Google digitally sign a contributor license agreement (CLA). After that is done, they submit pull requests from their own forked copy of the SageTV repository to the Google SageTV repository on GitHub. A continuous integrator (CI) compiles the entire Linux part of SageTV with the pull request changes and displays an error if it doesn't compile. If it fails, you need to fix your code. Then usually Narflex goes over the changes and might make suggestions or indicate things that must be changed/fixed for various reasons. After he is ok with the request, he merges it into the Google repository.

Thank you. That fully explains how it works and, combined with stuckless's response, why there is a separate repo.