From: Alex Vong <alexvong1995@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org, Hartmut Goebel <h.goebel@goebel-consult.de>
Subject: Re: Feedback, ideas, discussion: tracking patches, discussions, bugs.
Date: Mon, 15 Aug 2016 23:18:47 +0800 [thread overview]
Message-ID: <87h9am5aco.fsf@gmail.com> (raw)
In-Reply-To: <20160815153059.7c8201e6@scratchpost.org> (Danny Milosavljevic's message of "Mon, 15 Aug 2016 15:30:59 +0200")
Hi guixers,
Actually, We have GNU Ethical Repository Criteria Evaluations
<https://www.gnu.org/software/repo-criteria-evaluation.html>, which was
published recently (about 1 yr ago).
Below is my understanding of the evaluations:
The essence of the criteria
<https://www.gnu.org/software/repo-criteria.html> is that, web service
is different from software, we (as users) cannot modify the software on
other's server. So, it is not about free or non-free. Rather, it is
about other ethical issues, e.g. privacy, accept users from all
countries...
Danny Milosavljevic <dannym@scratchpost.org> writes:
> On Mon, 15 Aug 2016 13:53:49 +0200
> Hartmut Goebel <h.goebel@goebel-consult.de> wrote:
>
>> A good alternative could be to use gitlab, which one could host on one's
>> own systems. It is "only" MIT licensed, but at least "open source" - in
>> contrast to github, which is propritary.
>
> I second the gitlab recommendation. I have multiple servers that use
> gitlab and it's very nice. It supports merge requests, continuous
> integration buiulds etc.
Agree, if we were to host it on our own server, then we simply need to
follow the criteria and be done with it. Of course, there are other
alternatives, such as gogs, which is used by `notabug.org'.
Cheers,
Alex
next prev parent reply other threads:[~2016-08-15 15:19 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 [this message]
2016-08-16 7:20 ` Hartmut Goebel
2016-08-16 14:06 ` Alex Vong
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
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=87h9am5aco.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=dannym@scratchpost.org \
--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 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).