3 ms·

Thanks for sharing! I wrote this post some time ago, and more recently built a thing to do roughly this for my small business: https://github.com/42futures/fir

Thanks for sharing! I wrote this post some time ago, and more recently built a thing to do roughly this for my small business: https://github.com/42futures/firm https://github.com/42futures/firm Had it in practice for about 4 months now and happy so far. It works for me, at my small scale. Hoping to share a follow-up with lessons learned soon.

gearhart 8mo ago
This is incredibly cool. Licensing it as AGPL-v3 throws up an interesting question - given the thing this produces is your company as code, if you use this does your entire company count as a larger work that would need to be open sourced? Or is there an explicit distinction between the "firmware" (excuse me) and the work product?
- jasonpeacock 8mo ago
  Licensing generally applies only to the thing being licensed and not its output. Otherwise all software written with a GPLv3 editor would also be GPLv3…or all software built with a GPLv3 compiler would be GPLv3. (Neither are true)
  - ronsor 8mo ago
    That's because the output isn't a derivative work of the licensed software.