1 |
On Sun, Feb 15, 2015 at 6:24 PM, Patrick Lauer <patrick@g.o> wrote: |
2 |
> On 02/16/15 01:42, Ciaran McCreesh wrote: |
3 |
>> On Sun, 15 Feb 2015 11:17:54 -0500 |
4 |
>> "Anthony G. Basile" <blueness@g.o> wrote: |
5 |
>>> But the big difference here is that github is a company while infra |
6 |
>>> is volunteer work. |
7 |
>> |
8 |
>> And the equipment and hosting is paid for by... |
9 |
>> |
10 |
> |
11 |
> Volunteers. |
12 |
> |
13 |
|
14 |
Honestly, it is a lot more complex than that. Infra could probably |
15 |
provide a better overview, but I'm not sure how much time they want to |
16 |
spend on giving one, so I'll muddle through as best I can from what |
17 |
I've seen in my time as a Trustee. |
18 |
|
19 |
Gentoo infra consists of many elements. There is the hardware, the |
20 |
maintenance of the hardware, the OS/software and the maintenance of |
21 |
that, and the money to pay for all that stuff. |
22 |
|
23 |
One of the largest areas of infra by volume are the mirrors. These |
24 |
are almost entirely hands-off on Gentoo's part as far as I'm aware. |
25 |
They're mostly donated by organizations, and they're told how to set |
26 |
them up, and they just run some Gentoo-provided scripts/etc to stay up |
27 |
to date. The money/labor to keep them running/bandwidth/etc is all |
28 |
donated by the mirror hosts. I'm sure that if something goes wrong |
29 |
somebody from Gentoo infra helps them out, so there probably is a bit |
30 |
of labor on their part. Not really anything in the way of "equipment |
31 |
and hosting" though. |
32 |
|
33 |
Then you have the core infra. This is stuff where infra spends the |
34 |
bulk of its time. As I understand it some of the hardware is |
35 |
Gentoo-owned, and some of it is owned by sponsors who provide infra |
36 |
access to it. Almost all of this stuff has a sponsor providing |
37 |
hosting/network/power/etc, and generally if a disk dies or whatever it |
38 |
ends up being an employee of a sponsor or such who swaps stuff out for |
39 |
us (perhaps with us sending them the hardware to swap with). |
40 |
Sponsor-provided stuff tends to have the bulk of the costs paid by |
41 |
sponsors. Gentoo-owned stuff tends to have the money come from |
42 |
Gentoo, which comes from our many donors (lots of individuals, and |
43 |
Google Summer of Code is a big source of income I believe even after |
44 |
expenses). Recently Gentoo has been kicking in for some of the costs |
45 |
at one of our sponsors, but they kick in a fair bit themselves. |
46 |
|
47 |
So, quite a bit of labor comes from volunteers. However, the "paid |
48 |
for" bit largely comes down to our sponsors, augmented by numerous |
49 |
small donations from within the community. |
50 |
|
51 |
All that said, I honestly don't consider the risk of one of our |
52 |
sponsors "censoring" us is all that likely unless Gentoo as a |
53 |
community really got out of hand (such that being associated with us |
54 |
were damaging to their reputations). The more realistic risk with our |
55 |
model is that individual sponsors can come and go - maybe a sponsor |
56 |
gets bought out or goes out of business or just is having hard times |
57 |
and can't afford to support us any longer. This happens on occasion, |
58 |
and obviously we try to be gracious about it since they ARE donors |
59 |
(usually they work with us on migration too). However, my sense is |
60 |
that most/all of our infra is hand-built servers running on bare |
61 |
metal, which means that moving services around involves a lot of |
62 |
labor. It isn't like copying a disk image to a new VM provider and |
63 |
cutting over DNS, let alone something like puppet/chef/ansible. |
64 |
|
65 |
As we build out new infra services (whether they be git, gitlab, or |
66 |
whatever) it would be really nice if the server configs (minus |
67 |
credentials) could be open. That would make it far easier for others |
68 |
to contribute to them, automate their deployment, and so on. There |
69 |
really shouldn't be any reason that somebody shouldn't be able to set |
70 |
up their own gentoo.org with everything but the domain name. Sure, we |
71 |
won't get there overnight, but it is a direction that makes sense. We |
72 |
just don't have the manpower to be excluding potential contributions. |
73 |
|
74 |
-- |
75 |
Rich |