Okuna License for dummies

[sultanmyrza]

Hello,
As a regular developer who wants to build on top of okuna for my local community I want to know things that I can and can't do. Please let's keep this open because I'm sure other developers can add their own questions.

My questions will be strict and simple not in a fancy, complex and unclear as lawyer or that guys!
Because reading this http://www.gnu.org/licenses/agpl-3.0.html for me is not clear as to other ~70% of developers who just want to build on top of okuna for their own local communities!

If I build on top of okuna-app and okuna-api

Can I change logo of okuna-app, okuna-api?
Can I change name of okuna-app, okuna-api to something like matata-app, matat-api?
Can I deploy to my own server?
If I have to tell my local community users that this app is powered or built on top of okuna can I do it with very small text somewhere in settings screen or I have to do it significant like facebook does for WhatsApp example?

Thats it so far but lets keep this open maybe others also have question or I will add more later

Best regards,

P.S: okuna app (great ui)!

[lifenautjoe]

Hey there.

This one is a pretty good TLDR for our license.

https://tldrlegal.com/license/gnu-affero-general-public-license-v3-(agpl-3.0)

As for your questions, although you will find them there too

Can I change logo of okuna-app, okuna-api?
Yes as long as it complies with the rest of the license.

Can I change name of okuna-app, okuna-api to something like matata-app, matat-api?
Yes as long as it complies with the rest of the license.

** Can I deploy to my own server?**
Yes as long as it complies with the rest of the license.

If I have to tell my local community users that this app is powered or built on top of okuna...
Not necessarily. You do however have to include a copy of our License and Copyright somewhere in your app.

As in for the rest of the license, one of the important things to keep in mind is that you must disclose your source code and state what changes were made to it at all times, both for the frontend and backend.

We do this to prevent a hostile situation where the components are made private, rebranded, improved and sold, rendering our previous efforts useless.

Let me know if this helps.

Best,
Joel.

[sultanmyrza]

As in for the rest of the license, one of the important things to keep in mind is that you must disclose your source code and state what changes were made to it at all times, both for the frontend and backend

for this case if I just fork and do some changes like own logo etc and keep that fork in public git repo is that enough? or I should do additional things?

[kitlu007]

Hi Joel. Thanks for the comment. I would like to know one important aspect. There is a statement which states "You must not include any code that is not agpl3."

Does that mean, if we find a code for a valuable feature elsewhere and would like to include the feature here, are we allowed to do that ? Because there are several plugins, feature repos available for sevarl products features written in dart on git that can be inserted in the app to make an enhanced app.

If we are allowed to do that, we would have to state what piece of code is License other than Agpl3 ?

[lifenautjoe]

As in for the rest of the license, one of the important things to keep in mind is that you must disclose your source code and state what changes were made to it at all times, both for the frontend and backend

for this case if I just fork and do some changes like own logo etc and keep that fork in public git repo is that enough? or I should do additional things?

You must disclose any kind of change made to the source code and the source code has to also be publicly available. So in that case, no, the repo should be public.

[kitlu007]

Understood joel. What you just stated is for modification on our end - both front-end and backend which will be agpl3. But what i wanted to know is any feature which we implement from some other repo not originally developed by us but we use it and modify it and add it to rur app. The original license which is say MIT license or any other, are we allowed to implement that third part repo with changes at our end, state the changes and the license which is MIT ?

[lifenautjoe]

Hi Joel. Thanks for the comment. I would like to know one important aspect. There is a statement which states "You must not include any code that is not agpl3."

Does that mean, if we find a code for a valuable feature elsewhere and would like to include the feature here, are we allowed to do that ? Because there are several plugins, feature repos available for sevarl products features written in dart on git that can be inserted in the app to make an enhanced app.

If we are allowed to do that, we would have to state what piece of code is License other than Agpl3 ?

The problem is that you are not allowed to sublicense the code. So you must not include any code that cannot share the same restrictions of AGPL3, meaning that you cannot use any proprietary/closed source code in it.

If the extra flutter code and plugins are licensed MIT or AGPL3, its okay as long as you include their corresponding licenses in your repository.

[kitlu007]

Sure joel, understood. We would he relying on third part open source projects only written in dart not closed source. So in that case, we would be stating the changes, disclosing the source code with changes at our end and the license as well. Thanks for the clarification.