[Board] Travis-CI & OSGeo

[María Arias de Reyna]

As Angelos noted, the board already moved in favor of buying the
subscription to Travis CI, at least until we have a better choice (if
we ever have it). Please, continue this discussion and consider:

* If a project has a need, the best moment to ask for money is at the
end of the year, when we write the budget. This can be modified later,
as we are doing now, but that makes it more difficult to be fair
distributing money.
* If it is something that is going to be shared with more projects, it
won't be a burden for the project that request the money. We just need
to know this is a shared resource and it would be good knowing who is
going to benefit from it.
* If some other projects have some alternative, please document and
share it. Like having a mirror on gitlab and use gitlab-ci.

Personally, I prefer to have an owned Jenkins. Specially if we note
that the maximum number of threads in Travis is 10 (even paying),
which is easily done with a simple Jenkins on a decent hardware, no
need for a farm of slaves. But I understand your concerns and your
will to simplify the work and just rent something which is already
working for you.


On Wed, May 2, 2018 at 11:36 AM, Sandro Santilli <strk at kbt.io> wrote:
> On Tue, May 01, 2018 at 12:22:26PM -0500, Howard Butler wrote:
>
>> Should OSGeo pay you so you never burn out (you
>> would anyway, suffering people's build farms is a thankless task)? Or
>> should it pay for specialists who only run build farms for many more
>> organizations and users than OSGeo's?
>
> When available (in this case it is) I'd be in favour of OSGeo paying
> specialists who run build farms based on free software, so that when
> that service goes out of business (the corporate version of "burn
> out") we don't need to change our habits but can just change provider
> of the _same_ (free software based) service.
>
> --strk;