-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSyobonAction's license #6
Comments
Yes, the project needs a license, I would recommend BSD 2-Clause or MIT, as they are the true definition of "free" because they do not have many requirements. |
Hi everyone — sorry for the literal years-late reply. While I do agree that the project should ideally be relicensed to one of the various established open-source licenses (preferably a permissive one such as MIT or BSD 2-clause, which are usually my go-tos), this is unfortunately a rather complicated situation. This is the original "license" that was included with the original Syobon Action source code from 2007, in Japanese:
Here's my English translation of the above:
(※ I am aware that this repo does not have a complete history of all changes prior to RC 2 tracked in Git — this will be corrected.) All that being said, in order to relicense the code and associated assets, you must seek permission from all other contributors for a given project. Unfortunately, my attempts at getting into contact with the other upstream contributors several years ago in 2019 (when this issue was first created) have failed — I never got a response from anyone involved. (In fact, that's why this reply is so delayed — I thought I would post a comment here after getting a reply but uh… that sure worked out!) As a result, I unfortunately do not think I can legally relicense this. I'll keep this issue thread open, though, as I do want to perhaps make another attempt sometime again now that some time has passed (so as to not be a bother). ※ Also, I plan to fully clean up this project in general, including doing another translation pass of the README from the original Japanese text so that it sounds a little less awkward in English. |
If the content wasn't licensed initially then it is considered |
@nekobbbbbbit I am (obviously) not a lawyer, but uh… I don't think that's correct, based on everything else I've read about similar situations. I'll try again to establish contact sometime soon and hope for a proper answer. |
did you write the source code? https://sourceforge.net/projects/opensyobon/ specifies it as GPLv2 |
… Gods, all these years and I never saw that. Thank you for sharing your findings. It's odd that a I'll still make another attempt at contacting both upstream contributors just to be extra sure — notably, I want to make sure that the GPLv2 relicense was done with the permission of the original author. If I don't receive a reply, I will just go ahead with licensing this repo as GPLv2. |
Please ping me for an update. I submitted a port email to [email protected] and it's ready. I even patched |
@akemin-dayo any update on this? |
@akemin-dayo, WRT the GPLv2-licensed Side notes:
I do not remember, if one can contact other SourceForge users when being logged in and I seem to have forgotten my credentials for SourceForge. Note that I also have not downloaded the source code archive and data archive of Syobon Action RC2 from SourceForge and compared it with a Git-checkout of commit 5902a6b here to see if they are identical. P.S.: The Syobon Action Fandom Wiki and the English Wikipedia does not seem to reveal any additional information of the source code history, maybe the Japanese Wikipedia does? |
There is no license specified for the source code and the resources. The following is not enough for this to qualify as an open-source project, since the following doesn't even allow modification and isn't clear on redistribution ("if you wish" doesn't mean "you can").
How to fix this:
This is of course only possible if you have created all of the files, which I assume might not be the case since this is a port, in which case you need to get a permission from the original author(s) to re-license their work.
The text was updated successfully, but these errors were encountered: