Skip to content
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

Future of the nftnl-rs project #49

Closed
nightmared opened this issue Nov 28, 2021 · 1 comment
Closed

Future of the nftnl-rs project #49

nightmared opened this issue Nov 28, 2021 · 1 comment

Comments

@nightmared
Copy link

Disclaimer: please do not take this as a project advertisement, this is a genuine message to discuss the future of this project.
Please tell us if you feel this is harmful, as this is absolutely not the way we intended this message to be taken.

Considering the lack of recent activity in the repository (until a couple of weeks ago when a PR or two were merged), and the fact that one of us had started experimenting with a different (higher level but slightly less efficient resource-wise) API, we (@lafleurdeboum and myself) took the decision a few months ago to build upon nftnl-rs to create an easier to use libnftnl abstraction.
That library aims at providing a practical and idiomatic library to build firewalls or network filtering tools.

We named that fork rustables and licensed it under GPLv3, thanks to the rights granted by nftnl-rs' MIT license.
(As #42 was pointing out, users of this library were already bound to the GPLv2+ requirement of libnftnl, so choosing to use either nftnl-rs or rustables shouldn't have much practical impact on them).
We included your initial copyright notices in our source code as visible in the README and in the main lib.rs.
We did this without any ill intent toward the nftnl-rs project, and with a spirit of fairness, and we emphasize that we absolutely don't want to harm the project.
Please tell us if you feel that what we did (or the way we did it, without consulting with you earlier) was not OK.

Which brings us to the crux of the matter: the future of nftnl-rs.
If we may ask: how do you envision the future of the library?
Do you believe the library is currently near feature complete, or is there endeavors you would like to see the nftnl-rs project tackle?
Do you see nftnl-rs as a value to yourself or your company, or do you see it as a burden that you need to maintain for your software to work on Linux?
Depending on the answer to these questions, I see three main paths ahead for both libraries:

  1. you wish to maintain nftnl-rs as-is and consider it is mostly feature-complete for your needs
    -> having two projects with separate goals is probably the path forward
  2. you wish to maintain nftnl-rs as-is and do not consider it feature-complete
    -> maybe we could join forces on some aspects, and who knows, even merge the two projects?
  3. you do not wish to maintain nftnl-rs but need it for other software parts
    -> maybe you could help us by pointing users that seek a higher-level library towards the rustables project, e.g. by adding a link at the bottom of the README

In the even of cases 1/2, or if the new licensing doesn't fit your need, we are open to contributing back the merge requests we have currently open against the project, and thus double-licensing this part of our work, as a testimony of our gratefulness for your work.

We want to thank you again for creating and developing this project, and we would be grateful for any insight into your position about rustables or the current status of nftnl-rs.

@nightmared
Copy link
Author

Given that this issue has been open for over a year without a comment, I believe I can close this?

@nightmared nightmared closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant