By the way, OpenHatch (http://openhatch.org ) recently moved from Gitorious to Github for similar reasons as the issues we have: http://lists.openhatch.org/pipermail/devel/2011-November/002521.html
I can only emphasize that Gitorious is also a centralized service. I can not use my account anywhere else, nor can I be sure they run the code they purportedly do. They can shut down any minute – and in fact, they have way more downtime or problems than Github. It often is a pain to work with when it simply doesn’t do what it is supposed to do – which is »just work, damnit«. On Wed, May 2, 2012 at 1:56 PM, Arthur Schiwon <[email protected]> wrote: > On 05/01/2012 03:14 AM, Sam Tuke wrote: >> >> On Sat, 2012-04-28 at 22:43 +0200, Klaas Freitag wrote: >>> >>> Freedom requires freedom, its not working otherwise. >> >> >> This is also my view. I disagree with the proposal to move to GitHub. >> >> ownCloud should not associate itself with proprietary or neo-proprietary >> (open core) partners or suppliers unless there is a significant benefit >> in doing so. I don't think GitHub offers sufficient benefits to merit >> such an association. >> >> However, an improvement to the availability of the ownCloud repo would >> be good, and I know that Frank is already looking into this. >> >> Best, >> >> Sam. > > > I fully second it. > > I do not see that we need to leave a free solution for a proprietary one. No > doubt there is room for improvement within Gitorious. > > Cheers > Arthur > > >> >> >> >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud > > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
