Community Member Monday: Aleksi Kallio

Tell us a bit about yourself!
I’m Aleksi, and I live in Oulu, northern Finland. I graduated this spring with a bachelor’s degree in business information technology, and before that I did a vocational degree in software development. Work-wise, my background is in software engineering: I worked on a secure Android smartphone, mostly fixing operating system bugs.
Outside of that, I’m into retro computing: old machines, old phones, and the software that ran on them. There is a lot to learn from software written back when it could only be shipped on physical media. Every time I sit down with a piece of old software, I notice a detail I want to try building myself: an interesting design decision that makes the UI stand out, or a feature that makes me wonder how on earth it was done.
I also like to hang out at my local hacklab and volunteer at gaming festivals. And of course, I like to work on LibreOffice too. What makes LibreOffice interesting to me is that its codebase has a long history. Reading the code and going through the commits allows me to look back in time and see how the software has evolved over the years.
What are you working on in the LibreOffice project right now?
I’m currently working on smaller code fixes. I pick up bugs from Bugzilla, try to reproduce them, and ultimately submit a patch that fixes the issue. In a codebase the size of LibreOffice one can’t just aimlessly duct tape a solution and hope it works. One has to understand the root cause to be able to look in the right place and understand the effect that the change has on the bigger picture.
Coming from a background of debugging Android, I quite enjoy that part of the work. Also, everyone in the community is genuinely great to work with. Code reviews in particular taught me a lot, when a more experienced developer pointed out something that I’d never have spotted myself.
Why did you choose to become a member of The Document Foundation?
Becoming a member felt like a way of saying that I’m in this for the long term rather than just passing through. Before I started contributing, I was a bit scared of putting code out under my own name. I felt like my code wouldn’t be good enough, and that I could only contribute to open source after decades of development experience.
Boy, was I wrong. Going through the issues thoroughly (the community likes to leave hints in Bugzilla comments), understanding the problem, and submitting the best patch I could manage turned out to be enough. Having a mentor and the community’s support on IRC, where I could ask questions whenever I needed to, helped a lot too.
Anything else you plan to do in the future?
I’m planning to move from smaller fixes towards more interesting bugs (our Bugzilla doesn’t contain any hard issues, only interesting ones). I’m also looking forward to working with other teams. I’ve been interested in quality assurance and documentation lately, so picking up small tasks in those areas to build up knowledge for larger work sounds like fun to me.
Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.
If you accept this notice, your choice will be saved and the page will refresh.
What does LibreOffice really need?
This is a tough question. At least in Finland, LibreOffice needs to be offered as a real option in schools. That also means we need more people who know it well enough to teach it.
On a lighter note, we recently watched the Excel World Championships at the hacklab. I’m not sure it’s what LibreOffice actually needs, but it would be great to see people who are seriously proficient with Calc solving problems and competing. In its simplest form, it could be a community competition to see who solves the most brain teasers.













