Where KDE is going – Part 2
This is the second half of the ‘where KDE is going’ write-up. Last week, I discussed what is happening with KDE’s technologies: Platform is turning modular in Frameworks, Plasma is moving to new technologies and the Applications change their release schedule. In this post, I will discuss the social and organizational aspects: our governance.
You can’t talk about KDE and governance without bringing up KDE e.V. (eingetragener Verein or, in English, registered association). This Germany-based non-profit is the legal organization behind the KDE community, and it plays several important roles.
Initially set up to handle funding for KDE’s conferences, the e.V. still has the organization of events as a major task. But that is no longer limited to the yearly Akademy conference. There are now events all over the world, from Camp KDE and Lakademy in the Americas to conf.kde.in in India. In addition, many Developer Sprints, usually with about 5-15 people, are supported, as are the annual Randa Meetings which can attract 40-60 developers.
KDE e.V. also provides legal services, pays for infrastructure and takes care of our trademarks. The KDE Free Qt Foundation is equally represented by KDE and Digia. The Foundation was set up between the former Trolltech and KDE to maintain Qt’s open status, and has been continued with Nokia and Digia, the successive holders of the Qt trademark. KDE e.V. is not the guardian of technical decisions, however. This is up to the natural community development processes.
But KDE e.V. does act as an agent of change. It provides a place where core KDE contributors come together and discuss a wide variety of subjects.
In the last 8 years or so, KDE e.V. has been the major driver behind increasing the number of developer sprints and has created the Fiduciary Licensing Agreement which allows it to re-license KDE code when needed, while protecting developers’ interests. The Code of Conduct originated with KDE e.V., as did our Community Working Group which helps deal with communication issues in the community.
A recent example of our ongoing improvement efforts is the KDE Manifesto. This has been for a very long time coming but Kévin Ottens got it to the finish line.
The Manifesto explicitly defines our community: our values and our commitments to each other. The importance of this can hardly be overstated – knowing who you are and what you want helps you make decisions but also shows others what you are about. The Manifesto made plain what was involved in being part of the KDE Community, including the benefits and the ways we operate.
Joining the KDE community
Since the Manifesto was written, several projects have joined KDE or begun the process of doing so:
It is clear that these projects contribute to the growing diversity in the KDE community. The many projects joining us has prompted some refinement of the KDE Incubator, an effort to document the process of becoming part of the KDE community (also started by Kévin, who probably felt sorry for the fallout of his manifesto creating so much extra work ;-)).
Other projects have moved on, or emerged from the KDE community and have become independent communities. Examples are Necessitas (provides Qt-on-Android) and Ministro (installer for libraries on Android) but also the well-known ownCloud project which was announced at Camp KDE 2010 in San Diego and still has many KDE folks involved in it.
KDE has grown – and so has Qt (pronounced ‘cute’). The Qt ecosystem today is very big – it is estimated that there are half a million Qt developers world wide! And not only has Qt usage grown, but so has the ecosystem around it, with more and more contributions from more and more companies, communities and individuals. Including KDE.
KDE has always been close to the Qt community, with many KDE developers working for former Trolltech, now Digia, or in one of the companies providing Qt consulting. KDE played a major role in establishing the KDE Free Qt Foundation, and KDE people were critical to the process of creating Open Governance within the Qt Project in 2011. In 2013, the Qt Contributor Summit was co-located with Akademy, and as discussed in the previous article, KDE is contributing a lot of code to Qt and building closer bonds with the Qt ecosystem through our Frameworks 5 efforts.
Based on the above, one could extrapolate. More projects will join the KDE Community, and KDE will become more diverse. KDE is also working on formalizing the relationships with external entities through a community partnership program. This will allow KDE e.V. to work closer with other communities in legal and financial matters and share KDE’s strengths with them. With these changes, the community shows a desire to expand its scope.
Another area where change might take place is in the financial area. KDE e.V. does not have the mandate to define technical directions. To sponsor a developer, the Krita team set up the Dutch Krita Foundation to handle the funds. Currently, Krita, Free Software’s most successful and powerful drawing application, is running a Kickstarter campaign to obtain funding for several developers with the aim of bringing the upcoming Krita 2.9 release to a new level. In other cases, external organizations supported developers working on KDE code, like Kolabsys supporting several developers on the KDE PIM suite (like Christian), and of course the various Linux Distributions (like Red Hat) which have made massive improvements to KDE possible over the years.
Paid development is a complicated topic, as most KDE contributors volunteer their time. Money can be damaging to such intrinsic motivation. At the same time, some tasks are just no fun – paid developers can perhaps help. Some people in the community feel that KDE e.V. (or perhaps another organization?) could play a more active role in raising funds for certain projects, for example. The Randa Meetings fundraiser 2 years ago might be a sign of things to come, and again we’ve started a fundraiser to make Randa 2014 as successful as the earlier meetings: Please support it!
There may be more sustaining membership programs such as ‘Join the Game’ in the future, and suggestions, ideas and practical help in obtaining and using funds for KDE development are very much welcome.
Not all change
But in all this change, it is crucial that the KDE community preserves what makes it work well. KDE has gotten where it is today by the culture and practices of today (see some of my thoughts on this). Like in any community, these are hidden rules that allow KDE to pool the knowledge of so many brilliant people, and without too much politics, to make the best decisions possible. The KDE culture, so to say. This includes well known Free Software soft rules like Who Codes, Decides, RTFM, Talk is Cheap and Just Do It but also very ‘KDE’ rules like Assume Good Intentions and Respect the Elders. And just like in the French Liberté, Egalité, Fraternité, the rules are inseparable and interdependent. They are what makes KDE such an amazing place, full of creativity, innovation and fun.
Of course, in other areas, it can hamper progress or block people from making changes as quickly as they like. All culture has good and bad aspects, and we should stay flexible to adapt to changes and fix shortcomings. This is a slow process, often counted in years, rather than months – putting off some people who wish things went a little faster. But change happens.
Change to keep things healthy
The KDE Community Working Group is an institution with the goal of preserving positive aspects of our culture. The CWG consists of a group of trusted community members dealing with conflicts and social issues. It has been around since 2008 and has recently been given the ability to deal with ‘stormy day’ scenarios – they will now handle situations where somebody is persistently behaving contrary to the culture. Luckily such situations are extremely rare but it is good to have a process in place to deal with them.
The kde-community mailing list has moved many discussions into an open forum that used to be limited to KDE e.V. members. Opening up our internal discussions is more inclusive; it preserves the open nature of our project in the face of growth and change.
Putting these changes together, a pattern starts to emerge:
I think KDE is going meta.
KDE is becoming a meta organization. Perhaps you can call it an Eclipse for GUI or end user software, bringing a wide variety of projects together under one umbrella. The challenge for the KDE community is to guide these changes, keep good practices and develop new ones that fit the new world!
KDE is becoming a umbrella-community, a community of communities. A place where people with a huge variety of interests and ideas come together, sharing a common vision about the world. Not a technical vision, mind you, but a vision about HOW to do things. Shared values are what brings us together. And with KDE going meta, there is more room for everybody!
These articles are based on a talk given at conf.kde.in by Jos Poortvliet with lots of input from KDE contributors. A more extensive version of these articles, quoting members of the KDE community for more background, can be found in the upcoming September issue of Linux Voice magazine, ‘the magazine that gives back to the Free Software community’
Comments are closed.