How to write a basic closed-source license for a software project?

We have a project that needs to remain closed-source, but will need to be distributed to software developers who need access to the source code in order to build another project, that happens to be open-source.

Is there a simple license that should be used here that basically restricts the use of the software with the exception of for the intended purpose of developing the other open source project?

From stackoverflow

• Okay, two things here.

  First thing is that closed source is actually sort of easy. You automatically have at least a copyright as soon as you write it, although the conventional copyright notice in each file is good. You know "Copyright © 2009" and your name or firm's name.

  Second thing is: get an attorney. Don't take advice from some guy on Stack Overflow.

  Eliza : I agree completely on the attorney point. And it isn't as expensive as you might imagine- especially since this is the kind of work that an associate would be doing. And you get the assurance of having it be correct.

  JaredPar : +1 for asking OP to not trust your answer.

  Nick Sergeant : Great suggestions. Totally agree on the attorney part. I wasn't so much putting 'all' of my trust in some guy on Stack, just looking for general tips :) Thanks!

• If your company is short on cash, you could try taking a sample license to an attorney (I still recommend having an attorney review the license). Here's an example.

  OR ... you could just take one of the GPLs and add the word "not" in front of every verb. =)

• Most simple contracts are boiler plate. There are books at all law libraries that have these contracts in them. There are also places like legalzoom.com that sell basic contracts. If you are short on cash, look to one of those places. If you have some money, you are much better off going to a lawyer and getting what you really need drawn up.