From: Hartmut Goebel <h.goebel@goebel-consult.de>
To: guix-devel@gnu.org
Subject: Re: GHM debriefing
Date: Sat, 3 Sep 2016 10:05:24 +0200 [thread overview]
Message-ID: <f985fcf3-698f-b7a0-66bc-a82ca393d07e@goebel-consult.de> (raw)
In-Reply-To: <877fawh8t8.fsf@lassieur.org>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Am 01.09.2016 um 00:28 schrieb Clément Lassieur:
> The libreboot website [3] explains "what's wrong with Gitlab", I think
> it is worth reading.
Below the line these thoughts are worth to consider. Esp. that the
"Community Edition" will always be on the drip of the vendor. This is
the same problem for all "community edition" projects.
(Beside this the libreboot page holds some un-backed statements like
"the opinions expressed", which makes me take that page with a grain of
salt.)
--
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development
Goebel Consult, Landshut
http://www.goebel-consult.de
Blog:
http://www.goebel-consult.de/blog/bestanden-iso-27001-lead-implementer
Kolumne:
http://www.cissp-gefluester.de/2012-01-in-die-cloud-in-die-cloud-aber-wo-soll-die-sein
[-- Attachment #2: Type: text/html, Size: 2050 bytes --]
next prev parent reply other threads:[~2016-09-03 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 22:09 GHM debriefing Ludovic Courtès
2016-08-29 12:48 ` David Craven
2016-08-29 13:50 ` Vincent Legoll
2016-08-29 15:20 ` Christopher Allan Webber
2016-08-30 15:57 ` Ludovic Courtès
2016-08-31 13:40 ` ng0
2016-08-31 13:48 ` David Craven
2016-08-31 22:28 ` Clément Lassieur
2016-08-31 23:08 ` Leo Famulari
2016-09-01 6:41 ` ng0
2016-09-01 12:24 ` Ludovic Courtès
2016-09-03 8:05 ` Hartmut Goebel [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-29 21:52 Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f985fcf3-698f-b7a0-66bc-a82ca393d07e@goebel-consult.de \
--to=h.goebel@goebel-consult.de \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).