3 ms·
Wait a second...is he correct on the AGPL? We have a legacy application which runs on linux...I'd be very interested in exposing it to our internal business use
by rufugee 15y ago
Wait a second...is he correct on the AGPL? We have a legacy application which runs on linux...I'd be very interested in exposing it to our internal business users through something like this, but not if I had to give the source away. However, I'm not sure how this could be the case...it technically wouldn't be part of the application...it'd only be a way of accessing it.
That said, if we get value of it, I'm not opposed to paying for it either. I'm just more interested in understanding whether the AGPL really forces this.
- radarsat1 15y agoianal, but i believe that using it to connect to your service would not require you to release the code of your service. You'd only be required to release the code of any modifications to the Gate One software. (that is, i personally would not interpret it as making your service a "derivative" of the terminal emulator.. Maybe a lawyer could make that case though.) either way though, nothing stops you from making him an offer, provided he has the full rights to relicense it for you.
- icebraining 15y agoDoes the GPL require that source code of modified versions be posted to the public? The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization. http://www.gnu.org/licenses/gpl-faq.html http://www.gnu.org/licenses/gpl-faq.html As long as all the users are internal to your organization, you don't have to provide the source to anyone.
- riskable 15y agoAs long as the use was strictly internal to your organization the only people you'd have to give the source to would be the users. This includes 3rd party companies you might have a business relationship with (though I doubt they'd put such a pressure on you =). The bigger concern with such an integration is if it ever gets exposed to the Internet at large. Then you'll need to distribute the source or be in violation. Why risk it? Licenses will be pretty cheap for such one-off situations. Everything is negotiable regardless. -- Dan McDougall - Author of Gate One