Firstly, thanks for the suggestion summersab!
We (as in TurnKey - I'm one of the core team) could definitely help in this regard; although we don't yet have an RPi port (currently we only support amd64). I did start work on it some time ago but I ended up having to redirect my attention to higher priority (for us) matters. I really want to get back to it but I'm not sure when that will happen...
summersab has summed us up pretty well and essentially once we have an RPi port and modify TKLDev to support building RPi images then we can build all of our current library for RPi no problems. Some of them may not perform that well on the low spec hardware (I'm thinking particularly Ruby apps like GitLab and Canvas which are very resource hungry), but perhaps the RPi community might be able to help us make them work better? Or perhaps we could just exclude them from RPi builds?
We are more than happy to accept new appliance build code so long as it confirms to our requirements/standards. Appliance code contributions are a great thing for us as it increases our library (and we would build them for amd64 too). So there would be plenty of room for the community to be involved.
Even if we didn't include specific community supplied appliances in our library; there would be nothing stopping people from sharing their build code (on GitHub or similar). Then individuals could build custom images themselves using TKLDev (from the source on GitHub). All of our tools are open source and public (again on GitHub). So even if we didn't officially provide them, there would still be the transparency that would (hopefully) alleviate Heater's (legitimate) security concerns. Whilst we are nowhere near as popular as RPi; I'd like to think that with literally millions of downloads over the last 8 years we have a pretty good reputation on security to uphold!
@Heater - To further respond to the points you raised; we "pay the rent" already and have a comprehensive global mirror network (for image distribution). Adding an additional build format to our current batch builds (~100 appliances
in 9 different build formats
) is relatively insignificant. We already take responsibility for our images and would continue to do so.
The only point that I can't properly answer is "who will do the work". At this point I am not in a position to take this on (but I would really love to!) Once TKLDev supports RPi and we have a version of Core (our base appliance) that runs reliably on RPi then we would happily take on the rest of the work to get as many of our existing appliances built and publicly available. As we develop new appliances we would automatically batch build them for RPi too. And as I suggested above, anyone from the community that wanted to contribute new appliances could (and would be welcome).
@summersab & @stderr if you (and/or anyone else) is interested in discussing this further then perhaps it might be better to move that discussion to our forums? summersab has already started a thread
- which is what bought me here. I won't be able to be directly involved at this point, but am happy to give as much support and mentoring as I can.