[MEI-L] Github considerations

[Craig Sapp]

I would agree with Peter's points about git and decentralization.  This
feature of git makes any instability in a web host nearly moot.  The only
caveat is that issue tracking is done outside of the git repository, so you
could lose interesting secondary material if a particular service were to
shut down.

For example, I have a mirror of one of my code repositories in two
different github accounts:
     https://github.com/craigsapp/humextra
and
     https://github.com/humdrum-tools/humextra

These are identical repositories (not an original and a fork).  To update I
run these commands:

git push origin craigsapp
git push origin humdrum-tools

with these two origins set up in the git config file.  I disable issue
tracking in the second repository so that they remain all in one place.

This system should work well for Mei repositories.  The google code
repository would be converted to git (assuming that the issue tracker would
not be lost).  Then a duplicate copy of the repository would be placed on
GitHub (or bitbucket, etc.) with the only difference being that the issue
tracker would be disabled and a pointer given to google code if someone
wants to report bugs or ask for new features.

-=+Craig

On Friday, July 4, 2014, Peter Stadler <stadler at edirom.de> wrote:

> I’d say this is actually an argument in favor of Git(Hub) ;-)
> Google is known to remove or change (even successful) services at will, so
> to me it seems more save to move to a hoster who’s sole purpose is code
> repository management.
> That said, you can never be 100% sure relying on free (or even paid)
> services but moving to Git (not GitHub now) will make the whole setup more
> robust since every clone carries the complete history while svn working
> copies are dumb and can do almost nothing without a server connection (svn
> = centralized, git = decentralized).
>
> Best
> Peter
>
> Am 03.07.2014 um 15:35 schrieb Urs Liska <ul at openlilylib.org
> <javascript:;>>:
>
> > Joining the party late ...
> >
> > I am referring to this thread:
> > https://lists.uni-paderborn.de/pipermail/mei-l/2014/001244.html
> >
> > I don't know if there has been a decision in the meantime and how it
> turned out in the end, but I wanted to point to a intense discussion we had
> about moving LilyPond's source code to Github.
> >
> > While most people agree that Github's interface and collaborative
> possibilities are awesome (apart from a few people who actually prefer
> exchanging patches via email) it was pointed out that Github's Terms of
> Service are questionable when it comes to Free or Open Source software. In
> particular they reserve the right to close their free services or restrict
> access to projects or revoke contracts at will and at any time.
> >
> > Although I personally use Github very much I think these are issues that
> should be considered for a project of MEI's intent.
> >
> > Best regards
> > Urs Liska
> >
> > _______________________________________________
> > mei-l mailing list
> > mei-l at lists.uni-paderborn.de <javascript:;>
> > https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20140704/542f45f7/attachment.html>