openSUSE 2016: taking a picture of openSUSE today

As some of you know, the openSUSE Team at SUSE is publishing a series of proposals to the openSUSE community in several key areas of the project. The first of those mails tried to provide a general picture of the project based, among other sources, on the data mining done during these past few months. 

Many of you do not follow the project closely or you do but are not subscribed to openSUSE mailing lists. I would like you to read the below article/mail and share your thoughts.

I believe that sharing a common understanding of the current strengths and weaknesses of the openSUSE project is helpful in order to agree on the steps to be taken in the near future and evaluating them. But above all, agreeing in an initial picture, even if not in the details, is relevant to have a chance to agree in the direction the project might take in the future.

Before reading the text of that first mail, posted below, there are three remarks to be made:

1. I think some people from the openSUSE community has perceived this first mail as a negative criticism to the project and their contributors. Cold analysis based on numbers do not provide a complete picture of the project... but provides a good one, in my opinion. I wrote the below mail/article thinking about a better future, not to revisit a past I am part of. 
2. A summary of the proposals was published in an openSUSE Team blog post. Please read it to get in context. As stated in that article, this first mail/article has as goal to share the motivations behind the later published proposals, trying to open a discussion about our current state that can lead us to agree on a picture we can use as starting point.
3. At the end of the article/mail, I proposed some questions. If you are interested in answering them (I would appreciate it), please:

• Subscribe to the openSUSE-project mailing list. Check how to do it first. 
• Make your comments as a reply of this thread.

Otherwise, in order to keep the debate centralized (for record purposes also), I will post/summarize your answers and comments also in that mailing list.

----------
 

openSUSE 2016: taking a picture of openSUSE today

Once openSUSE 13.1 has been released, it is time for the openSUSE Team to focus on the future. We want to share some ideas we have about the project in general and factory in particular. The topic is not easy. so this mail is a little long and dense, but hopefully worth it. It won't be the last one so let me know how to improve it.

INTRODUCTION/GOALS

This is the first of a series of mails we will publish the following days with different ideas. The process we are proposing has no intention of pointing at anybody, revisiting the past or enforce any situation within the community. Our goals are:

• Share a picture as a starting point of discussion.
• Use the discussed picture as a reference to agree on actions we all can/want to execute. 

FIRST STEP: PIECES OF THE PUZZLE

One of the first things we did was digging into numbers that provided us information about the status of the project. Data cannot be the only source to create a complete picture, but it is helpful as first step.

In order to better understand the rest of the mail, you probably want to look the following references:

• Alberto Planas talk at oSC13: openSUSE in Numbers[1]
• Alberto Planas' slides from the above talk[2]
• First openSUSE Team blog post: Numbers in openSUSE[3]
• Second openSUSE Team blog post: More on statistics[4]
• Jos post about numbers[5] 

One important note about the numbers: since most of the behaviors of the variables reflected on the graphs were consolidated, at some point we decided to stop adding effort in collecting numbers until 13.1 was released. Once the Release is well established, we will update them and evaluate the influence of this Release in the global picture.

 

I won't try to go very deep in the analysis. It would be too long. There are many interpretations that can be done based on the graphs. I will just point out the most relevant for our purpose. Feel free to add others.

 

Following Alberto Planas' order from his slides[2]...

1.- Downloads

The number of downloads do not measure our user base, but provide hints about the impact of the work done every 8 months, the potential new users we might bring to the project and, looking at pre-release downloads, the number of testers. 

Taking a look at the graphs, we can see that the overall number of downloads is growing at a slow path (slope). This behavior is not consistent in every release. For instance, 12.1 was more downloaded that 12.2 or 12.3. More and more people uses zypper for updating the distribution though.

2.- UUIDs (installations that update regularly)

