Going Open Source under GPLv3 but not being Google Dev Library worthy
Mar 15, 2022
Towards the end of 2021 and since then, more and more users and software developers have expressed interest in Track My Indoor Workout. I mostly get feature requests, but several users went to great technical depths to help me support their fitness machines. As I involved more developers in the project, I needed to get it ready for contributors, so I set up CI/CD on GitHub. Right now that consists of three steps:
- Flutter CLI formatting check with 100 characters (“flutter format –line-length 100”)
- Flutter analyze check with the CLI (“flutter analyze”), based on the official flutter_lints package (see configuration)
- Flutter test run, which right now mostly consists of unit tests
At that point, the source code was still closed. The only reason was proprietary fitness machine protocols. Not only did I have to reverse-engineer Precor Spinner Chrono Power’s protocol, but I also ran into several other examples: the Matrix treadmill (TF50) and indoor bike (R50) claimed FTMS compatibility, but both of them botched the standard and I had to reverse-engineer them. I reached out to many companies, and I was ready to receive documentation that might require a signed NDA (Non-Disclosure Agreement). Manufacturers are very protective of functions that modify a machine’s behavior (for example, changing a treadmill’s speed) due to liability reasons. Unfortunately, not one manufacturer has gotten back to me so far, with the exception of KayakPro ergometers. So I won’t wait for any information or NDA anymore, because I’d like to follow the traditional open-source contribution model. After going open source, I felt a tremendous relief.
Let’s talk about the license. The most popular ones are MIT and Apache; these are very permissive, but I wanted something that aligns better with the application’s mission. Preventing machines from becoming coat racks and fighting the subscription-fee milking of athletes required the application to remain free. GPLv3 guarantees that: if anyone forks or uses the source code, any modification must be published as open source!
I tried to nominate the project to the Google Dev Library to get it out to the public more. I had a feeling in the back of my mind that GPLv3 would be a no-no, but I didn’t see any signs of license limitations on the Dev Library’s pages. Only during the actual submission process did it turn out that—surprise—only MIT and Apache licenses are accepted. So I landed on an Apache 2.0 + GPLv3 dual-license model for the submission to go through.
Unfortunately, the submission wasn’t accepted. I assume I’ll need to increase test coverage and code quality, have more contributors, and ultimately have a more thriving project. Therefore, I reverted the license back to GPLv3 and will keep adding new features requested by users. I’ve been working on support for these machines, to name a few: Yesoul S3, LifePro FlexStride Pro, Stages SB20.