The KDE e.V. report for the first half of 2015 is now available. It presents a survey of all the activities and events carried out, supported, and funded by KDE e.V. in that period, as well as the reporting of major events, conferences and mentoring programs that KDE has been involved in.
Featured Article – conf.kde.in 2015
The featured article covers a bit of conf.kde.in history and how it brought together nearly 300 students in its 2015’s edition. It presents an overview of conf.kde.in 2015 keynotes, information regarding the many talks about all sort of KDE projects presented at the conference, and details about the lab sessions devoted to game development with Qt and QML. The article concludes with some thoughts on the KDE presence in India and its massive potential for raising new contributors.
The report also describes a synopsis of member activities during the first half of 2015. The Plasma Sprint, in Barcelona, focused mostly on lowering contributions barriers, improving power management, and Plasma’s future goals. During the KDE PIM Spring Sprint, in Toulouse, several contributors started the port of Kontact Suite to KDE Frameworks 5 and did a massive cleanup of KMail reported bugs. The 3rd edition of LaKademy – the Latin-American KDE Summit – took place at Federal University of Bahia (in the city of Salvador) and contributed to establishing a regular and consolidated venue for discussing actions, making contributions of many facets, and supporting newcomers for KDE in Brazil and Latin America.
The report concludes with a summary of activities undertaken by the Sysadmin Working Group, and the contributors who joined KDE e.V. during the period. We invite you to read the entire report!
Kai Uwe Broulik reports from open source conference Augsburger Linux-Tag which happened in Bavaria last weekend.
On Saturday, 16 April I had the honor of representing KDE at the 15. Augsburger Linux-Tag, one of the oldest and largest Linux gatherings in southern Germany.
Konqi guarding the KDE booth
It was my first time attending such an event and it was a great experience. With me I had a computer running the latest and greatest KDE neon with Plasma 5.6 – hooked up to a gorgeous 4K monitor. In addition to that I brought a Nexus 5 running Plasma Mobile and an infrared remote control for browsing Plasma Media Center.
The place was quite busy and due to lots of talks and presentations going on, people stopped by in batches usually. Feedback on the new Breeze look and feel of Plasma 5 was overwhelmingly positive, kudos to the VDG and everyone involved in making this software masterpiece. Critics of our “flat design” were happy to hear that we continue to ship Oxygen style and icons, enabling you to visually turn Plasma 5 into Plasma 4 with ease.
The common architecture between desktop and phone was easily illustrated by common widgets
Plasma Mobile did its job well, getting people excited about the possibilities to come: having a full-fledged KRunner on a phone, deep KDE Connect integration, a full Linux-stack underneath, and more.
Kirigami UI concepts, especially the ability to go “forward” rather than just back, were well-received and made people look forward to our gesture-driven user interface.
Skeptics of Plasma Mobile were relieved to hear that Plasma Mobile – which is running Wayland rather than X – helped our Wayland adoption on the desktop and resources spent there benefit the entire Plasma stack.
Three input concepts, touch, keyboard, few-buton remote control; easily served using Plasma technology
Augsburg visitors ranged from a 5 year old running across the hallway yelling “how cuuuuute” Konqi is, to an elderly man proudly telling his story about how he recently switched from Windows to Linux and enjoys using Plasma and KDE Applications. I then showed him how easily he could get a full screen application launcher he got used to from his old operating system (Right-click Kickoff → “Alternatives” → “Application Dashboard”).
There were also quite a few users of alternative desktop environments and window managers who were glad to be able to use KDE software, such as KWin, Kate, Dolphin, outside a full Plasma session.
Browsing Plasma Media Center using the input device it was designed for.
In the afternoon I came across a guy from LiMux, a project by the city of Munich to migrate their software systems to free and open-source software, who are using Plasma for their desktop computers. He illustrated some of the challenges they’re facing with Plasma in such a large enterprise deployment with a sheer number of novice users. We got invited to the LiMux Hackfest in May where we will work together to prepare Plasma 5 for the requirements they have.
In conclusion, I can say the day was a success: we got lots of comments, feedback, and praise, and I am looking forward to attending this and other similar events in the future.
Special thanks to Ingo Blechschmidt of Hochschule Augsburg for inviting us and Jonathan Riddell for sending me his KDE stand-up display!
Like a routine now, the KDE PIM spring sprint was held in Toulouse again, first week of April at Ekito's city center office, many thanks to them.
First of all thank to all the participants: Franck Arrecot, Andre Heinecke, Sandro Knauß, Volker Krause, John Layt, Christian Mollekopf, Laurent Montel, Kevin Ottens, Daniel Vrátil that made of this sprint an awesome moment.
As a general theme you could say we were preparing the future of PIM with the goal of stability: reducing some library dependencies, designing a way to reach a better internal architecture, cleaner codebase and improving communication among each contributor of the suite on the release process.
Since there are plenty of different applications within PIM Suite we will break down what happened on each subproject and what benefit each thread gave to the main rope:
This sprint was kind of special because the famous John Layt was around, so the opportunity to work on removing the final uses of KDELibs4Support from PIM had to be taken! Most remaining uses of KCalendarSystem and KLocale could be ported, and the use of KTimeZone was largely contained to KCalCore implementation details. John is working on a replacement for the remaining features in KDateTime that are not yet covered by Qt, which would allow the remaining uses of KDELibs4Support code to be removed eventually. KAddressBook was able to work entirely without loading KDELibs4Support at the end of the sprint.
Daniel has been working with our awesome sysadmins on debugging and fixing an issue in the new CI that was causing (not just KDE PIM) unit tests to fail. He also worked on further improving Akonadi performance by redesigning the notification system, which opens doors to a new set of cool features like starting Akonadi agents on-demand and shutting them down when no longer needed.
Laurent did plenty of bug fixing and worked on the QtWebEngine support within PIM, this will later allow us to get rid of the unsupported QtWebkit.
Christian presented to us the state of Kube and Sink, the two new open source Kolab projects, how these would work and what are the issues they are facing. This overview helped us thinking of a possible integration when the project would reach a more mature phase.
Sandro and Christian started to work on a way to represent mails in QML instead of plain HTML. With HTML all interactions must go via HTML too so e.g. start decryption or show more info are links inside a browser window. With rendering to QML we can directly interact with the mail via QML Elements buttons, what is a cleaner way of user-feedback loop. MimeTreeParser was prepared by Sandro to render to both outputs and mimetreeparser was cleaned up and refactored while at the sprint. Also it was discussed how to get rid of unnecessary dependencies, to untangle MimeTreeParser.
Andre took a dive into our crypto libraries, moving some generic non-GUI code from libkleo into QGpgMe. He also started preparing the QGpgMe library to be moved to GpgMe upstream. It was also discussed how error messages could be more helpful and how the API of QGpgMe could be modified to be more easy to use.
The Zanshin team, Kevin and Franck, added a couple of fixes and prepared a 0.4 release and designed a road map for the next 0.5 release.
One of the great benefits of this sprint was to share some experiences that have been made in Zanshin and that can be extend into the rest of the suite. The architectural work and experimentation done on Zanshin lead us to apply some of its principle to PIM, that is what we called the "zanshinification". We discussed how well the Zanshin onion architecture would fit the KDE PIM codebase and laid down a step by step plan with a couple of critical steps where we had to make sure performance are still good enough. We think this architectural change would bring more stability, readability within the codebase and might help to attract new contributors. We have to keep in mind how important PIM is as one of the most feature-filled suite of personal information management in free software.
Release cycles and version numbers was another big topic on the sprint. Looking at how to manage versions among different PIM projects in a smoother way, Sandro identified some part of the process that could be improved. The main idea is to make sure everyone is aware of upcoming releases and changes to the dependency set of the software, and to make this clear to packagers as well.
Long live KDE PIM!
Your happy PIM team, Andre, Volker, John, Christian, Sandro (front), Franck (back), Laurent, Daniel
KDE contributors showing their personal visions at Akademy 2015
KDE is a highly diverse community and every one of our contributors has his or her own motives, such as having fun, developing new skills and meeting nice people. However, a common desire unites all of KDE: to change the world for the better. This shared motivation, although the major driving force behind KDE, has never really been made explicit.
A survey conducted among KDE contributors and users last year showed that the respondents were missing exactly that: an explicit vision and strategy for KDE. As a result, we began working on a shared vision at last year's Akademy (KDE's annual contributor conference). After months of collecting ideas and holding open discussion across our community, we have united around a simple statement of what we want to achieve:
A world in which everyone has control over their digital life and enjoys freedom and privacy.
This is our vision.
Our Vision in Detail
Each part of the vision has been carefully chosen to convey our intent and scope:
A world: We are not doing this only for ourselves, our friends and family, our employer or customers, and we recognize no geographical barriers to our work. We want to change no less than the world we live in.
Everyone: The work should not just be for a small group of people. The fruits of our work should be available to all, without being restricted to materially, educationally or socially privileged people.
Control: KDE has always aimed to put people in control. We don't want to hand over control to anybody else. Not to some service providers, not to some hardware vendors, not to governments, not even to KDE. KDE wants to put you in the driver's seat.
Digital life: We want to allow people to control every aspect of their digital lives: Hardware, software, data, communication, everything. Of course, there is much more to life than the 'digital' part. While we all want freedom and control in the other parts too, influencing that is beyond KDE's scope, so we limit our vision to "digital life".
Freedom: We believe that freedom is a prerequisite to true control. Some may feel in control of a proprietary application as long as it obeys their commands, but without the freedom to make changes and share them, they are entirely reliant on the vendor's benevolence for this apparent 'control'.
Privacy: In a world where our privacy is increasingly threatened, we wanted to emphasize its importance. Freedom without the right to privacy is no freedom at all.
Next Steps: From Vision to Mission
Our vision unites KDE in common purpose. It sets out where we want to get to, but it provides no guidance on how we should get there. After finalizing our vision (the "what"), we have immediately started the process of defining KDE's Mission Statement (the "how"). As with all things KDE, you are invited to contribute. You can easily add your thoughts on our mission brainstorming wiki page.
If you share our vision you can also support us by helping to fund our work, either via a regular payment as an official Supporting Member or via a one-off donation.
QtCon 2016 Call for Papers is open. The event will assemble KDE Akademy, VideoLAN Developer Days, Qt Contributors' Summit, FSFE Summit and KDAB Qt training day. We invite contributors to these projects to present their work and insight at QtCon 2016. The conference will take place from 1st to 8th September in Berlin, Germany. The talks will be from 2nd to 4th with KDE continuing with BoFs till the 8th
If you know of someone else who should present, please nominate them. For more details see the proposal guidelines and the Call for Papers.
The submission deadline is 15th May, 23:59:59 CEST.
About QtCon 2016, Berlin, Germany
QtCon is a congress of hundreds of developers, translators, artists, writers, users, supporters, sponsors and other people interested in collaborating with our FLOSS projects. Contributors from KDE, Qt, FSFE and VideoLAN usually meet annually in their respective events to share their ideas and knowledge, develop new technologies and improve existing ones. They also make plans for the future of their projects and meet people from their communities face to face. This year all these events will gather to celebrate a very special moment in the history of the FLOSS movement: KDE, one of the largest communities of free software in the world is celebrating its 20th anniversary. Additionally, VideoLAN and FSFE also celebrate their 15th anniversary. It will be a historic event with trainings, talks, meetings and coding sessions. Companies building on technology of these projects, and those that are looking for opportunities are welcome.
For more information, please contact the QtCon Team
KDE has a long tradition of providing user interface components beyond the basics that are offered in Qt itself. With KDE Frameworks 5, these have become more easily available for Qt developers who are not part of KDE. Now, with KDE's focus expanding beyond desktop and laptop computers into the mobile and embedded sector, our QWidgets-based components alone are not sufficient anymore. In order to allow developers to easily create Qt-based applications that run on any major mobile or desktop operating system (including our very own existing Plasma Desktop and upcoming Plasma Mobile, of course), we have created a framework that extends the touch-friendly Qt Quick Controls: Welcome Kirigami UI!
Kirigami UI isn't just a set of components, it's also a philosophy: It defines precise UI/UX patterns to allow developers to quickly develop intuitive and consistent apps that provide a great user experience. Some concepts are: Actions are available in two drawers and additionally through some shortcuts (buttons or swipes); actions and options are distinguished into global ones and contextual ones, put in two different drawers in the opposite vertical sides of the screen; app's content is organized in pages that you can browse through with horizontal swipes. The Kirigami Components for smartphones are optimized to allow easy navigation and interaction with just one hand, making it ideal for using applications casually "on the move". Kirigami UI is not only for smartphone applications, however: It will allow to create convergent applications, which are not simply the exact same user interface scaled to different sizes, but morphing between optimized interfaces based on the input method and screen size, changing as the context changes (e.g. flipping over a convertible, docking a phone). Another important concept is non-invasive pop-ups to undo an action, rather than confirmation dialogs.
As Kirigami aims to seamlessly integrate with the basic sets of controls offered by QtQuick, such as QtQuickcontrols, it does not duplicate the effort to provide essential controls such as buttons and text input fields, but provides ready to use, high level controls to implement its design philosophy and UX guidelines.
Why the name Kirigami? Kirigami is a Japanese art of papercraft. It is derived from origami, but adds cutting as an additional technique to folding. The reason we chose it as the name for our UI framework is that different layers or "sheets" in the UI are an important element in its design philosophy. Navigating through screens and the pop up of the drawers are like flicking through sheets of paper.
The first real-world application implemented using Kirigami Components, Subsurface-mobile, has recently been released for Android, a version for iOS is currently in the works, and the cool thing is: The two versions share most of their code! The Subsurface mobile team (which is lead by Intel's Chief Linux and Open Source Technologist Dirk Hohndel and has a certain Linus Torvalds as one of their core contributors) and their group of enthusiastic beta testers have worked closely with the developers and designers behind Kirigami to improve both the framework and the application based on their real-world experiences.
The Kirigami Components are planned to become part of KDE Frameworks 5, but will initially be released stand-alone around the end of April. They are aimed to be a Tier 1 framework, meaning they have no other dependencies apart from Qt, and therefore won't increase your application's size any more than necessary.
Long story short: If you're planning to build a mobile or convergent mobile/desktop application using Qt and would like to give your users easy ways to navigate through pages and access functions, be sure to give Kirigami UI a try!
In March, the yearly meeting of KDE's Plasma team was held in Geneva, kindly hosted by the European Centre for Nuclear Research (CERN). In-person meetings provide unique opportunities to work together face-to-face, at high bandwidth to tackle problems together and plan for the future. As there were some other groups present during this meeting, notably the visual design group and the Wiki cleanup team, there was ample opportunity to think outside of the Plasma box.
The Plasma team discussed many topics that are currently being worked on, or need more attention, but also sat down to hack on the code. The result was a nice mix of hands-on activities and dreaming of the future.
As the Wayland port is nearing completion, the team had a closer look at the current state. Bugs, that have gone previously undiscovered have been identified and fixed, code that lived in branches was reviewed and merged, and holes in the implementation were discussed. Most Plasma developers actually returned home with a fairly functional Plasma/Wayland session, which will accelerate dogfooding and make tracking of problems easier. An ongoing effort is also to spread the work on Wayland across more shoulders.
A Plasma/Wayland session is currently somewhat functional, but not suitable yet for being a daily driver, or even beta testing. The goal is to have a beta-level version ready by summer and fix bugs and regressions from there. The final Plasma/Wayland session should be hardly any different from an X11 session in terms of functionality and features, but run just a little bit smoother and carry less annoying idiosyncracies of a typical X11 session or jerky animations.
Together with the visual design group, many smaller and bigger issues have been discussed, and fixed. Among the bigger parts was a redesigned settings module for Plasma themes, featuring live previews and a more user-friendly design. This new module has already been merged into Plasma master (which currently is the tree that will eventually become Plasma 5.7 this summer). A lot of work has been put into correcting and completing usage of icons. New icons have been created, applications' icon usage has been reviewed and fixed. The result are lots of small fixes all over the place, which result in a yet more consistent look and feel.
One of the central roles of a desktop is to show and switch between application windows. This means that the "desktop shell" has to be able to communicate with applications (it wants to know its title, icon, set its state, etc.). To further improve the integration between the desktop and the applications, the Plasma developers have designed the Windowmetadata framework, which provides bi-directional communication between applications and the desktop to allow for a richer experience. The results will be better previews, and improved functionality of the task manager. The Window Metadata framework has been designed to be independant of the desktop or window decoration that might, or might not be present, and thereby addresses one of the major concerns with client-sidewindow decorations. The Window Metadata framework is still in its early design phase, so if you are interested in working on this topic, now is an excellent time to get involved.
Bits and Pieces
Among other things that have been the topic of this meeting are
Documentation for developers. Plasma 5 has been quite radically redesigned under the hood, that means that some of the documentation now needs a revamp. The docs and Plasma teams sat down and reviewed a preliminary developer guide, and jointly created a list of things to be improved in there, before it can be made available to a wider public.
The weather widget, which has been re-added to the latest Plasma 5.6 release has been reviewed, and a new visual design has been created for it, likely to be realized by the next Plasma release, 5.7, this summer.
Together with the VDG, some of the system settings modules have been reviewed and design improvements have been proposed.
The Plasma team would like to thank the KDE e.V. for their generous support of our travel costs. If you are using Plasma and would like to support its development, we encourage you to sign up as a Supporting Member or to donate.
Tuesday, 22 March 2016. Today KDE releases a feature-packed new version of its desktop user interface, Plasma 5.6.
This release of Plasma brings many improvements to the task manager, KRunner, activities, and Wayland support as well as a much more refined look and feel.
Slicker Plasma Theme
Breeze Color Scheme Support
The default Plasma theme, Breeze, now follows the application color scheme allowing for a more personalized experience. A new 'Breeze Light' together with 'Breeze Dark' theme can be used to bring back the previous behavior. Additionally, tooltip animations have become more subtle.
Supercharged Task Manager
Multitasking has just become easier. The much improved task manager in Plasma 5.6 now displays progress of tasks, such as downloading or copying files.
Media Controls in Panel and Tooltips
Moreover, hovering a music or video player shows beautiful album art and media controls, so you never have to leave the application you're currently working with. Our media controller applet that shows up during playback also received some updates, notably support for multiple players running simultaneously.
Jump List Using Firefox Jump List Using Steam
Not only did we improve interacting with running applications, starting applications gets in your way less, too. Using Jump Lists you can launch an application and jump, hence the name, to a specific task right away. This feature is also present in the application launchers.
KRunner's Smoother look and Folderview in Panel
There are many refinements to the overall visuals of Plasma in this release. KRunner gained support for drag and drop and lost separator lines to look smoother while icons on the desktop traded the solid label background for a chic drop shadow. Users that place a folder applet in their panel can enjoy improved drag and drop, support for the back button on a mouse as well as choosing between list and icon view. On the more technical side, many small fixes to hi-dpi scaling have found their way into this release.
Another feature returns from the old days, the weather widget.
On the road to Wayland
Plasma using Wayland
With Plasma 5.5 for the first time we shipped a Wayland session for you to try out. While we still do not recommend using Wayland as a daily driver, we've made some significant advances:
Window decorations are now supported for Wayland clients giving you a beautiful and unified user experience
Input handling gained all features you've come to know and love from the X11 world, including 'Focus follows mouse', Alt + mouse button to move and resize windows, etc
Different keyboard layouts and layout switching
Tech Preview System Integration Themes
We are trailing a tech preview of Breeze themes for Plymouth and Grub, so Plasma can give you a complete system experience from the moment you turn your computer on.
Also previewed in simple systemtray, an experimental systemtray replacement. Plasma Media Center remains in tech preview but work is ongoing for Plasma 5.7.
All interested students are encouraged to begin working with the KDE community.
The KDE GSOC guide is a good place for students to start before beginning to create their proposals. The KDE community creates software in teams; students should find a team working on software they want to help with, get to know team members, familiarize themselves with the code-base, and start fixing bugs.
Mentors are presenting their ideas for students as an aid to students creating their proposals. Students will use each team's preferred channels, but can ask general questions in #kde-soc on freenode IRC, or KDE-Soc Telegram group.
The KDE Student Programs team looks forward to getting mentors signed up in Google's new SoC webapp, and meeting with prospective students before student applications begin.
The people who package and distribute our software to the world are crucial to our user's experience. In keeping with our original KDE vision, we want to improve the working relationships between distributions and KDE developers. Not only do we want to foster professional friendship, but we also want to help our software shine in each distribution.
KDE is distro-agnostic. We do not prefer any distributions over others, and want our software to run everywhere. This extends beyond Linux; we want our software to work for our users on Windows, Mac, BSD and Android as well. Our focus is always on our users having the best experience possible.
We are aware that the more closely we cooperate, the better the experience for all, including those who package our software, and we think that open and free communication is the best way to cooperate. KDE developers should be able to tell distributions what our software needs from a distribution in order to work best. And in turn, distributions should be able to tell us what makes our software easy to distribute.
To centralize this communication, we have created email@example.com. We'd encourage everyone who is interested in improving the collaboration between KDE and distributions who distribute our software to join this list. The list is not for packagers only; KDE-distro-packagers is for packaging issues. We want to extend the communication to everyone interested. So whether you are part of KDE or part of a distribution team or both, please subscribe now at https://mail.kde.org/mailman/listinfo/distributions.
한국LUG 사이트는 1024 x 768 해상도(운영자 노트북:14")에 최적화 되어 있습니다. : LINUX FANSITE
WWW.LUG.OR.KR Server is made by CentOS Linux, P4 1.8G, Memory 512MB, Main HDD 160GB, Backup HDD 40GB and LAMP, qmail MTA.
CentOS Linux & Mozilla Firefox UTF-8 Base Created.
1998-2016 www.lug.or.kr Directed By Great Dragon, Kim.
LUG 포인트 정책 : [회원가입 : +100점] [로그인(하루한번) : +100점] [글쓰기 : +20점] [코멘트 : +10점] [다운로드 : -200점] [질문 포인트 : 최소 200점]
데스크탑 프로그래밍(gcc, g++, wxGTK[wxWidgets] 등)은 "Fedora"를 사용하고, 서버 운영(WEB, FTP 등)은 "CentOS"를 사용하시길 권장합니다.
도전하는자, 자신을 투자하는자만이 뜻하는바를 이룰 수 있다.
Information should be Exchanged with Interactive, not One Way Direction.
관리자 Be Maker!
인생에서, 100% 순이익을 보장하는건 없다. 1%의 지식을 나눔으로써, 가끔씩 손해볼 필요도 있다.
그대가 가진 1%의 지식만이라도 공공을 위해 포스팅하라. 손해본다는 생각이 앞선다면 그대의 인생은 힘들어질것이다.
자신이 가진 지식의 1%도 투자하지 않고, 오로지 자신의 이익만 탐하는자와는 동지가 되지마라.
만나서 대화하면 모두 좋은 사람들이지만, 유독 인터넷에서만 자신을 밝히지 않고, 좀비로 서식하는 사람들이 많다.
부지불식간[不知不識間], 좀비(하류) 인생이 될지도 모르니, 항상 자신을 경계하도록 하라.
1. CentOS Linux
2. gcc로 공부하는 C++