• Looking at the number of machines that regularly update against openSUSE repositories (daily, weekly and monthly), we can easily conclude that the situation is very stable. The speed of growth (daily and weekly stats) or decline (monthly) is low.
• What the graph do not show is the acceleration. It has been negative (small in value) for quiet some time now.
• When looking at the architectures, we see that x86_64 is more popular than i586. This behavior is accelerating, as confirmed in the download numbers collected for 12.3
• When looking at the mediums where those installations come from, we clearly see three dominant ones: .iso (dvd version), ftp (net installs) and Live CD.
• There is a relevant detail that Alberto mentioned in his talk. More than half, almost 2/3, of openSUSE installations are not using the last version many weeks after Release date. There is also a significant amount of installations using unmaintained or Evergreen versions.

3.- Factory and Tumbleweed installations/"users"

Factory is our ongoing development effort. As you can see in the graph, the number of Factory installations is constant. Tumbleweed was very successful when it came out. Many developers and bleeding edge users liked it. Its popularity is decreasing though.

4.- Contributors to factory and devel projects

The numbers of users that are submitting request to factory/devel projects is increasing. Now we have more non SUSE contributors. SUSE ones remain constant. The overall growth is about 27 new contributors per year, a little bit more than 2 new contributors per month.

5.- Social media and comparison with Fedora

openSUSE is, in the social media channels evaluated, in the range of Fedora. Comparing our numbers, I guess we all agree with this general trend that states that openSUSE is a more user oriented distribution than Fedora is. We have less downloads but more users (installations updating regularly).

SOLVING THE PUZZLE

All the above pieces shows a stable picture. Every sign of growth or decline is, in absolute and/or relative numbers, small except social media, due  to their explosion as communication channels (which I do not think is way different from what other Free Software communities are experiencing).

ADDING CONTEXT TO THE PICTURE

openSUSE coexist with other "coopetitors" (Free Software competitors+cooperators) and competitors (closed sources distributions). Touchscreens, cloud, big data, games...the Linux ecosystem is evolving and there are new users with new needs.

New players are consolidating their positions: Arch, Chakra, Mint... Ubuntu is moving to the mobile space, Debian is getting some attention back from previous Ubuntu users....

On the other hand, some distros that were relevant in the past have disappeared, our 13.1 has got more attention than previous ones, SUSE is healthy and willing to invest more in openSUSE in the future ...

In the above context, how is our "stable" situation perceived? How do we think it should be perceived?

INTERPRETING THE PICTURE

