1
Quote:
The GPL in this case doesn't have anything to do with it. If you're familiar/have seen the XOOPS code and then go write something with similar functionality, you could be open to accusations of apropriating code (really, it's hard NOT to do in some cases). This is an issue with any license (unless the code in quesiton is under an open source license and you're relesing your own code compatible license terms)
That's why you have the "clean room" aproach when companies reverse engineer. They have one team disassemble and work out the protocol/product. Document it fully (without code) and pass it into a second team to implement.
RicoCali wrote:
Quote:
Although if you've seen the XOOPS code I guess you may be considered "contaminated".
There's alot of truth to that...I would not touch GPL with a ten foot pole if I had a multimillion dollar operation. Wouldnt want to take that risk.
The GPL in this case doesn't have anything to do with it. If you're familiar/have seen the XOOPS code and then go write something with similar functionality, you could be open to accusations of apropriating code (really, it's hard NOT to do in some cases). This is an issue with any license (unless the code in quesiton is under an open source license and you're relesing your own code compatible license terms)
That's why you have the "clean room" aproach when companies reverse engineer. They have one team disassemble and work out the protocol/product. Document it fully (without code) and pass it into a second team to implement.