Just to let you know, after the release of Zentyal 2.0, we are completely focused in bugfixing instead of adding new features. We will start working on new features once we have a rock-solid 2.0, which has no due date yet.
On the other hand, you need to understand that we are prioritizing the fixing of critical bugs that directly affect our current customers and partners. Any contribution in fixing other bugs is very welcome and it will help accelerating the stabilization of Zentyal.
It definitely makes sense and, as I wrote, I've no doubt you will succeed with such goal.
I will spend some more time trying to report more accurately issues I'm facing on platform I currently use (permanent errors reported for network module while applying updated, however network works. Errors reported for mailfilter module although it looks like it works to. Error with log module - I need to investigate further here...).
I will not be able to report any error with LDAP and Samba because I gave up with such service and will give a try again only after I will have better understanding on how master/slave works.
However, even with no slave installed, there is a lot of messages in logs related to it. It's not a bug - in term of feature - but could be avoided with configuration management storing whenever slave is deployed or not, and therefore triggering replication.
Same for missing indexes. This is not a bug, just annoying...
Yes, this can be changed by managing indexes. I could do that :-), changing configuration templates (stubs) but next update will erase my customization :-(
Definitely, aside some - quite few btw - real bugs, I've 2 main concerns preventing me to "invest" further on this platform:
- Zentyal is quite well designed for standalone deployment but not - for what I've experienced and understand - for multi boxes deployment. Sure one can deploy as many Zentyal servers as needed, in standalone mode, but when it comes to have service spread accross multiple boxes (like LDAP, DNS or mail) then it's much more difficult and doesn't work smoothly.
- change management: editing stubs permits to avoid customization when service restarts but does not permit to prevent this customization to be erased when update is published
I do realize that above statements fit better in the "new feature requests" than "bug fixing" area.
And do not misunderstand my point: Zentyal is really a nice piece of software: team and community working on it really deserve respect.
My point here above aims at pushing it a bit further in hwat I believe to be the right direction in order to reach platform suitable for the "M" of SMB.