Public SourceMage Discussion List

[Ismael Luceno <ismael.luceno AT gmail.com>]

On 04/Mar/2017 21:47, Vlad Glagolev wrote:
<...>
> Tech specs: Python, multi-processing, uses clean YAML config and
> 'requests' module to perform API calls against GitHub and Bitbucket.
<...>

First, let me comment on the software:

Why not have site-specific rewritting rules for the repo names and 
make it scan the root directory? that would save quite some config.

The project relationship can be stored in the gitdir, and the project
key for bitbucket can be deduced.

What do you think?


Now, about the mirrors:

Public mirrors are useless by themselves. If scm.sourcemage.org dies,
we stall, no matter how many mirrors.

Our Achilles heel is our reliance on git-receive-pack for
serialization, until we fix that there's no improvement.

Since we lack the manpower to do it manually, the only option is
to develop some lockstepping solution; only then the mirrors become
interchangeable.


<...>
> Mirroring part is quite important. We need to resolve our fallback
> consistency once and for all.

Indeed.

<...>
> Quick question: do we have any scripts responsible for auto-summon
> and hash-verification for all spells in the grimoire hanging
> somewhere? If yes, I'd like to revive them.

IIRC, no. Thomas had some script, and I prototyped a parsing engine in
AWK to process our grimoires faster:
http://git.iodev.co.uk/ismael/smgl/experiments/spell-parser.git/

While far from perfect, it does a pretty good job already. Could be
rewritten in C for more speed.


> The last, but not least: I'd like to introduce a new component for our
> project. For now I called it 'Wand', but if you want to replace it with
> something better -- I'd love to hear about your suggestions!
<...>

+1.

Suggestion: recovery system and procedures could be called arround
the topic of "necromancy" (since "resurrect" is already used), and
mirroring around "reflection".