If we agree that the overall number of users of Linux based server + "traditional" desktop OS (let's remove the mobile/embedded space and cloud for now), is growing, not following the "market" growing trend might be perceived as a wake up call, a clear sign that improvements needs to be done.

But if we agree that we are playing in a risky and challenging field, stability can be perceived as a healthy sign.

After these months of analysis and discussions with both, contributors and users, I would like to ask you if you agree with the the idea that the first picture is more prominent than the second one. But, does the second one provide us a good platform to improve our current position?

 

SHARE YOUR OWN PICTURE

Let me propose you some questions:

1. What other variables we should put in place to create an accurate picture of the current state of the project?
2. What is the perception you think others have from the project?
3. What is your perception, your picture?

To get some context you might want to take a look at the following contents:

• Current strategy[6]
• Ralf Flaxa keynote at oSC'13[7]
• Jos article: Strategy and Stable[8]
• Jos article: Strategy and Factory[9]

REFERENCES:

Please point us to other relevant references:

[1] Alberto Planas talk at oSC13: openSUSE in Numbers:

http://youtu.be/NwfohZ8RBd8
[2] Alberto Planas' slides from the above talk:

https://github.com/aplanas/opensuse-data/tree/master/osc13
[3] First openSUSE at SUSE team blog post: Numbers in openSUSE http://lizards.opensuse.org/2013/07/04/numbers-is-opensuse/
[4] Second openSUSE at SUSE team blog post: More on statistics http://lizards.opensuse.org/2013/08/23/more-on-statistics/
[5] Jos article about numbers:

http://blog.jospoortvliet.com/2013/08/on-distributions-numbers-and-breaking.html
[6] Current strategy: http://en.opensuse.org/openSUSE:Strategy
[7] Ralf Flaxa keynote at oSC'13: http://youtu.be/fdroo2JZano
[8] Jos article: Strategy and Factory:

http://blog.jospoortvliet.com/2013/07/osc13-strategy-and-factory.html
[9] Jos article: Strategy and Stable:

http://blog.jospoortvliet.com/2013/08/osc13-strategy-and-stable.html

---------------------------------

Summary about what the openSUSE Team @ SUSE is doing

openSUSE 13.1 is about to be Released (Nov. 19th) and I would like to share what the team I am part of is doing.

I joined SUSE in June 2012, almost 18 months ago. I haven't written much about anything during this time. And it haven't been because I hadn't time, but because I haven't have enough energy. I have received though these past months several requests to write a little about what I do at SUSE, so here we go....

The openSUSE Team is a good mix of long term SUSE employees and fresh blood, youth and experience, openSUSE and other distros background, on site and remote workers, people with management or commercial/customer support experience together with integrators and developers, people coming from R&D or product focus companies together with people with a strong community profile.... a very diverse (1 Taiwanese, 2 Czechs, 1 Dutch, 1 Serbian, 4 Spaniards and 3 Germans) and talented group. We also have trainees in the team. Having students is something I like because it helps any team to develop engagement skills.

The Team has as major focus the openSUSE distribution. It is element around which the whole project circles. It is the key point that sustain everything else in openSUSE. Obviously we put effort in other actions but we try that everything we do is directly related, have its roots, in the distribution, in the software. Obviously we are not the only force in openSUSE, not even the most numerous. There are hundreds (literally) of people that participates in this collective effort.

The team have a big impact since we are dedicated full time to work on the project, we have focused our activity in limited areas and we are fairly well organized. But in terms of effort, the rest of the community has a much bigger weight than my team... fortunately :-).

Those familiar with KDE will understand what I mean if I name Blue Systems work in the project today.

From the community perspective we have focused our action in two major areas:
* The openSUSE Conference.
* openSUSE news portal (marketing).

In 2012, like it happened before, SUSE took the lead in organizing the Conference. This changed in 2013. A group of contributors led by Kostas and Stella, reputed community members, organized it, opening the door for a new model within openSUSE.

SUSE role in the organization changed. Now we support the organizers in different tasks instead of leading the organization. For me, this is a relevant success story that should serve as example for many in the future. I feel very comfortable in this new role because the efficiency of our contribution has increased significantly. Organizing an event FOR a community is different than supporting the community in organizing THEIR event, right?

In marketing my team makes a significant impact by keeping the News portal as a reference point of information about openSUSE. We focus most of our action around the openSUSE Releases. We also link the innovation brought by SUSE into openSUSE with our community. We help SUSE Teams in marketing their work when it makes sense.

These two actions leave us little time for supporting further initiatives in the news portal. We do it once in a while though, not in regular basis. The situation in this regard is not much different than other communities I know. Keeping the main news portal up and healthy requires more people than usually is available. A more collective approach is what we all want. It is not an easy goal to achieve in any case.

So we basically have concentrated our effort in three main areas:

• What we call "the future". You will know more about it soon.
• The openSUSE Development and Release process, that will have openSUSE 13.1 as the main result, coming in a few days (November 19th).
• Community work. Specially around the openSUSE Conference and the news portal.

I hope this overview provides some answers to those of you interested in what I am up to lately. You can follow closely our actions through our Team blog, that has Jos Poortvliet as main editor and the whole team as authors.

This week I am participating together with other colleagues in SUSECon'13 and openSUSE Summit 2013. If you are in the Orlando Area, FL, US, consider coming. You won't regret it.

Two risks when working as employee in Free Software communities

I would like to point two risks that I have experienced myself and as manager throughout the last few years working in open environments (Free Software Communities) or projects involving interactions with them.

