<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>KDE.news</title><link>David Edmundson</link><description>David Edmundson</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>2024-11-14T07:21:23+00:00</lastBuildDate><atom:link href="https://dot.kde.org/authors/david-edmundson/index.xml" rel="self" type="application/rss+xml"/><item><title>Down to Business with Major Deployments</title><link>https://dot.kde.org/2015/10/06/down-business-major-deployments/</link><pubDate>Tue, 06 Oct 2015 00:00:00 +0000</pubDate><guid>https://dot.kde.org/2015/10/06/down-business-major-deployments/</guid><description>
&lt;div style="float: right; padding: 1ex; margin: 1ex; ">&lt;img src="https://dot.kde.org/sites/dot.kde.org/files/klogo-official-lineart_detailed-100.png" />&lt;/div>
KDE software has been used in many large scale deployments, including &lt;a href="https://dot.kde.org/2010/10/07/jes%C3%BAs-torres-talks-about-bardinux-spains-biggest-deployment-kde-software">universities&lt;/a>, &lt;a href="https://joinup.ec.europa.eu/community/osor/case/limux-it-evolution-open-source-success-story-never">governments&lt;/a> and countless companies.
&lt;p>One of these organizations suggested that KDE create a deployment forum so that others can benefit from their deployment experience. The forum would provide an opportunity for sysadmins and developers to ask questions and discuss problems/solutions related to deploying KDE software in large, complex environments.&lt;/p>
&lt;div style="float: right; padding: 1ex; margin: 1ex; ">&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/DSC_0460.JPG" />&lt;/div>
We have created a new mailing list for these discussions at https://mail.kde.org/mailman/listinfo/enterprise.
&lt;p>All administrators of any deployments planned or in progress are invited to join this list to share and field questions. KDE developers and people maintaining Linux distributions with KDE software will also participate.&lt;/p>
&lt;!--break--></description></item><item><title>KDE Telepathy Sprint</title><link>https://dot.kde.org/2014/04/29/kde-telepathy-sprint/</link><pubDate>Tue, 29 Apr 2014 00:00:00 +0000</pubDate><guid>https://dot.kde.org/2014/04/29/kde-telepathy-sprint/</guid><description>
&lt;p>In April 2014, we had a sprint for KDE Telepathy, KDE's foremost instant messaging client. The sprint consisted of both past and new contributors from around the world.&lt;/p>
&lt;h2>Group chats&lt;/h2>
For the sprint we decided to concentrate our hacking efforts into a few key areas that are currently weak inside KDE Telepathy. We chose group chats as it was one of the most repeated feature requests coming especially from enterprise circles. It was something we supported at a basic level but, since none of us used it on a daily basis, it did not receive the attention it deserved.
&lt;p>Firstly, we forced ourselves to use a conference room for the duration of the sprint for all our chatting purposes and made a list of every potential improvement we could find. Afterwards we picked things off the list one by one and made significant improvements to the group chatting experience.&lt;/p>
&lt;p>Our usability expert, Thomas Pfeiffer, was there with us providing valuable input from the usability point of view; thanks to that it was not just a mad hacking on features but also about making the application more usable. The screenshots below speak for themselves!&lt;/p>
&lt;img style="max-width:100%" src="http://dot.kde.org/sites/dot.kde.org/files/ktp_before_after.png" />
&lt;div style="width: 300px; float: right; padding: 1ex; margin: 1ex; border: 1px solid grey;">&lt;a href="http://dot.kde.org/sites/dot.kde.org/files/kdeconnect.jpg">&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/kdeconnect_wee.jpg" />&lt;/a>&lt;br />Answer text messages from your desktop&lt;/div>
&lt;h2>Easy chat via SMS using KDE Telepathy&lt;/h2>
During the sprint Albert Vaca and Alexandr Akulich worked on making a backend for Telepathy to talk to &lt;a href="http://community.kde.org/KDEConnect">KDE Connect&lt;/a>. This allows you to receive SMS messages from your phone and reply through a comfortable and familiar chat interface on your desktop.
&lt;h2>Reducing the bug count&lt;/h2>
Another area we focused on at the sprint was our bug count. At the beginning we had 62 reported bugs (excluding wishes and tasks), some of them had been open for a longer time. So we allocated some space on the whiteboard for a giant bug counter; whoever then fixed a bug from that list got the honor of erasing the number on the whiteboard and writing a new one.
We are now under 50 bugs, with under 50 further wishlist items.
&lt;h2>Building for the future&lt;/h2>
We didn't just hack but also discussed where to go with KDE Telepathy.
&lt;h3>Vision&lt;/h3>
According to the &lt;a href="http://techbase.kde.org/Projects/Usability/HIG/Vision">KDE Human Interface Guidelines&lt;/a>, "A vision describes the goal of the project. It can be emotive and a source of inspiration, for instance by outlining how the final product makes the world a better place. It is roughly similar to purpose or aim, and guides through the development." In order to guide KDE Telepathy's development, Thomas, our aforementioned usability expert, led a session where we defined a vision for us.
&lt;div style="width: 300px; float: right; padding: 1ex; margin: 1ex; border: 1px solid grey;">&lt;a href="http://dot.kde.org/sites/dot.kde.org/files/whiteboard.JPG">&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/whiteboard_wee.jpg" />&lt;/a>&lt;br />Whiteboard work&lt;/div>
&lt;p>The first question that was important for us was &amp;quot;Which users do we want to focus on?&amp;quot;. We decided that we want to focus on Plasma users. We do not shut out users of other desktop environments or operating systems, but we clearly focus on integrating well with Plasma and provide the best experience for Plasma users.&lt;/p>
&lt;p>The other defining question for our focus was &amp;quot;Do we want to focus on providing the best possible experience for users of popular instant messaging systems such as Facebook Chat or Google Hangouts, or do we want to focus on providing an awesome experience to users of open protocols such as Jabber?&amp;quot; Our answer to this question was that while we do not want to exclude users of popular systems, we realise that for them, we can only create an &amp;quot;okay-ish&amp;quot; experience at best, because those systems' APIs are very restricted and always subject to change. Only with open protocols we can use all of our capabilities to create a truly awesome experience for users.&lt;/p>
&lt;p>Our vision draft is still being discussed on the mailing list and will be published once it's been agreed upon by the whole KDE Telepathy community.&lt;/p>
&lt;h3>Frameworks&lt;/h3>
In KDE Telepathy we provide several plasma widgets, which need to be ported in order to run on Plasma Next. In order to do this we first had to port our libraries to work on top of KDE Frameworks. By the end of the sprint we had the contact list and chat plasma widgets fully running and working on Plasma Next. We hope to release the widgets so that they are available for Plasma Next users.
&lt;img style="max-width:100%" src="http://dot.kde.org/sites/dot.kde.org/files/ktp5.png" />
&lt;h3>API Breaks in the larger Telepathy stack&lt;/h3>
There is an upcoming change in the interfaces to the Telepathy backends that talk to the various protocols such as jabber. We need to be prepared for this change - otherwise when distributions update Telepathy, our application will cease working. We are making sure we have code ported and ready, so we can release at the same time as upstream switches. Most of these updates are inside TelepathyQt and we are working on the elements lower in the stack that will benefit not only us but also Ubuntu and Jolla.
&lt;p>Planning how to handle these two upcoming changes at once is awkward at best and required some delicate planning.&lt;/p>
&lt;h2>Wrapping up&lt;/h2>
Overall the sprint was incredibly useful in helping push our project forward both in terms of the extra development and planning moving forwards.
&lt;p>&lt;strong>Thanks to the Blue Systems Barcelona office for hosting us.&lt;/strong>&lt;/p>
&lt;p>More photos &lt;a href="https://plus.google.com/photos/101026761070865237619/albums/6003955002855280545/6003956266031555314?pid=6003956266031555314&amp;oid=101026761070865237619">here&lt;/a>&lt;/p>
&lt;img style="max-width:100%" src="http://dot.kde.org/sites/dot.kde.org/files/IMG_3635_v1.JPG" />
&lt;p>&lt;em>This document was written by the KDE Telepathy team; written using KDE Telepathy's collaborative editing features.&lt;/em>&lt;/p></description></item><item><title>Season of KDE 2013 Applications Open</title><link>https://dot.kde.org/2013/08/09/season-kde-2013-applications-open/</link><pubDate>Fri, 09 Aug 2013 00:00:00 +0000</pubDate><guid>https://dot.kde.org/2013/08/09/season-kde-2013-applications-open/</guid><description>
&lt;h2>Season of KDE is now officially open for applications.&lt;/h2>
&lt;p>To apply head to &lt;a href="http://season.kde.org/">season.kde.org&lt;/a> register as a student and click &amp;quot;Submit a proposal&amp;quot;&lt;/p>
&lt;h3>What is Season of KDE?&lt;/h3>
&lt;p>Season of KDE is a community outreach program, much like Google Summer of Code that has been hosted by the KDE community for five years straight.&lt;/p>
&lt;p>It is meant for people who could not get into Google Summer of Code for various reasons, or people who simply prefer a differently structured, somewhat less constrained program. Season of KDE is managed by the same team of admins and mentors that take care of Google Summer of Code and Google Code-in matters for KDE, with the same level of quality and care.&lt;/p>
&lt;h3>Who can take part?&lt;/h3>
&lt;p>Everyone can apply for Season of KDE. We give preference to those who have applied for Google Summer of Code and to students, but we will gladly consider applications from anyone.&lt;/p>
&lt;h3>What do I get out of this?&lt;/h3>
&lt;p>A great summer working on a really cool KDE project and gaining valuable experience. If you complete your project successfully you also get a T-shirt, a certificate, and maybe a few other goodies.&lt;/p>
&lt;h3>What is the timeline?&lt;/h3>
&lt;p>Season of KDE is a flexible project to fit around school terms, work, and other commitments, and start and end dates can be discussed with your mentor. Projects should be completed before the end of the year, a typical Season of KDE project should take around 2 months.&lt;/p>
&lt;h3>How do I apply?&lt;/h3>
&lt;p>First get in touch with a mentor about your ideas, and what projects they want to run.&lt;/p>
&lt;p>Then head to &lt;a href="http://season.kde.org/">season.kde.org&lt;/a> and follow the instructions.&lt;/p>
&lt;h3>Do I need to have a mentor before applying?&lt;/h3>
&lt;p>It is preferred. Ideally, you should contact a KDE sub-project well before applying, ask for feedback on your idea if you have one, and request a mentor directly. A list of KDE sub-project contacts is available on the Google Summer of Code 2013 &lt;a href="http://community.kde.org/GSoC/2013/Ideas">ideas page&lt;/a>. You can also apply without a mentor and we will try to find one for you.&lt;/p>
&lt;h3>Do I need to have a project idea before applying?&lt;/h3>
&lt;p>It is preferred. If you do not have one we will try to find one for you. Keep in mind that the KDE community is pretty big, so you should at least have an idea of which KDE sub-project you wish to work on.&lt;/p>
&lt;h3>Do I need to write a proposal like in Google Summer of Code?&lt;/h3>
&lt;p>No, but we would like to see a brief project plan describing what you will be working on.&lt;/p>
&lt;h3>Is it only for coders like Google Summer of Code?&lt;/h3>
&lt;p>We are willing to consider non-coding projects as well including artwork and promotion, but you should definitely get in touch to figure out the details beforehand. The &lt;a href="http://community.kde.org/Getinvolved">KDE Community Wiki&lt;/a> describes ways to get involved with KDE that do not require coding.&lt;/p>
&lt;h3>I applied for a project in Google Summer of Code but another student got selected for it. Can I still work on it?&lt;/h3>
&lt;p>Maybe, but likely not. You should ask the mentor that was assigned to your idea. We can try to find something related for you if you want, or something completely different. Let us know what you wish and we will do our best to accommodate your request.&lt;/p>
&lt;h3>Is this an extension of Google Summer of Code or connected to Google?&lt;/h3>
&lt;p>No. While Season of KDE is in many ways modelled after Google Summer of Code and administered by the same members of the KDE community, it is completely independent from Google Summer of Code and has no connection to Google whatsoever.&lt;/p>
&lt;p>—&lt;/p>
&lt;p>For further questions feel free to join our IRC channel #kde-soc on Freenode or email the admin team at &lt;a href="mailto:kde-soc-mentor-owner@kde.org">&lt;a href="mailto:kde-soc-mentor-owner@kde.org">kde-soc-mentor-owner@kde.org&lt;/a>&lt;/a>&lt;/p></description></item><item><title>New KDE Telepathy brings Better Text Editing and Improved Notifications</title><link>https://dot.kde.org/2013/04/09/new-kde-telepathy-brings-better-text-editing-and-improved-notifications/</link><pubDate>Tue, 09 Apr 2013 00:00:00 +0000</pubDate><guid>https://dot.kde.org/2013/04/09/new-kde-telepathy-brings-better-text-editing-and-improved-notifications/</guid><description>
&lt;p>Good news, everyone! The KDE Telepathy team has just released version 0.6.0 of KDE Telepathy (KTp), KDE's instant messaging suite. This version brings a number of new features as well as a large amount of bug fixes.&lt;/p>
&lt;h2>About KDE Telepathy&lt;/h2>
KDE Telepathy is an instant messaging suite built upon the &lt;a href="http://telepathy.freedesktop.org/">Telepathy&lt;/a> framework. KDE Telepathy provides text chat, video calls and file transfer services over many popular instant messaging platforms including Facebook Chat and Google Talk. In addition KTp provides libraries for embedding instant messaging or real-time collaboration inside your application.
&lt;p>KDE Telepathy follows the philosophy that communication is a service offered to applications and the desktop. A more in-depth technical explanation can be read over &lt;a href="http://www.aosabook.org/en/telepathy.html">here&lt;/a>, but in practice, this means that KDE Telepathy consists of independent components. This allows KDE Telepathy to be well integrated with Plasma by providing plasmoids and runner interfaces as well as providing the traditional contact list and chatting application. This level of desktop integration allows endless possibilities and greater freedom in the way in which you interact with your contacts. Boundaries of Telepathy however do not stop at communication, the next step is collaboration, for example games can take advantage of Telepathy and provide a multi-player capabilities without the hassle of setting up network connections.&lt;/p>
&lt;h2>New Features&lt;/h2>
This release brings in a number of major new features. An overview:
&lt;p>&lt;strong>Kopete log migration&lt;/strong>
KTp now imports logs from Kopete accounts into our log format. For new KTp users this will be asked if they wish to import when they create an account, existing users can also import logs by opening the log viewer.&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/log_import.png" style="width:80%"/>
&lt;p>&lt;strong>Clearer message notifications&lt;/strong>
KTp had some feedback to improve the notifications of new messages. KTp now shows an icon in the contact list when a new message arrives, change the icon in the system tray, and for group chats show who is typing.&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/new_messages.png" style="width:80%"/>
&lt;p>&lt;strong>Better text editing&lt;/strong>
The chat window now features tab completion for group chats, as well as text navigation for editing messages.&lt;/p>
&lt;p>KTp has made adding emoticons easier too, with a new optional emoticon toolbar.&lt;/p>
&lt;p>&lt;strong>Advanced notifications&lt;/strong>
KTp now supports setting different notifications for each of your contacts. This means it is possible to set an optional notification if your favourite friends come online, or play sounds when messages arrive from certain contacts but not others.&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/notifications.png" style="width:80%"/>
&lt;p>&lt;strong>Improved password and security management&lt;/strong>
KTp is now able to connect to password protected jabber rooms, a much requested feature. We have also improved our connection certificate handling, now using KDE SSL certificates manager and allowing the user to override invalid certificates.&lt;/p>
&lt;p>&lt;strong>Under the hood changes and cleanups&lt;/strong>
A lot of our effort has been spent in a big refactoring under the hood, getting ourselves ready for the future as well as bringing speed and stability closing over 85 bug reports in 0.6.&lt;/p>
&lt;p>0.6.0 features completely redone connection error notifications and other important UI areas.&lt;/p>
&lt;p>&lt;strong>Core filtering plugins&lt;/strong>&lt;/p>
&lt;p>KTp has an extended range of message plugins to make chatting more dynamic and interactive.&lt;/p>
&lt;p>&lt;em>Text messages can be formatted in bold or italics&lt;/em>&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/formatting.png" style="width:80%"/>
&lt;p>&lt;em>Youtube links are show and can be played directly in your chat window&lt;/b>&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/youtube.png" style="width:80%"/>
&lt;p>&lt;em>Links to bugzilla are shown inline with the bug title and resolution&lt;/b>&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/bug.png" style="width:80%"/>
&lt;p>&lt;em>When sending messages can use your KDE webshortcuts to make it quicker to send links&lt;/b>&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/search_replace.png" style="width:80%"/>
&lt;p>&lt;em>Messages containing your name are highlighted and a special notification with sound can be emitted. This is especially useful if you lurk in conference rooms&lt;/b>&lt;/p>
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/highlight.png" style="width:80%"/>
&lt;h2>Getting 0.6&lt;/h2>
After this huge list of awesome new things, you might want to try KTp for yourself! So, where to get it?
&lt;p>First of all, the source tarballs are available from &lt;a href="http://download.kde.org/stable/kde-telepathy/0.6.0/src/">the KDE download servers&lt;/a>. This contains our full set of applications and applets.&lt;/p>
&lt;p>Most distributions, including &lt;a href="http://software.opensuse.org/search?q=ktp">openSUSE&lt;/a> (in &lt;a href="https://en.opensuse.org/KDE_repositories#Updated_applications_only">the KDE-extra repository&lt;/a>), &lt;a href="https://apps.fedoraproject.org/packages/s/kde%20telepathy">Fedora&lt;/a> and &lt;a href="https://launchpad.net/~telepathy-kde/+archive/ppa">Kubuntu&lt;/a>, have packages available already or will have, soon. Note that you will need the full set of packages for KTp to work properly. In most distributions, that means installing the right repository and getting the ktp* packages.&lt;/p>
&lt;p>Of course, if you find issues or think of possible improvements, you can either &lt;a href="https://bugs.kde.org/enter_bug.cgi?product=telepathy&amp;format=guided">file a bug&lt;/a> or &lt;a href="http://community.kde.org/KTp/Getting_Involved">join development&lt;/a>!&lt;/p>
&lt;a href="http://dot.kde.org/sites/dot.kde.org/files/ktp_all.png">
&lt;img src="http://dot.kde.org/sites/dot.kde.org/files/ktp_all_small.png" style="width:80%"/>
&lt;/a></description></item></channel></rss>