Discussion: Licensing and distribution #2
Description
Dr. Cotterell made a brief mention of licensing and distribution considerations in his comment here. I'm making this separate issue to continue discussion on those topics.
Here are the licenses of the projects we're using in-tree:
| Project | License |
|---|---|
| OnlinePythonTutor | MIT |
| traceprinter | AGPL-3.0 |
| java_visualize | AGPL-3.0 |
| codemirror | MIT |
So, the potentially problematic license would be the AGPL, particularly the virality aspect of it. Since we (at least currently) don't plan to distribute binaries or code (only generated images), I don't think we will incur any responsibilities from the license in terms of sharing source. I have no opposition to licensing my code under the AGPL, but I know that UGA retains most IP rights to work done by their employees (i.e. me) on the clock, so we might have to get a sign-off from somebody in the legal office to keep things completely above-board.
While traceprinter and codemirror have been left untouched, I have made some modifications to the sources of OnlinePythonTutor and java_visualize, so I think having the script download those at runtime wouldn't be a great solution. If we did go that route we'd have to patch the changes in after they're downloaded, which seems kind of hacky to me.