From: ng0 <ng0@infotropique.org>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: project hosting
Date: Mon, 11 Sep 2017 13:47:18 +0000 [thread overview]
Message-ID: <20170911134718.zlx4rhvwarbqkokr@abyayala> (raw)
In-Reply-To: <CAJ98PDzTUoFBN25GPs7UdvKotHuwFRaijyLqr6zdBsD0+wVexw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Catonano transcribed 1.3K bytes:
> At the GHM I showed Rekado this
>
> https://git.fsfe.org/
>
> and he didn't know, although he does know the fsfe people, as they are
> German and based in Berlin
As far as I took from the fsfe public discussion when it was released,
it is for FSFE internal projects (supporting activities of the org,
and only for sustaining members). The important piece is "only for
sustaining members". You can try to question it again, but as far as
I remember the voted presentatives were clear on this, as opening it
up for the public would mean increased costs (cpu time, bandwidth)
and increased time spent with tech support.
This is just from my memory, I did not participate in the discussion
in fsfe.
> If Gitea has a viable issue tracker (if it has an email interface, that
> is), it could be a good alternative to debbugs
>
> These people are devoted to support Free Software projects, their
> organization name is free Software Foundation Europe
>
> They could very well host the Guix project and be a good fit, in my opinion.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://www.krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-11 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 12:47 project hosting Catonano
2017-09-11 13:47 ` ng0 [this message]
2017-09-11 14:50 ` Catonano
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=20170911134718.zlx4rhvwarbqkokr@abyayala \
--to=ng0@infotropique.org \
--cc=catonano@gmail.com \
--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 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.