Now that my world domination plans for migrating open-dis to the Maven build system are in place, I've set my sights on my next ambitious goal!
Is there any interest within the community to migrate open-dis source code from svn to git?
If there is I'd be happy to lend a hand. I've migrated a number of small and large projects to git before. They were all cvs projects mind you, but I have experience using the "git svn" bridge [1] so I expect it to be straight forward. I expect it would go smoothly and preserve all history.
My personal motivation is because a) I love git b) and I want to include open-dis source code as a submodule in one of my git projects. Obviously, without open-dis being a git project it makes that pretty difficult! (I could host a svn to git mirror like I did last time, but that's added maintenance I'd prefer to avoid).
Again, if there is interest, I see two options for the migration; stay on SourceForge and just migrate the repository to git or... drum roll... move to GitHub, where all the cool projects are these days. The former would be least disruptive. The later would expose the open-dis project to the many great features [2] of GitHub like pull-requests and issues.
Sounds wonderful. I've been using git a bit, and there's some javascript files at https://github.com/mcgredonps/open-dis for use with the node package manager.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If we were to host the source code on GitHub, one option would be to create an organization account for "Open DIS". This would act like an umbrella for the project so that you could have one or more code repositories under the organization. It may also make it easier to manage permissions for contributors if you wish to do so. And we'd get an organization website url e.g. http://open-dis.github.io
One hair brain idea I had would be to split up the single open-dis svn repository into multiple git repositories e.g. one per languages, one per app, etc. This may make your skin crawl, if so let me know and we can skip it. But it has it's advantages in the GitHub world. Doing this would encapsulate things like issues and pull requests with the language or app. So users of the java language wouldn't have to see things that affect the other languages for example. One possible disadvantage though (or maybe it's an advantage) would be that when you go to cut the next open-dis release e.g. 4.X, you'd have to tag each repository one at a time. I'm part of the asciidoctor organization on GitHub and this is how they've structured their projects, it's a fairly common pattern now.
So here's one way thought for how the Open-DIS Organization on GitHub might look in terms of repositories:
// git repositories for languages
open-dis-cpp.git
open-dis-csharp.git
open-dis-java.git
open-dis-javascript.git
open-dis-objective-c.git
open-dis-python.git
// git repositories for apps (i'd need some help naming these repositories)
open-dis-xplane
DisMapIpad
darkstar
... etc
// misc git repositories
open-dis-hla.git (<--- portico code dump, maybe we don't need to keep?)
// git repository for the website (has to be named like this to just-work)
open-dis.github.io
If you're not comfortable this idea that's fine too, we could ignore this whole step and just do a plain svn to git migration. Let me know what you think and if it's worth exploring further. I could start by creating the organization account.
Cheers
Last edit: Leif Gruenwoldt 2015-01-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Last year I moved my Open Source defence analysis tool from SVN (on Assembla) to Git (on GitHub). It worked really well, and all of the history transferred without any trouble: https://github.com/debrief/debrief
The organisation route also worked well.
I'd also recommend breaking Open-Dis down into separate language repos. Git stores the whole repo on each developer's machine - so there's no reason for a Java developer to have a local copy of all of the sources in the other languages.
Good luck with it :-)
Ian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
has there been any progress on the move to Git?
I can see that Leif has created a repo [1], and that Don has created the JS repo mentioned earlier [2].
I expect to spend the next couple of months adding DIS listener support to Debrief [3]. It would be great if there was a clear way to feed and fixes/mods/suggestions back into the trunk.
My repository was where I did the initial Maven work (I should remove that
repo to avoid confusion. )Don merged that work into the upstream repository
(the 5.x branch I believe).
I'll let Don answer about the status of the other open-dis repositories on
github. But if I had to guess these might be what you want:
Hi all,
has there been any progress on the move to Git?
I can see that Leif has created a repo [1], and that Don has created the
JS repo mentioned earlier [2].
I expect to spend the next couple of months adding DIS listener support to
Debrief [3]. It would be great if there was a clear way to feed and
fixes/mods/suggestions back into the trunk.
That’s on my list for this December, when I’ve got a bunch of use-or-lose
leave to burn. I’ve got a bunch of cleanup tasks
to do as well—take another run through the DIS 7 description to make
sure it lines up, fix a few bugs, look at some server-side area of
interest management for the web version, and a scalable cloud
architecture for web-based networking.
I’m at IITSEC, have about a week of work after that, and then I
can start dive into this.
Hi all,
has there been any progress on the move to Git?
I can see that Leif has created a repo [1], and that Don has created the JS repo mentioned earlier [2].
I expect to spend the next couple of months adding DIS listener support to Debrief [3]. It would be great if there was a clear way to feed and fixes/mods/suggestions back into the trunk.
Hello all,
Now that my world domination plans for migrating open-dis to the Maven build system are in place, I've set my sights on my next ambitious goal!
Is there any interest within the community to migrate open-dis source code from svn to git?
If there is I'd be happy to lend a hand. I've migrated a number of small and large projects to git before. They were all cvs projects mind you, but I have experience using the "git svn" bridge [1] so I expect it to be straight forward. I expect it would go smoothly and preserve all history.
My personal motivation is because a) I love git b) and I want to include open-dis source code as a submodule in one of my git projects. Obviously, without open-dis being a git project it makes that pretty difficult! (I could host a svn to git mirror like I did last time, but that's added maintenance I'd prefer to avoid).
Again, if there is interest, I see two options for the migration; stay on SourceForge and just migrate the repository to git or... drum roll... move to GitHub, where all the cool projects are these days. The former would be least disruptive. The later would expose the open-dis project to the many great features [2] of GitHub like pull-requests and issues.
So what does everyone (in particular Don) ?
Cheers
Sounds wonderful. I've been using git a bit, and there's some javascript files at https://github.com/mcgredonps/open-dis for use with the node package manager.
Fantastic.
If we were to host the source code on GitHub, one option would be to create an organization account for "Open DIS". This would act like an umbrella for the project so that you could have one or more code repositories under the organization. It may also make it easier to manage permissions for contributors if you wish to do so. And we'd get an organization website url e.g. http://open-dis.github.io
One hair brain idea I had would be to split up the single open-dis svn repository into multiple git repositories e.g. one per languages, one per app, etc. This may make your skin crawl, if so let me know and we can skip it. But it has it's advantages in the GitHub world. Doing this would encapsulate things like issues and pull requests with the language or app. So users of the java language wouldn't have to see things that affect the other languages for example. One possible disadvantage though (or maybe it's an advantage) would be that when you go to cut the next open-dis release e.g. 4.X, you'd have to tag each repository one at a time. I'm part of the asciidoctor organization on GitHub and this is how they've structured their projects, it's a fairly common pattern now.
So here's one way thought for how the Open-DIS Organization on GitHub might look in terms of repositories:
// git repositories for languages
// git repositories for apps (i'd need some help naming these repositories)
... etc
// misc git repositories
// git repository for the website (has to be named like this to just-work)
If you're not comfortable this idea that's fine too, we could ignore this whole step and just do a plain svn to git migration. Let me know what you think and if it's worth exploring further. I could start by creating the organization account.
Cheers
Last edit: Leif Gruenwoldt 2015-01-27
Great, let's go for it!
I fully recommend the GitHub pull-request system.
Last year I moved my Open Source defence analysis tool from SVN (on Assembla) to Git (on GitHub). It worked really well, and all of the history transferred without any trouble: https://github.com/debrief/debrief
The organisation route also worked well.
I'd also recommend breaking Open-Dis down into separate language repos. Git stores the whole repo on each developer's machine - so there's no reason for a Java developer to have a local copy of all of the sources in the other languages.
Good luck with it :-)
Ian
Hi all,
has there been any progress on the move to Git?
I can see that Leif has created a repo [1], and that Don has created the JS repo mentioned earlier [2].
I expect to spend the next couple of months adding DIS listener support to Debrief [3]. It would be great if there was a clear way to feed and fixes/mods/suggestions back into the trunk.
Cheers,
Ian
[1]. https://github.com/leif81/open-dis
[2]. https://github.com/mcgredonps/open-dis
[3]. https://github.com/debrief/debrief & http://www.debrief.info
Hi Ian,
My repository was where I did the initial Maven work (I should remove that
repo to avoid confusion. )Don merged that work into the upstream repository
(the 5.x branch I believe).
I'll let Don answer about the status of the other open-dis repositories on
github. But if I had to guess these might be what you want:
https://github.com/mcgredonps/open-dis-java
https://github.com/mcgredonps/open-dis-cpp
etc.
On Fri, Nov 27, 2015 at 7:49 AM Ian Mayo ianmayo@users.sf.net wrote:
That’s on my list for this December, when I’ve got a bunch of use-or-lose
leave to burn. I’ve got a bunch of cleanup tasks
to do as well—take another run through the DIS 7 description to make
sure it lines up, fix a few bugs, look at some server-side area of
interest management for the web version, and a scalable cloud
architecture for web-based networking.
I’m at IITSEC, have about a week of work after that, and then I
can start dive into this.
On Nov 27, 2015, at 4:49 AM,
Ian Mayo ianmayo@users.sf.netamp#105;amp#97;amp#110;amp#109;amp#97;amp#121;amp#111;amp#64;amp#117;amp#115;amp#101;amp#114;amp#115;amp#46;amp#115;amp#102;amp#46;amp#110;amp#101;amp#116; wrote:
Hi all,
has there been any progress on the move to Git?
I can see that Leif has created a repo [1], and that Don has created the JS repo mentioned earlier [2].
I expect to spend the next couple of months adding DIS listener support to Debrief [3]. It would be great if there was a clear way to feed and fixes/mods/suggestions back into the trunk.
Cheers,
Ian
[1]. https://github.com/leif81/open-dis
[2]. https://github.com/mcgredonps/open-dis
[3]. https://github.com/debrief/debrief & http://www.debrief.infohttp://www.debrief.info/
Githttps://sourceforge.net/p/open-dis/discussion/general/thread/d855ff5a/?limit=25#f294
Sent from sourceforge.nethttp://sourceforge.net because you indicated interest in https://sourceforge.net/p/open-dis/discussion/general/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/