ThingPulse is committed to open-source software (OSS) and we uphold the values of the free and open-source software (FOSS) movement. By the time we founded ThingPulse in early 2018 we had already spent thousands of hours creating and/or supporting FOSS projects. Both on- and off-the-job we have experienced the enormous positive effects that open-source has.
Like many other companies actively supporting open-source we have to find a way to uphold our ideals while still be commercially successful. Sooner or later this little venture should generate enough revenues to feed two Swiss families. Our resources are limited – even if you consider that a developer’s day has 24h plus the night. We are simply not able to give all our open-source projects the same level of attention.
In order to transparently declare what users and customers can expect from us we classified our projects. Each one falls into one of the following categories. Consider this as a kind of mini-SLA, or a service level promise.
Prime projects are those essential for the hardware ThingPulse sells. They can be code infrastructure libraries (drivers et.al.) or sample applications. We commit ourselves to actively maintain the code base and release new versions regularly. The community is invited to raise issues which we will track and process.
Community projects are not actively maintained by ThingPulse. We provide the initial code base, that usually stems from one-off ideas or prototypes, but we do not intend to develop it further. The code may not be production ready but good enough to not be a reputation risk. It is shared because keeping it private wouldn’t help anyone. We invite the community to use, share, or fork the code. We do