[Trustable-distros] Minimim functionality in any candidate OS

[John Ellis]

I would add documentation. One of major issues we faced at Ford is the
woeful lack of documentation for any of the OS or application software
present on embedded hardware. And given the nature of the embedded
environment, it was (and continues to be) super hard to interrogate the
hardware to try and "understand."

I have updated the "intents" to reflect this. Happy to approve the merge
request though I appear unable to do so at the moment. Likely a user issue.

Cheers.

jte

On Tue, Jul 10, 2018 at 4:09 AM, Paul Sherwood <
paul.sherwood at codethink.co.uk> wrote:

> Hi folks
> based on the draft intents [1] it seems to me that at a minimum any
> candidate OS/distro needs to feature the following components:
>
> 1) boot loader *
> 2) init process *
> 3) kernel *
> 4) libraries for services to 'userland' *
> 5) compilation and build tooling to construct all of the above
> 6) infrastructure for maintenance of the above with mechanisms to
> - assert provenance
> - control/review/approve/reject/apply/revert all changes
> - upgrade all toolchain and target components
>
> Does this make sense?
>
> br
> Paul
>
> [1] https://gitlab.com/trustable/distros/overview/merge_requests/3/diffs
> * Depending on the implementation 1) - 4) may not be separate components
>
>
> _______________________________________________
> Trustable-distros mailing list
> Trustable-distros at lists.trustable.io
> https://lists.trustable.io/cgi-bin/mailman/listinfo/trustable-distros
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.trustable.io/pipermail/trustable-distros/attachments/20180710/e8295f31/attachment.html>