align to "Guidelines for authors submitting code & software"

[mxochicale]

https://www.nature.com/documents/GuidelinesCodePublication.pdf

[mxochicale]

Nice comments on choosing a Creative Commons for licensing software: https://github.com/github/choosealicense.com/issues/33. For further information on choosing a license, see https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository . Addiitonally, you can visit https://github.com/timoxley/osi-licenses-full/tree/master/licenses for licences in markdown style.

[mxochicale]

• [x] double check corrections in code and tidies up data path

[mxochicale]

• [x] Do a final revision of the repo.
• [x] Merge branch 10 to main and,
• [x] create DOI link for code in Zenodo as indicated below:

As a condition of publication, it is expected that access to the version of code associated with the paper is appropriately maintained by the authors. For subsequent source code revisions and upgrades, we strongly encourage authors to deposit and manage their source code revisions in an established software version control repository, such as GitHub, and use a DOI-minting repository like their institutional library, figshare or Zenodo.

Follow this for the above: https://guides.github.com/activities/citable-code/

DONE on : Sat 3 Apr 15:00:42 BST 2021

NOTES.

• Make a public repo and synchronise your repository with Zenodo.
• For the release in github, one needs to add description for the version:

  Release v1.0.0 of srep2021 repository for the pre-print of "Nonlinear methods to quantify Movement Variability in Human-Humanoid Interaction Activities" contains a 100% reproducible work. For 100% reproducible, it is meant that code, data, tex project and CI-github action with free-cortex framework) is available and documented.

• Go to edit in the Zenodo repo to check details of the release: title, keywords. Then SAVE and click PUBLISH