#39 contributing guidelines

[mpetuska]

Closes #39

• Code of Conduct
• Contributing Guidelines
  • Styleguide
  • Issue guide
  • PR guide
  • Development env setup
  • Using Sandbox
• Tips and Tricks documentation for wrapping MDC modules

[mpetuska]

@OliverO2 I'd appreciate your feedback on the docs once you're back from holidays.

[mpetuska]

@OliverO2 I've merged this PR to unblock some further work, but I'd very much be interested to hear your thoughts for a potential separate PR with improvements.

[OliverO2]

@mpetuska I've just completed reviewing the new documentation. Excellent work! I've placed a PR with slight corrections as #56.

Need some more time to check the new Gradle setup and familiarize myself with docs/CONTRIBUTING.md.

[OliverO2]

Still investigating the new Gradle setup with Kotlin 1.6.10 plugin changes:

It seems that my sandbox/kotlin-js-store/yarn.lock changed automatically during a Gradle build. This implies that new/updated packages were downloaded from NPM, installed and run, re-opening the door for immediate execution of hijacked code via Node. Could we return to a setup that

• requires explicit manual invocation to update kotlin-js-store/yarn.lock and
• validates yarn.lock before proceeding to execute anything?