On 8 December 2011 03:22, Ricardo Salveti ricardo.salveti@linaro.org wrote:
On Wed, Dec 7, 2011 at 6:15 PM, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Hi folks.
So there's been some justified uproar about me moving some stuff to github without asking. I wanted to let you all know that we have a Linaro organization on github (ping danilos to get your github account included there). I've created the validation team there and allowed it to push/pull to https://github.com/Linaro/lava-deployment-tool I also have my own fork.
I'm not much concerned about you moving the code hosting to github, as we already have quite a few projects using git instead of bzr (just check git.linaro.org).
What I just didn't understand much is the relation with git.linaro.org, as now it sees we have 2 official git hosting places for projects. I know that technically using github is a lot easier, as setting up a git repository at git.linaro.org can be a real pain.
Are we taking any official position on this front? Are we going to support both? Why can't we just use one single place for codehosting?
We also need to thing that this is quite confusing for our users, as the code most of the time is what we end up delivering, and trying to have it all in one place makes things a lot easier for our consumers :-)
afaik, we don't have an official position on the source code hosting place when it applies to git. The de facto standard is git.linaro.org. It's up to the team to choose where they want to host the code, though you probably don't want to use several vcs/workflows and will prefer to consolidate on a single solution for your projects.
Cheers,
Ricardo Salveti de Araujo