Hi Boudhayan and everyone else, On 01/12/2015, at 8:48 PM, Boudhayan Gupta wrote: > On 1 December 2015 at 10:40, Ian Wadham <iandw...@gmail.com> wrote: >> In my experience, the only way to solve the problems with KDE software, >> as implemented on Apple OS X, is to institute day-to-day co-operation >> between a small number of MacPorts and KDE developers, not "policies", >> patches, reviews and endless email threads. That small group should ask >> each other questions about their respective systems until there is a good >> understanding of how problems are arising and how they can best be solved. > > You must be completely unaware of one of the core tenets of the KDE > manifesto: common code ownership. All code in all KDE projects belongs > to all of us, and we all have an equal say in what happens to these > codebases. On technical decisions, we reserve comment because the > maintainer knows best. But on non-technical issues, we decide on > matters together as a community. Because as a community, we can think > better. More eyeballs, more brains. "Policies, patches, reviews and > endless email threads", as you put it, is how we've democratized > software development. If you want the governance to change to a style > where an elite few make decisions behind closed doors, it won't happen > in KDE.
See my reply to Luca, especially the last part. I am certainly NOT advocating "a style where an elite few make decisions behind closed doors". Please do not lecture me about the manifesto. I was practising its principles, as a KDE developer, for several years before it was written. > Let me make clear what my position on all of this is: > > If there are patches that make an application or a framework work well > on OSX or Windows, we'd like to welcome it with open arms, as long as > it doesn't significantly impact existing Linux/BSD code. But more > invasive patches (yes, I'll use that term because of all the words in > the English vocabulary, this one describes what I'm trying to convey > the best) - ones that touch build system code, session management, > system interface APIs etc - should be treated with caution. OSX and > Windows are two platforms where you shouldn't install systemwide > shared libraries and try to do window management, session management > etc, or even install your custom crash handler if it needs additional > privileges - and if you're trying to send patches that do any of that, > maintain them separately outside of upstream please. These are matters that need further study and recommendations, hence my suggestion of what I call a Working Party (see my reply to Luca). Cheers, Ian W. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
