-
Notifications
You must be signed in to change notification settings - Fork 938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anouncing n3n: A fork with improvements and no CLA required #1171
Comments
@hamishcoleman Said that you are free to do what you like, the CLA protects contributors and developers that the code that is incorporated in n2n is original, is not copied violating the original coder's license, and that it is patent-free so users should not be concerned when using it. If making a fork for circumventing all this means more freedom to you, I have a different opinion. |
I agree with you about keeping n2n alive rather than slowly dying, but n3n is a weird name. n2n is a very good name. Its meaning can be net to net or nat to nat. The branch can be renamed n2n-ng or n2n+? n2m:net to mesh |
I would like to announce the first stable release of n3n.
This is a fork with different licensing and the aim to remain protocol compatible with n2n.
Since neither of the maintainers of this n2n project have been happy to contribute under the new ntop Contributor License Agreement (CLA), it is unfortunately time to create a fork. See #1156 for some discussion about the license.
It is also important for n2n users to realise that the n2n project appears to be unmaintained - the ntop team have not made any ticket triage or code changes in over six months.
Major improvements since the fork from n2n:
The text was updated successfully, but these errors were encountered: