Gentoo Archives: gentoo-dev

From: Andrew Savchenko <bircoph@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Please subscribe to travis-ci mail alias to get notifications on depgraph breakages
Date: Sun, 12 Apr 2015 14:54:50
Message-Id: 20150412175436.7ba3904e220c9077ee1b68f2@gentoo.org
In Reply to: Re: [gentoo-dev] Please subscribe to travis-ci mail alias to get notifications on depgraph breakages by "Jorge Manuel B. S. Vicetto"
1 On Sun, 12 Apr 2015 03:03:18 +0000 (UTC) Jorge Manuel B. S. Vicetto
2 wrote:
3 > > If travis will change their terms of service in future and our
4 > > workflow/infra will depends on these checks, whole development
5 > > process may be hampered.
6 >
7 > Our infra has no dependency over travis. The only thing we've done infra
8 > side about this is to create the alias travis-ci and an ml[1]
9 > (gentoo-automated-testing) where we plan to send the output of several
10 > automated tools so that interested parties can check the status and "fix"
11 > any issues.
12 >
13 > [1] - https://archives.gentoo.org/gentoo-automated-testing/
14 >
15 > > So developers should think twice before depending their workflow on
16 > > this solution. I'm refusing to sign up to the list which in my
17 > > opinion indirectly violates Gentoo social contract.
18 >
19 > I fail to see how by adding yourself to the alias, joining the ml or
20 > checking the archives, you are breaking in any way the Social Contract -
21 > but every developer is free to choose whether to use this tool or not.
22
23 Right now there is no hard dependency on github or travis, of
24 course. But present pathway worries me: with current pace at some
25 point we _will_ depend on travis or github too much. Then they may
26 change their terms of service or license argeement, or just shut
27 down the whole service (as Google recently shut down Google Code).
28 And then we will be in a great trouble. And then it may be too late
29 to change anything. I want to avoid this, that's all.
30
31 What we should really do is to develop our own QA tools or use
32 existing free ones on our own infrastructure, thus that Gentoo
33 development may continue to be independent and unbiased.
34
35 Please understand that I'm grateful for all people improving
36 Gentoo, including Michał, for their hard work. But we should not
37 solely rely on third-party proprietary solutions (travis is a
38 github lock-in) because of convenience.
39
40 Best regards,
41 Andrew Savchenko

Replies