Language Selection

English French German Italian Portuguese Spanish

GSoC Funds for Krita Development and Outreachy for Summer 2019

Filed under
KDE
Google
  • Our 2019 Google Summer of Code Students

    Krita, part of KDE, takes part in the fourteenth edition of Google Summer of Code. Four students will be working on a wide variety of  projects. Here’s the shortlist:

    Sharaf Zaman will be working on porting Krita to Android. In fact, he already has a port of Krita for Android that already starts on some devices! The port is still missing libraries, scripts to automate building the dependencies and Krita: the first goal of the project is have a dependable, reproducible way of building Krita for Android. Initially, we won’t do much if any work on a nice tablet GUI.

  • Outreachy Summer 2019 Participants & Projects Announced

    In addition to Google announcing the accepted GSoC 2019 summer projects, the Outreachy organization on Monday also announced their accepted participants and projects for this internship effort that encourages women and other under-represented groups in technology to get involved in the open-source movement.

More in Tux Machines

today's howtos

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights