📜 Choice of license for the project

[Vianpyro]

Hey team! 👋

As we're moving forward with TindETS, it's time to decide on the open-source license that fits our needs best. The license we choose will determine how others can use, modify, and share our code, so it's a pretty important decision. Below are some questions to guide our thoughts:

---

🤔 Questions to Consider:

1. Usage Freedom:

   • Should anyone be allowed to use our code for any purpose, including commercial apps?

2. Contributions:

   • Do we want contributors to be required to release their modifications as open-source if they distribute them?

3. Forking Concerns:

   • Are we okay with others creating similar apps (e.g., for different schools) without needing our permission?

4. Attribution:

   • Should anyone using our code have to credit TindETS in their projects?

5. Patent Protection:

   • Should we include protections against patents or patent lawsuits?

6. Control vs. Freedom:

   • Do we prioritize ensuring TindETS and all derivatives stay open-source (control) or maximizing adoption and flexibility (freedom)?

7. Long-Term Vision:

   • Do we see TindETS as a community project for everyone, or do we want to retain some level of control over how it evolves?

8. Legal Simplicity:

   • Do we prefer a simple license or one that addresses nuanced concerns like patents?

---

🎯 The Options:

Here are the most popular licenses we could consider:

• MIT License: Simple and permissive, allows broad use with minimal restrictions. Requires attribution.
• Apache License 2.0: Like MIT but includes explicit patent protections.
• GNU GPLv3: Strong copyleft, ensuring all derivatives remain open-source.
• Creative Commons Zero (CC0): Puts the code in the public domain, no restrictions.

---

🗳️ Let’s Vote!

Please share your thoughts or vote for one of the options below. If you have suggestions for other licenses or concerns about specific ones, comment away!

Let’s decide together and make sure TindETS is on the right path!