north-star / commit
added license reasoning
readme.md | 27 +++++++++++++++++++++------ 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/readme.md b/readme.md index d95f35a..d935eba 100644 --- a/readme.md +++ b/readme.md @@ -31,9 +31,9 @@ If your link gets leaked or compromised, you can simply create a new room and sh ## Links -Repo: https://gitlab.com/PavelSafronov/north-star +Repo: [https://gitlab.com/PavelSafronov/north-star](https://gitlab.com/PavelSafronov/north-star) -App: https://pavelsafronov.gitlab.io/north-star/ +App: [https://pavelsafronov.gitlab.io/north-star/](https://pavelsafronov.gitlab.io/north-star/) ## Dev stuff @@ -43,10 +43,10 @@ This repo includes Realtime Database security rules in [database.rules.json](dat Before sharing the app publicly, add these rules in Firebase Console: -0. https://console.firebase.google.com/project/north-star-e5dee/overview is the project used for the public instance of the app. You can create your own Firebase project and use it instead. -1. Open Firebase Console -> your project -> Realtime Database -> Rules. -2. Replace the current rules with the contents of [database.rules.json](database.rules.json). -3. Publish the rules. +1. [https://console.firebase.google.com/project/north-star-e5dee/overview](https://console.firebase.google.com/project/north-star-e5dee/overview) is the project used for the public instance of the app. You can create your own Firebase project and use it instead. +2. Open Firebase Console -> your project -> Realtime Database -> Rules. +3. Replace the current rules with the contents of [database.rules.json](database.rules.json). +4. Publish the rules. Without these rules, your database may allow unsafe writes. @@ -57,3 +57,18 @@ You're looking at it. ### License This project is licensed under the MIT License. + +#### Why MIT for this project? + +Short version: emotional simplicity and momentum. + +- This is a weekend project, and I want low-friction freedom to build, share, and potentially monetize my own work without overthinking legal structure. +- I considered stricter licenses (for example AGPL) to make clone monetization harder, but that adds policy/process overhead I do not want right now. +- MIT is the simplest path to keep shipping and enjoying the project. + +Tradeoff accepted: + +- MIT allows others to clone and monetize too, including with better marketing. +- For this project, that risk is acceptable compared to the cost (time + mental load) of managing a more restrictive licensing setup. + +If priorities change later (for example, stronger anti-closed-clone goals), future versions can be relicensed with a different strategy.