KDE e.V. Endorses Community Working Group, Code of Conduct

On Monday at Akademy, KDE's yearly world summit, the KDE e.V. held its general assembly, covering a wide range hot topics, regarding licensing and community scalability. While part of the meeting is dictated by intricacies of German association law, the AGM also provides a way of effectively solving issues arising in the KDE community and deciding on ways to move forward as an organisation. This year's KDE e.V. General Assembly endorsed a Code of Conduct, the Community Working Group and a Fiduciary License Agreement for KDE contributors.

Code of Conduct

The KDE e.V. has ratified a proposal for a Code of Conduct as accepted shared set of values for participating in the KDE Community. This Code of Conduct presents a summary of the shared values and "common sense" thinking in our community. The basic social ingredients that hold our project together include:

  • Be considerate
  • Be respectful
  • Be collaborative
  • Be pragmatic
  • Support others in the Community
  • Get support from others in the Community

The full version of the KDE Code of Conduct is online now.

Community Working Group

Preparations in the last months have now led to the founding of KDE's first Community Working Group. The purpose of this new body endorsed by KDE e.V. is summarised as:

"The Community Working Group aims to act as a central point of contact
by being available to communicate user needs and concerns to
developers, and developer intentions and plans to users."

The initial members of KDE's Community Working Group are:

  • Anne Wilson
  • Juan Carlos Torres
  • Lydia Pintscher
  • Martin Fitzpatrick
  • Tom Albers

KDE e.V. Logo

As KDE e.V. is a different entity from the more comprehensive KDE Community, the spirit of this organisation is now displayed by having its own logo. The three flags on top of the logo represent the three main tasks of the KDE e.V.: supporting the KDE Community, representing the KDE Community, and governing the KDE Community. The logo has been contributed by Oxygen team member David Vignoni.

Fiduciary License Agreement

The Fiduciary License Agreement is a legal safety net to keep KDE's licensing effective in cases where a change of licensing is required (for example in the unlikely case that the GPL is void) and the contributor holding the copyright of a certain piece of code is not able to change the license of her work.

The FLA is in no way required for KDE developers, but a suggestion by the KDE e.V. to mitigate the risk of possible problems surrounding copyright assignment and licensing. It is left to each individual copyright holder whether or not to sign the agreement.

Details on all the above points will be published on the KDE e.V. website soon.


I really really like it!

Now only one thing is missing:

Great documentation!

KDE should be as well documented as Qt.
If you look at posts like this one:

you can clearly see that the pillars message is not coming across.

All websites should up to date and be a great marketing tools for getting new contribututors. ( not like that will be updated next month for years now or so it seems )

So why don`t you put the money in the bank to good use and pay someone to document KDE for 2 months right before each release. I think that would serve the communtiy way better than e.g. paying for a executive director that talks about open source sueing people and liking Amazons DRM and buying diapers ( sorry, I couldn't resist ).

I really think KDE has the best tech out there, but documenting it is something nobody seems to like to do. So the solution IMHO is to pay someone to do it.

Only then can you truely rival Apple and MS for developer mindshare on all platforms. ( Just look at if you don`t believe me. )

KDE4 obviously rocks and you should try to explain that to everybody.

By Tom at Tue, 2008/08/12 - 5:00am

> I think that would serve the communtiy way better than e.g. paying for a
> executive director that talks about open source sueing people and liking Amazons
> DRM and buying diapers ( sorry, I couldn't resist ).

None of the e.V. board are paid, they are all volunteers.

By Richard Moore at Tue, 2008/08/12 - 5:00am

Sorry, misunderstanding.
I meant the the executive director of some other fairly big unix desktop software project.

Does KDE even have a executive director?

By Tom at Tue, 2008/08/12 - 5:00am


By anon at Sun, 2008/10/12 - 5:00am

Good point. M$ soft is definitely better in this aspect. It's documentation is crappy and inaccurate, but it has this subtle advantage over KDE's docs in that it EXISTS.

By slacker at Tue, 2008/08/12 - 5:00am

What is wrong about techbase?

As of documentation of applications the main problem seems to be that it covers the irrelevant or obvious aspects but not the real problems you usually run into. I would like to see a link to an application specific user forum. In order to avoid a disappearence of the forum it should be a generic forward. E.g. to link to the existing Kdevelop forum: and to link to a Kate user forum.

By andy at Tue, 2008/08/12 - 5:00am

Oh, I just read this here:

"Danimo had a quick meeting on the state of KDE’s wiki. If you want to help out, please contact him. Important, as TechBase is starting to get used for everything, and might eventually…wait for it….turn into another bloated chaotic wiki if we aren’t careful in keeping it topical. I wasn’t able to attend, but it was certainly for a Good Reason ™ (no comment possible now)."

I personally can recommend the concept of wiki farms to you. With great Affero GPL wiki farm software as the one used by you can simplify the creation of dedicated and flexible wikis a lot and wikidot has a fantastic and easy permissions system. For your wiki farm you get a single sign-on mechanism and its easy to upgrade a user to an editor or admin (if it's a restricted wiki), theme the wiki, make the wiki private, get a new wiki hosted by the farm or even create de-facto "static sites".

Pitfall so far: it does not support login via Konqueror yet for whatever reasons.

By andy at Tue, 2008/08/12 - 5:00am

Hmm, techbase is OK. But it is far from _Great documentation_ and there are lots of missing pieces.

And don`t get me started on application documentation.

Try to start hacking on konqueror and you will see that there is close to nothing that will help you. Simple things like a manifest where each source file is explained briefly, an overview of how things work etc.

Simple things like that would really help new contributors. I tried and failed miserably because the solution given was: Look at the source!

That is not great documentation IMNSHO.

Starting to hack on the linux kernel is easier, although it is way more complex, because there are good books and the docs in the kernel are fairly up to date and the source is better commented.

By Tom at Tue, 2008/08/12 - 5:00am

By Juan Carlos Torres at Wed, 2008/08/13 - 5:00am

By Michael "api.kd... at Wed, 2008/08/13 - 5:00am

That is what I would call "OK documentation", but it is still far from great.

Just look around at:

and you will see a big difference. The content there is not generated by some doxygen scripts und it is indepth. It is done by humans and that is why it is so much better.
And the websites are not woefully out of date.

Just yesterday I saw two articles about Akademy pointing to
( on and ).
Documentation like that and generated stuff like give a very bad first impression if you ask me.

By Tom at Wed, 2008/08/13 - 5:00am

Do you know about ?

Also, it is good that is autogenerated, because each documentation-fix in the source code automatically ends up there the next day (or week, not sure how often it is being regenerated)

By Carsten Niehaus at Thu, 2008/08/14 - 5:00am

Seems like the new header that gives the KDE e.V. the authority to pick a later version of the GPL license mostly solves the license issue. But doesn't the FLA also protect the developer from being sued to some extent?

Though I (and probably most devs) have the ultimate defense from being sued: being too poor to bother suing. ;)

By Ian Monroe at Tue, 2008/08/12 - 5:00am

Money is rarely a reason to sue you. They might sue to stop you from developing FOSS, or scare others away.

By Jos Poortvliet at Sat, 2008/08/23 - 5:00am

That's a step in the right direction for FOSS. Very cool.

By winter at Wed, 2008/08/13 - 5:00am