May I iron some kinks here?
Cloud for NethServer8 is… wrong. Simply wrong.
Because if any adopter is wishing to use NS8 also outside from the network, in a public accessible space needs to buy hosting or housing if it’s wishing to be picking on hardware. Just like NS7.
Please Alessio, cloud is a incorrect word as environment because any sysadmin can know exactly where the metal (virtual or physical do not matter) is and who’s mantaining it. That’s what the company is paying for.
Ball is in Nethesis court, Alessio. As community manager you can collect the feelings of the adopter, refine that and polish, then forward to the developers who are not here to feel the vibe. The structure of NS8 has been decided from development team, a lot of feedbacks and critics/doubts/analysis came here, but the ship had already left the pier.
Now IMVHO two things could be done (not mutually exclusive)
- listen to the critics. This do not automatically mean that project must steer for every doubt and dissatisfactory feedback, but if any detailed complain is dismissed as “it’s not like that”… the feedback will be harsher and less understanding
- go for the route that Nethesis and Nethesis customers set. Consider that if not pleasant or fit enough for the adopters, the open source/access version of NethServer could lose a lot of the traction
For the Ivory tower… Alessio it’s quite tough evaluation, and you can feel that unfair. However someone felt like it, when decisions are taken while feedback has been provided. It’s not the same size, height, sturdiness of IBM/RH. However… someone felt like that.
For anyone unsatisfied about the current status of the project:
- It’s no eSmith/SMEserver/Shorewall anymore. Deal with it.
It’s sad, I would love to have both roles like NS7 but now it’s not. - Project is not in final state
I stopped considering NS as viable platform several months ago, because the project is different and both roles (firewall and server) currently are note satisfactory to me. I was not comfortable starting on both roles for new projects because of the short support time for NS7 and not mature enough status of NS8.
This will be still unsatisfactory to me when final? I don’t know, yet. However I won’t go full NS8 at release date, not willing to be a beta tester for at least 6 months. Probably “beta tester” will feel bitter for developers, however the paradigm shift from Module/service to Module/containter is not a version upgrade, is a new product. It’s understandable that will take more time to rewire, solve, fix issues and missing pieces.
Last but not least: if file server will be a module granular recover for single file is mandatory. And not only for file server module. Otherwise, if the developers cannot provide the right interface, drop the module and take the blame for not providing a upgrade path.