As discussed in the past, a read only mirror of the Github repo could be
placed in the SVN repo.

A script running on Tino's server can listen on Github's webhooks, and when
a commit is detected, unlock, git pull, svn commit and finally lock the
relevant SVN folder.

If there's interest in taking this approach to ensure backwards
compatibility, I can try my hand at writing the script.

On Tue, Jul 28, 2015, 12:26 PM Francis Tyers <[email protected]> wrote:

> A 2015-07-28 22:15, Flammie Pirinen escrigué:
> > FWIW, I've taken the opportunity to finally migrate apertium-fin[1] and
> > apertium-fin-eng[2] to github, I expect to move rest of fin-* as I
> > touch
> > them the next time. As those who follow IRC may know, this is not only
> > a response to the downtime but also continued controversies[3]
> > involving
> > sourceforge, which I do not really want to associate any of my projects
> > and name with, and constant slowness, bugginess and unresponsiveness of
> > their SVN and other systems.
> >
>
> Sounds reasonable, probably a good idea to remove them from the SVN
> after
> you migrate them. But leave the ones you haven't worked on, e.g.
> fin-est,
> fin-sme, fin-udm, fin-myv, eus-fin, etc.
>
> We should perhaps consider running our own SVN repository, seeing as
> Tino
> already has a mirror.
>
> F.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Apertium-stuff mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
------------------------------------------------------------------------------
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to