i don't know of anywhere with very good, simple explanations, unfortunately. i think the problem is that (1) if you simplify a licence then you leave something

i don't know of anywhere with very good, simple explanations, unfortunately. i think the problem is that (1) if you simplify a licence then you leave something out which could be important and (2) no-one wants the liability involved. on the other hand, people recognise that and the major licences do try to be fairly easy to read. but you do need to just "bite the bullet" and read them through (and think what they mean). this is a good place to start - http://www.opensource.org/licenses/index.html http://www.opensource.org/licenses/index.html (in particular, see "License[s] that are popular and widely used or with strong communities" at http://www.opensource.org/licenses/category http://www.opensource.org/licenses/category for a list of the ones you should focus on) have fun :o/