Language Selection

English French German Italian Portuguese Spanish

KDE and GNOME: KUnity, Presentations, GitLab and Flatpaks

Filed under
KDE
GNOME
  • A year as a KDE developer | The KUnity Setup

    It has been more than a year that I had push rights for all the KDE repositories. So this is an obligatory anniversary post.

    I got introduced to Linux while searching for development environments that came with all sorts of compilers & interpreters by default and I don't have to manually install those stuff. It was 2012 as far as I remember, Ubuntu 12.04 just came out and it was the first solution suggested by the search engines. Though the unavailability of a proper internet connection meant, that I had to wait a couple more years when one of my friends downloaded a copy of Ubuntu 14.04 for me.

  • FOSDEM and Plasma Mobile Sprint 2020

    This was the 20th anniversary for FOSDEM, I first attended 15 years ago, but this year was the first time I actually managed to present a talk there. The subject was, unsurprisingly, KDE Itinerary. You can find the slides and the video recording on the corresponding FOSDEM talk page.

    KDE had a very busy presence at FOSDEM, Plasma Mobile draw a lot of attention, as did efforts for truly free and user-controlled mobile platforms in general. I’m particularly happy seeing the cross-community collaborations going on in that space.

    FOSDEM is a great place to connect and coordinate with other communities, and by now that’s probably one of the main reasons for me to attend. The collaboration with Nextcloud on integrating itinerary extraction into Nextcloud Hub started there last year for example.

    FOSDEM two years ago saw the first successful flight using a KDE Itinerary rendered boarding pass, this year we had the first ever Thalys ride with a ticket presented in KDE Itinerary. We also made a bit of progress with decoding Thalys binary barcodes, more samples would help a lot here though.

  • Presentations Archive

    Some time ago I ran across remark-cmake, a CMake framework for building remark.js-based presentations. Since I’m a sucker for CMake I started using it, even if my presentations are rarely big-and-complicated enough to warrant a build-system.

    Since then I’ve submitted a few pull-requests to remark-cmake, but also given eight (8) presentations using that framework at four (4) different conferences in four countries on two continents. Current scheduling suggests that one more continent and at least four more talks will be added before summer.

  • Clean and linear history with GitLab

    Many GNOME projects still use clean and linear commit history without merge commits even after porting to GitLab. That means that each commit represents one comprehensive feature or bug fix and there are not any side branches. I am not about to discuss the pros and cons of this approach here, you can find many and many posts on this topic on the internet. I would like to explain some common issues for newcomers when using GitLab forks.

    To make some contribution, one has to create a fork of some repository, push desired changes in a new branch and create a merge request to the original project. Please be sure that the “Allows commits from members who can merge to the target branch” checkbox is checked when creating the merge request (or later using the “Edit” button on the top of the page). This is needed to simplify the consequent workflow for the contributor (and maintainers as well). One of the reasons, why this is needed is the fact, that the changes need to be often rebased before they can be merged (to ensure the linear history). Maintainers can’t do this when this feature is not enabled and have to ask contributors to do so. Another reason is that the maintainers can do some changes when the contributor needs help or doesn’t have time to do the changes itself.

  • Robocode and others

    As expressed in a previous post, I prefer to spend my free time with my kids than with technology (for technology I already have my job). However, when there is an exception to that, I do like to do some sort of smaller projects, like “porting” stuff to Flatpak.

    I did my share of Debian and RPM packaging in the past, and honestly I have never enjoyed it (for a number of reasons not really interesting for this post). But “flatpaking” stuff is completely different to me. Maybe it’s my early involvement with it, or maybe it’s my admiration for how its designed, but the feeling when making a Flatpak is of reward, rather than a chore.

WebKitGTK 2.28 Seeing Flatpak Sandbox Support, WebGL + WebAudio

  • WebKitGTK 2.28 Seeing Flatpak Sandbox Support, WebGL + WebAudio By Default

    Following this weekend's GNOME 3.36 beta, WebKitGTK 2.27.90 is available as a snapshot of this GTK-catered version of the WebKit layout engine on its path towards version 2.28.

    With WebKitGTK 2.27.90 there are many new features baking for WebKitGTK 2.28: Flatpak sandboxing support, WebGL and WebAudio are finally enabled by default in WebKitSettings, support for same-site cookies, support for the webkit-font-smoothing CSS property, support for inspecting service workers to the remote inspector, and various other changes.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Trim Video Clips on Linux Fast with This New GTK App

