sorry, it’s bad english from german. What I ment was week numbers.
On the left side (31 … 36) is was what I ment:
Thanks for the hint with the day and week numbers. That works. But for a quick overview I prefer the static view like above.
I found the sharing pane. But how about right’s? In other solutions there are mostly 3 types: public, confidential and private events and to that you can give different rights like see only, change everything, see only time and date or no rights. As example: I and my secretary can change my public events and all others can only see that I’m not available. My private events can only be changed by myself and the secetary can only see them and so on…(I found the privat checkbox, but nothing seems to change).
All excellent points. I appreciate the history of development and rationale for the existing structure.
In principle I am very much in favour of a web based interface. And if that is all that is required, Webtop is aces.
The issue that I face (both for myself and many other small business owners) is the need for a) our corporate email/calendar/contacts, b) multiple client email/calendar/contact access. This can be solved in one of two ways:
multiple tabs to multiple servers in a browser (then you must look at multiple tabs to coordinate events)
thick email client to all servers (showing calendar/contact/task overlaps etc)
Thunderbird is one such client. There are others as well. I use Thunderbird to access SOGo (which they state is their target audience), memotoo (using SOGo’s plugin), Exchange server (using DAVMAIL plugin) and a couple of others. I have one calendar page (for all calendars), one task page (for all servers) etc.
Truthfully, if that were possible in a web-interface (e.g. webtop), I would go there in a heartbeat. It would give me the total access from “anywhere” not just my laptop.
At the moment, @flatspin, there is just the possibility to share it rw or r only.
In any case, private events will always be shown as private.
WT5 has a more fine grained acl subsystem.
the main issue is that webtop is almost a closed project… in SF there are files dated 2011… using google there’s at least no results.
I know it was already discussed here, but…
moreover, webtop is java based (IIUC) and it isn’t a plus (regarding resources and debugging headaches)
I think that users needs mostly groupware features, so daemons to have mail (imap in primis), sharing addressbooks and calendars, sync with mobile devices…
in this perspective no web interface is needed, no webclient… everyone is free to use what he’s confortable with, were it TB, outlook or $whatever
finally, and please don’t get me wrong, we have no assurance of any kind about licensing changes in the future… sogo changed the access to their repos but it is still available (and the source code too)
we (all of us) saw many good things changing in the past:
zarafa, dropping outlook support and this made people angry
zentyal
other distros or just good pieces of code, becoming closed or available only paying
As agreed with Nethesis, sources will be pushed and available at github soon but only for WT5.
We’re looking forward for a stable beta before starting to release and push sources to the public.
We stopped pushing sources of WT4 in 2011 because we had no time for a community at that moment.
There is no reason to push them now: WT5 will be the new starting point.
In my previous posts I tried to clarify that we have received the input from the many of you (the need for full support for cal/card standards) and we’re working on wt5 for this.
Though we understand and will work to bring more compatibility to external softwares and devices, still I want to insist on the fact that Webtop is not only a groupware platform, so the specific features won’t be accessible there, but only on the web interface or specific device app we may decide to create.
Finally, and don’t get me wrong , Sogo is php based and, as stated by @filippo_carletti , suffered “crashes, failures to restart, high system load, missing functionalities and support from the developers”. I don’t see the point about java and resources/headaches : in our cloud we manage many instances of webtop in a multi-domain environment, all running inside a zone 24x7, and we’re never experiencing “crashes, failures to restart, high system load”.
Come on Steph that’s a bit unfair
NethServer is a community project, made by the community and for the community, supported by a company. Business helps to sustain development, I think that FOSS is much more effective if people are actually paid to work on the things.
Most of the decisions, discussions are taken here in community, and think that most of these guys can confirm it what I mean. We’re not perfect, we can fail, we have room for improvements.
Regarding, SOGo vs Webtop, I was a huge fan of SOGo (as I stated recently) but
many of our users asked us, several times, an outlook/exchange replacement,
SOGo has closed its rpms and we are forced to build and maintain packages by ourself
we can’t follow the outlook connector way, simply they don’t work and you have to pay for them.
WebTop seemed a great chance to achieved all of this, besides the fact that we have the opportunity to work close with Webtop Developers, as we’re doing the same with Nextcloud developers (news soon!)
Thanks to @gabriele_bulfon who has answered to all doubts and requests, giving a sneak peek at the webtop future.
I encountered this all from very close since I was one of those community members that tried to get the community from the ground. You probably refer to Ignacio Correas, the CEO of Zentyal.
I greatly disagreed with his vision to drop modules and leave them for the community to maintain. Since there were literally 0 (zero) community developers in the Zentyal community, it didn’t take rocketscience to predict that all those modules would get deprecated for good.
Learning from this all, NethServer shouldn’t fall into the same trap. And I do see a bright future ahead. Focusing on a solid community driven project the options are infinite. We will do our very best to get members motivated to contribute to NethForge repository.
I hope we get the knowledge in the community to add whatever Groupware application so you get to choose whatever you like best.
well, I re-quoted it because, IIUC, in NS7 sogo has been replaced (or, at least, it won’t be directly supported)
I was referring to the “upgrade/migration” path, which is interesting for people using NS6 with sogo (and maybe joined to an AD DC…) that will move to NS7…
I hope thuis doesnt quote your whole post, I mean to reply to the part where you ask what holds people back from using wt instead of a regular mail client.
Users. Users who are used to a certain setup, and resilliant to change, and in management positions. I had to be able to provide outlook support. Please don’t drop Sogo the upcoming releases … my keyusers won’t die that fast.
I do worry when technology companies drop any and all support to key technologies / software with little concern for their existing customers, especially if the software has been supported for a long duration of time.
Whilst I understand that some of these technologies have become ‘long in the tooth’ (and maybe not be supported any more by the original developers) and competing software may have improved, more modern features and improved user interfaces, my concern would be with end-users that are accustomed to said tech.
Dropping accomplished software may mean that the organisation (that has been using this software for a long duration) may now have to make a heavy investment in time and expense within retraining / reskilling their base users and support staff.
Also I do understand that there maybe a need to drop certain software due to new security concerns (then there should be some effort to examine and demonstrate / explain these security issues to the existing user base), but in the case of SoGo, there are no security issues that should be a threat.
Sure, introduce alternative software that could be used in-conjunction (or could be used to replace) with the existing tech and encourage the base users / organisations to make the transition to the new technologies but I think it would upset many existing users and give NS a negative reputation if it is decided to drop certain key end-user based applications.
What I ment was week numbers.
, Sogo is php based and, as stated by 
that’s a bit unfair
