Today we have a guest post from Buovjaga, our friendly local QA evangelist for LibreOffice, KDE, Inkscape, Firefox and Thunderbird. Without further ado, I’d like to present…
With this post I hope to convince you that a strong quality assurance team can do miraculous things for a free software project.
The spectrum of QA is wide, and reducing the skill requirements is particularly relevant for KDE’s onboarding initiative.
The critical phase of onboarding a new contributor is the first contact. Sometimes the new person does not know what they want to do. Often you do not have a clear picture of what skills they have. You need to act fast or they will lose interest and disappear! This is the moment where you should hand them snacks: a query of bugs that need to be confirmed or re-confirmed. This is the lowest threshold for them to step across and into being a contributor, because:
QA is highly important in itself, but it is also a gateway drug. A simplified story of the evolution of a contributor might be as follows:
Not only does this evolution flow naturally through the QA team, but the experienced members are in a unique position to speed it up. This is because QA in the course of its work typically has to ferret out information from all the other teams. This leads to QA
In this aspect QA is acting like neurotransmitters in the body of the project.
The most apparent beneficial effect of having a strong QA team is that the developers are not distracted by massive amounts of first-stage bug analysis.
In QA, too many cooks do not spoil the broth. A large and diverse team is more effective than a small one when trying to keep up with a myriad of software and hardware configurations.
A large teams allows the freedom for members to level up their skills. The more experience on advanced triaging techniques the members have, the less work developers have to spend per bug fix.
There is a long road ahead for KDE to reach a healthy state regarding QA. Recruit contributors early and often. Aim for a feedback loop of recruiting, where even fresh contributors brainstorm to come up with ways to find new people.
I invite everyone to go through these articles and improve them:
I also recommend KDE to look into making it easy for QA to perform git bisects for pinpointing regressions. Perhaps this could be achieved by offering compressed repositories containing binary snapshots for every single commit in a project like LibreOffice does.
Since the introduction of the Plasma/Wayland session we set the QT_QPA_PLATFORM variable to wayland by default. After a long and hard discussion we decided to no longer do this with Plasma 5.13. This was a hard decision and unliked by everyone involved.
The environment variable forced Qt applications to use the wayland QPA platform plugin. This showed a problem which is difficult to address: if Qt does not have the wayland QPA platform plugin the application just doesn’t start. If you start through the console, the application will tell you:
This application failed to start because it could not find or load the Qt platform plugin "wayland" in "". Available platform plugins are: minimal, xcb. Reinstalling the application may fix this problem. Aborted (core dumped)
That is not really a useful information and does not tell the user what to do. Neither does it tell the user where the actual problem is and how to solve it. As mentioned when using a graphical launcher it’s worse as the app just doesn’t start without any feedback.
But how can it happen that the qpa platform plugin is missing although Plasma itself happily uses it? The problem is that application installed outside of the system bundle their own Qt and Qt does not (yet) include QtWayland QPA platform plugin. This affects proprietary applications, FLOSS applications bundled as appimages, FLOSS applications bundled as flatpaks and not distributed by KDE and even the Qt installer itself. In my opinion this is a showstopper for running a Wayland session.
The best solution is for Qt including the QPA platform plugin and having a proper auto-detection based on XDG_SESSION_TYPE. The situation will improve with Qt 5.11, but it doesn’t really help as the Qt LTS versions will continue to face the problem.
For now we implemented a change in Plasma 5.13 so that we don’t need to set the env variable any more. Plasma is able to select the appropriate platform plugin based on XDG_SESSION_TYPE environment variable. Non-Plasma processes will use the default platform plugin. With Qt < 5.11 this is xcb, with Qt 5.11 this will most likely change to wayland. KDE’s flatpak applications pick Wayland by default in a Wayland session and are unaffected by the change.
What is really sad about the change is that the Wayland qpa platform plugin gets less testing now. So we would like to ask our users to continue testing application with the Wayland platform plugin by setting the env variable manually or specifying –platform wayland when starting an application.
Dan Bielefeld is an activist that works for a South Korean NGO. Dan worked in the Washington, D.C. area training young activists in the areas of politics and journalism before going into researching atrocities committed by the North Korean regime. He is currently the Technical Director of the Transitional Justice Working Group and helps pinpoint the locations of mass burial and execution sites using mapping technologies.
Dan will be delivering the opening keynote at this year's Akademy and he kindly agreed to talk to us about activism, Free Software, and the sobering things he deals with every day.
Paul Brown: Hello Dan and thanks for agreeing to sit down with us for this interview.
Dan Bielefeld: Thanks for the opportunity, Paul.
Paul: You work for the the Transitional Justice Working Group, an organization that researches human rights violations of the North Korean regime, correct?
Dan: Yes, we have a mapping project that tries to identify specific coordinates of sites with evidence related to human rights violations.
Paul: And you were a web designer before joining the organisation... I've got to ask: How does one make the transition from web designer to human rights activist?
Dan: I was a web developer for several years before moving to Korea. When I moved here, I enrolled as a Korean language student and also spent most of my free time volunteering with North Korean human rights groups. So, unfortunately, that meant putting the tech stuff on hold for a while (except when groups wanted help with their websites).
Paul: You are originally from the US, right?
Dan: Yes, from Wisconsin.
Paul: Was this a thing that preoccupied you before coming to Korea?
Dan: I initially came on a vacation with no idea that I'd one day live and work here. In the lead-up to that trip, and especially after that trip, I sought out more information about Korea, which inevitably brought me repeatedly to the subject of North Korea.
Most of the news about North Korea doesn't grab my attention (talking about whether to resume talking, for instance), but the situation of regular citizens really jumped out at me. For instance, it must've been in 2005 or so that I read the book The Aquariums of Pyongyang by a man who had literally grown up in a prison camp because of something his grandfather supposedly did. This just didn't seem fair to me. I had thought the gulags where only a thing of history, but I learned they still exist today.
Paul: Wait... So people can inherit "crimes" in North Korea?
Dan: They call it the "guilt-by-association" system. If your relative is guilty of a political crime (e.g., defected to the South during the Korean War), up to three generations may be punished.
Paul: Wow. That is awful, but somehow I feel this is not the most awful thing I am going to hear today...
Dan: For a long time I thought it was just North Korea, but I have since learned that this logic / punishment method is older than the division of the North and South. For a long time after the division, in the South it was hard to hold a government position if your relative was suspected of having fled to the North, for instance.
Paul: What's your role in Transitional Justice Working Group?
Dan: I'm the technical director, so I'm responsible for our computer systems and networks, which includes our digital security. I also manage the mapping project, and I am also building our mapping system.
Paul: Digital security... I read that North Korea is becoming a powerhouse when it comes to electronic terrorism. How much credibility do these stories have? I mean, they seem to be technologically behind in nearly everything else.
Dan: This is a really interesting question and the answer is very important to my work, of course.
Going up against great powers like the US, the North Korean leadership practices asymmetrical warfare. Guerilla warfare, terrorism, these are things that can have a big impact with relatively little resources against a stronger power.
In digital security, offense tends to be easier than defense, so they naturally have gravitated online. Eike [Hein -- vice-president at KDE e.V.] and I went to a conference last year at which a journalist, Martyn Williams of NorthKoreaTech.org said they train thousands of hackers from an early age. The average person in North Korea doesn't have a lot of money and may not even have a computer, but those the regime identifies and trains will have used computers and received a great deal of training from an early age. They do this not only for cyber-warfare, but to earn money for the regime. For instance, the $81 million from the Bangladesh bank heist.
Paul: Ah, yes! They did Wannacry too.
Paul: Do your systems get attacked?
Dan: One of our staff members recently received a targeted phishing email that looked very much like a proper email from Google. The only thing not real was the actual URL it went to. Google sent her the warning about being targeted by state-sponsored attackers and recommended she join their Advanced Protection Program, which they launched last year for journalists, activists, political campaign teams, and other high-risk users.
We of course do our best to monitor our systems, but the reality today is that you almost have to assume they're already in if they're motivated to do so.
Paul: That is disturbing. So what do you do about that? What tools do you use to protect and monitor your systems?
Dan: What I've learned over the last three years is that the hardest part of digital security is the human element. You can have the best software or the best system, but if the password is 123456 or is reused everywhere, you aren't really very secure.
We try to make sure that, for instance, two-factor authentication is turned on for all online accounts that offer it -- for both work and personal accounts. You have to start with the low-hanging fruit, which is what the attackers do. No reason to burn a zero-day if the password is "password". Getting people to establish good digital hygiene habits is crucial. It's sort of like wearing a seatbelt -- using 2FA might take extra time every single time you do it, and 99.9% of the time, it's a waste of time, but you'll never really know in advance when you'll really need it, so it's best to just make it a habit and do it every time.
Another thing, of course, is defense in layers: don't assume your firewall stopped them, etc.
Paul: What about your infrastructure? Bringing things more to our terrain: Do you rely on Free Software or do you have a mix of Free and proprietary? Are there any tools in particular you find especially useful in your day-to-day?
Dan: I personally love FOSS and use it as much as I can. Also, being at a small NGO with a very limited budget, it's not just the freedom I appreciate, but the price often almost makes it a necessity.
Paul: But surely having access to the code makes it a bit more trustworthy than proprietary blackboxes. Or am I being too biased here?
Dan: Not all of my colleagues have the same approach, but most of them use, for instance, LibreOffice everyday. For mapping, we use Postgres (with PostGIS) and QGIS, which are wonderful. QGIS is a massive project that so far we've only scratched the surface of. We also use Google Earth, which provides us with imagery of North Korea for our interviews (I realize GE is proprietary).
I agree, though, that FOSS is more trustworthy -- not just for security, but privacy reasons. It doesn't phone home as much!
Paul: What about your email server, firewalls, monitoring software, and so on. What is that? FLOSS or proprietary?
Dan: Mostly FLOSS, but one exception, I must admit, is our email hosting. We do not have the resources to safely run our own email. A few years ago we selected a provider that was a partner with a FOSS project to run our own email service, but we ultimately switched to Google because that provider was slow to implement two-factor authentication.
Paul: Getting back to North Korea's human rights violations, you are mapping burial sites and scenes of mass killings, and so on, is that right? How bad is it?
Dan: The human right situation in North Korea is very disturbing and the sad thing is it's continued for 60+ years. The UN's Report of the Commission of Inquiry on human rights in the Democratic People’s Republic of Korea from 2014 is a must-read on the general human rights situation in North Korea. From the principal findings section (para. 24), "The commission finds that systematic, widespread and gross human rights violations have been and are being committed by the Democratic People’s Republic of Korea. In many instances, the violations found entailed crimes against humanity based on State policies."
Their mandate looked at violations of the right to food, the full range of violations associated with prison camps, torture and inhuman treatment, arbitrary arrest and detention, discrimination; in particular, in the systemic denial and violation of basic human rights and fundamental freedoms, violations of the freedom of expression, violations of the right to life, enforced disappearances, including in the form of abductions of nationals of other States, and so on.
For our mapping project, we published our first report last year, based on interviews with 375 escapees from North Korea who have now settled in South Korea.
They collectively told us the coordinates of 333 killing sites, usually the sites of public executions, which local residents, including school children, are encouraged and sometimes forced to watch. It should be noted that this number hasn't been consolidated to eliminate duplicates. Some people reported more than one site, others none at all, but on average, almost one site per person was reported.
Paul: And how do you feel about the situation? I am guessing you have met North Korean refugees passing through your workplace and that you, like most of us, come from a very sheltered and even cushy Western society background. How do you feel when faced with such misery?
Dan: It's a good question and hard to put into words what I feel. I guess, more than anything, I find the North Korean regime so unfair. Those we met in Seoul have been through so much, but they also are the ones who overcame so many obstacles and now have landed on their feet somewhere. It's not easy for them, but usually the longer they're here, the better they end up doing.
Continuing about the mapping project's first report findings, from those 375 interviewees, we were also told the coordinates of 47 "body sites" - we use the term "body sites" because it's more general than burial sites. Most of the sites were burial sites, but some were cremation sites or places where bodies had been dumped without being buried, or stored temporarily before being buried. This 47 figure IS consolidated / de-duped (from 52), unlike the killing sites number.
Paul: You manually plot sites on maps, correct? You have to rely on witnesses remembering where they saw things happen...
Dan: We manually plot them using Google Earth, yes. During the interview, our interviewer (who himself is originally from the North) looks together with the interviewee at Google Earth's satellite imagery. You have to get used to looking down at the world, which takes some getting used to for some people.
Paul: Is there no technology that would help map these things? Some sort of... I don't know... thermal imaging from satellites?
Dan: Our goal eventually would be to interview all 30,000-plus North Koreans who've resettled in South Korea. The more we interview, and the more data points we get, the more we can cross-reference testimonies and hopefully get a better picture of what happened at these locations. I went to the big FOSS4G (G=Geospatial) conference last year in Boston and also the Korean FOSS4G in Seoul, and got to meet people developing mapping systems on drones. The only problem right now with drones is that flying them over North Korea will probably be seen as an act of war.
When we get enough data points, we could use machine learning to help identify more potential burial sites across all of North Korea. Something similar is being done in Mexico, for instance, where they predict burial sites of the victims of the drug wars.
Dan: Patrick Ball of the Human Rights Data Analysis Group is doing very, very good stuff.
Paul: You mentioned that the crimes have been going on for 60 years now. What should other countries be doing to help stop the atrocities? Because it seems to me that, whatever they have been doing, hasn't worked that well...
Dan: Very true, that. North Korea is very good at playing divide and conquer. The rivalry between the Soviets and the Chinese, for instance, allowed them to extract more aid or resources from them.
They also try to negotiate one-on-one, they don't want to sit down to negotiate with the US and South Korea at the same time, only with one or the other, for instance. North Korea - Southe Korea and North Korea - US meetings are dramatically being planned right now, and it puts a lot of stress on the alliance between the US and South Korea. That's definitely a goal of North Korea's leadership. Again, divide and conquer.
So one thing that's an absolute must is for South Korea to work very closely with other countries and for them to all hold to the same line. But there are domestic and external forces that are pulling all of the countries in other directions, of course.
I would say to any government to always keep human rights on the agenda. This does raise the bar for negotiations, but it also indicates what's important. It also sends an important message to the people of North Korea, whom we’re trying to help.
I also think strategies that increase the flow of information into, out of, and within North Korea are key. For instance, the BBC recently opened a Korea-language service that the whole peninsula including North Korea. And Google’s Project Loon and Facebook’s similar project with drones could theoretically bring the internet to millions.
Paul: Do you think these much-trumpeted US - North Korean negotiations will happen? And if so, anything productive will come from them?
Dan: I really don't know. Also, one can't talk about all this without mentioning that China is North Korea's enabler, so if you want to significantly change North Korea, you have to influence China.
To more directly answer the question, two US presidents (one from each party) made big deals with the North Koreans but the deals fell apart. We’ll see.
Paul: We've covered what governments can do, but what can private citizens do to help?
Dan: One major thing is to help amplify the voices of North Korean refugees and defectors. There are a few groups in Seoul, for instance, that connect English speakers with North Korean defectors who want to learn and practice their English. There are small North Korean defector communities in cities like London, Washington DC, etc. I don't know about Berlin, but I wouldn't be surprised!
That's at the individual-to-individual level, but also, those with expertise as software developers, could use their skills to empower North Korean refugee organizations and activists, as well as other North Korean human rights groups.
Paul: Empower how? Give me a specific thing they can do.
Dan: For instance, one time I invited an activist to the Korea KDE group. He and some KDE community leaders had a very interesting discussion about how to use Arduino or something similar to control a helium-filled balloon to better drop leaflets, USB sticks, etc. over North Korea.
Paul: That is a thing? What do the Arduinos do, control some sort of rotor?
Dan: I can't really get into specifics, but, speaking of USB sticks with foreign media and content on it, one group has a project to reuse your old USB sticks and SD cards for just that purpose.
Paul: What do you put on the sticks and cards? "The Interview"? "Team America"?
Dan: There are several groups doing this, which is good, since they all probably have different ideas of what North Koreans want to watch. I think South Korean TV shows, movies, and K-Pop are staples. I have heard Wikipedia also goes on to some sticks, as do interviews with North Koreans resettled in South Korea...
Paul: Dan, thank you so much for your time.
Dan: Thanks so much, Paul, I look forward to meeting you and the rest of the KDE gang this summer.
Paul: I too look forward to seeing you in Vienna.
Dan will be delivering the opening keynote at Akademy 2018 on the 11th of August. Come to Akademy and find out live how you too can fight injustice from the realms of Free Software.
For most of the year, KDE—one of the largest free and open software communities in the world—works on-line by email, IRC, forums and mailing lists. Akademy provides all KDE contributors the opportunity to meet in person to foster social bonds, work on concrete technology issues, consider new ideas, and reinforce the innovative, dynamic culture of KDE. Akademy brings together artists, designers, developers, translators, users, writers, sponsors and many other types of KDE contributors to celebrate the achievements of the past year and help determine the direction for the next year. Hands-on sessions offer the opportunity for intense work bringing those plans to reality. The KDE Community welcomes companies building on KDE technology, and those that are looking for opportunities.
You can join us by registering for Akademy 2018. Registrations open in April. Please watch this space.
For more information, please contact the Akademy Team.
Cutelyst the Qt/C++ web framework just got a major release update, around one and half year ago Cutelyst v1 got the first release with a stable API/ABI, many improvements where made during this period but now it was time to clean up the mistakes and give room for new features.
Porting applications to v2 is mostly a breeze, since most API changes were done on the Engine class replacing 1 with 2 and recompiling should be enough on most cases, at least this was the case for CMlyst, Stickyst and my personal applications.
Due cleanup Cutelyst Core module got a size reduction, and WSGI module increased a bit due the new HTTP/2 parser. Windows MSVC was finally able to build and test all modules.
WSGI module now defaults to using our custom EPoll event loop (can be switched back to Qt’s default one with an environment variable), this allows for a steady performance without degradation when an increased number of simultaneous connections is made.
Validators plugins by Matthias got their share of improvements and a new password quality validator was added, plus manual pages for the tools.
The HTTP/2 parser adds more value to our framework, it’s binary nature makes it very easy to implement, in two days most of it was already working but HTTP/2 comes with a dependency, called HPACK which has it’s own RFC. HPACK is the header compression mechanism created for HTTP/2 because gzip compression as used in SPDY had security issues when on HTTPS called CRIME .
The problem is that HPACK is not very trivial to implement and it took many hours and made KCalc my best friend when converting hex to binary to decimal and what not…
Cutelyst HTTP/2 parser passes all tests of a tool named h2spec, using h2load it even showed more requests per second than HTTP/1 but it’s complicated to benchmark this two different protocols specially with different load tools.
Upgrading from HTTP/1.1 is supported with a switch, as well as enabling H2 on HTTPS using the ALPN negotiation (which is the only option browsers support), H2C or HTTP/2 in clear text is also supported but it’s only useful if the client can connect with previous knowledge.
I strongly recommend reading this https://jakearchibald.com/2017/h2-push-tougher-than-i-thought/ .
This does not mean SERVER_PUSH won’t be implemented, quite the opposite, due the need to implement it properly I want more time to study the RFC and browsers behavior so that I can provide a good API.
I have also done some last minute performance improvements with the help of KDAB Hotspot/perf, and I must say that the days of profiling with weird/huge perf command line options are gone, awesome tool!
If you like it please give us a star on GitHub!
Ayer martes 19 de marzo se emitió y grabó en directo un nuevo podcast de la cuarta temporada de KDE España. Un episodio que lleva por nombre KDE y empresas, donde se analizaron los aspectos más importantes de estas
Nuevo mes, nuevo podcast. Los chicos de KDE España nos ofrecieron una nueva edición de su charla mensual sobre aspectos del mundo KDE con dos personas especialistas en las relaciones del Software Libre y las empresas: Carlos Rodriguez, presidente de Agasol -asociación de empresas gallegas de software libre- y fundador y gerente de Librebit, y Agustín Benito, miembro de KDE España, desarrollador de KDE, ex-tesorero de KDE e.V. y ex-presidente de Asolif.
Además, y como es habitual participaron, Ruben Gómez Antolí, miembro de KDE España que realizó las labores de presentador, y un servidor, Baltasar Ortega, secretario de KDE España y creador y editor del presente blog.
De esta forma, tras una extensa charla de más de dos horas donde aparecieron términos como migraciones, aplicaciones cautivas, aplicaciones nativas, modo kiosco, formación, piratería y un largo etcétera, se llegó a la conclusión de que las empresas van migrando poco a poco al Software Libre, luchando en ocasiones contra las Administraciones Públicas y contra la propia inercia del miedo al cambio, como algo inexorable y que aquella que no lo haga irá perdiendo competividad.
Un gran podcast que no os podéis perder con dos grandes oradores.
Como siempre, esperamos vuestros comentarios que os aseguro que son muy valiosos para los desarrolladores, aunque sean críticas constructivas (las otras nunca son buenas para nadie). Así mismo, también nos gustaría saber los temas sobre los que gustaría que hablásemos en los próximos podcast.
Aprovecho la ocasión para invitaros a suscribiros al canal de Ivoox de los podcast de KDE España que pronto estará al día.
With the introduction of the Qt Quick software renderer it became possible to use Qt Quick on devices without a GPU. We investigated how viable this option is on a lower end device, particularly the NXP i.MX6 ULL. It turns out that with some (partially not yet integrated) patches developed by KDAB and The Qt Company, the performance is very competitive. Even smooth video playback (with at least half-size VGA resolution) can be done by using the PXP engine on the i.MX6 ULL.
We haven’t blogged about KDE Connect in a long time, but that doesn’t mean that we’ve been lazy. Some new people have joined the project and together we have implemented some exciting features. Our last post was about version 1.0, but recently we released version 1.8 of the Android app and 1.2.1 of the desktop component some time ago, which we did not blog about yet. Until now!
We got some fancy new features in place:
I think most of us can agree that typing long texts on the phone sucks compared to typing on a proper keyboard. Before, you could type your text on the desktop and copy & paste it to your phone using our clipboard sync. Now we got an even fancier method: our new Remote Keyboard plugin.
Before using it you need to enable the KDE Connect Remote Keyboard in your phones settings.
Whenever you are confronted with a text input field you can switch to the KDE Connect Remote Keyboard. Then you open up the Plasmoid, click the input field and start typing.
Big thanks to Holger Kaelberer for implementing this!
Previously you only could reply to SMS, but not other IM apps like Whatsapp. We are pleased to announce that we were able to enable replying for several other messaging apps that support Androids quick reply, including Whatsapp. Please note that it is not within our control which apps are supported and which not.
Big thanks to Julian Wolff for implementing this!
On Android, most notifications have some kind of icon, like a contact picture for messaging apps or album art for media player notifications. KDE Connect now forwards those and displays them on the desktop and inside the Plasmoid.
Android Marshmallow introduced a new permission system, giving the users fine-grained control about their apps. To support this new system each plugin got a set of required and optional permissions assigned. If a required permission has not been granted the respective plugin won’t be loaded. If an optional permission has not been granted the plugin will be loaded with reduced features.
Android Marshmallow also introduced Direct Share. Using this we enabled you to send files or urls to your desktop without opening KDE Connect.
Our Plasmoid got some love
A small but requested feature is selecting a ringtone for Find-my-Phone.
You are now able to blacklist numbers so that calls and SMS are not forwarded to the desktop. This is especially useful when you are using two-factor-authentification with your phone so it won’t get leaked to the desktop.
Those features were implemented by me.
Matthijs Tijink has been working really hard on improving the media controller plugin. It now displays the album cover art and a media control notification as well as other polish. Make sure to check out his blog.
Aleix Pol has implemented an URL handler that enables you to trigger phone calls for example by clicking a tel:// url in your browser.
Additionally we have fixed loads of bugs, crashes and papercuts and made many under-the-hood improvements.
There is also a lot going on in related KDE software. Friedrich Kossebau is working on bringing MPRIS support to Gwenview and Okular, enabling controlling slideshows and presentations from KDE Connect. Furthermore we fixed some issues in the MPRIS implementation of Plasma Browser Integration and Elisa (the next-gen KDE music player).
Speaking of Plasma Browser Integration: In case you haven’t, make sure to check out this awesome project which integrates neatly with KDE Connect, enabling you for example to control Youtube videos or Netflix from your phone or to send browser tabs to your phone. Thanks Kai Uwe Broulik for this awesome project!
But this is not the end. We got some more features in the pipeline and this week the core developers are meeting for a sprint to discuss the future of KDE Connect. Some weeks ago we asked people on Reddit which features they like to see and got a ton of valuable feedback. We’ll discuss it and let you know which of them are feasible.
If you are as excited about KDE Connect as we are we would love to see you join our development team. Make sure to subscribe to and ask for help at our mailing list. If you can’t contribute in a technical way but still want to support us consider donating to KDE. Your donations enable us to meet in person and work more closely on KDE Connect and other KDE Software.
Make sure you commit anything you want to end up in the KDE Applications 18.04 release to them :)
We're already past the dependency freeze.
The Freeze and Beta is this Thursday 22 of March.
More interesting dates
April 5: KDE Applications 18.04 RC (18.03.90) Tagging and Release
April 12: KDE Applications 18.04 Tagging
April 19: KDE Applications 18.04 Release
The KMyMoney development team is proud to present the first maintenance version 5.0.1 of its open source Personal Finance Manager. Although several members of the development team had been using the new version 5.0.0 in production for some time, a
I’m almost 35 years old, from a city called Passo Fundo, state of Rio Grande do Sul, Brazil. I like cats, cartoons and rock and roll. 1994 was the year when I started to have some interest in drawing. I looked for learning how to draw just for fun and sometimes to let my soul talk. But I can say that the digital art that I started practicing last year has helped me get rid of a recent depression.
As a hobby. At least for now.
I usually draw cartoons. But I also like painting nature and fantasy elements.
Most times when I draw, I don’t look up to a specific artist. I search random images on internet or the painting comes from my own mind. I think any kind of art should come from the artist’s inner soul.
It occurred last year, in May, I guess. I had no job but I had a nasty depression. Then my husband said he would like to learn how to draw and start work with that. It was when I started to draw again. Yes, I had stopped drawing, limiting myself to draw just when I had nothing more to do. Then we got an online course from Ivan Quirino and here I am, less than an year later, doing all kinds of digital painting.
The practicality. It is really hard when you do something wrong drawing at the traditional way. In digital painting, you can redo as many times as necessary.
At Youtube or at some blog. I can’t tell for sure.
When I used Krita for the first time I already knew most of the tools, so it was easy to use. But I needed to learn more, then I watched a video that explained the basic tools and method to paint. I thought then that Krita was a good tool for painting. Today I can tell it’s a great tool for digital artists. My personal opinion: Krita is the best and I really can’t use a different program.
The quick access to the tools I need. The ease to work with it. I like so much of that function that allows you to paint just the line art. It’s awesome.
Nothing! As I said before: I really enjoy work with Krita and I recommend it to anyone who is choosing this path of digital art.
The brushes, the way Krita works with layers (for example: if you have a line on the top layer and you paint a background on the layer below, you won’t paint over what is drawn on the top layer). I don’t know about the functionality of all painting software, but I think this is pretty cool.
I like my latest work. At the time I made the work, I hadn’t thought about a name yet. But looking at it now, I could call it “The peace of the mermaid”. I think it fits well.
Well, I’m not good with names of techniques, but I used the default brushes and some of those by David Revoy (airbrush, fill brush, wet brushes, some ink for the little details, some customized brush “LJF water brush 3”). I also used effect layers. So I started with the water base, just filling the area with blue and white tones. Then I painted the sky, mixing tones of blue with white. The sun was made with an airbrush, mixing yellow and white. After that, I used the customized brush to do the details of the water. Always mixing the colors to get the vision that I was looking for. Then I painted the blocks of sand, leaving the details, done with “splat_texture – Marcas”, for the end. At this point, I could start drawing the mermaid. Started by doing a shadow mermaid. After that, I put the colors, lights and shadows and the details. The effect layers were used to get more luminance on a specific element (In Portuguese: Luz viva – used on the mermaid and the starfish -, Luz suave – used to get the luminance on the full scene – , Desvio linear – to get the effect on the water light).
For the moment I have:
Facebook page: https://www.facebook.com/JBHdigitalart/?ref=bookmarks
I just wanted to thank the people that work to improve Krita, an amazing box of tools for digital painting!
Hace tiempo que se anunció la sede y desde ese momento el blog va dando los detalles necesarios para ir abriendo boca.. Y es que en poco más de mes y medio se celebrará en Valencia la reunión anual en España de usuarios y desarrolladores de KDE, Akademy-es 2018. Concretamente se celebrará del 11 al 13 de mayo y es el momento de seguir preparando el programa. Como el evento es una celebración comunitaria se abrió en el momento del anuncio de la sede la posibilidad de que todo el mundo, además de acudir, participara de forma activa. Así que presenta tu charla para Akademy-es 2018 de Valencia y muestra a toda el mundo tu proyecto personal o comunitario.
Recordemos que en Akademy-es se realizarán las típicas charlas que presentan las novedades tanto de las aplicaciones como de las herramientas de programación, sin olvidar de los proyectos activos o de aquellos de los que se quieren lanzar en un futuro cercano.
En anteriores ediciones en estas charlas (extraído del programa de Akademy-es 2017 de Almería) descubrimos KDE, nos pusimos a colaborar con KDE, conocimos la asociación KDE España, aprendimos más de Plasma 5, vimos pinceladas de un posible futuro de KDE, aprendimos como colaborar con KDE sin ser programador, conocimos mejor la relación de Slimbook co KDE, aprendimos a hacer aplicaciones para el móvil y recibimos las primeras leccions de Qt.
¿Y qué encontraremos en esta edición? Pues depende de ti, ya que si tienes algún tema que crees que interesará a la Comunidad KDE y sus simpatizantes, no lo dudes a y presenta tu charla para Akademy-es 2018. Estaremos encantados en escuchar tu propuesta.
Si quieres más información, basta con que leas el siguiente texto oficial o que visites la web oficial de Akademy-es 2018, no obstante aquí te lo puedo contar yo:
Para proponer actividades se deberá enviar un correo a email@example.com antes del 31 de marzo con un resumen breve de la presentación.
Es importante tener en cuenta las siguientes consideraciones:
Se trata de una gran oportunidad de darte a conocer en el mundo KDE y en el mundo del Software Libre en general.
Más información: Akademy-es 2018
Akademy-es (#akademyes, que es la etiqueta para las redes sociales) es evento más importante para los desarrolladores y simpatizantes de KDE, que se ha ido celebrando desde el 2006 con éxito creciente.
En general, las Akademy-es son el lugar adecuado para conocer a los desarrolladores, diseñadores, traductores, usuarios y empresas que mueven este gran proyecto.
En ellas se realizan ponencias, se presentan programas, se hace un poco de caja para los proyectos libres (camisetas, chapas, etc) pero sobre todo se conoce a gente muy interesante y se cargan baterías para el futuro.
Podéis repasar las anteriores ediciones en estas entradas del blog:
Esta semana sigue la sección que inicié de forma no oficial ya hace más de un mes y que se dedica a mostrar las novedades del mundo GNU/Linux que no aparecen en el blog por falta de tiempo y que deberían aparecer. Así que os doy la bienvenida a Noticias linux 02, correspondiente tercer domingo de marzo de 2018 con Firefox, Kubuntu, Plasma 5.12.3 y editores multimedia GNU/Linux
La semana de las mil actividades ha llegado a su fin, dejándome a las puertas de otra un poco más relajada en cuanto a obligaciones laborales, pero llena de tareas que hacer para poder sobrevivir a este tercer trimestre que llega.
Así que aprovecho la tranquilidad de este domingo para seguir con la nueva sección de Noticias Linux, que llega a su segunda edición, compartiendo noticias que han aparecido en otros blogs o webs y que hubiera estado genial que aparecieran en éste.
Mientras esperamos que madure Falkon, los usuarios de la Comunidad KDE podemos seguir utilizando Firefox, el gran explorador web, que sigue mejorando y evolucionando.
Según podemos leer en Genbeta, el pasado 13 de marzo fue lanzado Firefox 59, una nueva versión del excelente explorador (disponible ya en las principales distribuciones GNU/Linux) que nos ofrece las siguientes novedades:
Más información: Firefox
Los usuario de Kubuntu 17.10 están de enhorabuena. Según leemos en Ubunlog, ya está disponible la versión de Plasma 5.12.3 para sus escritorios.
Para hacerlo debéis activar los repositorios backports, abriendo una konsola y escribiendo los siguientes comandos:
sudo add-apt-repository ppa:kubuntu-ppa/backports -y
sudo apt update && sudo apt full-upgrade
Y finalizo esta entrada de Noticias Linux 02, con otra mención a un blog que se ha convertido en imprescindible para cualquier simpatizante del Software Libre: Maslinux.
En esta ocasión nos ha obsequiado con un recopilatorio de los 10 mejores editores multimedia GNU/Linux: A modo de resumen, los mejores editores en orden de aparición son: Shotcut, VidCutter, FlowBlade, Kdenlive, Blender, Openshot, Cinelerra, Pitivi, Ardour y Rosegarden.
Y como siempre digo, son todos los que están, pero no están todos los que son. ¿Qué noticia os ha llamado la atención esta semana? Ponedlo en los comentarios y mejores esta entrada.
Christmas came early this week! Today’s Usability & Productivity status is jam-packed with awesome stuff that I think you’re all really gonna love.
There’s all the awesome work on Discover, but it doesn’t stop there:
Finally, A notorious and longstanding bug has been fixed! The bug was this: in KDE environments where KWallet had not been set up (such as live sessions and barebones/DIY-style distros like Arch), you would be prompted for your password twice when connecting to a password-protected wifi network. This turned out to be a bug not in KDE software, but rather in the upstream FreeDesktop networkmanager software. It’s now been fixed as of networkmanager 1.10.6. If your distro doesn’t have that yet, please ask them to update or backport the fix.
Pretty awesome stuff, huh? Well there’s even more coming! We’re committed to making KDE Plasma the finest computing environment on planet earth, and I hope this kind of progress demonstrates the depth of that commitment. Want to hop on board and become a part of something big? Consider becoming a KDE contributor, particularly in development!
Hello Guys, My life since 2018 started is going on like crazy. I'm trying to get my bachelor degree this year, a lot of events to attend, Atelier and AtCore needing love and a lot of work... And more than a month later I'm going to report what happened at the 11th edition of Campus... Continue Reading →
This week saw many positive changes for Discover, and I feel that it’s really coming into its own. Discover rumbles inexorably along toward the finish line of becoming the most-loved Linux app store! Take a look at this week’s improvements:
Just take a look at these screenshots! Isn’t discover looking really good these days? We’ve chewed through most of our backlog of architectural issues and are working hard on adding much-requested features and polishing the UI.
This blog is about KDE Connect. KDE Connect is a project to communicate across all your devices. For example, with KDE Connect you can receive your phone notifications on your desktop computer, control music playing on your desktop from your phone, or use your phone as a remote control for your desktop.
Well this is my first blog.
I've started working on KDE Connect last November. My first big features were released yesterday in KDE Connect 1.8 for Android, so cause for celebration and a blog post!
My first big feature is media notifications. KDE Connect has, since it's inception, allowed you to remotely control your music and video's. Now you can also do this with a notification, like all Android music apps do! So next time a bad song comes up, you don't need to switch to the KDE Connect app. Just click next on the notification without closing you current app. And just in case you don't like notifications popping up, there's an option to disable it.
The second big feature is album art for the media control. Since most songs belong to an album, and people put serious time into designing those album covers, it's a shame we haven't been showing those covers all this time! But wait no more: we've finally got album art in KDE Connect!
Currently, only remote album art is supported (used in e.g. Spotify). Local album art and album art in the media notifications will come in a future release of KDE Connect.
Elisa is a music player developed by the KDE community that strives to be simple and nice to use. We also recognize that we need a flexible product to account for the different workflows and use-cases of our users.
We focus on a very good integration with the Plasma desktop of the KDE community without compromising the support for other platforms (other Linux desktop environments, Windows and Android).
We are creating a reliable product that is a joy to use and respects our users privacy. As such, we will prefer to support online services where users are in control of their data.
We are preparing the 0.1 release of Elisa. A stable branch has been created and translations set up for the stable branch.
We plan to have a string freeze starting 24th March.
The release will be tagged on 7th April with the release happening shortly after.
We are also continuing development of what will become the 0.2 release. We plan to make a release each 3 months and to support the stable release with a few bug fix releases. We have summarized the schedule for the next releases in the KDE community wiki.
Now is really a good time to join the Elisa team. You will be able to work on code that will soon reach potential users. You will not have to wait for a long time given that we will soon release.
Since the last blog posts, quite some changes went into Elisa. Most notably is the partial migration to raw Qt Quick Controls v2 and all the fixes for HighDPI support. Alexander is also looking at opportunities to leverage Kirigami.
Here is the raw git changelog:
The following authors have contributed to Elisa:
Thanks a lot for those contributions.
There are several way to test Elisa but the easiest one is using the flatpak package produced by KDE if you are running a system supporting flatpak. The flatpak service is back automatically building a package when changes are integrated in Elisa. This is the kind of services the awesome KDE community provides. You can easily contribute your energy or some money to help this to continue.
There are also some packages built for your distributions from the git repository. This is a nice way to test Elisa. Thanks for the effort of the packagers.
LibAlkimia is a base library that contains support for financial applications based on the Qt C++ framework. One of its main features is the encapsulation of The GNU Multiple Precision Arithmetic Library (GMP) and so providing a simple object to be
We are happy to announce the release of Qt Creator 4.6 RC!
Since the beta release we have been busy with bug fixing. Please refer to the beta blog post and our change log for an overview of what is new in Qt Creator 4.6. As always this is a final call for feedback from you before we release 4.6.0, so we would be happy to hear from you on our bug tracker, the mailing list, or on IRC.
The opensource version is available on the Qt download page, and you find commercially licensed packages on the Qt Account Portal. Qt Creator 4.6 RC is also available under Preview > Qt Creator 4.6.0-rc1 in the online installer, as an update to the beta release. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on chat.freenode.net, and on the Qt Creator mailing list.
((Okular contributors, take a note of the end))
KDE Applications 18.04 Feature Freeze is setting in. Or: reminder to do finally that feature you always wanted to implement.
This time for me it’s remote control for presentation-like media shows. Think slideshows of images/videolets e.g with the image browser Gwenview, or presentations given with the document viewer Okular. Would be nice to do this from across the room or stage, being deep in your comfortable furniture or when standing by the auditorium, would it not?
There is your wireless input controllers to help you. But…
… we want more, like:
Obvious idea: use your smartphone as rich remote control. Just write a controller app which talks to your app on the computer running the presentation. Profit.
Though only profit for the given app. Would it not be nicer if there were some standard interfaces, so remote controllers would work across applications? We have seen that before, for music and movie players. In the FLOSS world there is e.g. the Media Player Remote Interfacing Specification (MPRIS). And if we think about it, “media” is an abstraction, one which also can cover images & slides. Though the rest of the spec then uses concepts and terms which are rather bound to typical music players, like “track” or “playlist”.
So not usable for our purpose. Or? If we ignore the actual terms, we find we can map their abstract data model with some flexibility onto the data model of a simple one-dimensional slide-by-slide/image-by-image presentation. And by doing so instantly can get access to the existing MPRIS controllers, allowing us to walk through the slides, going fullscreen, start playing & pausing and so on. Controllers like e.g. the MPRIS-based media controller plugin for KDE Connect.
So it’s just adding a MPRIS-wrapper to e.g. Gwenview or Okular, and we have some initial working remote controllers for them. Now this sounds fancy to have, no?
And for Gwenview, I can happily report that by some hard review work of Henrik F. a first version has just been merged. Shipping to everyone as part of KDE Applications 18.04.
For Okular we have a similar patch. Though it needs some good souls to give it a complete review in the next 7 days, otherwise it will miss out for the upcoming release and be at least delayed some more four months.
The patches should be also interesting to adapt for photo management applications like Digikam or KPhotoAlbum.
So want to give your vacation report to your friends while sitting next to them on the couch as well? Have a look at those two patches and try to adapt them for those applications, you will see it is rather simple value and action forwarding code
We are happy to bring you GCompris 0.90.
This new version contains 8 new activities:
We always have new features, content and bug fixes:
You can find this new version on the download page.
On the translation side, we have 14 languages fully supported: British English, Catalan, Catalan (Valencian), Chinese Traditional , Dutch, French, Greek, Indonesian, Italian, Portuguese, Romanian, Spanish, Swedish, Ukrainian;
And some partially supported: Belarusian (87%), Brazilian Portuguese (87%), Breton (65%), Chinese Simplified (80%), Estonian (79%), Finnish (78%), Galician(87%), German (83%), Hindi (86%), Irish Gaelic (99%), Norwegian Nynorsk (86%), Russian (80%), Slovak (76%), Slovenian (70%), Polish (99%), Turkish (93%).
If you want to help, please make some posts in your community about GCompris and don’t hesitate to give feedbacks.
Thank you all,
Timothée & Johnny
We are happy to announce the release of Qt Creator 4.5.2!
This release includes a workaround for an issue in Qt which makes Qt Creator’s summary progress bar and some other controls disappear (QTCREATORBUG-19716).
The opensource version is available on the Qt download page, and you find commercially licensed packages on the Qt Account Portal. Qt Creator 4.5.2 is also available through an update in the online installer. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on chat.freenode.net, and on the Qt Creator mailing list.
After many months of hard work and more than 200 bugs fixed, KEXI is back with a new major release that will excite Windows and Linux users alike.
If you are looking for a Free and open source alternative to Microsoft Access, KEXI is the right tool for you.
As part of the Calligra suite, KEXI integrates with other office software, providing an easy, visual way to design tables, queries, and forms, build database applications, and export data into multiple formats. KEXI also offers rich data searching options, as well as support for parametrized queries, designing relational data, and storing object data (including images).
A new version of KEXI has just been released, so if you have never tried this powerful database designer application, now is the right time.
KEXI 3.1 is available for Linux and macOS, and after many years, for Windows as well.
Business environments are often concerned about migrating to FOSS solutions because of compatibility issues with the proprietary software and formats they currently use. KEXI solves that problem with its Microsoft Access migration assistant that ensures database tables are preserved and editable between applications. Even better, KEXI works natively on the Windows operating system. In fact, KEXI was the first KDE application offered in full version on Windows.
After a long hiatus, the new version of KEXI offers convenient installers for Windows once again. Although it's a preview version, the users are invited to try it out, report bugs, and provide feedback.
Similar to Plasma 5.12 LTS, the focus of KEXI 3.1 was to improve stability and (backward) compatibility. With more than 200 bugfixes and visibly improved integration with other desktop environments, the goal has definitely been achieved.
Usability improvements have also made their way into KEXI 3.1 dialogs. When using the Import Table Assistant, it is now possible to set character encoding for the source database. Property groups are now supported, and users can set custom sizes for report pages.
KEXI 3.1 marks the first official release of KEXI Frameworks - a powerful backend aimed at developers who want to simplify their codebase while making their Qt and C++ applications more featureful. KDb is a database connectivity and creation framework for various database vendors. In KEXI 3.1, KDb offers new debugging functions for SQL statements and comes with improved database schema caching.
KProperty is a property editing framework which now comes with improved support for measurement units and visual property grouping. Last but not least, KReport is a framework for building reports in various formats, offering similar functionality to the reports in MS Access, SAP Crystal or FileMaker. The most useful new feature in KEXI 3.1 is the ability to set custom page sizes for KReport.
Alongside Frameworks, KEXI 3.1 offers greatly refined APIs and updated API documentation. According to the developers, “the frameworks are now guaranteed to be backward-compatible between minor versions”.
Translations have also been improved, and KEXI 3.1 is the first version where they are bundled with the Frameworks. This will make it easier for the developers using KEXI Frameworks, as they will be able to use translated messages in their apps.
Even with all the excitement about the new release, KEXI developers are already working on new features and improving the existing ones. If you'd like to help make KEXI better, it's never too late to join the project! Take a look at the list of available coding and non-coding jobs.
Although the API documentation has been updated, the user documentation could use some love. If you're good at writing or teaching others, why not chip in?
Finally, if you know a business or an individual that's looking for a Microsoft Access replacement, tell them about KEXI.
They just might be pleasantly surprised with what they'll discover.
I figured out a solution to a hardware troubleshooting problem I’ve had going off and on for at least a couple of years. I feel like others might run across it and, not knowing anywhere better to note it, suppose I might as well dump it on my blog and hope search engines can make it available to those who need it.
Anyways, the problem is that sometimes my computer wouldn’t boot. Particularly after power outages (in retrospect, clue 1). Sometimes resetting the CMOS would work. Sometimes resetting CMOS wouldn’t work but pulling various cards / memory modules around and reseating them would work.
Once when I encountered this issue, I discovered that plugging in my monitor using HDMI instead of DisplayPort worked (clue 2). This, however, lead to a separate problem which took me months to figure out (HDMI only supports 30 fps on my monitor’s native resolution, an issue fixed an a later rev of my monitor’s hardware).
When the issue recently started to recur (after a weather-related power outage), I discovered that plugging in an alternate GPU (an incredibly cheap emergency backup discrete unit I have) also worked. This one only had HDMI but it couldn’t drive native resolution anyways, so at least I didn’t have to worry about 30fps.
The issue had gotten significantly worse when I upgraded my CPU and motherboard a year ago, so I spent weeks thinking that my GPU simply didn’t work well with the new CPU/motherboard and that it was time to find a different GPU.
The new GPU recently showed up and had the exact same problem as the previous one (oops). Everything finally dawned on me when I tried the HDMI output on the off chance that it wouldn’t be also affected by the 30fps issue (it was, but at least the computer booted!).
It turned out that the problem was my monitor this whole time. I went with a full power cycle to my computer probably dozens of time in the course of debugging this issue. But I didn’t power cycle my monitor once… doing so fixed my issue fully.
I guess I’ve been thinking that monitors are still “dumb”, that they just show pixels coming in over the wire. But that is no longer the case, hasn’t been for years, and so if you’re having issues that you think are GPU issues, don’t forget to do the “turn it off and then back on again” routine with your monitor as well!
In my case, what I think the issue was, is that the monitor had its display connection state corrupted slightly (whether due to power cycling or something else), and that the GPU was unable to complete a valid connection to the monitor during computer boot. Without a GPU in a valid state to drive a display, the motherboard would apparently abort the boot process (it had a GPU debug LED lit up, which I couldn’t figure out the cause of since the GPU always worked fine if I could get the computer to boot).
I could never find this problem described in any of my searches, but hopefully this will help someone else if they encounter something similar.
KDE has set the focus on 3 goals around improved usability and productivity, privacy and easier onboarding of new contributors to KDE. On Thursday (15. March 2018) we are going to hold an office hour. During the office hour you can ask all your questions around these goals and tell us about your ideas for pushing them forward. We will be meeting in the channel #kde on freenode IRC at 16:00 UTC. We hope to see many of you there.
Sou usuário e empacotador do Mageia desde o lançamento do fork, e não me levem a mal, para mim continua sendo uma distribuição de excelente qualidade para o seu propósito: comunitária, aberta para as mais diferentes contribuições e com ênfase na estabilidade. Mageia é das poucas distros com suporte há mais de 8 ambientes desktop (sem contar os gerenciadores de janelas leve), e com o lançamento da versão 6 passou a ter suporte ao AppImage, Fedora Copr, Open Build Service, dnf, e muito mais tecnologias que dão uma cara moderna para o projeto. Uso Mageia nos meus computadores pessoais e de trabalho e também nos computadores que meus alunos utilizam no laboratório.
Como desenvolvedor tanto do KDE quanto do Mageia, utilizo a versão instável da distro (chamada Cauldron) desde sempre. Ela me entrega as versões mais recentes da “pilha KDE” (KDE Plasma, Applications e Frameworks) e também do Qt. No geral funciona bem, mas volta e meia alguns software importantes deixam de funcionar ou ficam muito instáveis, prejudicando o desenvolvimento de algumas tarefas.
Antigamente isso não era um problema para mim – mesmo sendo estudante de mestrado ou doutorado, eu normalmente aguardava algum desenvolvedor corrigir os erros ou eu mesmo ia lá e metia a mão pra tentar solucionar. Essa é uma forma muito efetiva de contribuir com software livre.
Mas hoje em dia tenho pouca disposição para tanto. O trabalho como professor, somado às outras coisas a que me dedico, exaurem meu tempo para realizar esse tipo de tarefa.
Passar a utilizar o Mageia estável não é uma boa opção: o preço da estabilidade é ter um sistema com versões antigas dos software. Por exemplo, o Mageia 6 ainda utiliza o Plasma 5.8, enquanto o Cauldron tem o 5.12. Infelizmente, meu caso de uso mudou e as opções que o Mageia dispõe não casam muito bem com ele. Até propus um projeto não-oficial de construir os software mais recentes do KDE para a versão estável do Mageia, mas estou esperando um retorno do time de empacotadores da distro para ver o que eles acham (pois é, parágrafos cima eu disse que estava sem tempo e vejam só, estou propondo um novo projeto aqui :D).
Gostaria, portanto, de ouvir o pessoal sobre opções de distros que utilizam os software do KDE que atendam ao seguinte caso de uso:
Na verdade eu já fiz uma pesquisa assim e há várias opções disponíveis. Por exemplo, o próprio KDE tem o projeto neon, que faz o caso de uso descrito acima tendo o Ubuntu como base. Há também o OpenSUSE com os repositórios Argon/Krypton, e mesmo distros específicas nesse modelo, como o KaOS e o Chakra. Inclusive isso vai render outro post sobre essas distros.
Minha principal dúvida é sobre a estabilidade e experiência de uso desses projetos. Se você usa algum deles, ou mesmo conhece outro não citado, coloque aí nos comentários para que embase minha decisão de migrar para outra distro (ou não).
KDE contributors continue to polish up KDE software! In addition to our recent work on Discover, KDE Plasma and other apps got a lot of love too, especially Konsole. See for yourself!
We need your help! KDE is committed to polishing our software to a mirror sheen and focusing in the kind of usability that our community is clamoring for, but we need the community’s help to make it happen as fast as everyone wants! Consider becoming a KDE contributor, particularly in development, and help make KDE Plasma and KDE apps total no-brainer choices in the Linux world, and then eventually the whole world…
This is the last day left of the Call for Papers for foss-north 2018. With the help of our great sponsors we have the opportunity to transport you to our conference if you are selected to speak. Make sure to make your submission before March 11 and you are in the race.
Don’t spend time pondering on why you should not talk at foss-north – instead – submit your talk proposal today!
When building the KSyntaxHighlighting framework, the syntax highlighting xml files are compiled into the KSyntaxHighlighting library. In order to do so, we have a small little helper program that generates an index of all xml files. This indexer also validates the xml files against the XML Schema, and performs some more sanity checks.
Review request D10621 tries to extend the indexer even further and suggest optimizations for our highlighting files. For instance, the rule
<AnyChar context="#stay" String="&space;" attribute="Normal Text" />
should be replaced by the faster rule
<DetectChar context="#stay" char="&space;" attribute="Normal Text" />
Similarly, the rule
<RegExpr attribute="Normal" context="conditionNot" String="\bnot\b" lookAhead="true" insensitive="true"/>
should be replaced by the much faster rule
<WordDetect attribute="Normal" context="conditionNot" String="not" lookAhead="true" insensitive="true"/>
The proposed patch above generates more than 1500 suggestions to improve our highlighting files, so a lot of work. Help would be very much appreciated. So if you would like to contribute to KDE and are looking for simple work to do, then feel free to get started by sending improved highlighting files to us via phabricator.kde.org (click “Code Review” on the left, and then “Create Diff” on the top right – or even better use arc to automatically manage your patches). Oh, and please increase the version number in the xml files whenever you provide a patch