@cas said in GPL Source Code:
I think it's a reasonable assumption that there is a private repo for the oboo clock (closed source) and all the current application and firmware development effort is taking place there and is focused on that.
Very likely, yes.
That they want to keep the oboo-specifics closed, I can understand.
But what I really think is plain stupid, even from a commercial point of view, is that they do not work in the open improving their OpenWrt/LEDE tree for the Omega2 platform.
They could serve both the oboo project and their Omega2 customers! But how they do it now alienates the Omega2 maker community, instead of involving it.
It's "wow, they build something cool and professional based on the Omega2 platform, I could do that, too" vs. "oh, they are no longer interested in the Omega2 platform they sold me and doing something entirely different".
I hoped the oboo clock would help bringing the Omega2 forward as a platform. Now it looks like the result will be the opposite :-(
Really, @onion, it's not that hard!
I can tell because I'm doing exactly this. I do commercial products based on Omega2+LEDE 17.01 for a living. And I have a number of fully open fun projects also based on the same platform (pixelboard, a LoRA gateway, a DC motor controller...).
Only a few packages related to my commercial products are not public (such as the site specific updater tool). The rest is the same for all projects, and open! Including things like a kernel driver for WS28xx LED chains or making i2s sound work to play MOD sounds...
And guess what? I'm doing it that way primarily because it is the most efficient way to get stuff done! I could not do all that if I had to worry about a separate LEDE for each project, all the back- and forth merging etc.
And OpenWrt/LEDE is a phantastic environment to do exactly that. No problem to have a public and a private feed to organize different projects. The only thing I had to do, to make my workflow really smooth, was to write a little shell script that allows to apply a
diffconfig plus some tree-wide patches (e.g. this one to make SPI work) for a certain project to a virgin LEDE checkout.
This way I can make use of the enormous and continuous work that goes into OpenWrt/LEDE every day, and others can make use of my work as they see fit.
I really don't get how Onion can miss out on the benefits of a more open development.