From: Alex Vong <alexvong1995@gmail.com>
To: Hartmut Goebel <h.goebel@goebel-consult.de>
Cc: guix-devel@gnu.org
Subject: Re: Feedback, ideas, discussion: tracking patches, discussions, bugs.
Date: Tue, 16 Aug 2016 22:06:19 +0800 [thread overview]
Message-ID: <874m6kbyg4.fsf@gmail.com> (raw)
In-Reply-To: <57B2BEDA.2020202@goebel-consult.de> (Hartmut Goebel's message of "Tue, 16 Aug 2016 09:20:58 +0200")
Hartmut Goebel <h.goebel@goebel-consult.de> writes:
> Am 15.08.2016 um 17:18 schrieb Alex Vong:
>
> Of course, there are other alternatives, such as gogs,
>
> The gogs.io website is using a lot of external content, namely from
> google and jquery. The FAQ is hosted a another external side, discus.
> Gogs is not even self-hosting gogs but hosted at github. gogs.io does
> not even state which license it has ("Open Source It all at guithub"),
>
I am a bit confused here, are we going to (1) host the code on our own
server, or (2) using code-hosting service provided by other
organization?
If we are doing (1), then it is up to us to meet the GNU ethical
repository criteria [0]. If we are doing (2), then we need to ensure
that our service provider meet the criteria [0].
What I suggested is doing (1) with gogs. Do I understand the situation
correctly? WDYT?
> So there would be at least some work to be done to fulfil the "B"
> criteria "Does not report visitors to other organizations"
>
> (I have to admit that I did not check this for gitlab, though.)
[0]: https://www.gnu.org/software/repo-criteria.en.html
next prev parent reply other threads:[~2016-08-16 14:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 10:46 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-13 11:11 ` David Craven
2016-08-13 11:23 ` ng0
2016-08-14 5:41 ` Pjotr Prins
2016-08-14 9:14 ` ng0
2016-08-15 1:39 ` David Craven
2016-08-15 4:55 ` Pjotr Prins
2016-08-15 9:11 ` David Craven
2016-08-16 13:17 ` Ricardo Wurmus
2016-08-16 13:29 ` Pjotr Prins
2016-08-15 11:53 ` Hartmut Goebel
2016-08-15 13:30 ` Danny Milosavljevic
2016-08-15 15:18 ` Alex Vong
2016-08-16 7:20 ` Hartmut Goebel
2016-08-16 14:06 ` Alex Vong [this message]
2016-08-18 11:47 ` Hartmut Goebel
2016-09-01 6:32 ` ng0
2016-09-01 11:19 ` ng0
2016-09-02 0:27 ` John Darrington
2016-09-02 0:58 ` ng0
2016-09-02 5:50 ` Alex Vong
2016-09-02 8:21 ` ng0
2016-09-02 10:54 ` Alex Vong
2016-09-03 16:44 ` Pjotr Prins
2016-09-03 16:55 ` David Craven
2016-09-03 19:19 ` Brendan Tildesley
2016-09-03 19:53 ` David Craven
2016-09-03 20:42 ` Efraim Flashner
2016-09-02 12:39 ` Tracking package submissions with Debbugs Ludovic Courtès
2016-09-02 14:29 ` Ricardo Wurmus
2016-09-03 0:35 ` Alex Vong
2016-09-03 13:47 ` Ludovic Courtès
2016-09-04 2:21 ` Alex Vong
2016-09-03 21:00 ` Efraim Flashner
2016-09-04 2:37 ` Alex Vong
2016-09-04 7:05 ` Andreas Enge
2016-09-04 16:57 ` ng0
2016-09-04 17:00 ` ng0
2016-09-04 17:09 ` David Craven
2016-09-05 12:52 ` Alex Kost
2016-09-05 20:22 ` Ludovic Courtès
2016-09-05 20:39 ` David Craven
2016-09-05 23:12 ` ng0
2016-09-07 20:38 ` Ludovic Courtès
2016-09-05 23:17 ` ng0
2016-09-05 23:54 ` David Craven
2016-09-06 0:01 ` Ben Woodcroft
2016-09-06 7:57 ` ng0
2016-09-06 11:26 ` David Craven
2016-09-06 1:24 ` Alex Vong
-- strict thread matches above, loose matches on Subject: below --
2016-08-16 8:37 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-16 9:01 ` David Craven
2016-08-13 10:18 ng0
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m6kbyg4.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=h.goebel@goebel-consult.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.