> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Tuesday, August 04, 2020 5:28 AM
>
> [ On process, and (single branch) git for ground truth storage. ]
>
>> A Schemerepository page off of http://srfi.schemers.org/, which we
>> have much more control over,
>
> If the plan was to not require Arthur's involvement, we should go with
> registry.scheme.org. A web server is easy to arrange.

It's to avoid burdening him with day to day tasks.  If
GitHub/Microsoft betrays us and for example nukes all of
https://github.com/scheme-requests-for-implementation/srfi-common
he will perforce be involved in recovering from it as a one off.

>> can point to one or two canonical copies of the registry, and
>> almost effortlessly change if we get betrayed by GitHub or whomever
>> (certainly effortlessly compared to generally setting up on a new
>> hosting provider if we must move).
>
> Yes. Many Schemers are also in gitlab nowadays.

Not sure if running parallel hosting providers is worth the effort,
especially in my plan for discussion to happen in pull request
comments, to be scraped and archived in a single message batch to a
mailing list when the request is resolved.  But the current obvious
place to move if GitHub/Microsoft betrays us.

>>> - SRFI Git repos need to be archived anyway.
>>
>> I'm going to make my last call for using the rsync.net backup account
>> I created for SRFI artifacts, like these repos, and the mailing list
>> contents.  After October 1st when its year of initial funding
>> expires, I'm going to let it go poof or use it for my own purposes.
>
> Backing up there is fine.

Indeed, but people other than me have to start doing it.  Well, I
could set up an automated process for repos (see below, it provides
a git server), but it might make more sense to have it be part of
Arthur's the new draft workflow.

>>> - A dump of all SRFI data, "srfi.tgz" is published at
>>> <https://srfi.schemers.org/srfi.tgz>. The registry source files could be
>>> included in it.
>>
>> The only advantage this has it that there's already a process for
>> doing it, and the total compressed data for the repository should be
>> quite small by today's standards.  But presumably a parallel process
>> that does this as well as HTML generation could be created.
>
> Yes, e.g. a shell script that runs rsync :)

Turns out rsync.net also provides a git server!

https://blog.kozubik.com/john_kozubik/2010/02/git-and-subversion-support-at-rsyncnet.html

https://www.rsync.net/resources/howto/github.html

Raw storage is expensive compared to dumb object storage like AWS's
iconic S3, or Deep Glacier at 1 US$/TiB/month (!!!), but the use and
support of it is really attuned to people like us.  It's overall a
class act owned and run by one of us vs. a "suit", let alone VCs.

- Harold