|
From: Chris F. <cd...@fo...> - 2010-03-16 03:44:42
|
On Sat, Mar 13, 2010 at 04:15:32PM +0200, Juha Tuomala wrote: > In the reality where i live and lot of othres, it never succeeded > from slow sync. That means tons of duplicated entries and mess that > renders it useless. If my reality would be very different from rest > of the world, we would have userspace of millions of people. We > don't. [...] > In order to develop opensource software, you need a community > ecosystem that supports that development work. Developers, testers, > occasional bug fixers and end users each need each other. Before you can have a community, you need one dedicated developer. Unfortunately, nobody has any dedicated time for opensync, that I know of. It doesn't matter if 0.22 is out there or not. If 0.39 was better, people would be using it. You mention slow sync problems in 0.22. Are all your problems solved in 0.39? If the user can avoid the slow sync, or if the user always knows that one side will be authoritative, 0.22 does work. It's not convenient, but it can be wrestled and scripted into submission. But you can't script a lack of plugins into submission. I'd like to see 0.40 released even now, even if it is incomplete. I outlined what I thought was necessary before. Mostly, it just needs API changes loudly published. If worrying about the API hinders development, it's better to throw API stability out for now. There is no need to kill 0.22 to make 0.40 succeed. There are no developers on 0.22 or 0.40 right now. And my talking about it isn't getting any code written either. I think that if neither 0.22 nor 0.40 are available to the end user on Debian, opensync might not even be considered when looking for syncing solutions. Removing your last foot from the dock before you're in the boat just puts you in the water. :-) - Chris |