contract work | Haiku Project

'Packaging Infrastructure' Contract Weekly Report #4

Blog post by waddlesplash on Fri, 2015-07-03 16:20

contract work, infrastructure, package management

After I took last week off for vacation, this week went very well. HaikuPorts has been migrated to GitHub, many corner cases related to HaikuPorter have been resolved, and most of the infrastructure issues that were directly related to setting up the package build server are gone.

'Packaging Infrastructure' Contract Weekly Report #3

Blog post by waddlesplash on Fri, 2015-06-19 18:48

contract work, infrastructure, package management

Hello again!

As mentioned in last week's report, I planned to work on integration with IRC to allow the developers to get real-time updates on what the builder was doing, finishing the documentation, and then working on the logic that actually builds packages. The first two of the three are pretty much done, and the last one I did get started on. So this week went pretty well.

'Packaging Infrastructure' Contract Weekly Report #2

Blog post by waddlesplash on Fri, 2015-06-12 18:04

contract work, infrastructure, package management

Hello, Haikuvians!

This week was just as productive as last week. I did start on the builds logic, which now can run "builds" (lists of commands) in sequential order. I also improved the builder management system, and created documentation for pretty much everything.

'Packaging Infrastructure' Contract Weekly Report #1

Blog post by waddlesplash on Fri, 2015-06-05 17:52

contract work, infrastructure, package management

Hello world!

This week was rather slow: I've logged only 18 hours of contract time this week. I expected this, partly because I didn't expect to do any work on Monday (as mentioned in my first blog post) and partly because I still had some coursework to finish up the semester with. But despite that, I got a ton of stuff done, and the foundations for the following weeks' work are well laid.

Beginning of 'Packaging Infrastructure' Contract

Blog post by waddlesplash on Mon, 2015-06-01 13:14

contract work, package management, infrastructure

Anyone following the "haiku-inc" ML will have noticed that I've been approved to spend 240 hours (around 6 weeks of full-time work) on Haiku's packaging infrastructure. This mostly means I'll be working on the package building system, which will manage the "HaikuPorts" package repository, ensuring it's up-to-date across architectures (and later, across both nightly & release builds).

End of contract - closing words.

Blog post by PulkoMandy on Wed, 2015-02-18 08:21

contract work

Hi,

As you probably have noticed, there were no weekly report in the previous weeks. The reason for this is that my contract is currently stopped. There is currently not enough money in Haiku's treasure chest to safely continue it. So, it's time to me to get back to "real life" and a full-time job in a software development company.

First of all I want to thank everyone who made this long contract possible by donating money to Haiku. It was a great experience for me, and a lot of fun as well. I did my best to move Haiku forward towards the R1 release. Unfortunately the beta 1 still isn't there, and we currently have 57 blocking tickets. It is a small number, but only the most complex or big issues are left.

Contract weekly report #61

Blog post by PulkoMandy on Fri, 2015-01-30 09:27

contract work

Hello there!

As you may have noticed if you watch the commit list closely, my libbind work has not been merged yet. There are still some bugs to solve there, but I got sidetracked. I use BReferenceable in my DNS cache implementation to keep track of the cache entries. BReferenceable is a class used in Haiku to implement reference counted objects. In C++, the language only has very simple memory management, in the form of the new and delete operators. Objects can be allocated on the stack (they are temporary and only last as long as the function they are declared in is executing), or on the heap (for long lived objects). Objects allocated on the stack are deleted automatically when the function exits, while objects allocated on the heap must be deleted manually. This is one of the annoying parts of C++: managing the lifetime of these objects, making sure they are deleted only once, and that no one will try to use them after deletion.