Moritz, we can use a Jenkins job to synchronize the repositories. Let’s discuss this off-list. I did not see the documentation on the GitHub repository, can we add this?
best regards, René. > On 27 jul. 2015, at 15:06, Moritz Hoffmann <[email protected]> wrote: > > Hi Gil, > I used git svn to fetch all revisions from svn and then push them to github. > It would be possible to integrate this with SVN triggers, but to my knowledge > we cannot do this in Sourceforge. At the moment, I do it manually whenever I > notice an update, but it could be automated using a cron job for example. > Using the mirror process only partly mitigates the SF problem. It does not > allow two-way synchronization between Git and SVN (while possible in theory > it is quite an effort to maintain). > > Git has a different structure for repositories than SVN. In SVN you share > something like a file system tree, and a sandbox/fork/release/tag are just > copies of the whole tree, but not SVN objects. Git changes this by turning > branches and tags into first-class citizens. Instead of having a sandbox in > the ooRexx tree, everyone could just fork ooRexx, work on it, merge upstream > changes and provide patches for the main tree. It is a much cleaner approach > to handling sandboxes than what we have right now. Everyone can create his or > her own fork and once it is in a good shape, offer to merge changes back into > the main tree. > > Other projects could be housed as individual repositories under the umbrella > of the ooRexx team. > > I noticed that there is a RexxLA user on Github, which maintains netrexx > repositories. The problem here: It's a user and not a team, so we cannot > possibly use it to contain the ooRexx repository. (Users are only meant for > one user and cannot share repositories, team repositories can be accessed by > multiple users) > > Best, > Moritz > > > On Mon, Jul 27, 2015 at 2:56 PM Gil Barmwater <[email protected] > <mailto:[email protected]>> wrote: > Thanks Moritz! And thanks for your initiative in putting a copy on github > initially. It was our only access to the source while SF was down. > > The RexxLA Board has been discussing what our plan for going forward should > be and, hopefully, there will be a decision very shortly. > > As my knowledge of github is effectively non-existent, please help me > understand the process you use to do the update. Is it something like a SVN > checkout and then some sort of a "merge" on github? Is this a manual > process or is/could it be triggered by a SVN commit? And I believe only the > main ooRexx tree is currently on github, not any of the sandboxes or other > (sub)projects, correct? A better understanding of the "mirror" process will > help the Board to decide how to proceed going forward. > > Thanks once again for your efforts! > > Gil B. > > > On 7/27/2015 4:20 AM, Moritz Hoffmann wrote: >> I updated the official copy on github: https://github.com/ooRexx/ooRexx >> <https://github.com/ooRexx/ooRexx> >> >> What about a plan to escape the sourceforge chaos? >> Cheers, >> Moritz >> >> On Sun, Jul 26, 2015 at 12:33 PM René Jansen <[email protected] >> <mailto:[email protected]>> wrote: >> As the build machine indicates, already 7 hours ago the svn was up again. >> >> Let’s implement our plan to get all history from it and have a safe copy on >> github. >> >> best regards, >> >> René. >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Oorexx-devel mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Oorexx-devel mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> > >> -- >> Gil Barmwater > ------------------------------------------------------------------------------ > _______________________________________________ > Oorexx-devel mailing list > [email protected] <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > ------------------------------------------------------------------------------ > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
