Contract weekly report #59

Blog post by PulkoMandy on Fri, 2015-01-16 08:11

Hello world!

I have not given any news from the Google Code-In for some time. It ends this week, and students have completed more than 400 tasks for Haiku. While this includes a lot of simple tasks (the simplest “getting started” ones involved just booting Haiku and running StyledEdit), it means the students at least got to see what Haiku is. We have a more complete set of recipes in haikuporter waiting to be packaged.

Contract weekly report #58

Blog post by PulkoMandy on Fri, 2015-01-09 08:45

Hello there, welcome to the first contract report for 2015!

This report summarizes changes done since 19 of december as I was a bit away from keyboard for the winter break. But I’m back for another year of Haiku coding!

Contract weekly report #57

Blog post by PulkoMandy on Fri, 2014-12-19 07:56

Hi! Work continues on putting Haiku in shape for the R1 release. This week I worked mostly on UI fixes to make our apps look a bit better.

Contract weekly report #56 - Media fixes and more!

Blog post by PulkoMandy on Fri, 2014-12-12 09:18

Hello world!

With the fixes done this week, we now have less than 2500 open tickets left before R1. I had crossed this bar last week already, but not for long as new tickets sometimes come faster than we can close old ones. I think now we are under that bar in a more durable way.

Contract weekly report #55 - GCI and more

Blog post by PulkoMandy on Fri, 2014-12-05 08:39

Hi! So, this week marks the start of the Google Code-In contest. I’ve spent some of my time preparing some tasks for it as well as reviewing the work from students. Our IRC channel is incredibly busy, and there have been 110 tasks completed by 65 students already. You can currently watch the leaderboard here for unofficial stats: http://ematirov.tk/org/haiku/

Contract weekly report #54

Blog post by PulkoMandy on Fri, 2014-11-28 08:30

Hello world!

Work continue this week with a lot of long overdue UI enhancements. Not very technical work there, but finally closing all those tickets allows us to more easily find the important ones in the bugtracker. These changes also make Haiku more polished and easier to use, which is one of the project goals, after all.

Contract weekly report #53

Blog post by PulkoMandy on Fri, 2014-11-21 09:12

Hi!

After a great week-end at the Capitole du Libre showing Haiku to other people in the free software community (read François' report for more details - video of my talk should be available “soon”), I’m back to work on the code.

Contract weekly report #52 - On to beta1!

Blog post by PulkoMandy on Fri, 2014-11-14 08:52

Hi,

This week I continued work on moving Beta1 forward, fixing some important and less important bugs. To make things clear about what to expect in the upcoming weeks, I will spend more time on Beta1 tasks, but I’ll also continue working on WebKit. However, my work there will focus on fixing bugs, rather than adding new features.

WebKit weekly report #51 - back to normal schedule

Blog post by PulkoMandy on Fri, 2014-11-07 07:57

Hello there! I'm now back home after BeGeistert. As you may have noticed if you read the development mailing list, there is a general agreement from the development team for a beta 1 release "real soon now", and after that, it will be time for R1. I will be coordinator for these, which means I will spend a bit less time on WebKit to take care of some other tasks. But I'm not giving up on WebKit, which still needs a lot of changes to reach release-quality. I was a bit less active this week as I had to recover from the lack of sleep at BeGeistert. But it's all fine now and I should soon be back at full speed.

BeGeistert 028 coding sprint report

Blog post by PulkoMandy on Fri, 2014-10-31 08:29

Hello world! As you probably know, I'm reporting from Düsseldorf this week, where the BeGeistert coding sprint is about to end. I won't cover the events of the weekend as Humdinger has already written a complete report for it, including videos of all the talks. So let's instead dive into the coding sprint event, and see what we hacked on during the week