Closed danlangford closed 1 year ago
however I did notice that technically the legacy license included with your original readme is technically non-compliant with MIT or any open source software. we might want to address that.
Yes, we can address that. Is there something specific or is it more of a boilerplate issue?
here is the license section of the current readme
6. LICENSE AGREEMENT
By using or modifying the contained source code, you agree to the following
terms:
a) You are hereby granted license to use and modify the contained source code.
b) You are not permitted to sell or otherwise use the source code (or modified
source code) for commercial means, without consent of the original author.
c) You are not permitted to distribute the source code (or modified source code),
without consent of the original author.
d) The original author must be acknowledged in derivative works.
e) You will not use the source code (or modified source code) to assist
you in playing online against other human players, without notifying
your opponent that you have this advantage.
f) You will not use the source code (or modified source code) to have an
AI player play other players (whether online through a BM web site or
through other means), without posting a notice or otherwise
indicating that the player is an AI.
the pieces of this that are not compliant with any existing open source license are as follows
b) You are not permitted to sell or otherwise use the source code (or modified source code) for commercial means, without consent of the original author.
c) You are not permitted to distribute the source code (or modified source code), without consent of the original author.
the "consent from original author" bit is a barrier that makes the code technically not "free" as in free to access or free to use without some additional effort (be it money, contact, agreements, etc.)
I also dont know if there is an existing open source license that covers points E and F. I have been researching and havent found anything so far.
one approach could be to label that section as "Gentleman's Agreement" or "Informal Agreement" and have the code technically under MIT.
MIT legally requires that the Copyright line, with your name, follows the source code
revisiting this issue, I think the readme statement can be made consistent with the MIT license. Is there some boilerplate that would then replace this section, or would it simply be deleted since it's covered by the license.md?
i think you can delete this section, use it to summarize and link to the LICENSE file, or duplicate the entire license into this section.
On Sun, Sep 29, 2024 at 8:48 PM Denis Papp @.***> wrote:
revisiting this issue, I think the readme statement can be made consistent with the MIT license. Is there some boilerplate that would then replace this section, or would it simply be deleted since it's covered by the license.md?
— Reply to this email directly, view it on GitHub https://github.com/pappde/bmai/pull/40#issuecomment-2381899097, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFQDVA5HFWY3JSWBR4MOMTZZC3ZJAVCNFSM6AAAAABPCKFM7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBRHA4TSMBZG4 . You are receiving this because you authored the thread.Message ID: @.***>
added pr #61
I made the README a little more rich for displaying on GitHub. markdown is nice in that its generally still very consumable without a markdown parser/displayer
however I did notice that technically the legacy license included with your original readme is technically non-compliant with MIT or any open source software. we might want to address that.