<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Flatpak on Jente Hidskes&#39; website</title>
    <link>https://www.hjdskes.nl/tags/flatpak/</link>
    <description>Recent content in Flatpak on Jente Hidskes&#39; website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Copyright © 2016-2022 Jente Hidskes</copyright>
    <lastBuildDate>Sat, 01 Sep 2018 00:00:21 +0200</lastBuildDate><atom:link href="https://www.hjdskes.nl/tags/flatpak/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Gcolor3 version 2.3 is out!</title>
      <link>https://www.hjdskes.nl/blog/gcolor3-2.3/</link>
      <pubDate>Sat, 01 Sep 2018 00:00:21 +0200</pubDate>
      
      <guid>https://www.hjdskes.nl/blog/gcolor3-2.3/</guid>
      <description>Finally, after a long period of sporadic commits, I released Gcolor3 version 2.3 out into the wild!
          This release was two years in the making (two years and twelve days, to be precise). It features 67 commits, resulting in a redesigned saved colors page, a redesigned headerbar and loads of under-the-hood changes. In this post, I want to go into a little more detail on the development and what led up to Gcolor 2.</description>
    </item>
    
    <item>
      <title>GSoC part 2: community bonding</title>
      <link>https://www.hjdskes.nl/blog/gsoc-part-2/</link>
      <pubDate>Fri, 19 May 2017 16:01:04 +0200</pubDate>
      
      <guid>https://www.hjdskes.nl/blog/gsoc-part-2/</guid>
      <description>Two weeks have now passed since my introductory blog post, so as promised here is part two! The theme of this blog post is probably something along the lines of preparation, as that is what I&amp;rsquo;ve been doing mostly.
The period between that of announcing the accepted student proposals and phase one is called the community bonding period. In this period students are supposed to get to know their mentors, their organizations, familiarize themselves with their projects (even more) and get everything ready to start off the coding period on May 30th.</description>
    </item>
    
  </channel>
</rss>
