Change license from MPL-2.0 to BUSL-1.1

.github/workflows/check-license.yml

@@ -21,4 +21,4 @@ jobs:
         uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
 
       - name: Check for files without license header
-        run: "! grep -rL --include='*.go' -e'// Copyright (c) Edgeless Systems GmbH.' -e'DO NOT EDIT' | grep ''"
+        run: "! grep -rL --include='*.go' -e'Copyright (c) Edgeless Systems GmbH' -e'DO NOT EDIT' | grep ''"

CONTRIBUTING.md

@@ -1,25 +1,26 @@
-## First steps
+# First steps
+
 Thank you for getting involved! Before you start, please familiarize yourself with the [documentation](https://docs.edgeless.systems/marblerun).
 
 Please follow our [Code of Conduct](CODE_OF_CONDUCT.md) when interacting with this project.
 
 If you want to support our development:
+
 * Add a GitHub Star to the project
 * Share our projects on social media
 * Join the [Confidential Computing Discord](https://discord.gg/rH8QTH56JN)
 
-MarbleRun is licensed under the [Mozilla Public License 2.0](LICENSE). When contributing, you also need to agree to our [Contributor License Agreement](https://cla-assistant.io/edgelesssys/marblerun).
+MarbleRun is licensed under the [Business Source License 1.1](LICENSE). When contributing, you also need to agree to our [Contributor License Agreement](https://cla-assistant.io/edgelesssys/marblerun).
 
 ## Development guidelines
 
-
 Adhere to the style and best practices described in [Effective Go](https://golang.org/doc/effective_go.html). Read [Common Review Comments](https://github.com/golang/go/wiki/CodeReviewComments) for further information.
 
-
 ## Pull request process
 
 Submissions should remain focused in scope and avoid containing unrelated commits.
 For pull requests, we employ the following workflow:
+
 1. Fork the repository to your own GitHub account
 2. Create a branch locally with a descriptive name
 3. Commit changes to the branch
@@ -28,20 +29,22 @@ For pull requests, we employ the following workflow:
 6. Clean up your commit history
 7. Open a PR in our repository and summarize the changes in the description
 
-
 ## Reporting issues and bugs, asking questions
+
 This project uses the GitHub issue tracker. Please check the existing issues before submitting to avoid duplicates.
 
-Please report any security issue via a [private GitHub vulnerability report](https://github.com/edgelesssys/marblerun/security/advisories/new) or write to [email protected].
+Please report any security issue via a [private GitHub vulnerability report](https://github.com/edgelesssys/marblerun/security/advisories/new) or write to <[email protected]>.
 
 Your bug report should cover the following points:
-*	A quick summary and/or background of the issue
-*	Steps to reproduce (be specific, e.g., provide sample code)
-*	What you expected would happen
-*	What actually happens
-*	Further notes:
-    * Thoughts on possible causes
-    * Tested workarounds or fixes
+
+* A quick summary and/or background of the issue
+* Steps to reproduce (be specific, e.g., provide sample code)
+* What you expected would happen
+* What actually happens
+* Further notes:
+  * Thoughts on possible causes
+  * Tested workarounds or fixes
 
 ## Major changes and feature requests
+
 You should discuss larger changes and feature requests with the maintainers. Please open an issue describing your plans.