1.- In any community, there is so much to do...., so many interesting and innovative areas, so many disruptive ideas that can make a difference. There are so many projects that, with a little extra effort and some knowledge, could improve so much....everybody would notice the change, the difference, the impact.

When working as employee or as sponsored contributor you interact with so many people that needs help, that deserves to be helped, that you can learn from... that if you are not strong enough, after a while, without noticing, a significant part of your agenda is somehow determined by those who you help. But although you work on the same project that they do, share principles and environment, they not necessarily share your goals, your responsibilities, your duties, your motivations.

Spreading the energy through different areas, working under demand instead of having a clear control of your agenda, focusing on short term results instead of mid term ones, becoming a pillar for everybody else work in detriment of your own goals, of your own results, is a common syndrome I have suffered myself for a while, specially when working remotely from home, and I have experienced as manager of teams and projects.

What makes the action of any team (or professional) significant in any environment, and particularly in a open ecosystem like a Free Software community, is their ability to maintain during a long period of time a sustained effort focusing its energy in a single point. Only when the plan is achieved or after a proper analysis, jumping to another one is the right thing to do (in normal conditions, obviously).

The effect is even bigger when those points of focus are linked, serving a mid/long term purpose, aligned in a concrete direction. Then the impact is multiplied by the alignment of other people around you.

A key toward success is selecting targets with high impact, spreading its positive effect through the entire project. This multiplying effect requires a high amount of energy in early stages (activation energy).  The chances to create a significant and direct impact in several areas of any project at once are very low unless your team is big... and many not even then.

So the first risk is the loose of focus and its consequence is a reduced impact of the work done.

2.- Working in a Free Software community is one of the most rewarding experiences I have had in my life. I feel appreciated. My contributions counts. Many people is aware of them. I can work to make them more noticeable. The more popular my contributions become, the more people express me gratitude. The more relevant I become, the more people listen and interact with me...

This process is a spiral that you can learn how to climb in an effective way after some years. We end up learning how to play the game.

When you are a long term contributor and you are in charge of a key part of a project this is exactly what might happen. You arrive to the top of the pyramid, which is a comfortable zone. Too comfortable sometimes. If internal and external balanced forces are not applied, like competition, an adequate professional environment, external pressure/challenges... even the best professional can become too pleasant.

Reward can become a strong drug. It might elevate you in a bubble that, in the mid term, might have a direct and negative impact in the quality of the work you deliver. This is specially true for engineers/contributors that lead significant areas of a community project in which there are not enough contributors to create quality assurance procedures. Or are not applied to the leaders.

The second risk is the lose of "self demand" and its consequence is the reduction of quality of your work.

In my case, changing responsibilities and working environments every few years have helped me. I am not sure to what extend though. Others should judge it, I assume.

A champion instead of a leader.

I am one of those who actively supported Canonical in the past. Mark Shuttleworth succeed in linking his success to our success in Ubuntu's early years. I believe that customers/users are smart. Ubuntu became, still is, the number one distribution for good reasons.

In his journey toward success, Mark played hard, too hard sometimes. Not many put attention on it because the results were spectacular. Some did. KDE did and we suffered attacks for not following the trend. What some didn't understand back then is that there was a price to pay for Canonical's success. Mark made that price unaffordable for KDE. We have being around for over 15 years also for good reasons. We survived the early attacks to Qt, Nokia's disaster...  and obviously we were confident we would survive the explosion of Ubuntu and Mark's particular way of understanding leadership. We had our own roadmap. We still do and put quiet some effort on explaining it.

But we as a community were not blind or insensitive to what Mark Shuttleworth and Canonical were doing. The fact that Kubuntu is the number one distro among KDE developers and that Mark has been in several Akademy is just a reflection of the way most people in KDE appreciated what he represented. Canonical's effort, Ubuntu success, has been good for all of us, including KDE. I have no doubt about it. There were more things we shared than those that separated us. I still think this is the case nowadays.

