secure-systems-lab / sample-documents Goto Github PK

Most of the sample documents in this repo are outdated. See, eg.

• theupdateframework/python-tuf#890, uptane/obsolete-reference-implementation#195, in-toto/in-toto#295 and secure-systems-lab/securesystemslib#171 for important fixes related to automated testing with travis and tox and code coverage measurement
• in-toto/in-toto#296 for a massive overhaul of the pylint config file
• in-toto/in-toto#294 for a new way of doing dependency monitoring
• theupdateframework/python-tuf#892 for automated license scanning
• GitHub's issue and PR template guide for a new way of providing these templates (not yet adopted by any of our projects).

We should either keep the documents here up-to-date, or replace them with pointers to our most mature projects (i.e. TUF/in-toto). A mix of both is conceivable as well, i.e. add a disclaimer (or strengthen the existing one) that up-to-date sample documents can be found in above mentioned repos, while also syncing the docs here every now and then.

Any thoughts, @JustinCappos, @SantiagoTorres, @mnm678?

Is this repository a good place for general project templates for the lab? For example, .pyup.yml, .travis.yml...?