Hi, Regarding quality, between not doing anything and trying our best, there's a lot of possibilities. I also think that assuming we have good intentions can help too.
I see the policy as tagging the releases with our sign, and our names. Taking some kind of responsibility (not as in law). The sign is Calligra, that's all. Features back-ported with separation of the development process make _different_ software that would IMHO be better not called Calligra version x.y. Users and distributors have all the freedoms assumed, but giving the freedom (in worst case) of pretending that any patched Calligra software is still Calligra would be as big abuse as giving the freedom of forking Deban/OpenSUSE/Fedora and still calling the fork Deban/OpenSUSE/Fedora. From my perspective there's also matter of complexity. Most KDE apps, or even not KDE ones, use typically rather simple document formats. Office apps have formats defined by many thousands pages of specification, and huge set of inter-dependencies. Silent patching can add extra risk here. To paraphrase someone very smart, we can release features ASAP but not sooner... Lastly, to be clear, I cannot imagine living without cooperation with distributors of course. They do a great job. IMHO. -- regards / pozdrawiam, Jaroslaw Staniek http://www.linkedin.com/in/jstaniek Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) KDE Software Development Platform on MS Windows (windows.kde.org) _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
