Re^2: License terms for monastery code?

Yeah, but it's never really been resolved. In my own Super search the most pertinent node I came across was How to license projects that come from Perlmonks. The problem with "contact the author" is people tend to fall away from the Monastery...

An interesting "solution" (not addressing formerly active users) might be to have a (selective set, with "Other") of options to choose from in user settings which is then shown on a user's home node.

-- In Bob We Trust, All Others Bring Data.

Comment on Re^2: License terms for monastery code?

Replies are listed 'Best First'.
Re^3: License terms for monastery code? by roboticus (Chancellor) on Nov 30, 2006 at 22:56 UTC
belg4mit: D'Oh! Shame on me for not reading the thread I mentioned. I guess I should've at least checked to see if the matter was resolved before posting... --roboticus	[reply]
Re^3: License terms for monastery code? by wazoox (Prior) on Dec 01, 2006 at 13:57 UTC
Another possibility would be to define a "lowest common denominator" ( for instance "code on Perlmonks by default comes with the same license as perl itself", or "code on Perlmonks by default is in public domain"), then display a disclaimer about this at account creation ( "unless otherwise stated, published code will be licensed as follow"). I know, how do we manage code posted since 1999 by 50000 existing monks? :)	[reply]