I use an Android based phone. I am becoming more and more concerned about the embedded space. Linux based devices are becoming more and more popular but our freedom has not increased significantly. We need a strong action towards freedom, focusing not just in software but also in data and services. At this point I think that the problem has been identified. Now it is more about taking action. This is why in KDE we have been working on it for some time. And this is why, once more, KDE and Ubuntu might share a vision. We have another opportunity to work together to achieve it.

The situation today is different from the one in which Mark's leadership was born though. Today he has a history that can be evaluated and the battle ahead of us in the embedded space has very little to do with the desktop one. Mark's action will need to leave a greater room for other players, for other opinions, for other technologies. He cannot expect to be followed this time just because his vision is shared, just because his success is good for all of us. He still don't seem to understand that, for many, it is very important how success is reached.

But to me there is something else he needs to demostrate. Mark needs to create a profitable project, compatible with the Free Software spirit, so he can sustain his effort long enough, unlike he did in the past. The battle we need to fight in the embedded world will be long and expensive. Mark has demonstrated he is not persistent enough. I don't know if it was because he did not want to or he simply couldn't. He failed explaining his "turns".

Instead of avoiding the mistakes he made in previous years, he is digging into them. Instead of searching for allies in his new effort, he moves toward isolation. Instead of concentrating more on making his project sustainable, he is increasing costs by creating new technologies on his own and increasing the barrier to adopt them. Instead of leading us toward a solution, he is dividing those who should fight by his side.

He works toward becoming a champion, not a leader.

Most of my colleagues has nothing against Canonical becoming a champion of freedom in the embedded space. He is putting his own money and reputation in place. All my respect for that. But many of us do not understand the motivations and reasons behind Canonical decisions (Unity, Mir... ). We are not stupid. Mark simply failed in explaining them. So it is hard for me to digest his irritation when KDE colleagues do not support him as he expected.

Mark Shuttleworth has done and will do many relevant actions for increasing our freedom. He has created a great company full of talent and positive energy, capable of achieving a remarkable success once again. Ubuntu is still a great community, of course. I wish them nothing but luck in this trip through the embedded world. I just hope Mark understands AND assumes the consequences of the choice he made some time ago: becoming a champion instead of a leader.

Meanwhile, I would like to see no more of this "Tea Party" game, that hurts us all so badly. My colleagues at KDE do not deserve it. Ubuntu community and Canonical employees either. Even Mark Shuttleworth's reputation deserves better than what he is receiving lately. It is in his hands to revert this situation that he has created. I encourage him to, at least, not making it worse. We all have enough challenges already.

Insides about the new openSUSE Team at SUSE blog

Yesterday we created a new blog [1]to communicate to our community and readers what do we do as a team within the openSUSE project. It is a collective effort and it will be part of our duties to create and publish contents for it.

Its main goal is to talk about what we do so in the long run, it becomes a reference channel to follow up the activity of the group of people that SUSE employs to work full time in openSUSE.

Once of the discussion topics we faced was how to make compatible this blog, that has a corporate nature, with our personal blogs, our work in the community and the motivations of our team members. It is a very interesting topic since it is not trivial in practice to separate the information you handle as employee and your work within a community, in a case like our ours, employees that work for a community.

The easy approach is to say that, by default,  all what we do is public and treated as "community" work, or the opposite, but there are many corner cases, some of them relevant, that are not cover by these general approaches. Usually this topic has no relevance until something happens, usually bad. We need to understand that, as employees, we hold a responsibility that, if non properly managed, can potentially harm our company. It also can hurt us as professionals or affect our community. Often you are not a perceived as a regular community member only, but as a company advocate/representative too.

As a manager, I have to make compatible the community interest, the personal interest of the people under my responsibility and the company interest. In a company like SUSE, specially when talking about openSUSE, conflicts are small in this regard. We are a very open company in general and in my area in particular. I am glad of being part of a company that understand Free Software.

