Well, it looks like this year it will be difficult to have the usual coding sprint, due to travel restrictions and other organizational problems. Let’s do an online one instead.
I suggest to run it sometime between 18 and 31 of october, mainly because I already took these days off work before waddlesplash brought up the idea of an online sprint again (that’s two weeks long, but you don’t have to stay online the whole time, read on for more info); and because it matches with the traditional dates for the coding sprint and BeGeistert conference. Also, this more or less lines up with Hacktoberfest, so if you work on something that’s hosted on github or gitlab, it’s an opportunity to get some hacktoberfest goodies as well (that won’t work for Haiku itself, but it could work for HaikuArchives and HaikuPorts projects, and the haiku website). This could also be used to replace Google Code-In.
If you are not familiar with our coding sprints, here is a summary of how it goes:
The idea is to gather developers in a room (usually a real meeting room but this time we’ll have to do with an IRC channel or something like that). It is open to anyone who wants to work on Haiku, resurrect their own or someone else’s BeOS app, port applications, help finalize patches that are waiting on our Gerrit for some cleanup work, or generally anything around Haiku. The idea is that you can ask for help from other developers, discuss your technical problems and see if anyone has an idea on how to solve them, etc.
You can decide to use this time to focus on one single big task, or to try to fix as many small problems as you can. You can decide to take two weeks off work like I did and work day and night on things, or just do the weekends or a few hours in the evening. It’s very flexible (let’s make the most of the online way of doing things).
At the end we can write an article on the website showing what was accomplished in two weeks.
There is no formal registration, but let us know here if you are interested and maybe what you plan to work on.