From: Mike Gerwitz <mtg@gnu.org>
To: Wilfred Hughes <me@wilfred.me.uk>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Setting up CI for Guile
Date: Mon, 17 Oct 2016 21:39:27 -0400 [thread overview]
Message-ID: <87vawqqvu8.fsf@gnu.org> (raw)
In-Reply-To: CAFXAjY5HwP07aBuoGzEAT2ZcqYF=YZ6Uueza-p_RLAFsQzdmmg@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Wilfred:
On Thu, Oct 06, 2016 at 00:26:28 -0400, Wilfred Hughes wrote:
> So, I decided to set it up! This isn't something that's available on
> GNU Savannah, so I've used GitLab (which is still FSF-approved Free
> Software).
GitLab CE is free software. GitLab EE is not, but all of the JavaScript
served to the browser is.[0]
But their CI services are SaaSS.[1] If all builds took place on servers
that Guile developers control---like the current Hydra servers---then
this wouldn't be a problem.
The GNU Project has criteria for hosts that it considers to be
acceptable for hosting GNU software.[2] GitLab is an acceptable host
under those criteria, but one of the criteria---A5---requires that the
host not recommend SaaSS. Unfortunately, GitLab won't ever be able to
meet that. It's okay to use GitLab to host repositories, but not for
SaaSS.
[0]: https://about.gitlab.com/2015/05/20/gitlab-gitorious-free-software/
[1]: https://www.gnu.org/philosophy/who-does-that-server-really-serve.html
[2]: https://www.gnu.org/software/repo-criteria.html
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
Old: 2217 5B02 E626 BC98 D7C0 C2E5 F22B B815 8EE3 0EAB
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2016-10-18 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 4:26 Setting up CI for Guile Wilfred Hughes
2016-10-06 9:43 ` Taylan Ulrich Bayırlı/Kammer
2016-10-06 14:34 ` Thompson, David
2016-10-06 15:16 ` Jan Nieuwenhuizen
2016-10-11 19:56 ` Ludovic Courtès
2016-10-18 1:39 ` Mike Gerwitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vawqqvu8.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=guile-devel@gnu.org \
--cc=me@wilfred.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).