Update licensing #102

New issue

Open

opened 2025-07-18 23:08:33 +00:00 by Vectornaut · 2 comments

Vectornaut commented

2025-07-18 23:08:33 +00:00

Member

The initial commit of the old prototype put a GPL 3 license file in the repository, and that file is still there as of pull request #91 (commit 4cb3262). We need to decide which open source license we want for the new prototype, and we should update the license file if necessary.

The [initial commit](https://code.studioinfinity.org/StudioInfinity/dyna3/commit/ec10233738459c07667aefbc227fc5f1fceef218) of the old prototype put a GPL 3 license file in the repository, and [that file](https://code.studioinfinity.org/StudioInfinity/dyna3/src/commit/4cb32625556743de30b49eed4b6bfce8ab9190dc/LICENSE) is still there as of pull request #91 (commit 4cb3262). We need to decide which open source license we want for the new prototype, and we should update the license file if necessary.

Vectornaut added the

todo

label 2025-07-18 23:08:33 +00:00

glen commented

2025-07-18 23:17:26 +00:00

Owner

Probably something simpler than GPL3, maybe Apache or even MIT. Thoughts?

Vectornaut commented

2025-07-19 02:56:35 +00:00

Author

Member

I haven't thought about licensing since we talked about it at the very beginning of the project. This crowdsourced license guide, apparently curated by GitHub, might be helpful. I think we said earlier that if we go with some version of the GPL, we should probably use the Affero GPL, because we're building software that's designed to be accessed over a network.

I've started a "Licensing" wiki page with some guiding questions that might help us choose a license:

What are we hoping that other people might get out of our code?
If an ed-tech company started offering a closed-source fork of dyna3 alongside their other products, how would we feel?

If you think of answers to those questions, or come up with more questions, feel free to add them to the page.

I haven't thought about licensing since we talked about it at the very beginning of the project. This crowdsourced [license guide](https://choosealicense.com/licenses/), apparently curated by GitHub, might be helpful. I think we said earlier that if we go with some version of the GPL, we should probably use the Affero GPL, because we're building software that's designed to be accessed over a network. I've started a ["Licensing"](wiki/Licensing) wiki page with some guiding questions that might help us choose a license: - What are we hoping that other people might get out of our code? - If an ed-tech company started offering a closed-source fork of dyna3 alongside their other products, how would we feel? If you think of answers to those questions, or come up with more questions, feel free to add them to the page.