first of all:
@alefattorini Thank you very much for sharing the video of the community meeting last saturday. Also a big thank you to every speaker there, you all held very informative and interesting talks!
The very first presentation on the future of Nethserver 8 by @robb made me think, especially the part on moving to a type of a… well „containerised Nethserver 8“ (please correct me if I got that wrong)
Moving towards more flexibilty as well as more recent versions but having less of headaches on dependencies sounds quite nice as the future of Nethserver. However, I was quite puzzled that to achive this the gateway as well as the IDS module might vanish completely - did I got this right @ambassadors_group ?
I fully understand that a containerised approach will not allow for a „gateway mode“ (at least in terms of security) as well as an IDS will cause (even more ) trouble in such an environment.
I also know, there are (very) specialised distribution explicitely focussing on being a (fully-fledged security aka UTM) gateway.
However, the beauty of being able to achive both, UTM gateway and e.g. a Mailserver, by simple deploying nethserver as needed is what I was searching for: Not having to deal with two (of more) different managing/templating/GUI systems. Although I obey the principle „one tool for one job“ for me nethserver is the toolbox I can fill with what I need to get the job done a la best-effort.
There are quite a few topics on current changes and decisions which have to be taken:
But unfortunately I was not able to find a promising answer in those topics, so finally here comes my question:
Might ist be desireable to have two „flavours“ of Nethserver 8, e.g. called „gateway“ and „standard“?
Or is this way too far away from what Nethserver is and will be (as well as wants to be) in the future?