1 |
On Sun, 12 Apr 2015, Andrew Savchenko wrote: |
2 |
|
3 |
> On Thu, 9 Apr 2015 00:23:29 +0200 Michał Górny wrote: |
4 |
>> Hello, developers. |
5 |
>> |
6 |
>> We have added a new mail alias travis-ci@g.o and set up travis-ci [1] |
7 |
>> to send notifications on status change there. Please seriously consider |
8 |
>> adding yourself to the alias, and contributing to the quality |
9 |
>> of Gentoo. |
10 |
|
11 |
<snip> |
12 |
|
13 |
> While I must admit that travis is a quite convenient tool (thought |
14 |
> it has its limitations), I'd like to raise related software freedom |
15 |
> concern. |
16 |
> |
17 |
> Travis itself is a closed, proprietary and non-trivial-to-replace |
18 |
> solution. If travis will become essential for Gentoo development, |
19 |
> it may undermine development freedom and Gentoo social contract, |
20 |
> which states: "Gentoo will never depend upon a piece of software or |
21 |
> metadata unless it conforms to the GNU General Public License, the |
22 |
> GNU Lesser General Public License, the Creative Commons - |
23 |
> Attribution/Share Alike or some other license approved by the Open |
24 |
> Source Initiative (OSI)." |
25 |
|
26 |
I've seen no one suggest the use of travis is or will be mandatory. |
27 |
What Michał has done is setup the environment to help identify tree |
28 |
breakage. I want to thank him for working on a tool to improve the quality |
29 |
of Gentoo. |
30 |
|
31 |
> If travis will change their terms of service in future and our |
32 |
> workflow/infra will depends on these checks, whole development |
33 |
> process may be hampered. |
34 |
|
35 |
Our infra has no dependency over travis. The only thing we've done infra |
36 |
side about this is to create the alias travis-ci and an ml[1] |
37 |
(gentoo-automated-testing) where we plan to send the output of several |
38 |
automated tools so that interested parties can check the status and "fix" |
39 |
any issues. |
40 |
|
41 |
[1] - https://archives.gentoo.org/gentoo-automated-testing/ |
42 |
|
43 |
> So developers should think twice before depending their workflow on |
44 |
> this solution. I'm refusing to sign up to the list which in my |
45 |
> opinion indirectly violates Gentoo social contract. |
46 |
|
47 |
I fail to see how by adding yourself to the alias, joining the ml or |
48 |
checking the archives, you are breaking in any way the Social Contract - |
49 |
but every developer is free to choose whether to use this tool or not. |
50 |
|
51 |
> If some other free tool (preferably deployed on Gentoo |
52 |
> infrastructure) will be used for this task, I'll sign-up right away. |
53 |
|
54 |
If you care about this topic, you should talk to the QA team and |
55 |
developers that have showed an interest in automated testing. |
56 |
Just the other day Magnus sent an email to this ml about a project his |
57 |
working on. |
58 |
|
59 |
> Best regards, |
60 |
> Andrew Savchenko |
61 |
|
62 |
Regards, |
63 |
Jorge Manuel B. S. Vicetto |