-1

We're getting ready to deploy a commercial application. Our software makes use of several other libraries, which have licenses ranging from the Code Project Open License (CPOL), the LGPL, the Apache License, and the MIT License

We want to comply with all of these licenses, obviously, but we're a small outfit that doesn't have a legal department to help us out with these things. Currently, as all the libraries are dynamically linked, and not embedded into the executable, I think we're mostly in the clear. Our project is closed-source, and is intended to be sold, and possibly resold by those we provide it to.

In the source code that uses these libraries, we've placed the related license at the head of the file.

In our About Box, we've placed the licenses as well (Is this step necessary)

Would we also need to include a LICENSE file upon distribution of our software?

Thanks for your help!

DTI-Matt
  • 2,065
  • 9
  • 35
  • 60
  • Fair enough, I was just wondering if anyone had any experience with how to display licenses, but I guess that could be worded "How to comply with X license" – DTI-Matt Jun 26 '12 at 16:56
  • 1
    If you as programmer use some code, look into it's license text and comply with it. If you have understanding problems, you can ask other developers what they think about that, but we can not answer your legal questions if you need legal help. A tip if you want to save some money: Contact the original copyright holder(s), ask what's applicable and if you're kind and respect others, I'm pretty sure you can sort this out in no time. Also if you ask here, not only drop the license names but also the concrete software because often people don't know the exact license. – hakre Jun 27 '12 at 11:27

1 Answers1

5

When talking about selling, and possibility reselling, you don't want your programmers writing your licensing.

Hire a lawyer.

James Hill
  • 60,353
  • 20
  • 145
  • 161