On Sun, Apr 12, 2015 at 05:54:36PM +0300, Andrew Savchenko wrote: > Right now there is no hard dependency on github or travis, of > course. But present pathway worries me: with current pace at some > point we _will_ depend on travis or github too much. Then they may > change their terms of service or license argeement, or just shut > down the whole service (as Google recently shut down Google Code). > And then we will be in a great trouble. And then it may be too late > to change anything. I want to avoid this, that's all. It may take some work, but I do not think we could reach a point where nothing could be changed.
Remember that, unlike cvs, every git clone, by default, has all of the history of the repository, so all we would have to do is find another place to host the repository and push it there. > What we should really do is to develop our own QA tools or use > existing free ones on our own infrastructure, thus that Gentoo > development may continue to be independent and unbiased. This is more likely once the main Gentoo ebuild repository is migrated to git. > Please understand that I'm grateful for all people improving > Gentoo, including Michał, for their hard work. But we should not > solely rely on third-party proprietary solutions (travis is a > github lock-in) because of convenience. wrt travis-ci, why not contribute code to it so that isn't a github lock-in? Have you checked to see if the authors are opposed to that kind of contribution? I think all of these extra solutions are coming up because folks are frustrated with the current status of our main portage tree not being under git. > Best regards, > Andrew Savchenko William
signature.asc
Description: Digital signature
