Skip to content
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

License info #13

Open
BlackFire51 opened this issue Jan 7, 2022 · 5 comments
Open

License info #13

BlackFire51 opened this issue Jan 7, 2022 · 5 comments
Assignees

Comments

@BlackFire51
Copy link

Hi,
the repo currenty has no license info included and is therefore copyright protected.
If this is not your intention could you add a license please ?

regards, Matze

@icedream
Copy link
Owner

I currently don't know which license to settle on due to the fact that I compile with TeamSpeak3 Client SDK code. I don't think I can release it under the MIT or GPL 2+ licenses like I normally would. BSD 3 seems to be a candidate.

I'm going to approach this once I have thought about it more.

@icedream
Copy link
Owner

icedream commented Apr 27, 2022

Unfortunately after sitting on this issue for a few months no further clarity has been reached:

  • TeamSpeak's copyright on the plugin SDK is merely this which would effectively disallow any proper open-source licensing up front.

    Copyright © TeamSpeak Systems GmbH. All rights reserved.

  • The Plugin SDK code (with example plugin code being the only bits containing any licensing hints) does not provide any more exact licensing hints.
  • The only official download web page only links the GitHub repository, so even the website provides no exact licensing hints.
  • There is this so far unaddressed issue: License for this repo teamspeak/ts3client-pluginsdk#3
  • The best hint is the official .NET SDK which is licensed under BSD-3, assuming that the plugin SDK is a derived subset of the full client SDK which is not proven.
  • Package maintainers repackaging the original code only mark the code as custom-licensed

Please feel free to generate activity in the linked issue, or to discuss how to handle this situation here. I am unsure whether declaring the TeamSpeak-owned code as "All Rights Reserved" and adding my code as BSD-3 licensed would solve the issue or put me deeper into copyright violation at this point - maybe I will even have to remove the pluginsdk folder altogether. Not an easy issue.

@BlackFire51
Copy link
Author

Thanks for looking into it and for the update.

Removing the SDK code form the repo and just compiling againt the headers sould be fine under the interoperability clause of the DMCA (i'm no legal expert so no legal advice), but sice Teamspeak is a German company german copyright could also apply.

Als long as the do not add a licence all ts3 addons seam to be in copyright hell.

I guess i will have to rewrite everything in C++ or something and use handwritten headers to compile the lib.

@icedream
Copy link
Owner

Definitely gonna look into the removal option then, possibly will have to do the workaround a lot of cgo-bound Go libraries seem to go which is configuring some odd compiler flags to get it working. Annoying, but will have to do.

Afterwards, I can tackle this issue again.

@icedream
Copy link
Owner

icedream commented Jun 15, 2023

Heads-up: I am preparing to introduce the BSD 3-Clause license as part of the update required to make the library work for API version 26.

This will remove the pluginsdk/ folder from this repository and I will rely on properly set cgo environment flags for this. How exactly that needs to be done will be documented in the README once tested by me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants