Related work

[ronys]

Consider referencing or including texts from similar documents, such as https://www.acm.org/about-acm/acm-code-of-ethics-and-professional-conduct

[mo-g]

It might be worth adding an index of 'similar oaths' to the bottom of the readme, but to include text is almost certainly not possible.

From the ACM website:

This Code may be published without permission as long as it is not changed in any way and it carries the copyright notice.

The Oath is public domain as of the other day, and so the ACM are free to include parts of it in their code - but the ACM code is copyright with all remix rights withheld, so there is no scope to 'embed' parts of it.

[ronys]

Point well taken re copyright terms.

Referring to it (and similar works - I believe IEEE has something along these lines too) is fine.

Also worth reviewing for interesting ideas, such as continuous learning, to add to the oath, rephrased appropriately.

[bortzmeyer]

Related work (or should I say "earlier attempt"?) https://github.com/larswirzenius/HippocraticOathForIT

[mo-g]

Also falls foul of copyright, but interesting. Ours is cleaner and much more strongly divergent from the hippocratic oath, but the shared ancestry is clearly visible.

Side note, I'm amused that they used the oath-in-separate-file design decision that was rejected a while back. :)