View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Supportez nous sur Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - AGPLv3 licence change - ProjeQtOr

Prochaines Sessions

Les prochaines formations et démonstrations sont ouvertes, inscrivez-vous rapidement !

 

Démonstration de ProjeQtOr

(gratuit, sur inscription)
 

5 juin 2025 (16h-17h30)

19 juin 2025 (16h-17h30)

9 septembre 2025 (10h30-12h)

 
 

Planifiez avec ProjeQtOr

18 et 19 juin 2025 (9h-12h30)

17 et 18 septembre 2025 (9h-12h30)

 
 

Administrez avec ProjeQtOr

20 et 21 mai 2025 (9h-12h30)

25 et 26 juin 2025 (9h-12h30)

24 et 25 septembre 2025 (9h-12h30)

 

 

 

AGPLv3 licence change

More
23 Nov 2016 09:53 - 23 Nov 2016 10:18 #1 by papjul
AGPLv3 licence change was created by papjul
Hi,

I noticed that ProjeQtOr licence changed at 6.0.1 version for AGPLv3 and requires that every single modification to ProjeQtOr source are to be made open source (this includes even just hiding a field in a Model file, for those who are asking).
I'm not sure to understand this licence change because it also means the plugins you're selling have to be made under AGPLv3 as well and anyone can then re-releasing it under AGPLv3 for free (as in beer).
I'm willing to open source generic development I made, as I already did in the past if you remember, but some of our development are specific to us, won't be helpful to anyone and I may have trouble if some things go in the wild.
So, at the moment, I'm not sure if we will stay on 5.5.4 version or if I can find some way to make my specific development "generic".

If you want to release ProjeQtOr under open source licence, without these issues, you can have a look at this Wikipedia page: en.wikipedia.org/wiki/Comparison_of_free...ce_software_licenses or at this tool to help you choose: oss-watch.ac.uk/apps/licdiff/
I'm also interested in hearing what ProjeQtOr users think of this change…
Last edit: 23 Nov 2016 10:18 by papjul.

Please Connexion or Create an account to join the conversation.

More
23 Nov 2016 10:12 #2 by babynus
Replied by babynus on topic AGPLv3 licence change
Hi,

Thanks for pointing out this important change.

Yes licence hase changes from GPL to AGPL in V6.0. We will explain in next days why we did it.
What is important to understand is the change it brings :
if you just use ProjeQtOr without changing it : it changes nothing
if you develop some changes and deploy it to customers : it changes nothing (you still need to deploy changes under same licence)
if you develop some changes to provide a service to customers : then you now need to provide source code to your customers (it is the only difference between GPL and AGPL)
if you develop some changes for your own needs (inside your organization) : it changes nothing, you can keep your code for yourself.

Hope this is more clean.

Babynus
Administrator of ProjeQtOr web site

Please Connexion or Create an account to join the conversation.

More
23 Nov 2016 10:23 #3 by babynus
Replied by babynus on topic AGPLv3 licence change
What made us change the licence to AGPL
www.gnu.org/licenses/why-affero-gpl.en.html

(in french : www.gnu.org/licenses/why-affero-gpl.html)

Babynus
Administrator of ProjeQtOr web site

Please Connexion or Create an account to join the conversation.

More
23 Nov 2016 10:24 #4 by papjul
Replied by papjul on topic AGPLv3 licence change
You're right, I missed the part where "code source must be released to the users", not necessarly to everybody in the world. But it also means that if you make some developments for your organization, you have to make the source code available to every user of the organization, which is not what I understand from your comment.
It's more clear anyway, thank you.

Please Connexion or Create an account to join the conversation.

More
23 Nov 2016 10:27 #5 by papjul
Replied by papjul on topic AGPLv3 licence change
Yes, I know what the AGPLv3 does, as I use it for some little projects, and that's why I started this topic when I saw this change. It fixes the "privacy loophole", but that's not the only licence doing it. For example, the Common Public Attribution License 1.0 does the same, but modules (or plugins) of the original work can be licenced under whatever the developer want.

Please Connexion or Create an account to join the conversation.

More
23 Nov 2016 10:30 #6 by babynus
Replied by babynus on topic AGPLv3 licence change

But it also means that if you make some developments for your organization, you have to make the source code available to every user of the organization,.

Yes, in the idea of the licence, and to be able to spead licence to SaaS services, it is written this way.
But sure we will never have a look at your own servers if your service is inside your organization. ;)
What we really want to force is the redistribution of code to "customers" in all cases, even if ProjeQtOr code is used in SaaS mode.

Babynus
Administrator of ProjeQtOr web site

Please Connexion or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.064 seconds

Paramétrages de cookies

×

Cookies fonctionnels

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Veuillez vous connecter pour voir vos activités!

Autres cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.