Relicensing request

[tomhenderson]

Hello, I'm an ns-3 maintainer and wanted to explore making your code up to date and more broadly available to the ns-3 community. However, ns-3 is licensed as GPL-v2-only but this repo is licensed as GPLv3, which is incompatible. Will the authors (@npowell3, @nhpowell3) consent to providing this code with a GPLv2 license? Either adding a GPLv2 license (so that it is dual-licensed) or replacing the GPLv3 with a GPLv2 would work for ns-3.

[nhpowell3]

I'm fine with either way. What would you prefer? I haven't played with this code in a long time.

[tomhenderson]

I'm fine with either way. What would you prefer? I haven't played with this code in a long time.

Thank you for replying so fast. Actually, if you were just to agree to allow me to set up a separate repository that is updated to current ns-3 releases, and post the GPLv2 there, you don't have to touch your repo here. I would provide a back pointer in the documentation to this repo and note that you are the original author and you agreed to license it also under GPLv2.

I have a collaborator who recently worked on updating your BATMAN model to a recent version of ns-3 and I plan to apply that patch once the model is set up in a separate repo according to the current contributed module structure. But I want to make sure that we can then bundle it with future ns-3 before doing further work on your code.

[NelsonHPowell]

That is totally acceptable. I look forward to seeing the improvements. It's pretty exciting. The Aggregator probably needs additional work.

I also have some work with buzz66boy at https://github.com/buzz66boy/ns3-lxc that automates integration of LXC containers with ns-3 and a pseudo-object-oriented topology parser. I have recent updates I haven't pushed, but if you're interested, I can upload them. It's a fix to the code such that external software apps can link against a .so and override their system time functions so that they're sync'd with the ns-3 timeline to avoid time dilations.