At the end of 2024 with FOSDEM fast approaching we realised that there might be a number of OCA contributors in Brussels for the conference and took the opportunity to organise a small code sprint.
With a number of experienced OCA supporters and some newbies in the mix we had a couple of days of great camaraderie and coding!
My name is Michel Stroom. It was the first time joining an OCA Code Sprint for me and while I wasn’t sure what to expect, I was pleasantly surprised by the results and progress we made in just a couple of days.
How to join an OCA Code Sprint
Here’s a brief overview of how the OCA Code Sprint concept works — maybe it’s something you'd like to organize or participate in as well.
The sprint kicks off with a clean slate: you note the location, dates, and hours of the event. Then, you invite OCA contributors and members to join, either in person or online. Next, participants list the topics they want to work on, whether it’s an OCA module or another topic relevant to the OCA community.
Throughout the day, all participants update a single document to share their progress, inform others of what they are working on, and add results.
The topics aren’t always strictly OCA-related; sometimes, they can be sharing ideas for fun activities, like organizing a folk dance venue for the next OCA Days in Brussels in September. Or sharing links to interesting podcast about the OCA. This was also added to the shared document.
An OCA Code Sprint is a great opportunity to meet face-to-face, catch up, and talk about the software. Plus, others can easily join and participate online.
Code Sprint Work and Results
| Belgium Localization: | https://github.com/OCA/l10n-belgium |
| German Localization: | Kickstart and improve the migration process. Created two PRs for migration of modules. https://github.com/OCA/l10n-germany |
| OCA database migration: | First estimation for migrating OCA database from 14 to 18 done. with the tool Odoo OpenUpgrade Wizard.
|
| Accounting: | Review and merge this PR: https://github.com/OCA/account-financial-tools/pull/1725 |
| MIS Builder: | Finish v18 migration.
https://github.com/OCA/mis-builder/pull/652 |
| Queue: | Finish the new dead job auto re-queuing mechanism following first feedback from production. https://github.com/OCA/queue/pull/716 |
| Odoo OpenUpgrade Wizard: | Merge request: 104, 110 Fixed issue: 65 https://gitlab.com/odoo-openupgrade-wizard/odoo-openupgrade-wizard/-/issues/65 |
| Maintainer Tools: Migration v18 | https://github.com/OCA/maintainer-tools Create new repos https://github.com/OCA/repo-maintainer-conf/pull/66 Review PRs for missing ports Shopfloor https://github.com/OCA/wms/pull/968 Fixed in https://github.com/OCA/wms/pull/977 |
Non Code Results
| OCA website: | Improvement of various pages. Become A Member: https://odoo-community.org/get-involved/become-a-member Get Involved: https://odoo-community.org/get-involved Sponsor on Github: https://odoo-community.org/get-involved/github-sponsorship |
| OCA branding work: | Received 2 testimonies: Why contribute to the oca, why become a member? |
| New icon for the OCA modules: |  https://github.com/OCA/maintainer-tools/pull/639 |
| OCA Days Venue Hunt: | Checking out “La Tricoterie” near the code sprint location. |
Start your own OCA Code Sprint
If you’d like to organize a code sprint, email Rebecca at events@odoo-community.org and she will help guide you. You can also see more information on our website.
The OCA thanks all involved in the Brussels Code Sprint this January. It was great to have technical and non-technical people to come together and help keep our community thriving!
Written by Michel Stroom, reviewed by Virginie Dewulf, formatted on the website by Rebecca Gellatly