But under certain situations, nobody is out of risk. I even face this limitations being the KDE Treasurer. Being open is one thing and publishing all the information is another one. Obvious in theory but....where are the limits in practice? Who should take care of ensuring those limits are respected? What measures should be taken to satisfy all parties interest? When managing information, how to be fair with your community, yourself and your company at the same time? 

It is impossible to clearly define how to react in every case, what things should be kept private and what things don't, how to deal with the information you get as an employee but should be publish as part of your everyday activity within the community....

But what is possible is to create a clear field in which the people involved can move as freely as possible, making sure that some processes are put in place to avoid harmful mistakes. But above all, you have to rely on people, train them and be close to them so they understand the risks and the possible conflicts. Experience usually helps a lot in this field.

Behind this team blog, there are some processes that try to answer some of the previous questions and concerns, reducing the risk for the company and the authors but, at the same time, keeping the spirit of our work and goals: being open. I will talk about the concrete measures in a couple of months, when we get some conclusions about their efficiency.

I hope you will find the blog interesting.

[1] Link to the blog: https://lizards.opensuse.org/author/calumma/

Are you a senior KDE developer? Join openSUSE Team at SUSE

openSUSE Team at SUSE is looking for a senior KDE developer that is willing to join the company to work on openSUSE distribution and customer products where KDE technologies are present.

As those of you who are closer to KDE and/or openSUSE know, Will Stephenson has been leading this area the last few years. He is now facing new professional challenges within SUSE so we are looking for somebody that coordinates the openSUSE Team efforts related with KDE together with the openSUSE community, upstream and other SUSE Teams.

Our default openSUSE desktop, KDE, is obviously a relevant piece of our puzzle. But beyond pure KDE work, the selected candidate will also work in other areas of the distribution and will play an important role as openSUSE/SUSE advocate in technical forums.

openSUSE currently ships other desktops too so it will be important for the selected candidate to drive high levels of cooperation with the openSUSE GNOME (and others) team and upstream in cross-distro development efforts.

As a preferred choice, we are looking for a KDE developer willing to move to our Headquarters in Nuremberg, GE or to our office in Prague, CZ.

If you are interested, please check the opening details and send your CV through the SUSE Careers website. Links to your contributions to KDE and contacts for references are welcome.

In a more personal note......

Will, thanks for standing strong and work hard for openSUSE and KDE. Good luck in your new position.

Distribution hacker wanted: join the openSUSE Team at SUSE

openSUSE Team at SUSE is looking for a hacker willing to work on the openSUSE distribution with us. You can find the details of the job opening at the SUSE career website.

So we are looking for a software engineer with experience in a Linux distribution or a recognized upstream project, that wants to work full time in our distribution and enjoys being part of a community effort. 

He/she will work in English and attend to community events so some international traveling should be expected. We would like to increase our team located at SUSE offices in Prague (I love Prague), although Nuremberg/remote work are also options.

If you are interested, apply through the SUSE career website. Please do not forget to provide us links to your code and references if you have them. There are many other interesting openings at SUSE for senior and junior professionals, specially software developers. Put an eye on the Career page at SUSE website.

Job opening for an artist/graphical designer at openSUSE Team at SUSE

openSUSE Team at SUSE is looking for an Artist / Graphical designer who help us in two main areas:

• The openSUSE distribution
• Different artwork needed for the project like merchandising, banners, etc.

This work will be done together with the openSUSE community so, besides good technical skills, it will be welcome previous experience in FLOSS communities. We have at SUSE several senior graphical designers, so the candidate will work in coordination with them too.

The candidate might work in Nuremberg, Prague (preferred) or even remotely (if you have previous experience working this way). Must be available to travel internationally three to four times per year, beside some regular visits to our offices in Nuremberg, where most of the openSUSE Team at SUSE currently works.

We are an international team so English is a requirement. Other languages will be welcome. The candidate will give talks, presentations, workshops, etc. so good communication skills will be also required.

