Year: 2015

I believe that in today’s world where more an more of our daily life depends on technology it is crucial that people have control over that technology. You should be empowered to know what your technology does and you should be empowered to influence it. This is at the core of Free Software. Unfortunately it is not at the core of most of the technology people interact with every day – quite the opposite – walled gardens and locks wherever you look with few exceptions. KDE is working hard to provide you with technology that you control every single day so you are empowered and the one ultimately in charge of your technology, data and life – the basis for freedom for many today. This is written down in the first sentence of our manifesto: “We are a community of technologists, designers, writers and advocates who work to ensure freedom for all people through our software.”

Therefor I am proud to announce that KDE (through KDE e.V.) is one of the launch partners and thereby initial signatories of the User Data Manifesto 2.0. The User Data Manifesto defines basic rights for people to control their own data in the internet age:

• Control over user data access
• Knowledge of how the data is stored
• Freedom to choose a platform

Do you want to join us in providing more people with more access to Free technology? Today is a good day!

Last year I went to Akademy with two notebooks and sharpies and asked people to draw or write about one thing they think would make KDE better. This year I did the same again. The question was: “What’s the one thing KDE should do to have more impact?” Here are some of the great results:

The complete set is in this Flickr album. Check it out! What’s your favorite? What’s your one thing – big or small – that would help KDE have more impact?

One of the outcomes of the survey we did for Evolving KDE was that we need to get more clarity on our vision, strategy and focus. At Akademy we had many discussions to explore more how we all see this topic. We discussed what different contributors think KDE’s vision and focus should be. We tried to clarify what it actually means for KDE to have a vision, strategy and focus. And we talked about ways to get to a vision that would work for KDE.

Here’s a visualization of how I see the different parts fitting together:

Some time ago we created KDE’s manifesto. It answers the question “Who are we?”. What we need to work out now is our vision. It will answer the questions “What do we aspire to do?”. Different teams inside KDE can then in addition find their own local vision which can overlap more or less with the global one. The manifesto and the vision together will give us a framework in which we can develop our strategy. The strategy gives us the answer to the question how we want to go about achieving our vision. From the strategy we can derive a number of concrete actions that will get us closer to where we want to be.

The goal of all this is to give us clarity on who we are, what we do, why we do it and what everyone’s part in the big picture is.

Over the next weeks we will summarize the different ideas and thoughts concerning the vision that were brought up at Akademy and open it up for wider input and discussion. We will also hold another office hour on IRC. Depending on how all this goes we will have a sprint to work on it more.

As part of Evolving KDE we have done a survey to get a better understanding of where we are, where we want to go and how we get there. I published a summary of the responses. Based on this I recommend a number of actions:

1. Develop our vision, strategy and focus
2. Review all initiatives and products and evaluate which we should concentrate our focus on
3. Improve recruiting and on-boarding processes and documentation
4. Simplify and clarify our main web-presence
5. Develop ideas and processes for how to make better use of our social media presence, dot and other outreach venues

The first point – develop our vision, strategy and focus – is crucial in order for KDE to move forward. When KDE started our goal was very clear: create a desktop environment and applications for end-users on Linux. But both KDE and the world around us has changed considerably since 1996. KDE has moved from being software to being a community. The world has rapidly moved towards more technology platforms (mobile, web, internet of things, …). In this transition we partially lost a shared vision that we can build a strategy on and that helps us focus our efforts. Without a clear and articulated vision we lack a frame of reference to make decisions in which makes taking these decisions considerably more difficult and sometimes painful. We need to change this and get back a shared vision so we have clarity, can focus our efforts and truly bring free and open technology to our users. We live in a time where free and open technology is crucial for everyone. We can only provide this if we have vision, strategy and focus for the work we do.

Once we have this shared vision and strategy we can have a look at the initiatives and products we have and decide which ones we should put more effort into and where our focus should be. This doesn’t mean that we will stop the rest. But it will guide our work, resources and communication. We get to say “More of this!” to the things that are important to us.

With more clarity gained through the first two steps we can then go and tackle the remaining three points. We will improve our recruiting and on-boarding processes and documentation. We need to analyze where and why people are struggling to get on board and then remove or lower these barriers together. We will simplify and clarify our main web-presence to match our vision, strategy and focus. And we will develop ideas and processes to make better use of all our communication media (social media, dot, etc).

Over the next days I will publish the next steps for finding our shared vision, strategy and focus as well as some clarification of what exactly I mean with these.

In April we started Evolving KDE. The goal of Evolving KDE is to take an honest look at ourselves and evaluate where we are and where we want to go. Based on the answers to these questions we can then figure out how to get us there. The result should bring clarity on a number of questions: What do we do, why do we do it and what is everyone’s role in it? We started with a survey for existing users and contributors to figure out how we all see KDE collectively. We have received 202 responses to the survey and gone through all of them. 92 of the respondends identified themselves as users and 91 as active contributors. (The rest specified “other”.) Most of the active contributors are involved casually or intermittent and are involved for 5 or more years. More than half of the survey responses came from Europe. The results (which were already sent to the KDE Community mailing list before Akademy) can be summarized as follows:

What motivates you and makes you happy when contributing within the KDE community?

The responses indicate that most people are motivated by being in a great community. After that the technology is mentioned. Runner ups include: the potential impact one’s contributions can have, identifying with the ideology of the project, scratching one’s own itch and the potential for learning by contributing.

What do you appreciate in the KDE Community?

Survey responses here almost uniformly focused on the friendliness of the KDE Community. Openness was mentioned second-most. People also appreciate that it is easy for them to get support from others inside the community. Runners ups include: technical excellence, diversity and the products we produce.

What holds you back in your involvement with the KDE community?

The most mentioned theme here was time and energy. Among users then came the lack of skills as well as clear tutorials and help pages that give a clear entry point to contributing. There seems to still be deeply-held belief that unless one is a programmer it is not possible to contribute to KDE. Among the existing contributors the most mentioned points were then: a lack of vision and focus, lacking documentation and other help, in-group behaviour as well as a lack of skills.

What are your ideas to improve the KDE community?

Users very clearly demanded better documentation and entry points for newcomers here. After that came focusing on quality, more user-centered development and more outreach. Existing contributors mentioned about equally focus (but opinions differed in what to focus on), improved outreach activities and better documentation for getting involved. Then came a more active role of KDE e.V., outreach to specific groups (women, countries, etc), being more welcoming to commercial contributors and taking a more active role inside the Qt ecosystem.

Imagine yourself as a happy member of the KDE community in 5 years, what does KDE look like?

The answers here focused a lot on bringing KDE’s software to more devices and the cloud and convergence – possibly by being a distributor directly to the end-user. Then came the focus on creating truly excellent free software that is better than any other – not just other free software. Continuing to be friendly and open was another major theme. Overall people expect KDE to be well known, its software used everywhere and still defending the freedom of our users – both by providing them with great free software and doing advocacy. We should be concentrating less on ourselves and more on the big ecosystem we are a part of and work together with other entities in it more closely. Respondents were also in favor of slightly more involvement by companies. Contributors have a clear desire for a vision and strategy. It seems it does not matter too much which vision and strategy it is as long as we have one.

Over the next days I will publish the recommendations based on these findings and thoughts about the next steps.