In this week’s KDE Commit-Digest:
The Calligra team is proud and pleased to announce the release of version 2.8 of the Calligra Suite, Calligra Active and the Calligra Office Engine. This version is the result of thousands of commits which provide new features, polishing of the user e…
Today KDE released updates for its Applications and Development Platform, the third in a series of monthly stabilization updates to the 4.12 series. This release also includes an updated Plasma Workspaces 4.11.7. Both releases contain only bugfixes and…
Frameworks 5 based apps on Wayland
In early 2013, it was established that “Osnabrück is not a place“. Meaning that the KDE PIM spring sprint, which traditionally takes place in Osnabrück, could happen at a different location and still be a continuation of the tradition.
KDE PIM’s autumn sprint has traditionally been in Berlin, but since the team decided that “Berlin is not a place” applies as well, this year’s installment of the sprint took place in Brno in the Czech Republic.
Even people without the exceptional skills of Sherlock Holmes have certainly deduced by now that KDE PIM sprints happen in cities that are not places but coincidentally contain the letters B, R and N.
Unlike with most other sprints, where all but some local people arrive on the first day of the sprint, there had already been a week of intense KDE hacking been going on.
Bob – you remember Bob? – and his merry henchmen from the KDE Barcelona Squad, had already arrived earlier that week and hacked on various pieces of KDE software and had beer delivered to them on trains. Yes, trains! That’s the Czech Republic for you.
We’re sorry to have to notify you of the fact that nobody worked on KNotes. There were plenty of old school sticky notes though. Because Kevin Ottens likes to draw rectangles on white boards and sticky notes are a natural choice for filling them.
There were also a lot of notes taken, notably on the outcome of the discussions which were scheduled by moving notes on the whiteboard.
This kind of structured handling of topics is a noteworthy improvement over some of the previous sprints and very necessary given the increased number of people who nowadays attend and take note of them.
Back row: Lukas Tinkl, John Layt, Michael Bohlender, David Edmundson, Ingo Klöcker, Daniel Vratil
Middle row: Kevin Krammer, Martin Klapetek, Mark Gaiser
Front row: Christian Mollekopf, Alex Fiestas, Vishesh Handa, Jan Grulich
As has become tradition, a significant portion of the meeting was dedicated to mercilessly squashing those nasty little buggers. David Faure, a man who certainly needs no further introduction, used the presence of several component maintainers to get issues fixed. “Getting fixed” meaning he did the actual fixing, being aided by the aforementioned component specialists with insight into inner workings and assumptions of the respective code.
The previous and current maintainers of Akonadi had fun with things so deep down in the guts of the system that not even the author of this article would be able to fully understand them. Those people are way smarter than him!
In addition to fixes in the sense of correcting erroneous behavior, this also included several improvements in the area of runtime performance. And a faster KDE PIM makes everybody happy.
One of the other fun aspects of a sprint, aside from the obvious awesomeness of hanging out with great people and doing interesting code work, is to ponder and prototype potential progressive programming pieces.
Mark Gaiser, Michael Bohlender and Thomas Pfeiffer had a closer look at how to get beyond quaint, dare I say boring, user interfaces and enable QtQuick-based applications to tap into the power provided by KDE PIM libraries. Some example code was written, plans were drawn – but much is still to be done.
Naturally the presence of the KDE Barcelona Squad made secrecy a paramount objective. Not only do we need to hide their identities, a job made easy by several Squad members disguising themselves with enormous fake beards, we are bound by oath—under threat of dragonian punishment—to not talk about rocket science like advances in PIM data search. Well, “rocket science” doesn’t even cut it, more likely on the level of warp science!
Editor’s note: recent leaks have nothing, absolutely nothing, to do with our ability to keep things, you know, secret. Really!
In this week’s KDE Commit-Digest:
KDE is happy to announce that it has been accepted as a mentoring organization for Google Summer of Code 2014. This will allow students from around the world to work with mentors on KDE software projects. Successful students will receive stipends from …
For years, KDE software has included a semantic (relationship-based) searching infrastructure. KDE’s Semantic Search was built around concepts previously developed in a European Union-funded research project NEPOMUK which explored the use of relationsh…
In this week’s KDE Commit-Digest:
Today we proudly feature an interview with Bernard Gray from De Bortoli Wines, an Australian winemaking company.
Hot and Dry in Australia
We spoke with Bernard Gray who has worked for the company for over 10 years in an IT project management and development role. He is, in his own words:
De Bortoli Wines is one of Australia’s largest family-owned wine makers. Bernard:
We started by asking him how long they have been using Linux.
“As a company, our first production Linux server was deployed in the mid-late 90s. Personally, I first used Linux in 1999 when I started University – I had very little idea of computing at the time, let alone Operating Systems and their differentiating qualities. It wasn’t until 2003 that I really began to get my teeth into Linux when I started developing the Linux based Live CD environment that we’ve internally branded “GTs” (Graphical Terminals, originally designed to replace our thin-client telnet terminals).”
“The beauty of these devices is that we could purchase commodity PC hardware, outsource hardware support, maintain a single image Live CD based operating system environment with its read-only root filesystem rendering it “unbreakable” so to speak. Combined with the fact that it runs out of a ramdisk and on generously spec’d desktop hardware, we finally managed to nail the trifecta of Cheap, Fast AND Good.”
“We deployed our first “GT” in production in April 2004.”
The Dot: Could you tell us a bit about the migration, both the reasons for it and the experiences you had with it?
“Our original GT shipped with an early 2.x Gnome release. This had more to do with my general lack of skills with package management and live image building than by design. Since the distro I was using at the time shipped Gnome by default – I went along with it. Since then, we’ve migrated to KDE 3.5, back to Gnome 2.8 and finally to KDE 4.9 which we’ve just completed the rollout for, and which now makes up approximately three quarters of our 250+ desktop fleet.”
“The key to all smooth migrations we’ve found is Desktop Environment consistency. Keep the major applications cross-platform where we can (browsers, office suites, assorted tools). Keep the icons where people are expecting them (they’re in the same spot on our Windows desktops too).”
“Still on the development side, the KDE techbase site has been an invaluable source of information for me, as has the KDE community–both users and developers. Often large technical communities struggle with a high amount of enthusiastic users but without a lot of knowledge, which make the skilled base hard to find/interact with for solving more difficult issues. With KDE I have had nothing but good experiences – it’s worth a special mention for a particular Okular bug we were experiencing which was resolved in record time after I contacted the Okular developers mailing list.”
“All these things combine to greatly reduce the development and training load requirement on our small team – which keeps us, and most importantly our users, happy and productive.”
That is great to hear! Thank you Bernard for taking the time to answer our questions. We wish you and De Bortoli wines a great time with our software.
Today KDE released the first alpha of Frameworks 5, part of a series of releases leading up to the final version planned for June 2014. This release includes progress since the Frameworks 5 Tech Preview in the beginning of this year.
In this week’s KDE Commit-Digest:
Today KDE released updates for its Applications and Development Platform, the second in a series of monthly stabilization updates to the 4.12 series. This release also includes an updated Plasma Workspaces 4.11.6. Both releases contain only bugfixes an…
Quick tip for Firefox users: GNotifier is a Firefox extension that makes the browser use native notifications on the Linux desktop. The extension currently supports GNOME (Shell), Unity, KDE and Xfce.Below you can see a Firefox notification in action using GNotifier, under Unity and GNOME Shell:Besides regular notifications, like the one displayed when a file […]
In the second week of January, KDE’s Plasma team gathered in the Blue Systems office in Barcelona, Spain, to discuss and work on the next generation of KDE’s popular workspace products. The meeting comes just at the right time, as the Plasma team has just finished a first technology preview, which puts the base technology in place and allows for an evaluation of the current progress. It also gives an opportunity for more refined plans for a first stable release.
In this article, we will give you an impression of some of the topics which have been discussed. Please note that discussions have by now moved to the various online communication channels, such as mailinglists and IRC. Not all results are set in stone, they rather serve as blueprints for ongoing discussions.
Naming and repository structure
One of the things that had been discussed online, but has not been concluded, is the naming of Plasma’s next release. A proposal has been made to continue calling KDE’s workspace products “Plasma”, possibly extended as “Plasma by KDE”. The term “workspace” will be on the way out, as it bears rather little meaning to most users. Plasma simply refers to all the workspace products, with the technology itself taking care of the distinguishing UI per device.
In line with this thinking, the repository structure will be changed. There is a number of interesting repositories, which are oriented towards likely deployment scenarios. The plasma-frameworks repository contains the library pieces needed to run a Plasma environment and build applications using Plasma technology. The kde-workspace repository will be split into a generic repository, which contains device-independent components. Then there will be repositories for different form-factor UIs. This means, that on a typical desktop system, one would install plasma-framework, plasma-generic and plasma-desktop. To add support for other devices, one can simply add another repository (such as a mediacenter or tablet user experience), and a specialized UI will be offered for this.
Plasma, being a central product for KDE, receives many bugreports. In order to provide good support, better prioritization and focus is needed. For this reason, the team plans to structure the different components in Bugzilla in a way that makes it easier to identify higher priority problems (for example in default components), and make a clearer distinction between “officially supported” and “community-supported” components. This should lead to improved stability and shorter reaction times for the core components of the desktop.
One of the things that kept the Plasma developers busy during the sprint was the question what to do with the main application launcher. This seems to be a question which has a different answer for almost every user. Plasma’s strategy has been to offer a well-tested default (Kickoff), with other options to choose from (traditional menu, Lancelot). For the next release, this flexibility will remain intact. The idea is to replace the traditional menu with one that works similarly, but sports an updated look and some interaction improvements. The current version of Kickoff, which has already been reimplemented in QML will get a visual update.
The future of KRunner, Plasma’s mini-commandline was discussed. There is a replacement in the works, though at this early stage is it unclear when it is going to land. In order to allow an alternative to fully mature before it replaces a core component, the team decided to port the current version of KRunner, and adapt it for improvements in the desktop search area.
The team also discussed the login procedure. While KDM has reached the end of its lifetime, being a fork of the ancient XDM, there are better alternatives on the horizon. The Plasma developers decided to improve and update the theming of LightDM and SDDM, although neither are currently perfect solutions. LightDM suffers from requirements around copyright assignment, which some developers refuse to sign; on the other hand, SDDM is not yet fully finished in terms of features needed.
Activity Switching (click for larger)
by Martin Klapetek (CC BY)
Plasma developer Ivan Čukić presented a redesign of Plasma Desktop’s activity switcher. The new design has a vertical layout and presents a more visual way to manage activities, move and assign windows, and add and rename them. The design presented was well thought out, and apart from a few visual changes, Ivan’s concept was received very positively.
Notication Area Improvements
The team discussed the current version of the systemtray, also known as notification area. The new approach to use one popup dialog for all, which reduces visual clutter, was welcomed. The team has identified a few issues with the current implementation, which will be addressed in the coming weeks. One of the things that was brought up is that applications or services should have a way to enable a Plasma widget in the system tray. This could be useful for Bluetooth, for example, where a widget would show up as soon as the Bluetooth hardware is found or enabled. On the other hand, some widgets which do not make sense in a given hardware environment could be entirely hidden (for example, the battery widget on non-laptop systems).
Wayland discussion (click for larger)
by Martin Klapetek (CC BY)
KWin maintainer Martin Gräßlin presented the status of KWin and Wayland support in the window manager and compositor, and shared his plans for the future. Wayland support is well under way, although not everything is entirely clear from an architectural point of view. There is simply no example or reference implementation for many of the technical problems we face, so his work is, to no small degree, about covering new ground.
A new focus on design
One of the hot topics during the sprint was the visual and interaction design in Plasma. These things have been identified as needing a more structured approach. Thanks to the effort of Jens Reuterberg, an illustrator from Sweden who recently joined the Plasma team, work has commenced on forming a stronger design team. Another topic in this area was the creation of visual guidelines, which has already been started. The team hopes that these efforts will result in greater visual consistency and more elegance throughout the whole user experience.
Group photo: Left to right: (top) Martin Klapetek, Mitch Curtis, Ivan Čukić, Jens Reuterberg, David Edmundson, Martin Gräßlin, Aleix Pol, Giorgos Tsiapaliokas, Sebastian Kügler, Antonis Tsiapaliokas, (front) Marco Martin, Vishesh Handa, Àlex Fiestas (click for larger)
by Martin Klapetek (CC BY)
Of course there is not sprint without hacking. Many ideas have been put into code already, various pieces have been cleaned up, missing features were implemented. Everyone attending enjoyed the sprint, especially the productive and friendly atmosphere. The whole team is excited and already working on the results of the sprint.
From its beginning, KDE has been a leader in innovation in free (libre) and open source software (FLOSS), but there is a threat to that leadership in one of the fastest growing areas of technology. The advantages of free and open development and use are clear for software; now closed and proprietary strategies have become standard in other kinds of technology. The need for technology freedom has moved from software to other more corporate-controllable areas—notably hardware and the Internet.
As was the case when KDE started, community-developed, freedom-oriented technology is necessary to break the stranglehold of large companies that are more committed to managers and investors than to users. But this won’t be easy and it can’t be left to a few people. The entire KDE Community has a stake in the outcome. For that matter, this should be a concern to anyone who develops free and open software, anyone who uses it, anyone who benefits from it. And that includes just about everyone using technology today.
New hardware has been announced that addresses the need for openness beyond software. Community help is needed to support a generous, far-sighted open hardware project involving mostly KDE people and certainly following KDE principles. Please consider contributing financially to open hardware for KDE.
More of the story follows…
The threat of proprietary & closed
The Internet is under threat from companies that seek unfair leverage with their massive investments…investments, by the way, that are already well compensated. The nature of these companies is such that every possible means must be used to extract value.
The digital hegemony of several U.S. companies (Amazon, Apple, Facebook, and Google) plus Samsung dominate technology. All of these companies depend to a great extent on free and open software. Microsoft tries (and fails) to stay in this league with such schemes as using its monopoly position to force conditioned users to adopt Windows 8—a mobile phone GUI blown up to a touch interface on a 19″ monitor, positioned by clever marketers as “platform convergence”.
What these companies are doing is not wrong; it’s the way most things work these days.
KDE’s leadership is an opportunity to extend free and open technology, providing creative minds unlimited room to innovate. Mainstream tech companies try to do this without disrupting their profits or stock prices. We are fortunate to have such freedom.
Nine years ago, KDE started planning for a shared technology base for all types of computers. In September 2011, Plasma Active was released. It shared almost all the underlying code base of the other Plasma Workspaces, along with an innovative user interface specifically designed for tablets and the way they are used. KDE quietly offered platform convergence well before Microsoft or Canonical jumped on the bandwagon.
Plasma Active fits well with KDE’s original goal. As Matthias Ettrich wrote in the announcement of KDE:
Plasma Active is free and open software, readily available to install on any tablet. But it has been installed on only a few types of tablets, and requires higher than average technical know-how to install and maintain.
Virtually all tablets on the market have either Google’s Android operating system or Apple’s iOS. Neither is truly free and open. Apple technology is closed and proprietary…Apple’s business model. Android is 23% open according to VisionMobile. Installing a different operating system and user interface means violating warranty terms. In addition, there is no standard version of the Android operating system even with the same version number. These operating systems and user interface designs are controlled by Apple, Google and Samsung (which sells approximately 40% of all Android devices). These companies have no interest in making their hardware run KDE software. In fact, doing so would be contrary to the fundamental purpose of such enterprises.
The environment for Plasma Active is far different (and more restricted) than that for other KDE software. With any commercially available desktop or laptop, it is simple to install and run KDE and other free and open software. While there may be some occasional hassles with wireless or graphics, those are easily overcome. Plasma Active comes standard on the open hardware platform called Improv.
Software can’t be free and open if its hardware is closed and proprietary. Improv is as open and free as possible.
The tablet market
In October 2013, Gartner reported that global tablet sales would grow 53.4% for the year, and PC shipments would be down over 11% from the previous year. By 2015, tablets and PCs will sell about the same level.
Users will continue to want the kind of software KDE provides for traditional PCs, for several reasons. (Jos Poortvliet’s presentation at Akademy 2013 has some background.) KDE is viable for the foreseeable future…in the desktop and laptop space. But not for tablets, the fastest growing and highly visible personal computing segment.
Several free and open projects have been started to address the need for alternatives to the Android/iOS market dominance in tablets and other devices. Those projects have faced difficulties that point to the daunting nature of challenges to the Google, Samsung and Apple mobile oligopoly. Other projects such as CyanogenMod have chosen the venture capital route to try and compete. The fundraising goals are substantial:
Where do these projects stand?
Jolla began offering a smartphone in Finland at the beginning of December 2013. Their tablet operating system has been exhibited but is not commercially available. A mainstream journalist reports that the Jolla smartphone is a “work in progress” that still has some rough edges, and refers to the ‘beta’ nature of the handset and software.
Prominent venture capitalists have made substantial investments in CyanogenMod. So at least for the moment CyanogenMod is doing fine. They will have to capture major market share to satisfy venture capital investors…time will tell. This professional investment establishes a substantial value for CyanogenMod as a company and hints at the attractiveness of the device market. A market in which there’s a danger of KDE being irrelevant.
Canonical tried to crowdfund a smartphone to round out their converged computing initiative. Against a goal of $32 million, there were commitments of about $12 million. Canonical hinted at backing from major hardware suppliers, but this news was light on detail.
Samsung was expected to launch a Tizen phone at Mobile World Congress in February. Now it appears that Tizen will not challenge Android and iOS this year after all. A Samsung switch to Tizen would be a blow to Android, but it would be good for Samsung’s already rich bottom line. And would further entrench the oligopoly.
According to the tech news site Gigaom, both Tizen and Ubuntu Touch have been set back. However with its substantial, prestigious backing, Tizen is almost certain of being successful.
All of these projects are associated to some degree with free and open software; their funding experiences—successful or not—indicate the potential value of the device industry. None of the organizations promise the degree of freedom and openness typical of KDE.
“The KDE Tablet”
Several years ago, KDE developers confronted 2 questions:
The answer was “NONE”.
So in early 2012, Aaron Seigo announced the Spark (later renamed “Vivaldi”) tablet, which would be produced by the Make Play Live (MPL) project (comprised mostly of people and companies associated with KDE). It would make the necessary hardware available.
Many readers will be familiar with the background. Plucky Aaron and his MPL team have faced significant challenges. One of the most difficult things to overcome has been the nonchalance of hardware suppliers about open source licensing. In addition, suppliers changed components without notice or consultation. In short, it has been an ongoing battle to produce hardware that would run Plasma Active out of the box.
In fact, Aaron and his small hardware development team were forced to engineer hardware from scratch. According to Aaron, there will be an open hardware tablet; it’s a question of when it will be available.
In the mean time, the efforts to produce an open hardware tablet revealed a need for general hardware development expertise for free and open projects. The Vivaldi lessons could be applied more broadly to all manner of hardware development.
Out of this realization, the MPL hardware development team created Improv.
Improv has two parts:
Improv hardware drawings are open and readily available, software is covered by free and open source licenses, and interfaces are well-documented. In other words, Improv is open hardware, as open as it can be given that all graphics processing units (GPU) are closed and proprietary.
More information and detailed specifications are available at the MakePlayLive website. Improv comes with the Mer operating system, the lean Core Linux distribution that is a direct descendent of MeeGo. Additional software configurations are available, in fact encouraged.
Improv has been designed, prototyped, tested and retested. It can’t be bricked by installing other software or experimenting with configurations; there’s no need to root the device. Concepts prototyped on Improv can be turned into complete, custom products using the same hardware.
Improv & Plasma Media Center
Improv is done. It’s ready. In typical KDE fashion, Improv was accomplished while others were saying what they were gonna do.
Aaron said this about the Improv:
Improv is a product that can open the doors to the world of ubiquitous, device-centric computing for KDE and other free and open projects. No more waiting for a big vendor to be kind and take our needs into consideration. No more trying to shoehorn KDE software into devices with proprietary lock-in.
Improv & Konqueror
I understand…how do I contribute?
That’s the pressing dilemma. With software, it’s easy for developers to contribute. A lot of people make their first contribution to free and open software with a single patch. Anyone can download the code and work with it. Start small. There’s room for many contributors.
Hardware development is different; it involves physical pieces and is done in chunks. For example, board layout with multiple components and complicated routing is a one-person job.
Aaron and the small team have succeeded at creating the hardware. No further contributions are necessary towards its development. Improv works and works well.
However, there is another big difference between hardware and software—cost. Creating software has no out-of-pocket expense beyond the initial investment in a computer. Distributing one more copy of a KDE application has virtually no associated cost. On the other hand, hardware has a direct cost. Designing a printed circuit board is mostly done in software. But there is a cost to prototype and produce each copy of that physical board.
Aaron and a few others have personally paid these development costs. As can be inferred from the budgets mentioned above, Improv hardware development has not come cheap. There are no venture capitalists handing out money on this project. This is not a get-rich-quick scheme. It is a many year project, involving considerable personal sacrifice on behalf of KDE and free/open technology. Improv is based on generosity, not greed.
The team had high expectations that Improv pre-production sales would be enough to cover these expenses. They will eventually, but people want to get their hands on Improvs now. Delivery delays harm the project.
Please lend a hand
Funding is needed for the direct costs associated with manufacturing: electronic parts, feature board assembly and CPU cards.
Hundreds of people have already supported the project by buying an Improv.
You can help…
Company engineers might use Improv as a platform for building a custom product. It serves well for prototyping, and can mature gracefully to market readiness. Most importantly, Improv can reduce a hardware development schedule by many months with substantial cost savings.
Please consider donating to the project. Donations will only be used for direct manufacturing costs. Any money contributed beyond the goal of $125,000 will be used to produce Improvs for education.
Improv works. Please help push it from proven-design-ready-for-manufacturing to full production.
Take a stand for digital choice. A stand for what KDE has proven to be successful—free and open wins.
In this week’s KDE Commit-Digest:
In this week’s KDE Commit-Digest:
conf.kde.in was announced in November, to take place February 21 – 23, 2014 in Gandhinagar, India. This three-day conference, the biggest KDE event in India, will bring together Qt developers, KDE contributors, open source enthusiasts and users from all across the nation. Visitors will have the opportunity to learn, share, contribute, innovate and create around Qt and KDE technology.
conf.kde.in is an excellent platform for you to learn about FOSS and start contributing to it. You will learn about KDE technology and community and how to participate, paving the way for future participation in programs like Google Summer of Code (GSoC) and Season of KDE. Last year, KDE was the largest participating organization in GSoC with 60 students selected. The conference sessions will range from beginner to advanced level, to facilitate all kinds of participants.
There will be a vibrant gamut of talks at the event; with a variety of technical as well as non technical talks covered by members of the KDE community from the extremes of India as well as the world. Be a witness to this cultural and intellectual infusion of ideas and experiences, of knowledge and guidance; by people from different walks of life, all with a common passion – open source and KDE; ready to ignite the same passion in you through their words and their minds.
Here are some of the talks currently scheduled for this event:
The above is the incomplete list of talks, we are adding more talks as we get confirmation from the speakers. The updated list of talks can be found at this page.
Every speaker at conf.kde.in is a bona fide contributor to KDE, some of them contributing already for over a decade. Attending the conference will give you the opportunity to meet seasoned open source contributors, discuss with them, exchange ideas with them, learn from them and also teach them something new.
Many of these contributors work for great companies (which themselves are involved in various open source projects) inluding Mozilla, SUSE, Red Hat, Blue Systems, ThoughtWorks, KDAB, Digia. Also you will find that many of these contributors were students until recently.
Wondering what KDE/Qt is?
KDE is one of the largest international free software communities. It has an integrated set of cross-platform applications designed to run on GNU/Linux, FreeBSD, Solaris, Microsoft Windows, and Apple OS X systems. KDE is known for its Plasma Workspace, an environment provided as the default working environment on many Linux distributions, such as Kubuntu, Pardus, and openSUSE.
To find more information about KDE, please visit kde.org.
Qt is a cross-platform application framework that is widely used for developing application software with a graphical user interface (GUI) and also used for developing non-GUI programs such as command-line tools and consoles for servers. Qt is used in Adobe Photoshop Elements, Skype, VLC media player, VirtualBox, Dassault DraftSight and Mathematica, and by the European Space Agency, DreamWorks, Google, HP, KDE, Lucasfilm, Autodesk Maya, The Foundry’s Nuke, Panasonic, Philips, Blackberry applications, Samsung, Siemens, Volvo, Walt Disney, Animation Studios and Research In Motion. Qt runs on multiple platforms which include Linux, Windows, Mac OS X, Embedded Linux, Blackberry 10, Android, Sailfish and Ubuntu Phone OS.
To find more information about Qt, please visit qt-project.org.
Details about conf.kde.in
Venue: Dhirubhai Ambani Institute of Information and Communication Technology, Gandhinagar
Registration for the conference is now open. Please register yourself here and grab the “Early Bird” discount until the 15th of January. There are limited seats so hurry up! You will find accommodation options at this page.
We are working very hard to make conf.kde.in 2014 a huge success. And it will happen with the help of your participation. Looking forward to meet you all. Stay tuned for regular updates about this event on our Facebook and Twitter page.
For any queries, feel free to reach us at email@example.com.
Today KDE released updates for its Applications and Development Platform, the first in a series of monthly stabilization updates to the 4.12 series. Starting with the next Applications and Development Platform release, 4.12.2, there will also be a main…