Using OSS for In-House Tools, Only?
Robert Hart writes "With people such as Microsoft and ADTI suggesting incorrectly that if you use GPL software in house (without distributing it to third parties) you must make your code publicly available, actual examples of people using GPL software internally would seem to be the best response (pragmatic examples to back up the 'theory').
I am interested in hearing about examples of corporations and government agencies, from around the world, using GPL software as part of an inhouse development effort. As there is also a potential for time/money saving by doing this, there is a possibility that this
may lead to some research to put numbers behind this."
In the FAQ, it states that an organization as a whole can make a modified copy and not distribute it. So the organization is the responsible body, not the individual employee.
That would imply that an employee could NOT distribute it without the permission of the organization, if the modified product was intended for in-house use only.
To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.