Re: lava-deployment-tool is now (also) on github
On Thu, Dec 8, 2011 at 5:46 AM, Alexander Sack wrote: > On Wed, Dec 7, 2011 at 9:15 PM, Zygmunt Krynicki < > zygmunt.kryni...@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. >> >> > LAVA is hosted on launchpad. unless you can convince the whole team to move > everything to git, please don't do one man shows like this and put this to > bzr as well... > > Thanks for applying common sense. > Zygmunt and I discussed this yesterday and I was very clear that we are not splitting up development of components across lp and github without more compelling reasons, and communication and decision in advance. To be very clear, the official repository for this project[1], as all other LAVA related projects[2] will be on Launchpad in bzr. I don't see any reason to change that in the foreseeable future, but if it does, it will be communicated well in advance. Thanks, Paul Larson [1] http://launchpad.net/lava-deployment-tool [2] http://launchpad.net/lava ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: lava-deployment-tool is now (also) on github
On Wed, Dec 7, 2011 at 9:15 PM, Zygmunt Krynicki < zygmunt.kryni...@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. > > LAVA is hosted on launchpad. unless you can convince the whole team to move everything to git, please don't do one man shows like this and put this to bzr as well... Thanks for applying common sense. On the question whether we have everything on git.linaro.org or if github.com/linaro is ok as well, we have not yet developed a strong feeling. Default is saying that it's odd that we do that. But stay tuned. Everybody: what are the benefits you see from github/Linaro versus using git.linaro.org? Happy to collect points on this one. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: lava-deployment-tool is now (also) on github
On 8 December 2011 03:22, Ricardo Salveti wrote: > On Wed, Dec 7, 2011 at 6:15 PM, Zygmunt Krynicki > 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 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: lava-deployment-tool is now (also) on github
On 8 December 2011 01:22, Ricardo Salveti wrote: > 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? Personally I think we should have one place for git-using projects, ie git.linaro.org. It's not that hard to set up a repo there (the process is documented on the wiki somewhere) and it's not like you have to do that very often anyway. git://git.linaro.org/qemu/qemu-linaro.git is much more obviously the official qemu-linaro tree than anything on github would be. -- PMM ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: lava-deployment-tool is now (also) on github
On Wed, Dec 7, 2011 at 6:15 PM, Zygmunt Krynicki 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 :-) Cheers, -- Ricardo Salveti de Araujo ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
lava-deployment-tool is now (also) on github
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 wanted to give you a few reasons why I wanted to use github instead of bzr (note, we've got a bzr mirror setup on launchpad so you can always get the code from there) 1) Linaro uses git a lot and not all of us are fluent in it. Using git on a small project is an excellent way to learn it without affecting a ton of things 2) Github is IMHO arguably a much much much better place for code than launchpad, this is a personal feeling but one I wanted to explain better below. 3) With the git model I can keep all my branches in one repo, that is a nice feature (I still prefer to work with many directories but the annoyance of syncing them all is bigger than the adjustment to single working directory model) So having said that, those are the things that I prefer on github over their launchpad counterparts: * Github has hands down better UI, it is more pleasant to use and I found myself to be a happier person. It has a ton of tiny things that matter (like automatic archives, tarballs, zips etc, for all the tags in your code, no more manual releases!) * I like the social aspects of github, ability to follow on other people's code and get notified. Launchpad feels like a corporate world in comparison. * Github has great code review UI, ability to do merges straight from the web, better commenting on code pieces (apart from UI) * Github still has an integrated bug tracker if you wanted to jump all the way there. It also shares the niceness of the UI compared to LP * Github does better stuff at presenting your projects, it can display the README file (with nice formatting) by default, it can store your wiki and your arbitrary static HTML site for free as well. It feels much more complete compared to launchpad's "bring your own for those two quite essential topics" * Github has an _awesome_ integration with bazillion 3rd party tools (for us we could get post-commit hooks for readthedocs for example, something that is just not possible with launchpad). There are many possibilities we could use for our own workflow (commit in production branch gets deployed automatically, etc etc). While it is possible to do such stuff with launchpad is always requires painful polling with the python LP api. So there you have it. Best regards ZK ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
