scenic asks:
"I was wondering if it's okay to learn from GPL'd code if I plan on creating a closed source product. I'm developing a product for work which has an undetermined license (open or closed) at this point. I don't plan on using code from another project directly, but I'd like to see how other projects deal with problems I will likely face in development. I've been reluctant to even look at GPL'd products because I don't want to violate the letter or the spirit of the GPL. I'm wondering if I'm just being too worried, though. Specifically, I'd like to know what other people think? Is there a definitive answer? " Learning from GPL'd code is one thing, then there's plagiarizing whole blocks of code into your own closed apps, which is a no-no. How do you all feel about this. If you
know you are planning on coding another project, is it OK to look through GPL code for ideas or should a programmer be safe and avoid GPL'd code until his obligations to the current project are satisfied?