Create CheckList for Safety Claims on a Generic Linux System.md

[igor-stoppa]

This is the first cut of the checklist proposed during last Autumn ELISA workshop

[reiterative]

Looking good, but a few typos / grammar nits to address

[reiterative]

@igor-stoppa In general, I would prefer to keep the number of individual commits in a PR to a minimum, so that the history is more readable. Would you be OK to rebase -i this to e.g. batch the review updates into a single commit? Or alternatively I could do a squash on merge (although I'm not sure how GitHub handles attributions and signatures when that happens).

[igor-stoppa]

@igor-stoppa In general, I would prefer to keep the number of individual commits in a PR to a minimum, so that the history is more readable. Would you be OK to rebase -i this to e.g. batch the review updates into a single commit? Or alternatively I could do a squash on merge (although I'm not sure how GitHub handles attributions and signatures when that happens).

@reiterative sure I can. How would you prefer that I mention your contributions in the commit message?

[reiterative]

@igor-stoppa sure I can. How would you prefer that I mention your contributions in the commit message?

Please use:

Co-authored-by: Paul Albertella [email protected]

(Turns out I had the privacy checkbox ticked in GitHub, hence the odd 'noreply' email)

[igor-stoppa]

@reiterative I think it should be done, but I'll leave it to you to decide if it's ok to pull the trigger and merge