Assuming there are benefits to a startup in licensing their source code, what needs to be considered? What general terms would you expect to see (a lawyer can help write it, but I'm looking for general points)?
For example, I would expect the customer has the right to:
The customer would probably not have the right to:
What other rights/responsibilities should I consider when drafting a source code license?
Lastly, what information will I need from the customer? Should I insist on getting a full legal name and address, or is "firstname.lastname@example.org" still fine?
(This is related to this question. However, that question focuses on whether licensing source is a good idea. My question is: assuming it is a good idea, what are some of the details to consider?)
Key thing you missed for the agreement.
They shouldn't be allowed to sell their new version of your code as an independant component, only within a larger project as a "building block". Otherwise, if I'm a component vendor, I can resell your stuff by changing a few property names and fixing a bug ... personally I don't think thats shouldn't be part of the rules.
They can submit the change back to you and if you don't take it on you get the right to say "Yes they can or no they can redistribute" ... possibly you open a market place to allow them to resell their "flavour" of yours or something as a seperate business model. BUT get first right of refusal.
The good and bad to consider.
The component vendors generally aren't doing anything super special or tricky with their development, people pay because its hours they haven't had to spend themselves developing and debugging. If your stuff fits into this "save me time" catagory then your pretty safe that your not giving away anything.
Lastly the legal agreement.
You want more detail because I can type in email@example.com and you have no idea who it was that just got the source code so you have no way of enforcing the agreement (thus may as well not have it).
More importantly you want to ask for all their other details like country, name, company, EMAIL, etc for marketing and demographic understanding so that you know exactly who to target with advertising and who to contact again when you have "Awesome component #2" to sell.
http://choosealicense.com/ from https://help.github.com/articles/open-source-licensing Another Good one http://www.codinghorror.com/blog/2007/04/pick-a-license-any-license.html a little less https://github.com/blog/1530-choosing-an-open-source-license and more linked to the github usage.
http://creativecommons.org/choose from creative commons
http://www.oss-watch.ac.uk/resources/licdiff Finally you need to learn about
intellectual property... I think intellectual property gives you right to choose a license.
Also, see that you can dual license something if you are the "owner" or the original.
I HOPE someone clarify more on the last points about IP, copyright and dual, extra licensing and change from one type to another type of license when for example you have closed source and want to change to public, or that you have one license in your files and later you want to change it and so on.