We are looking for somebody that can join us soon since we would like to begin working on our release, to be published this fall, as soon as possible.

If you are willing to work at SUSE for openSUSE, please send us your CV through our career website. Please include external and internal (SUSE/openSUSE) references, if you have them, along with links or examples of your work.

If you have further questions, I would be happy to answer them.

2012 for KDE: the financial perspective

2012, a great year for KDE

2012 has been an important year for KDE from many perspectives. KDE e.V. turned 15 years old, Nokia finally quit Qt and a new ecosystem lead by Digia is laying on KDE to get mature. We have published our Manifesto, that is the result of long internal and very interesting conversations (I wouldn't call them discussions) about who we are, how did we get here and what we want. ALERT, out first experience in EU R&D projects, is now a reality. KDE has broken every record in the GSoC program, our KDE 4 series is getting mature and attention is coming back little by little to our software since users are understanding that we are delivering what we promised. Plasma is way more than a crazy idea and now many people perceive how powerful can be, not in a few years, but in a few months.

Applications like Krita, Calligra, Dolphin, etc. are getting more and more popular and others, that lost track in the past, like Kontact, are recovering the favor of many users since improvements and better integration with Akonadi and Nepomuk (semantic desktop), are becoming obvious. We feel that more and more people recognize us as a key member of the Free Software ecosystem, not just for our software, but also for our commitment with freedom and our well desired reputation as serious and stable organization.

Financial situation

2012 has been the year in which Nokia showed us once again that corporations can become your best allies, but also that their commitment with freedom and specific technologies are strong only as far as they are compatible with their strategy, which  can vary quiet fast. Once again, KDE has shown others that strong principles are a great base for not just surviving, but digesting changes.

Our economic model, like many other FLOSS community projects, was based on the support of big corporations that invested in us as R&D environments (they were interested in our technologies), as cheap talent ecosystems (recruiting well formed young developers) and as branding feeders (investing in community projects has positive effects in company reputation).

But that support to upstream project, specially to desktops, from big corporations, has been reduced the last few years for different reasons. We are not the next year big thing in the desktop/mobile space anymore and that have a reflection in our financial situation. Many of those who have supported us in the past, link success to market share. That has never been our battle but, we did very little to fight against that wave. It was profitable.

So our past economic model, is drained and we need to adapt ourselves to a new field in which SMB (Small and Medium size Business) and individual support must become more relevant. Since previous Boards made a good job, we can face today those challenges with little risk, in financial terms, taking the required time to make the internal changes that, if we do them right, will define our future in this area the following five years. As simple as that.

This model change will take some time. This 2012 we have taken relevant decisions and some more are coming in 2013. Results must become clear in 2014. This is a very tough sector and it is very risky to make plans, but I have faith in the path initiated in 2012. Many Free Software projects around us are growing like hell. We have to catch up a little, yes, but we have been here long enough to understand that running is not always the fastest way to get to the finish line... and frequently not the healthiest.

2013 goals

Our major goal for 2013 is to get take more steps toward sustainability, in a very volatile environment.

How do we want to achieve this from the financial perspective?

There are two main work lines:

1. Reducing our exposure to market changes.
2. Becoming a more flexible organization.

In this journey, we will need everybody's support. As a technical community, finances haven't been a priority for our members. This do not have to change in the future since KDE e.V. is here to support KDE community. Just a little more collective focus will be needed. More communication effort from our side, as Board/Organization, and from those involved in this area, will speed up the process. We are already working on it.

I feel lucky of playing a key role in KDE these days. I am having fun and I am optimistic about our future in the financial area. If during 2013 we confirm the switch we began this year, we will have a good platform for growing healthy and strong the following years.

How can you help us?

If you are a KDE community member, please consider joining KDE e.V. If you are simply a KDE user or fan, you can get involved in our project as contributor or, if you do not have time to invest, please consider supporting us economically through our Join the Game program. KDE financial activity is summarized in our Quarterly Reports, you can download in .pdf format.