First of all, thank you for your messages. Considering Pydio Cells “not finished” seems a bit unfair to me. Using Cells as a collaboration tool for sharing documents in an organisation is a perfect match, and in fact many of our open source users as well as paying customers are super happy with that. It’s waaay smoother and much more reliable than Pydio 8. I’ve been doing open source for years now, and I am used to the standard “this is not a working project” messages, whereas tons of people all around the world use it everyday in production . It may just not fit the needs at a given point.
Also, all the codes (server and desktop client) are on Github, and we’ve put great effort in updating the admin and developer docs for Cells on the website. There’s already a lot of material for starting digging and contributing. But I totally agree that we do have to put more effort in talking to the community and being more transparent on the roadmap. Looking at other open source projects, what I am thinking of is writing some “help wanted” tickets with very defined user stories and even prototypes to have people step in on a small feature without having to understand the whole platform. Publishing the roadmap is must-do as well. Any suggestions are very welcome on that topic.
Now, regarding the sync, moving the whole application away from PHP was driven (among other reasons) by the fact that we were not happy with the quality Pydio 8 and its sync. Connecting tons of sync clients to a cloud storage application drastically raises the load on the server and php was not good at that, at all. Not to speak of the fact that syncing shared workspaces could lead to users to do wrong manipulations and eventually break some data.
This rewrite project was, as any software project, bigger than we expected. And we want to be 100% sure of how the application is behaving under the hood before reconnecting the PydioSync client to it (typically not publishing something “unfinished”). Still, it is definitely in the short-term roadmap to make PydioSync work with Cells, but it may still take some time. I would say we need 4 to 6 months to make sure we publish something really reliable. But maybe a bit less or maybe a bit more, that the life of IT projects (thus the "we’re working on it answers…). We will probably try to add some inherent limitations to avoid problematic use cases, e.g. allow sync only on the “Personal Files” workspaces or only in a uni-directional manner for shared ones, to avoid having people complain because they erased something.
Finally, another subject we are looking at is providing a “virtual drive” tool instead of a pure sync, to see the files appear in your OS without necessarily downloading the whole data locally, and selectively sync them as needed. We feel it is an important trend nowadays, where people have small laptops and do not want to sync Teras of data locally.
Anyway, I’ll be happy to continue the discussion if you wish to, or to have you on-board as contributors.