Answering general comments...
Unfortunately, I’m not a (patent/trademark) lawyer. Even more unfortunately,
one of the members of my client organization IS.
I know something about intellectual property, but I know much less when it
comes to software, especially with so many custom-made
Le 25/06/2014 20:24, Criss Ittermann a écrit :
Does this need to bother “upstream” folk?
yes, a bad licence can break the hole site licence
Could it just be as easy as adding “License: GPL 2” (as a default, being the
same as PmWiki’s license) to the Cookbook header template so that new
Criss Ittermann writes:
Could it just be as easy as adding “License: GPL 2” (as a default, being the
same as PmWiki’s license) to the Cookbook header template so that new authors
are encouraged to add their license information on each Cookbook page?
In the past Pm has stated that he prefers
Does this need to bother “upstream” folk?
Could it just be as easy as adding “License: GPL 2” (as a default, being the
same as PmWiki’s license) to the Cookbook header template so that new authors
are encouraged to add their license information on each Cookbook page?
If it’s under custom
This sounds like a good wiki-maintenance project!
However, we might want to agree on some sort of guidelines, first.
could you open a PITS for this?
-Michael Paulukonis
http://www.xradiograph.com
http://goog_2112721603Interference Patterns (a blog)
http://www.xradiograph.com%5Cinterference
Hello Criss,
Wednesday, June 25, 2014, 2:28:01 PM, you wrote:
Does PmWiki have a standing Cookbook licensing policy or is each cookbook
developer required to state their own license information for their plug-ins?
you need to check out each individual recipe. Hopefully there is some
Yes,
And I’m probably guilty of not putting licensing information in my own recipes.
But it would also be good to put licensing information on the recipe page.
It’s actually important, and in this case it would help me select recipes I can
and cannot use. I’ll have to chase down every recipe
