To close out our 25th-anniversary series, we sat down with two long-time voices of the Haiku community:
Korli, who discovered BeOS back in 1999 and has been part of the community ever since.
PulkoMandy, who joined via Google Summer of Code in 2009 and has since become one of the project's most active contributors and code reviewers
Between them, they cover a large span of the project's history — from the first lines of code to where Haiku stands today.
Grab a coffee — here's what they had to say.
___
HaikuInsider: How did you discover BeOS and then Haiku, and what made you stick with the Haiku project for so long ?
Korli: It's a long time, I remember I discovered BeOS from a friend. I think it was R4.5 in 1999, then I tried myself R5 PE and R5 later when I could buy my own computer.
From the start I had fun toying with the OS, following BeBits. I began to read about the API documentation, learning how to code small apps and a driver. All of it was challenging, and a diversion from my day job programming.
OpenBeOS was then started, I thought I could follow and eventually join to help a group of developers. It became a hobby, we got to know each other in person.
The Haiku codebase stays easy enough to navigate, the possibility of coding and fixing bugs in various parts of the OS revives my interest in case I get bored.
PulkoMandy: I discovered BeOS sometime around 2007. I was still in high school back then. A friend who didn’t have a DSL line at home asked me to download a version of BeOS for him, because he had a pretty old computer that wouldn’t run smooth with anything else.
At the time, Haiku wasn’t even in Alpha 1, and did not distribute even nightly images. I think app_server had barely started running Tracker, but maybe I’m mis-remembering and I was just reading older blog posts.
Since then I had been following progress on Haiku, and in 2008 I applied for GSoC. My application was rejected, but I tried again a second time the following year, with a little more experience (still being a student, that wasn’t a lot of experience, but enough to put up a better proposal).
The GSoC project was a success, and in the autumn after that we went to the BeGeistert conference together with Philipe Houdoin, Maxime Simon and mmu_man. Quite a trip by car accross France and then into Germany.
During and after this GSoC project, I learnt a lot from Haiku about software programming. So, I’m trying to give back a bit of that and share my experience with people joining the project. Also, at some point I started using Haiku as my main operating system, so, I’d better keep it running!
___
HaikuInsider: What has changed the most in the way Haiku is developed between when you started and today ?
Korli: What changed the most is probably the tooling,
CVS on Sourceforge for bug reports, not ideal to develop a complete OS.
PulkoMandy: A lot has changed! When I started contributing to Haiku, there was no continuous integration, no nightly builds, no code review tool. We were still running subversion, and often the server was locked on week-ends because hard disks were full. We had to wait for an admin at BerliOS to notice the problem when they were back to work on mondays.
We also now have a package manager, which is a great help in managing ported software and providing better quality packages. And, over the years, the focus of development changes from building new features to stabilizing and improving performance.
Some contributors have come and gone, others are still there since the very start. From that point of view, I really miss the BeGesitert conferences and the coding sprints. It’s sometimes important to meet other people in real life and discuss issues in a meeting room. Unfortunately, it seems pretty difficult to resume this, some of the current contributors are not interested or live too far away.
___
HaikuInsider: What would an "ideal Haiku" look like to you ?
Korli: An "ideal Haiku" for me is one which wouldn't get irrelevant, getting updated enough to be natively usable on newer computers.
PulkoMandy: I am pretty happy with how it is right now. Otherwise I would be working on changing it already.
The main limitation is hardware support, which would resolve some minor annoyances. For example, it sure would be nice to at least switch between external and internal display on my laptop without rebooting the machine.
___
HaikuInsider: Any advice for someone who wants to start contributing today ?
Korli: I'd say, it's usually easier and rewarding to take over something to maintain or modernize it, for instance at HaikuArchives, than track some bugs in the core OS.
PulkoMandy: There are a lot of things to do, small and large. I think the main advice is to pick a problem that affects you and see how you can improve things. I think some people try to approach the project by wanting to understand everything before trying to make any sense, which won’t quite work for a project so large.
So, pick one problem, and don’t hesitate to ask for help if you don’t know where to get started. Other people can surely give you a few hints on where the code you should look at is located, and maybe what kind of changes you should make. I’ve been working on the documentation, but it’s still very incomplete. So, don’t expect to learn it all on your own, you pretty much have to rely on the other contributors at the moment. But that’s fine, they are all nice and willing to help.
___
HaikuInsider: Is there a particular moment, bug, or contribution from your time on Haiku that you're especially proud of ?
Korli: Sorry I tend to forget some of my contributions, and sometimes find myself as the guy who wrote some sloppy code :)
PulkoMandy: My GSoC project brought internationalization to Haiku, before that it was available in English only. I think this is the most impactful thing I did, opening up Haiku to a lot more people who are not native English readers. However, I wouldn’t know much about it, because the community around the forums and mailing lists is still mostly in English.
I would love to hear from other language communities as well! Having a more diverse set of users and developers is certainly welcome, and we could do much better on that aspect still.
___
HaikuInsider: To finish is there a message you'd like to pass on ?
Korli: Yes, always publish project code when possible, it's better than it being lost.
PulkoMandy: I hope you all find happiness in whatever you do :)
I sure do with my contributions to Haiku.
___
HaikuInsider: Thank you for your time and the richness of your memories — it’s thanks to contributors like you that Haiku is still here, 25 years on.