I just received another anonymous happiness package, this time personal:
You have worn many hats in open source over the years, not just as a contributor, but also as a mentor. I put a lot of high value into your thought-out opinions and insights. You have a unique and open-minded way of thinking about things, in open source and personal things alike. I’m thankful that we have people like you in open source communities to build better software and also to build better communities. I am lucky to have someone like you around. Thanks for being there always.
Lots of love.
What can I say? I am feeling overwhelmed. Thank you so much to whoever has sent me this bit of love!
Dear anonymous happiness sender,
I woke up this morning to your love message for the WikiToLearn community, sent through happinesspackets.io. The e-mail address used to send the packet is only read by a few people, so I am reposting this love for the whole community to enjoy. Here are the contents of the packet:
I feel totally overwhelmed, excited and very, very grateful. Thank you for caring. You people are just unbelievable. You are a bunch of craziest, most awesome and the most positive people I’ve ever met. You inspire me to give back to the community.
I wish I could express properly what I’m feeling right now.
Thanks for everything guys. Sending hugs, you crazy, amazing people!
What can I say, if not sharing the love for the amazing community that got together? Your words are beautiful and inspiring, and I personally feel extremely happy to have contributed, in my little part, to create such great vibes.
Dear anonymous sender, I do not know who you are, but lots of thanks and love to you too.
Love only grows if shared.
My name is Marcos Ebrahim. I’m an Egyptian artist and illustrator specialized in children’s book art, having 5 years experience with children’s animation episodes as computer graphics artist. I have just finished my first whole book as children’s illustrator on a freelance basis that will be on the market at Amazon soon. I’m also working on my own children’s book project as author and illustrator.
Children’s illustrations and concept art in general or children’s book art specifically.
Because I’m not a member of any children’s illustration agencies, associations or publishing houses yet, I’m now doing this work on a small scale as a freelancer. I changed careers to be an illustrator a few months ago, so I can’t call myself a professional yet. I hope to achieve that soon.
Nathan Fowkes‘ works and illustrations. I found this illustrator and concept artist on a website that called him “the master of value and colour”. I was lucky engough to study online (an art program by Schoolism) under his supervision and learn a lot. However, I’m not a brilliant student
Other great illustrators and artists I like: Goro Fujita, Marco Bucci, Patrice Barton, Will Terry, Lynne Chapman, John Manders and many others. I always look forward to seeing their art works to learn from them.
About three years ago, when I was trying to use my new Wacom Intuos tablet for painting and drawing, practicing studies from the great Renaissance masters as fan art.
Let me describe it like this: “The Undo-Time Machine — the great digital button”. Beside the ability to make changes in illustrations easily, I found its benefit when I tried to work with authors and they asked me to make changes that I couldn’t have made in traditional painting without redoing the illustration from scratch.
I used to surf Youtube for viewing Illustrations and artists demo their work. Then I heard about Krita as open source art software. So I decided to search more and found out that the illustrations made with it could be similar to my work, so I should devote some of my time to know more about it and try it. Then I searched out more learning videos on Youtube. Frankly, the most impressive and helpful one was a long video tutorial by the art champion of the Krita community, David Revoy, making a whole comic page from scratch using Krita. He showed the whole illustration process, as well as the brushes and tools he provides for others to use (thank you very much!).
I think the Krita program has a user-friendly interface and tools that become more familiar when I configure the shortcuts similarly to most popular other art programs. This make it easier to work without the need to learn many things in a short time.
I think the most wonderful thing is the brush sets and the way they look like real-world tools. In addition some other tools like the transformation tool (perspective) and the pop-up tool.
Also I can say that working with Krita is the first time that I can work on one of my previous sketches and achieve a good result (according to my current art skills) that I’m happy with.
As I mentioned to the Krita team, there are some issues that we could call bugs. However, I know that Krita is in development and the great Krita team makes things better from one version to another and add new features all the time. Thanks to them and hoping that they will continue their great work!
I think that Krita, as open-source art software, could soon compete with commercial art software if it continues on this path (fixing bugs and adding new features).
Frankly, I’ve only recently started to use Krita and I’ve finished only two pictures. One I could call an illustration, the other is the background of my art blog, trying to use the wrap tool to make a tiled pattern. You can see this in the screenshots.
I prefer to make a sketch, then work on it adding base colors and adjusting
the lighting value to reach the final details.
I add new works to my art blog once or twice every month or more
often, depending on the time I have available and whether I make anything
All the best wishes to the great Krita team for continuing success in their
work in developing Krita open source software for all artists and all people.
This is not a GNOME vs Plasma comparison, this specifically for Ubuntu and its users, considering the innovative vision they had till now. Just very personal thoughs ordered by importance for Ubuntu success in my opinion.
The most important reason for me is that the new Ubuntu user generally was a Windows user. Plasma by default has a Windows-like look and feel: panel at the bottom with an icon to open a menu and search/launch applications and files, a task manager and a system tray. I installed Plasma to many Windows users during the years and they found it more intuitive than Ubuntu Unity and probably than GNOME 3. In fact I tried GNOME 3 many times but it took a while before I was able to understand the GNOME’s vision for workflow. It’s very interesting and innovative, but it’s imposed by default and you will learn how to use it well only if you want to do so or if you are a very experinced user of other particular UI. The Windows user that try Linux just want a working environment. I saw that Windows users that tried Plasma were satisfied from the first moment, start working and after a while (days, weeks) they customized their UI and explore new workflows, probably when they have free time and aren’t stressed by work.
Who like Unity experience can easily get it from a fresh Plasma installation by using a Look&Feel package. There is already a package for that on KDE Store. Eventually, the Ubuntu installer could provide a choice at the end of the process asking which experience the user prefer (Windows-like/Plasma-default, Unity-like, Mac OS-like etc).
KDE software, including Plasma and KDE Applications, is generally very simple and intuitive by default, but provides advanced features that user can easily discover with its own curiosity. Instead GNOME has a precise vision about minimalism, that means very elegant product but often also missing very important features for productivity.
KDE is developing its alternative to Android with many tech things in common with Ubuntu Touch. Ubuntu enthusiasts’ experience with Qt and QML could be used in Plasma Mobile world. At the moment Ubuntu Touch apps can run in Plasma Mobile.
The original idea about convergence of UIs born in KDE. Canonical developed it with Ubuntu Touch and now Plasma Mobile and Kirigami are continuing that vision. Convergence is pursued also by Google and Microsoft and in the future it will be a very common feature. Smartphones becoming desktop PCs when plugged to keyboard, mouse and monitor, tablet becoming laptop, files and configurations shared across different form-factor devices are here. Plasma and Kirigami takes advantage of the best technologies for this purpose like Qt/QML and Wayland.
Let’s be honest: Plasma Mobile and others will not be real alternatives to Android in the short term. But being in the mobile world, on Android or iOS, is very important for every software manufacturer and in fact KDE litterally did a revolution with KDE Connect that improve the desktop experience with Android. But think also to apps like Nextcloud, both available on Linux desktop and Android that sync our files. To provide a better Plasma and KDE software experience we need this kind of companion apps on Android and iOS. Kirigami is here to provide a cross-platform UI framework for Linux Desktop, Windows, Mac OS, Android, iOS and Plasma Mobile.
Though Gtk could be a good product, its focus is on Linux desktop and it’s developed mostly for GNOME’s vision. KDE software uses Qt instead, that is one of the best products in the industry and it’s available on Windows, Mac OS, Android and iOS. While many developers prefer Gtk for their Linux apps, if the purpose is promoting FOSS we should open to other platforms and as I said, especially on Android and iOS because we currently don’t have a mobile alternative platform.
KDE Neon provides a new way to join development by providing a complete set of builds, including directly from git-stable and git-unstable repositories. Also, using Docker images of KDE Neon users are able to quickly test new features providing feedbacks or to hunt bugs. I find very useful to try a daily build to check if a bug was fixed before I report it.
KDE software, including Plasma and Applications, can download very different types of addons from KDE Store without visiting any Web page, directly from applications: Plasma widgets, Plasma themes, Freedesktop icons, Service Menus for Dolphins, skins for Yakuake and many many others. We all see the success of Google Play Store and Apple’s one, the KDE Store and OpenDesktop in general is a step forward hosting addons. KDE integrations for them is continously improving: also Plasma Discover, the KDE’s software center, can manage addons from the KDE Store.
Very personal thought: Breeze theme looks more modern and it’s adopted also in non-KDE products, for example Breeze icons are now used in Libreoffice.
We are happy to announce the next release of LabPlot!
The concise list of changes is available in the changelog. In the following we describe the most important new features in more details.
Beginning with the previous release, LabPlot is available for the Windows platform. Now we further extend the support for different operating systems and starting with this release LabPlot will be available for Mac OS X, too. We’re providing a Mac OS X bundle in our download section.
This is the very first release for Mac OS X and we consider it “experimental”. More time and polishing will be invested into this in future but we want to share this already now and to collect some feedback.
Two major contributions to this release were done during the “Google Summer of Code 2016” program last summer. Fábián Kristóf added the support for the FITS format. FITS is an open standard file format widely used in the scientific community to store structured as well as unstructured multi-dimensional data. It is now possible to import different data units stored in a FITS file into LabPlot’s data containers. The screenshot below shows the import dialog with a FITS file and a two-dimensional data array imported into the matrix container and the image preview of it:
One of the major features of the FITS format is the ability to store the metadata in human-readable headers. Such headers are stored in the file, in addition to the actual data, as key-value pairs in the ASCII format and provide additional information about the origin of the data, its size, used measurement devices, etc. Fábián implemented the tool FITS Metadata Editor that allows to inspect and to modify the metadata. This editor parses the metadata part of the selected FITS file only and shows all available headers in a tree view. Already existing key-value pairs can be modified or deleted, new pairs can be added. It is also possible to open and to edit more then one file at the same time.
More screenshots are available in Fábián’s blog.
Prakriti Bhardwaj worked during GSoC2016 (blog ) on the Theme Manager for LabPlot which allows the user to quickly change the appearance of a plot and of all its curves. This selection together with the theme previews is available in the properties widget and in the context menu of the plot:
There are 13 different themes available at the moment:
We continue to work on the support for different computer algebra systems via Cantor. In this release the support for Julia vectors and tuples in CAS worksheets (requires Cantor v. 16.12 or higher) was added. Thanks to the work done by Ivan Lakhtanov during GSoC2016 who added Julia backend to Cantor (check Ivan’s blog), it was an easy task to add Julia to LabPlot.
Similar to the previous release, we invested a lot of time into the data analysis functionality in LabPlot. The already available capabilities for data fitting were extended – many new pre-defined fit models like Gompertz, Weibull, Log-Normal, Gumbel distributions, etc. were added. The available fit-models are now grouped thematically in categories and a LaTeX-rendered preview of the mathematical function is shown for each pre-defined fit model.
To have more influence on the fit procedure, the fit parameters can be fixed now or constrained by some boundary conditions (lower and/or upper limits).
New algorithms for data reduction were added. These algorithms allow to greatly reduce the number of points in the curve to be considered without changing the appearance of the curve to much. There’re many algorithms known to achieve this and we implemented couple of them like Douglas-Peucker, Reumann-Witkam, etc.
To further close the gaps to LabPlot1.x (and other similar projects), numerical differentiation (up to the 6th order) and numerical integration (rectangular, trapezoid and Simpson methods) were implemented. Similar to other analysis functions, the user can control these new functions via different parameters and options.
Support for LaTex-typesetting in LabPlot was strongly extended. LabPlot allows now to enter complete LaTeX documents everywhere where LaTex-syntax is supported (text label on the worksheet, plot title, etc.). With this, the user can now use documents with specific header and numerous packages for LaTex.
In LabPlot 2.4 there is new configuration parameter which allows to use different LaTex engines (LuaLaTex, XeLatex, pdfLaTex, LaTex) – the user can decide which rendering path to use and can e.g. select XeLatex to use Unicode in LaTex.
Also, there is a runtime check now in the application to disable LaTeX typesetting if no LaTex installation and other required tools are found on the system.
Among other smaller new features (check the changelog to see the full list of changes) we want to mention the new presenter mode for worksheets which shows the worksheet in the full-screen mode:
Today the Kubuntu team is happy to announce that Kubuntu Zesty Zapus (17.04) RC is released . With this release candidate, you can see and test what we are preparing for 17.04, which we will be releasing April 13, 2017.
NOTE: This is a release candidate. Kubuntu pre-releases are NOT recommended for:
* Regular users who are not aware of pre-release issues
* Anyone who needs a stable system
* Anyone uncomfortable running a possibly frequently broken system
* Anyone in a production environment with data or work-flows that need to be reliable
Getting Kubuntu 17.04 RC:
* Upgrade from 16.10: run `do-release-upgrade -d` from a command line.
* Download a bootable image (ISO) and put it onto a DVD or USB Drive : http://cdimage.ubuntu.com/kubuntu/daily-live/20170408/
Please see Release Notes for more details, where to download, and known problems. We welcome help to fix those final issues; please join the Kubuntu-Devel mail list, just hop into #kubuntu-devel on freenode to connect with us or use the Ubuntu tracker 
1. Kubuntu-devel mail list: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
2. Official Ubuntu tracker: http://iso.qa.ubuntu.com/
Springtime is here. So start planning for all the summer conferences. The KDE yearly summer conference, Akademy, takes place in the south of Spain from July 22nd to July 27th.
Akademy is a great opportunity for all community members to tell their fellow KDE-ers about the things they have been working on. It provides a friendly environment where people contribute to the wonderful projects of KDE.
We encourage everyone to give a presentation. You can register a presentation here.
More than 10 years ago, when I was a CC student, I don’t know how many times I created a bit of code (not the best code in the world, not the sanest, but it fixed a problem that I was having) and I would get the courage to send an e-mail to the project mailing list, they would think the idea was nice and then… I would throw the code into the trash because I was too afraid to send broken code or code that wasn’t perfect.
Before the fire age, when SVN was still used in the KDE repositories, I created patches for Amarok, for Ark, for K3b, for Juk, none of them had the light of the day shinning on their little faces. All of them had a premature death on my recycle bin, a few of them didn’t even bothered to cry before being deleted without mercy because of my adolescent impulses, and no, I’m not proud of that, I think that if I had the courage to send it those applications could be much better nowdays and I would have made a difference back then.
It really took me a while to realize that all code matters from small one liners that fixes a typo to huge amounts of code that fixes a really strange bug that only you appear to have, or staying on a irc channel (or gitter, for those new fancy kids) and answering questions or having questions to be answered… Remember that project members don’t bite, and if they do you can always bite back.
I don’t know how many times I’v send a 2 – to – 3 lines patch to $project and the maintainer thanked me for doing that, because it was something that always bothered him but at the same time it was such a small thing that he never had the time to stop doing the more important thing that he was doing at the time to actually stop and look a it. And it felt good.
If you are a professor, if you represent an university, please adopt a software, this will really lower the entry bareer for your students as they would need to work on the app for a few semesters (and if I may say so, pick one of KDE Edu or KDE Games applications, they usually small and good for a student to work with), but if you are just somebody that would like to start contributing with anything:
Really, it doesn’t matters if it’s a patch that only contains one line or two, what it matters is that you had to stop what you where doing to fix anything in an application without expecting money to do so, for the sake of your own knowledge and also to help others that could be happy because a silly bug got fixed.
Do you also know that the KDE project has more than 500 applications and libraries that could need a bit of help?
A week after the alpha release, we present the beta release for Krita 3.1.3. Krita 3.1.3 will be a stable bugfix release, 4.0 will have the vector work and the python scripting. The final release of 3.1.3 is planned for end of April.
We’re still working on fixing more bugs for the final 3.1.3 release, so please test these builds, and if you find an issue, check whether it’s already in the bug tracker, and if not, report it!
Things fixed in this release, compared to 3.1.3-alpha:
We are still struggling with Intel’s GPU drivers; recent Windows updates seem to have broken Krita’s OpenGL canvas on some systems, and since we don’t have access to a broken system, we cannot work around the issue. For now, if you are affected, you have to disable OpenGL in krita/settings/configure Krita/display.
Note for Windows users: if you encounter crashes, please follow these instructions to use the debug symbols so we can figure out where Krita crashes.
A snap image for the Ubuntu App Store is also available. You can also use the Krita Lime PPA to install Krita 3.1.3-beta.1 on Ubuntu and derivatives.
For all downloads:
I am pleased to announce that Qt 5.9 Beta is now released. Convenient binary installers are available for trying out the cool new features coming in Qt 5.9. With this release we are adjusting the release process to make it easier for users to check out the upcoming release conveniently using the online installer.
Qt 5.9, scheduled to be released at the end of May, completes the work started with Qt 5.7 and 5.8 to take Qt 5 to the next level. Compared to Qt 5.6 LTS we have added a lot of new features such as fully leveraging C++11, a new configuration system, new graphics architecture, a new set of Qt Quick Controls, convenient support for Wayland multi-process, Qt 3D, and many, many more. We have also worked hard to improve the performance to be even better across the board, but especially on embedded hardware. Our target is that a Qt application running on Qt 5.9 not only has more features to choose from, but also runs with better performance and increased maturity compared to an earlier version of Qt.
With Qt 5.9 we are slightly adjusting the release process of Qt. After the Beta that was released today we will push out multiple new Beta N releases using the online installer. With the new approach it is easier than before for users to test the features and provide feedback (via bugreports.qt.io). During the beta phase we expect to have new Beta N releases with 1-2 weeks intervals. When the maturity has increased sufficiently we will create a release candidate and then the final release of Qt 5.9.0. These will be made available directly via the online installer, we are not planning publish separate blogs for the subsequent beta releases and release candidates. In addition to binaries, source packages of each beta release are of course also available for those who prefer to build themselves.
I hope many of you will install the Qt 5.9 Beta release(s), test and provide us your feedback to complete Qt 5.9. For any issues you may find, please submit a detailed bug report to bugreports.qt.io (please remember to mention which beta you found the issue with). You are also welcome to join the discussions in the Qt Project mailing lists, developer forums and of course we encourage you to contribute to Qt. You may also want to check out the list of most important new features in Qt 5.9, as well as the new features in Qt 5.8 and new features in Qt 5.7 – in case you are still using Qt 5.6 LTS.
More than one year after the 3.0.1 release, here's a new minor release of Icemon: 3.1.0.
Lots of bug fixes and small code refactorings, but also a few feature additions made it into this release.
Here's the changelog for the 3.1.0 release:
Features: - Summary view: Multiple improvements (#23) - Displays average time for each submitted jobs - Added display of average build time for finished jobs - Added scheduler hostname option (#27) Bugfixes: - Fixed summary view stateWidget color not updated correctly (#23) - ListView: Sorted file sizes correctly (643abfbbdeed806aa5a08f0c1cfcdaf7ba79d748) - Fixed filtering in detailed host view (#26) Internal Changes: - Lots of cleanups, more strict compiler flags, etc.
$ git clone https://github.com/icecc/icemon $ git checkout v3.1.0
A brief note: If you're a developer or user of input methods in the free desktop space, or just interested in learning about "How does typing Chinese work anyway?", you might be interested in a discussion we're now having on the plasma-devel mailing list. In my opening mail I've tried to provide a general overview about what input methods are used for, how they work, who they benefit, and what we must do to improve support for them in KDE Plasma.
Bringing high-quality text input to as many language users as possible, as well as surfacing functionality such as Emoji input and word completion in a better way, is something we increasingly care about. With the situation around complex text input on Wayland and specifically KWin still in a state of flux and needing-to-crystallize, we're looking to form closer ties with developers and users in this space. Feel free to chime in on the list or hang out with us in #plasma on freenode.
Some things will never change on Programming classes in universities: There will always be students crying to understand pointers, there will always be people going to stackoverflow hoping that somebody would do their homework, Every semester the students would start thousands of lines for their conclusion project and those lines ould probably go to the trash bin as soon as the semester ends. This shouldn’t be like that, this really shouldn’t be like that.
While I was at the universities I was mostly focused on trying to do things that mattered, but every semester I had to create a new and improved “Library book rental service”, “Car rental service”, or “Payment system”, the differentes where that one runned on command line, one on java/swing, other on the web. but the systems where basically the same, and the code always went into the trash because that was nothing I was proud of (and there was more 10 projects virtually equals to mine created by my fellow colleagues).
There’s a rise of technology universities in the world as we don’t see in a long time. And it’s easily undertandable, as everything now has to be “smart”, from water bottles (that will tweet you when they need a refill) to can openers (that will tweet your friends when you open a can, if you have any), Eveyrthing is connected and everybody is trying the new trends using the fancy new words created by the marketing team. All of the students around the world are doing exactly the same algorithms with exactly the same semester projects, just changing the language that they are writting the application on.
But there are *tons* of softwares that could really improve if a student or a university could adopt them for a semester and work on top of it, let’s get KDE Edu and KDE Games for an example, There are really complex projects there like KStars and Marble, I’m not crazy to ask for a first or second semester to look into those softwares unless they are genius, but there’s also a lot of small and easy to develop software that we would love to have some help:
After two months of intensive reviews, discussions, fixes, and stripping down the initial commit, feature by feature, to make it acceptable, I am happy to announce that the first QStringView commits have landed in what will eventually become Qt 5.10. Even the docs are already on-line.
This is a good time to briefly recapitulate what QStringView is all about.
I used to use the IRC bouncer at bnc.kde.org to keep a constant presence for my IRC nickname, but an IRC bouncer has several limitations that always annoyed me. Then I discovered that Matrix has a built-in IRC bridge, and I’ve been using it ever since, shutting down my IRC bouncer account. Basically you use the Matrix protocol as IRC bouncer and you use any Matrix client as if it were an IRC client.
You can find everything you need to know here: https://community.kde.org/Matrix
You may be interested in Matrix if:
I’m a good procrastinator, I really am. Not something that I should feel proud, and I’m not. But I’m a good procrastinator. And by being a procrastinator I mean that I can think that something is utterly hard to make, and spend three months looking for an excuse not to do that, and suddenly one day I have an idea and finish what I tried for three months without success in one hour or less.
The story today is about Subsurface, the free software that I most dedicated myself on. the class MainTab is a godlike class that holds all of the main area tabs, and being a godlike class it has too much information and too much entanglement. I know what I had to do: kill it, kill it with fire. And then I started…
A hundred patches later and it still loocked like more hundred patches to go. I entered on procrastination mode again, didn’t touched that for more than a month trying and waiting for a light to come from heaven and illuminati me.
Yesterday the light came, and I nuked the whole branch ( hint: never do that in a job interview, I lost a job once because I nuke trial git branches when I reallize how to do something in the correct way), and started from scratch. One hour later and three patches I was done. the Utterly complex thing that I didn’t know how to solve was just in my head.
Hello Planet KDE, I am Matthieu Gallien. I am a software developer mainly working with C++ and PHP. I am passionate about free software in general and KDE in particular.
I have been working on a music player for some time. I have decided to try to implement a design made by KDE VDG and especially Andrew Lake (Design for a Music Player). I had this idea after I saw this article from Thomas Pfeiffer (Phoronix offers some criticism of KDE software, and this is how KDE deals with it).
I would like to thank them for being a source of inspiration and the high quality of their work.
Elisa is using Baloo indexer in order to get all music indexed by it without needing any configuration by the user. This also means that support for other indexers or platforms is not yet done.
In addition, KDE VDG have done a lot of design work that I am trying to follow (KDE Visual Design Group/Music Player).
You can browse music by albums or by artists. More navigation possibilities will be added latter (Genre, All tracks, …).
The playlist is always shown to allow feedback when inserting tracks in it. You can also display it maximized. In this case, extra information will be shown related to the currently playing track.
It is already usable but I still need to do a first release. There is at least one problem that need to be fixed before a release. If you move tracks inside directories indexed by Baloo, they will disappear from Elisa until you restart the application.
It is using some KDE Frameworks 5 libraries (Baloo, KFileMetaData, …), Qt Quick Controls 1 and QtMultimedia. Writing a music player on top of those foundations have been a real pleasure.
Some design points are still open:
I welcome all kind of feedback on it. Especially any bug reports would be much appreciated.
My available time being limited, any help would be also very much appreciated.
Development is happening in KDE infrastructure and can be followed from the workboard in KDE’s Phabricator (Elisa Workboard).
I would also like to thank the KDE community and especially all those that have helped me during the development of Elisa.
Since I was a kid I had dreamed about being a tech guy, I remember that I used to search the trash of my father looking for broken circuit boards back in 1988, he had a notebook computer, a Toshiba T1000 with amazing ~5mhz and 512kb ram, one of the best machines of the time. He tried to teach me how to Pascal back then, but I had better things to do like stuck my foot in my mouth, or look for broken circuits for I had learned on the TV that I could just plug random eletricity circuits and cables and I would have a Super Sentai robot for me, and I would fight crime dressed like Jaspion.
From there I forgot about computers for a while, I lived in a farm and had 18 dogs and 22 cats to play all thay long, sometimes even a duck or a goose would appear to my panick because my dogs liked to hunt things that they tougth it was good for eating. My second computer was a ~proper one?~, it was basically a keyboard with a Cassete Tape jack that would load applications, and a copy of Windows 1.0, for that I have no pictures to prove, nor I remember the names of the technologies, so I cannot actually say anything.
Around 1998 I started to use Irc, on the now defunc BrasIRC network, and I met many people that would help me on my desire to program, and a few of them are actually also in the same path as me nowdays. I discovered that the Irc clients of the time -for windows, as my dad didn’t allowed me to put linux on the computer for I had no experience on it and he feared I could break stuff- allowed scripts and programming from within it, I got together with a few fellow Irc mates (like Arx Cruz, now a Red Hat hacker) and started to create our own flavor of Irc.
More Years passed and I discovered Sphere, an ultima online emulator (I have no idea how the project is today, I have completely no idea if the project still exists today) – one of the best video games invented, I have no shame to say that I prefered Ultima Online to girls back then, girls where nice, but they didn’t had over 70 skills that you could master using macro applications that also could teach you how to program (and I was really awkward torwards, you know, people).
From Ultima Online I managed to make a bit of money with my knowledge gained from the Sphere programming language, programming little Ultima Online servers for Lan Hourses and Lan Parties back in Salvador, and I managed to buy my first Computer, an AMD K6, and I finally was able to install Linux on it. My first flavor was Connectiva 4, a brazilian distro that later joined Mandrake and became Mandriva.
From there I really wanted to be a programmer, like, a real one, that could get ideas and transform into code, not the ones that are shown in movies that just dragged things around and need a Visual Basic GUI to find an IP. I did the UFMG C Course, now completely outdated (for the compilers that it uses doesn’t exists anymore, or are completely unusable, like Borland Turbo C)
From the UFMG C to Qt C++ was a step, and I started to do every university thing with it, even when that meant having to stand up against my teacher: “This is OO class tomaz, you need to use Java!”, “But teacher, C++ is also OO” and things like that. I remember that I had a terrible time on Graph Theory class, too abstract, nodes, and edges are okay, but Matrices representing them being displayed on the monochrome letters of the terminal? I didn’t had the internal RAM to parse that things on my head and transform that into the data that I was trying to analize, the computer should do that for me.
And I talked with Annma, explained her what this application should do and she agreed that could be a good thing to go to KDE. and then I joined KDE edu, my first ever contribution to an Project. From that time I had won life, all my dreams where realized, and I could sleep in peace.
It’s time for a long-overdue blogpost about the status of Tanglu. Tanglu is a Debian derivative, started in early 2013 when the systemd debate at Debian was still hot. It was formed by a few people wanting to create a Debian derivative for workstations with a time-based release schedule using and showcasing new technologies (which include systemd, but also bundling systems and other things) and built in the open with a community using the similar infrastructure to Debian. Tanglu is designed explicitly to complement Debian and not to compete with it on all devices.
Tanglu has achieved a lot of great things. We were the first Debian derivative to adopt systemd and with the help of our contributors we could kill a few nasty issues affecting it and Debian before it ended up becoming default in Debian Jessie. We also started to use the Calamares installer relatively early, bringing a modern installation experience additionally to the traditional debian-installer. We performed the usrmerge early, uncovering a few more issues which were fed back into Debian to be resolved (while workarounds were added to Tanglu). We also briefly explored switching from initramfs-tools to Dracut, but this release goal was dropped due to issues (but might be revived later). A lot of other less-impactful changes happened as well, borrowing a lot of useful ideas and code from Ubuntu (kudos to them!).
On the infrastructure side, we set up the Debian Archive Kit (dak), managing to find a couple of issues (mostly hardcoded assumptions about Debian) and reporting them back to make using dak for distributions which aren’t Debian easier. We explored using fedmsg for our infrastructure, went through a long and painful iteration of build systems (buildbot -> Jenkins -> Debile) before finally ending up with Debile, and added a set of own custom tools to collect archive QA information and present it to our developers in an easy to digest way. Except for wanna-build, Tanglu is hosting an almost-complete clone of basic Debian archive management tools.
During the past year however, the project’s progress slowed down significantly. For this, mostly I am to blame. One of the biggest challenges for a young project is to attract new developers and members and keep them engaged. A lot of the people coming to Tanglu and being interested in contributing were unfortunately no packagers and sometimes no developers, and we didn’t have the manpower to individually mentor these people and teach them the necessary skills. People asking for tasks were usually asked where their interests were and what they would like to do to give them a useful task. This sounds great in principle, but in practice it is actually not very helpful. A curated list of “junior jobs” is a much better starting point. We also invested almost zero time in making our project known and create the necessary “buzz” and excitement that’s actually needed to sustain a project like this. Doing more in the advertisement domain and “help newcomers” area is a high priority issue in the Tanglu bugtracker, which to the day is still open. Doing good alone isn’t enough, talking about it is of crucial importance and that is something I knew about, but didn’t realize the impact of for quite a while. As strange as it sounds, investing in the tech only isn’t enough, community building is of equal importance.
Regardless of that, Tanglu has members working on the project, but way too few to manage a project of this magnitude (getting package transitions migrated alone is a large task requiring quite some time while at the same time being incredibly boring :P). A lot of our current developers can only invest small amounts of time into the project because they have a lot of other projects as well.
The other issue why Tanglu has problems is too much stuff being centralized on myself. That is a problem I wanted to rectify for a long time, but as soon as a task wasn’t done in Tanglu because no people were available to do it, I completed it. This essentially increased the project’s dependency on me as single person, giving it a really low bus factor. It not only centralizes power in one person (which actually isn’t a problem as long as that person is available enough to perform tasks if asked for), it also centralizes knowledge on how to run services and how to do things. And if you want to give up power, people will need the knowledge on how to perform the specific task first (which they will never gain if there’s always that one guy doing it). I still haven’t found a great way to solve this – it’s a problem that essentially kills itself as soon as the project is big enough, but until then the only way to counter it slightly is to write lots of documentation.
Last year I had way less time to work on Tanglu than the project deserves. I also started to work for Purism on their PureOS Debian derivative (which is heavily influenced by some of the choices we made for Tanglu, but with different focus – that’s probably something for another blogpost). A lot of the stuff I do for Purism duplicates the work I do on Tanglu, and also takes away time I have for the project. Additionally I need to invest a lot more time into other projects such as AppStream and a lot of random other stuff that just needs continuous maintenance and discussion (especially AppStream eats up a lot of time since it became really popular in a lot of places). There is also my MSc thesis in neuroscience that requires attention (and is actually in focus most of the time). All in all, I can’t split myself and KDE’s cloning machine remains broken, so I can’t even use that ;-). In terms of projects there is also a personal hard limit of how much stuff I can handle, and exceeding it long-term is not very healthy, as in these cases I try to satisfy all projects and in the end do not focus enough on any of them, which makes me end up with a lot of half-baked stuff (which helps nobody, and most importantly makes me loose the fun, energy and interest to work on it).
So, this sounded overly negative, so where does this leave Tanglu? Fact is, I can not commit the crazy amounts of time for it as I did in 2013. But, I love the project and I actually do have some time I can put into it. My work on Purism has an overlap with Tanglu, so Tanglu can actually benefit from the software I develop for them, maybe creating a synergy effect between PureOS and Tanglu. Tanglu is also important to me as a testing environment for future ideas (be it in infrastructure or in the “make bundling nice!” department).
So, what actually is the way forward? First, maybe I have the chance to find a few people willing to work on tasks in Tanglu. It’s a fun project, and I learned a lot while working on it. Tanglu also possesses some unique properties few other Debian derivatives have, like being built from source completely (allowing us things like swapping core components or compiling with more hardening flags, switching to newer KDE Plasma and GNOME faster, etc.). Second, if we do not have enough manpower, I think converting Tanglu into a rolling-release distribution might be the only viable way to keep the project running. A rolling release scheme creates much less effort for us than making releases (especially time-based ones!). That way, users will have a constantly updated and secure Tanglu system with machines doing most of the background work.
If it turns out that absolutely nothing works and we can’t attract new people to help with Tanglu, it would mean that there generally isn’t much interest from the developer or user side in a project like this, so shutting it down or scaling it down dramatically would be the only option. But I do not think that this is the case, and I believe that having Tanglu around is important. I also have some interesting plans for it which will be fun to implement for testing
The only thing that had to stop is leaving our users in the dark on what is happening.
Sorry for the long post, but there are some subjects which are worth writing more than 140 characters about
It looks like I will be at Debconf this year as well, so you can also catch me there! I might even talk about PureOS/Tanglu infrastructure at the conference.
|- @varlesh work -|
|- Latte youtube presentation -|
|- @varlesh work -|
|- robust multi-screen support -|
|- Unity layout -|
|- Plasma layout -|
|- My favourite ;) -|
|- plasma looks, an Always Visible Latte dock instance -|
|- kwin blur effect -|
|- Latte Dock inside MATE -|
(Read this listening to “Gostava Tanto de Voce”, from Tim Maia)
I moved from the southern brazilian lands, where history was made and some amazing things where invented (like the Airplane and the Wrist Watch) and stories about Ghosts, Ghouls, Sacis, Caiporas and Mba’e Tatas where told to children, trying to scare them to sleep fearing about the Black Faced Bull (that will catch and eat kids that fears him), and moved to Europe, where history was made and some amazing things where invented (like Dr Who and the English Accent) and stories about Gosts, Ghouls, Dragons, Hobgoblins and Werewolfs where told to children, trying to scare them to sleep fearing about the Baba Yaga (that will catch and eat kids that enters her house).
I’v been living here for the past six months, and I wanted to write earlier, but you guys know how things are, things like that can simply be in your head for quite a while before you actually do something. So, if anyone from the KDE community would like to get together for something in Munchen, please get in touch. I live near the Worthsee area, quite far from munchen ~40 minutes via SBahn, but I work in the heart of the city.
Some new features are:
In the work is also an AppImage version of Simon for easy testing. We hope to deliver one for the Beta release coming soon.
Known issues with Simon 0.4.80 are:
We hope to fix these bugs and look forward to your feedback and bug reports and maybe to see you at the next Simon IRC meeting: Tuesday, 4th of April, at 10pm (UTC+2) in #kde-accessibility on freenode.net.
Simon is an open source speech recognition program that can replace your mouse and keyboard. The system is designed to be as flexible as possible and will work with any language or dialect. For more information take a look at the Simon homepage.
today I want to expose my my thoughts about the general hype for micro-services.
The first objection that one can move against this approach is that it does not really solve the problem of having the maintainable code because the same principles can be found in a lot of other paradigms that did not prevent bad software to be produced.
I believe that the turning point of the micro-services stuff is that is compatible with the devops philosophy.
With the combination of micro-services and devops you get software that has some reasonably well-defined limits and whose management is assigned to the people who developed the software.
This combination avoids of development shortcuts that make management more difficult (maintenance is a big deal).
This thing also solve one of the great IT open problems: the documentation.
It is true that it can not force us to produce documentation, but, at least, who run the code is exactly who produced it and i can guess that who writes the code knows how the code has to work.
It is now possible to build applications with high performance and functionality unimmaginable before, all this thanks to the fact that each component can be realized, evolved and delployed with the best life cycle that we are able to develop, without limiting the entire ecosystem.
Thanks for reading, see you next time
I have just noticed that some old articles concerning Now Dock appeared in planetkde... So sorry for this!! I am preparing the announcement for the new Latte Dock and I touched a bit these Now Dock old articles in order to archive them in the future...
This was a mistake from my side, please dont give them any attention as Now Dock is considered deprecated...
thanks a lot...
|Now Dock Panel v0.5.0|
|Now Dock Panel v0.4|
|Now Dock Window Previews|
|task progress (copying a file)|
|Now Dock Panel hovering widgets|
|opening app launcher|
|Now Dock Panel Configuration|
|hovering the now dock plasmoid|
|hovering now dock panel|
|hovering now dock panel above a window|
Ever since the port to QT5/KF5 in 2015, Kdenlive has seen an increasing momentum to developing its full potential in being a stable and reliable video editing tool which the FLOSS community can use to create content and democratize communication. In 2016 the project saw a redesign of its visual identity (logo, website), the reintroduction of some much requested tools like rotoscoping and a Windows port. During these couple of years we’ve seen a boom in the size of the community.
We’ve had some highs and lows during this process and are now ready to go a step further and bring professional-grade features to the FLOSS video editing world. To make this happen faster we would love to see new contributors jumping in. These are some parts that you can contribute to:
Since the beginning of the year, we have been working on a big refactoring/rewrite of some of the core parts of Kdenlive. Being more than 10 years old, some parts of our code had become messy and impossible to maintain. Not to mention the difficulty in adding new features.
Part of the process involves improving the architecture of the code, adding some tests, and switching the timeline code from QGraphicsView to the more recent QML framework. This should hopefuly improve stability, allow further developments and also more flexibility in the display and user interaction of the timeline.
You can see a preview of some of the new QML timeline features in the above video.
We plan to release the refactoring branch for the Kdenlive 17.08 release cycle.
Our initial Alpha release of Windows has been a success. Some people have switched to editing fulltime in Kdenlive and reviewers have praised it. We need developers to help find and fix some Windows specific bugs and bring Kdenlive on par with its GNU/Linux counterpart. One example is currently a bug that prevents rendering Jpeg images.
Due to the refactoring efforts, the 17.04 release cycle, which is right down the corner, will include code cleanup and some welcome bugfixes but no major changes. More details about this release will follow soon.
Our next monthly café will be held on Tuesday, the 11th of april 2017, at 21pm (CET) on irc.freenode.net, channel #kdenlive, everyone is welcome to join and this is a great opportunity to get in touch with the dev team, which can otherwise be contacted through a good old mailing list.
On a side note, the Frei0r project, which powers many Kdenlive effects just released version 1.6.0 which brings some new filters as well as crash fixes, so all packagers are encouraged to upgrade.
All in all 2017 promises to be an exciting year for Kdenlive, join us!