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

apache license ok, I'm a licensee, who's the licenser? #44

Open
ghost opened this issue Nov 15, 2017 · 4 comments
Open

apache license ok, I'm a licensee, who's the licenser? #44

ghost opened this issue Nov 15, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Nov 15, 2017

I mean, who has the copyright?

look at the platform license:

universAAL is distributed with the Apache License, Version 2.0, January 2004,
as specified under https://www.apache.org/licenses/LICENSE-2.0.

Comparing with the info here, I can see apache web server is under "Permissive FOSS type", and actually with the same apache license 2.0 uAAL comes with, which "retains copyright".

So: who owns the copyright here?

regards,
corrado.

@Alfiva
Copy link
Member

Alfiva commented Nov 15, 2017

In every single separate code project in the repositories there is a NOTICE file describing the copyright of each of those.

@ghost
Copy link
Author

ghost commented Nov 15, 2017

I sampled a few, looks like it's the universities or other research centers who formed the uAAL alliance, right?

Now, given the ECB is buying junk bonds for low yields, what about having them investing in something more meaningful?

That could help the alliance funding next versions, including support for the "frozen 3.4.1", updated docs, a "complete SDK", and so on...

PS: I'm NOT joking.

cheers
corrado

@Alfiva
Copy link
Member

Alfiva commented Nov 15, 2017

yes, at the time there was no uAAL standalone entity that could copyright these things so each project belongs to whoever developed it in the first place. Only now that we have the uAAL Coalition in place that could be possible, but these kind of debates now belong there. I will mention this discussion next time we talk.

@ghost
Copy link
Author

ghost commented Nov 15, 2017

well,
I guess next steps are:

  • current owners to transfer copyrights to the coalition
  • update licenses (maybe a single file per repo)
  • coalition to find investors

Given the only restriction with Permissive FOSS is in the "Right to distribute" being "Yes, under same license", which is almost like the "virality" of GPL, but "postponed to the deployment phase", then the "value for investors" is when OEMs will want to buy the "right to redistribute under a more restrictive license", right?

I mean, let alone official branding, documentation & training activities, certifying and distributing the apps and so on.

Regards,
Corrado.

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

1 participant