Richard Fontana wrote at 07:31 (PDT) on Wednesday:
Since the gitoriousocalypse the de facto centralized source
repository
for copyleft-next has been [on]
github.com .... I am going to attempt
to treat the [
github.com/copyleft-next] repository as the
authoritative source repository.
I suppose I was the primary resistance in this project against GitHub,
and I haven't been on top of resisting enough apparently. :)
I wrote on 2015-04-02:
> I'm close to having Kallithea working on
copyleft.org, so
I'm willing
> to handle Kallithea for copyleft-next.
I forgot to mention months ago copyleft.org's Kallithea is now, so if
you want a repository on
k.copyleft.org for copyleft-next, I can set it
up as the canonical one for
copyleft.org. My only concern about that is
that FSF and Conservancy co-sponsor
copyleft.org, so we should spend
some effort to make it abundantly clear that copyleft-next isn't
endorsed by the sponsors of the main
copyleft.org project.
> The only hard part I've found has been getting data out of
Gitorious.
> If you don't mind losing it all, it's probably easy to switch to
> Kallithea.
I installed git-hub (
https://packages.debian.org/stretch/git-hub )
today and it seems to have features to access most of GitHub features
using Free Software, so it may be true that the full workflow can be
done without using the proprietary Javascript on their site, but....
I suppose I will spare the speech about repeating the past. Don't you
want a service you can control?
On a related note, I've been experimenting a bit with Docker
containers for certain free software source code hosting systems such
as Kallithea, with some hopeful results.
That solution would work too, no?
--
-- bkuhn
========================================================================
Become a Conservancy Supporter today:
https://sfconservancy.org/supporter