Tag Archives: FLOSS

KDE Akademy 2014 – Welcome, new KDE board!

Akademy 2014 is still in full swing in Brno in the Czech Republic with the traditional hack week that started on Monday. At about 200 participants it was well attended and organized. This years conference will very likely mark a milestone of change for KDE – a new board was elected, and a strategy discussion was started that will affect the direction and development of the KDE community for a decent amount of time. When I traveled home from Akademy 2014 on the train from Brno to Berlin, I personally felt a sense of satisfaction, because the community has managed to steer clear of the dangers of bike shedding about the board succession, and is accepting the change imposed by a shifting environment as a positive force.

Akademy 2014

Continue reading

The KDE Randa 2014 meeting, in easy-digestible video format!

In case you were wondering what was going on in Randa, here are some first hand impressions. The video was produced by Fran├žoise Wybrecht (alias Morgane Marquis) and Lucie Robin, and the people in it are the actual participants of the event. It was also created using KDenlive, one of the awesome Free Software tools a team has been working on at the Randa meeting itself. The video introduces the faces and personalities of the contributors and their different backgrounds and origins. Many thanks to our brand new ad-hoc media team for producing this video!

(In case the embedded video does not show up, see here: https://www.youtube.com/watch?v=yua6M9jqoEk)

How to contribute to the KDE Frameworks Cookbook

The annual KDE Randa Meeting, in itself already shock-ful of awesome, this year hosted the KDE Frameworks Cookbook sprint. Valorie, Cornelius and I already wrote a lot about it. Plenty of attention went into finding the place for the cookbook between the getting-started HOWTOs on KDE Techbase and the full-blown API documentation. Not surprisingly, there is a space and a good purpose for the book. Frameworks developers and maintainer have had to deal with the question of where to put introductions that segue newcomers into how to use the modules many times, and so far, the answer have been unsatisfactory. Newcomers only find the API documentation when they already know about a framework, and TechBase is a great resource for developers, but not necessarily a good introduction. What is missing is a good way to help and learn about what KDE Frameworks have to offer. So there is the purpose of the KDE Frameworks Cookbook – to help developers find and learn about the right tools for the problems they need to solve (and also, consumable on a e-book reader by the pool). For developers and maintainers, this means they need to know how to add sections to the book that cover this information about their frameworks. These tools and workflows will be explained in this post. Continue reading

KDE Frameworks Book Sprint at the Randa Meeting 2014

A couple of weeks before the KDE Randa Meeting of 2014, the meeting’s organizer Mario Fux suggested to have a book sprint to help developers adopt the newly released KDE 5 Frameworks. In the Open Source spirit, the idea was not to start from scratch, but rather to collect the various bits and pieces of documentation that exist in different places in one location that offers itself more to a developer than before. Valorie Zimmermann stepped up to organize it (many thanks!), and a number of people volunteered to take part. After a week the project completely changed its orientation and struggled and found and also newly defined its place as a part of KDE’s documentation efforts. And it produced an initial version of the book, which is currently circulated on people’s ebook readers around here. Continue reading

Defensive Publications: Shedding Light on Innovation


The patent system is broken. The point of patents is to encourage innovation and inventiveness. Instead of promoting innovation, patent offices have awarded overly broad, vague, and unoriginal patents that draw unclear lines allowing bad actors to profit and threaten costly lawsuits. Patent examiners have a strong sense of the technology that is patented, but they’re missing an understanding of what has been and is currently being developed in the open source world. As shocking as it may seem, the result is the examiner formulating an inaccurate sense of what is innovative. As the final arbiter of a very significant monopoly grant, they are often grossly uninformed in terms of what lies beyond their narrowly scoped search. This is not wholly their fault as they have limited resources and time. However, it is a strong indication of a faulty system that is so entrenched in the archaic methods under which patent offices have been operating.

We have faced and continue to cope with the effects of bad patents on multiple fronts. The most widely known are being displayed on the large stage where huge companies battle in the courts, resulting in large money settlements or high stakes jury verdicts (i.e. Apple v. Samsung). This leads to higher costs to consumers and users, uncertainty amongst innovators about what is patented, a veritable arms race to secure patents to corner the market, and limited competition. These ‘wars’ cost companies money and that cost trickles down to the consumer.

On another stage, we also see the threat of trolls exponentially increase as more patents are acquired and used against small companies, nonprofits, and independent developers. The fear of costly litigation forces licensing agreements with the result of stifling innovation by suffocating independent inventors. On all fronts, more money is being spent on co-existing with undeserving patents rather than developing new ideas. We are losing out on breakthroughs and advancement in technology because of the environment of fear and uncertainty that has been created.

The answer has to be more than abolition of the patent system, as from a pragmatic point of view, it won’t happen. It does us little service to ignore patents and abandon the system. Rather, we need to address and combat the threats to innovation so that we can begin to bring an end to the age of fear and litigation. We can continue to deal with patents as they are issued, identify those that abuse the system, then spend the money and invest time to work to invalidate these. Taking this one step further, we can also proactively prevent these obstacles to innovation from even existing by directly communicating to the examiner what is being and has been developed. The tools to do so are available through the use of defensive publications.

A defensive publication essentially describes what is known or currently being developed. For those who are developing software, these documents are regularly created in the form of blog posts, community updates or releases. However, examiner constraints prevent these sources from being found. The last step is formalizing this and ensuring that the patent examiner has access to an open source database of these documents.

With increasing amounts of low quality patents being issued worldwide and a lack of clear boundaries, patent examiners are losing a sense of what is indeed inventive. Those who patent are getting a voice. Every free software release, solved issue or innovative development process can be turned into a defensive publication. References to current or older releases can also be demonstrated to help illustrate how the community of developers resolves obstacles. By writing these disclosures, free software can demonstrate how to be proactive. In turn, a patent application is rejected and a potential lawsuit is avoided.

Through the Linux Defenders program, Open Invention Network works  with open source developer communities to create defensive publications. We will be working closely with Linux kernel and Qt  developers, because we think that these represent major driving innovative forces in the Open Source spectrum. Important innovations in Linux and Qt should be documented in defensive publications following the releases of the software. We invite interested individuals and companies to contribute to this, and will support the authors in getting their publications out. If you are interested in writing Qt related defensive publications, or will be able to help identifying topics that should be documented, consider joining the mailing list to follow the discussion: http://lists.qt-project.org/mailman/listinfo/defpubs

[Image by Nick Kocharhook, thanks: http://www.flickr.com/photos/k9/35010906/%5D