-- Leo's gemini proxy

-- Connecting to gemini.tuxmachines.org:1965...

-- Connected

-- Sending request

-- Meta line: 20 text/gemini;lang=en-GB

Tux Machines


KDE: Bugfixes and GSoC Reports


Posted by Roy Schestowitz on Aug 09, 2022


Today's HowTos

Programming Leftovers



Next week in KDE: mentioning fewer microscopic bugfixes – Adventures in Linux and KDE


↺ Next week in KDE: mentioning fewer microscopic bugfixes – Adventures in Linux and KDE


> I’ve started to worry that mentioning really small weird bugfixes week after week gives the impression that KDE software is buggier than it really is. The truth is that all responsibly maintained projects are constantly landing these kinds of maintenance bugfixes, so it’s probably a bit misleading to be talking about them all the time.


> Instead, I’m going to try only mentioning the big, consequential bugfixes: the ones for bugs marked HI or VHI priority, that have with multiple duplicates, that are really significant in effect, etc. Hopefully this should improve the signal-to-noise ratio in the blog posts.



GSOC Update 2


↺ GSOC Update 2


> Hello and welcome to my second GSOC update! I think I these last few weeks have been really productive in fixing some issues with my code and getting some direction in the next steps for my project. If you remember last time we had just figured out how to get the SVG option to appear in Krita so we can start testing out saving a test SVG file. We were getting a few errors actually trying to use that option and save the file but those should be all fixed now.


> Firstly we were getting a Permission denied: Krita is not allowed to read the file. error when actually trying to save with SVG. At first I thought this was due to how I was trying to use the svgWriter class. The svgWriter assumes that we are only getting to export one layer (the current one) so I thought by trying to save in the context of the whole file, that was tripping it up somehow. After doing some investigation and tracing all the steps in the code this didn’t seem to be the issue.



GSoC Mid-term evaluation: Week 8


↺ GSoC Mid-term evaluation: Week 8


> The major purpose of the mid-term evaluation during the Google Summer of Code program is to ensure the contributor’s progress for their committed timeline for both coding and communication.


> My progress till mid-term


> During the coding period, I started with “ten’s complement,” and after a thorough discussion among the mentors, we decided to divide the activity into three sub-activities. The details for all the sub-activities can be found here. At the time of mid-term evaluation, all these three sub-activities were functional, and the improvements were left, but the basic functioning and the dataset were present. Although, I was one week late to my timeline, which I proposed. I planned to complete “ten’s complement” by mid-term, but nonetheless, the activities are towards their completion now. I’ve added the to-do for this activity under the task. (here) But one thing I realized, and my mentors told me too, is that the small things require more time. One of the reasons why I was unable to complete the activity before mid-term was the incorrect estimation of time and work. And initially, the college was going to open a month later, but it started in the month of July itself. Due to this, I couldn’t provide much time for a few days.




gemini.tuxmachines.org

-- Response ended

-- Page fetched on Thu Jun 13 14:00:15 2024