The Path to Arcalibre 0.0.2
It's been a hot minute since our last update, but there has been a ton going on behind the scenes. Since announcing the 0.0.1 release of Arcalibre, we've:
- Separated out several parts of the original Calibre codebase into new Python packages that can be built and tested on their own.
- Set up continuous integration for building Arcalibre and all other rereading Project packages.
- Reworked features such as CHM and RAR file support to reduce external dependencies.
- Started building rereading Project packages on macOS; not Arcalibre itself yet, but we're making progress!
- Worked with external contributors, testers, and even participants at PyCascades sprints.
- Experimented with different ways of organizing contributions and community conversations (forums, IRC, in-person, etc).
Thank you so much to everyone who has helped us to get this far, including @sherbang, @carpaltunnel, @ddelemeny, @r-tae, @jasonmclaren, @mvanderkamp, @BumblingCoder, @siriusfox, @Firesphere, @aleteoryx, @Astatide, @DaforLynx, @Ember, @SnoopJ, @cthos, and @whitequark! The tech stack going into Arcalibre 0.0.2 is much more robust as a result, as it now builds within a container, can be used with the latest free-threaded Python builds, and can be developed using standard Python tooling such as pipx and PDM. That alone puts the rereading Project in a much better position to deliver future versions of Arcalibre, and to do what we set out to do: make an e-book management tool that works, and respects the importance of artistic labor.
So we're done, right? Surely, Arcalibre 0.0.2 is good enough to just start using? In the most honored of literary traditions, we find ourselves swearing at this point: fuck, no. There is much more to be done, including getting format conversion, e-reader device management, e-book viewing, and more back up and running. The focus in Arcalibre versions 0.0.1 and 0.0.2 has been getting the build process and tooling working, but that broke almost everything about the original Calibre application in the process. Now we start the long process of getting Arcalibre back into working order.
Moreover, there's much more work to be done in making Arcalibre work for as many people as possible, whether that's expanding the range of Linux versions and distributions supported, adding back macOS and Windows support, or even getting Arcalibre working on AI-free operating systems like NetBSD. No matter what your expertise and passions are, we can use your help in making Arcalibre work to support the art of the written word.
We've both made a lot of tangible progress, and have a long way to go. We've made friends along the way, and will continue building community going forward. Getting to a working build with proper CI and pipelines was a really important goal for the year, and we made it — the work ahead is that much more tractable as a result.
If you're looking to get involved, there's a few things that would be especially helpful as we get going into 2027 and Arcalibre 0.0.3:
- Testing and reporting bugs
- Diving into code and fixing bugs
- Improving DevOps across the board
- Packaging Arcalibre for various Linux distributions
- Helping with macOS and/or Windows builds
- Improving user documentation and contributor onboarding
- New logos and other artwork
- Community moderation
- Building awareness and spreading the word
Also in 2027, rereading Project members will be joining both tech conferences and reading conventions, so look to this space for chances to meet up in person!
In the meantime, thank you again for all the help, donations (over 250 people and counting!), moral support, technical contributions, and generalized good wishes. We'll see you on social media, in forums, and in the code. Keep reading, keep rereading, and friends — help keep art alive.