"Hacking" the licensing code is not an issue. You would get that no matter what happens.
You can make the licensing part OSS without an issue, I think
________________________________________
From: news [news_at_ger.gmane.org] On Behalf Of Nicolas Alvarez [nicolas.alvarez_at_gmail.com]
Sent: Tuesday, March 11, 2008 6:10 PM
To: dev_at_tortoisesvn.tigris.org
Subject: Re: bundling software with TSVN?
Steven Higgan escribió:
> Another thing, seriously look at 'Professional' vs 'Home' use licences - and enforce them via licence keys. Create a library that handles the licensing (obviously licence it in such a way that I cant pull the code and make my own key-gen) and delegate to that library for checking | enforcement.
>
> If a 'Professional' licence is only valid for 1.6.* versions then they don't get to upgrade to 1.7.* -
> Another way 'Professional' licences get as many upgrades that their 'subscription' allows them for, make their subscription a year long.
> You could also do something with 'seat licence' a corporate can buy a year long subscription for 50 users - enforce that by an online activation | enforcement process.
Seems kinda impossible due to licensing. Even if you make the license
key library closed-source, I could modify TSVN code so it doesn't even
load the library.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-03-12 18:36:21 CET