I won’t pretend that it’s difficult to trim video on Linux because, honestly, it isn’t; a plethora of ace apps designed to make basic cuts and simple edits exist (with Qt-based VidCutter and the best known). But if you’re a GNOME user you might be on the hunt for something that feels and functions a bit more like the rest of your apps. If so, then there’s a new option worth looking in to. The succinctly titled ‘Video Trimmer’ is a new(ish) addition to the roster of video trimming apps for Linux and it’s incredibly simple to use. Read more

ScreenKey Shows Keyboard Presses on Screen in Ubuntu

Mac and Windows screencasters have access to a wide array of apps designed specifically to display key presses on screen as they are typed with macOS tool Screenflick perhaps the best known. But for Ubuntu? You’ll want to try Screenkey. Screenkey is a free, open-source alternative to Screenflick designed for use on Linux desktops, like Ubuntu. When run the app shows each key press on screen as it’s pressed (and while you record, perhaps using the hidden GNOME Shell screen recorder). The majority of Ubuntu users won’t have much use for this tool. But for the 0.25% making video tutorials, explanatory gifs, or other how-to related content? For them Screenkey will be invaluable. Put simply: if you need to illustrate actions associated with a specific keyboard shortcut or command in a screenshot or video clip there is nothing easier to use than this. Screenkey features multi-monitor support, lets you customise font size, font style, and font colour, and offers a crop of advanced settings to control position, timing, opacity, specific character key presses, and more. You can also choose what shortcut activates the app, and decide whether multimedia keys (e.g., volume, pause, brightness, etc) are supported or not. ScreenKey Shows Keyboard Presses on Screen in Ubuntu Read more Also: Ubuntu Weekly Newsletter Issue 638

Mozilla: Accessibility, Net Neutrality, AMP and Rust

  • Mozilla Accessibility: Broadening Our Impact

    Last year, the accessibility team worked to identify and fix gaps in our screen reader support, as well as on some new areas of focus, like improving Firefox for users with low vision. As a result, we shipped some great features. In addition, we’ve begun building awareness across Mozilla and putting in place processes to help ensure delightful accessibility going forward, including a Firefox wide triage process. With a solid foundation for delightful accessibility well underway, we’re looking at the next step in broadening our impact: expanding our engagement with our passionate, global community. It’s our hope that we can get to a place where a broad community of interested people become active participants in the planning, design, development and testing of Firefox accessibility. To get there, the first step is open communication about what we’re doing and where we’re headed.

  • Mozilla Open Policy & Advocacy Blog: Next Steps for Net Neutrality

    Two years ago we first brought Mozilla v. FCC in federal court, in an effort to save the net neutrality rules protecting American consumers. Mozilla has long fought for net neutrality because we believe that the internet works best when people control their own online experiences. Today is the deadline to petition the Supreme Court for review of the D.C. Circuit decision in Mozilla v. FCC. After careful consideration, Mozilla—as well as its partners in this litigation—are not seeking Supreme Court review of the D.C. Circuit decision. Even though we did not achieve all that we hoped for in the lower court, the court recognized the flaws of the FCC’s action and sent parts of it back to the agency for reconsideration. And the court cleared a path for net neutrality to move forward at the state level. We believe the fight is best pursued there, as well as on other fronts including Congress or a future FCC. Net neutrality is more than a legal construct. It is a reflection of the fundamental belief that ISPs have tremendous power over our online experiences and that power should not be further concentrated in actors that have often demonstrated a disregard for consumers and their digital rights. The global pandemic has moved even more of our daily lives—our work, school, conversations with friends and family—online. Internet videos and social media debates are fueling an essential conversation about systemic racism in America. At this moment, net neutrality protections ensuring equal treatment of online traffic are critical. Recent moves by ISPs to favor their own content channels or impose data caps and usage-based pricing make concerns about the need for protections all the more real.

  • Frédéric Wang: Contributions to Web Platform Interoperability (First Half of 2020)

    Web developers continue to face challenges with web interoperability issues and a lack of implementation of important features. As an open-source project, the AMP Project can help represent developers and aid in addressing these challenges. In the last few years, we have partnered with Igalia to collaborate on helping advance predictability and interoperability among browsers. Standards and the degree of interoperability that we want can be a long process. New features frequently require experimentation to get things rolling, course corrections along the way and then, ultimately as more implementations and users begin exploring the space, doing really interesting things and finding issues at the edges we continue to advance interoperability. Both AMP and Igalia are very pleased to have been able to play important roles at all stages of this process and help drive things forward. During the first half of this year, here’s what we’ve been up to…

  • Community crossover, Rust at CNCF, and more industry trends

    The impact: The Rust community has a reputation of welcoming loveliness; increased overlap in the Rust and CNCF Venn diagrams is a harbinger of good things for both communities.

Videos: Software Freedom, OpenSUSE 15.2, "Rolling Rhino" and Linux Headlines