1 |
Hello, |
2 |
|
3 |
On Tue, 14 Apr 2015 01:13:02 +0000 Robin H. Johnson wrote: |
4 |
> Bircoph: |
5 |
> mgorny has worked with infra to get something that is suitable. |
6 |
> _ANY_ CI is an improvement over no CI. |
7 |
|
8 |
Yes and no, this depends on implications of such improvement. |
9 |
|
10 |
> > If travis will become essential for Gentoo development, it may |
11 |
> > undermine development freedom and Gentoo social contract, which |
12 |
> > states: "Gentoo will never depend upon a piece of software or metadata |
13 |
> > unless it conforms to the GNU General Public License, the GNU Lesser |
14 |
> > General Public License, the Creative Commons - Attribution/Share Alike |
15 |
> > or some other license approved by the Open Source Initiative (OSI)." |
16 |
> This argument has come up before, claiming that something one team is |
17 |
> doing isn't in line with the social contract. mgorny himself complained |
18 |
> about infra's repos being non-public. |
19 |
> |
20 |
> Let's expand that section somewhat, from the original text: |
21 |
> "We will release our contributions to Gentoo as free software, metadata or |
22 |
> documentation, under the GNU General Public License version 2 or the Creative |
23 |
> Commons - Attribution / Share Alike version 2. ... However, Gentoo will never |
24 |
> depend upon a piece of software or metadata unless it conforms to the GNU |
25 |
> General Public License, the GNU Lesser General Public License, the Creative |
26 |
> Commons - Attribution/Share Alike or some other license approved by the Open |
27 |
> Source Initiative." |
28 |
> |
29 |
> I'm going to use the word 'libre' below, to differentiate between a |
30 |
> 'free-as-in-freedom' license, and the 'free-as-in-beer' offering from |
31 |
> commerical CI providers. |
32 |
> |
33 |
> Infra's repo contents are licensed libre: most scripts I've written in the |
34 |
> infra repos carry a BSD license, in many cases because I wrote them for dayjob |
35 |
> purposes first, and later modified them for Gentoo. |
36 |
> |
37 |
> We can expand this, by stating that the repos we want to test with CI must |
38 |
> remain libre. |
39 |
> |
40 |
> It says NOTHING about the CI tools themselves. Why should we not be able to |
41 |
> benefit from really good closed-source CI tools that are offered for free to |
42 |
> the open-source community? As long as we can continue to function WITHOUT those |
43 |
> tools, there is no direct harm [1] done in using them. They cannot force us to |
44 |
> change the licenses of our repos at all. |
45 |
|
46 |
My primary concern lies in another plane: with time we'll depend on |
47 |
github, its features and companion projects more and more. Each |
48 |
dependency will likely be replaceable, but with some effort. The |
49 |
more features or tools we use, the harder it will be to replace all |
50 |
of them, especially at once. At some moment we will not be able to |
51 |
switch to another solution in practical terms without serious |
52 |
damage to our workflow, particularly if immediate change will be |
53 |
required. What if github will just cease to exist one day? |
54 |
|
55 |
Right now we use and depend (in terms of convenience) upon at least |
56 |
following github features (): |
57 |
|
58 |
1. pull requests; |
59 |
2. travis ci; |
60 |
3. many official overlays use github widely: repositories, issue |
61 |
trackers, pull requests and more. |
62 |
|
63 |
I bet this list will expand in future with more features. |
64 |
|
65 |
Argument about saving Gentoo Foundation financial resources by |
66 |
using hardware for CI for free is heard and taken. This is a |
67 |
serious one and I can't argue here. But frankly it looks like to me |
68 |
that we are just selling our freedom, slowly, bit by bit. |
69 |
|
70 |
Best regards, |
71 |
Andrew Savchenko |