From: "Antonin Décimo" <antonin.decimo@gmail.com>
To: "Juliusz Chroboczek" <jch@irif.fr>,
"Jeroen van Veen" <jvanveen@protonmail.com>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Docker config?
Date: Wed, 23 Dec 2020 14:49:06 +0100 [thread overview]
Message-ID: <C807O1UOTA8E.1LZKRFF5RUGVS@kobain> (raw)
In-Reply-To: <87y2ho1war.wl-jch@irif.fr>
> > * Move most documentation from the README to a Github wiki
> > (https://github.com/garage44/galene/wiki)
>
> I'm trying to avoid relying too much on third parties, and to keep
> as much as possible within Git. A git repository is easy to migrate
> if we decide to change providers, not so with a Github wifi
> [sic ;-)]. If people think that a Wiki is necessary, we could
> conceivably put one on galene.org.
I personally dislike GitHub wikis (I find them hard to browse), but
note that they’re itself git repositories. If edited from the web,
each change is commited with an optional message, using the GitHub
account. Provided the wiki has been created, it can be cloned with:
git clone git@github.com:jech/galene.wiki.git
> (Now if somebody were to design a usable issue tracker that allows easy
> migration, my happiness would be complete.)
If you haven't taken a look at it, maybe https://sourcehut.org/ would
better fit your needs.
-- Antonin
next prev parent reply other threads:[~2020-12-23 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 3:18 [Galene] " Jeroen van Veen
2020-12-23 13:33 ` [Galene] " Juliusz Chroboczek
2020-12-23 13:49 ` Antonin Décimo [this message]
2020-12-23 14:47 ` Juliusz Chroboczek
2020-12-23 15:14 ` Antonin Décimo
2020-12-24 14:25 ` Jeroen van Veen
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://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C807O1UOTA8E.1LZKRFF5RUGVS@kobain \
--to=antonin.decimo@gmail.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
--cc=jvanveen@protonmail.com \
/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