|
From: Juha T. <Juh...@ik...> - 2010-03-13 14:15:42
|
On Fri, 12 Mar 2010, Chris Frey wrote: > Well, on the other hand, 0.22 has already shipped, and is in use already. > Until something better comes along, it's the defacto standard in the > opensync world. 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. >> Apparently there is a strong will focus to that irrelvant, and it's >> doing well atm. > > Not sure I understand what you mean by this. 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. If you do actions that either prevent that ecosystem to exist in the first place or split it half - where other half has testers and users and other only developers, neither one is a healthy ecosystem nor work as expected and required. We need to get all hands into developmenet branch. Having something easy available in 0.2x branch drags focus there and the HEAD suffers from lack of activity. That's what i explained a year or more ago, suggested that we kill the whole 0.2x officially and recommend distros to drop it. It didn't happen nor did the 0.40 release. I see connection between these two, others don't. Someone may say that I'm wrong, but if the project has failed its own goals and mailstones, something is wrong and things are not working as planned. If I'm wrong, you probably have better explanation for that failure. I'd like to hear it. Br, Tuju -- You want to throw out the baby with the bathwater! - K. Kofler Your baby is my bathwater. I don't want the OS you're building. - J. Keating |