- Moderated by:
- Support
-
- rank:
-
Professional
- registered:
- December 1969
- Status:
- offline
- last visit:
- 10.01.08
- Posts:
- 1631
IANAL, but reading and learning IMHO have absolutely nothing to do with licensing. Especially coding styles.
Thats like saying you might have copyright issues from reading the PHP manual and learning from its examples or PEARS coding style.
Again, just my opinion and assumptions. Which is all your going to get here. -
- rank:
-
Software Foundation
- registered:
- December 1969
- Status:
- offline
- last visit:
- 15.11.08
- Posts:
- 4481
uheweb
So, is coding "the PostNuke way" enough to require the GPL, or is "from scratch" mainly referring to the code logic (rather than merely PHP techniques that are PostNuke oriented)?
"PNSF point of view"
Am I allowed to release commercial modules for PostNuke?
We believe it is permissible to release modules under a license other
than GNU/GPL and even to encode it providing they are not derivative
of existing GPL work, including the PostNuke "core". It is definitely
not acceptable to release a non-GNU/GPL module packaged/shipped or
distributed together with PostNuke: it must be a standalone module
distributed separately. The same applies to themes.
This is based on what we believe to be true after making enquiries.
The fact remains, there are no legal precedents confirming or denying
this and that such rulings, if there were ever to be any, could vary
from jurisdiction to jurisdiction.
DISCLAIMER: This is not meant to constitute legal advice nor
endorsement - we take no responsibility for the consequences of anyone
charting this unknown territory. This is simply stating what we feel
at PostNuke.
--
regards from germany
..::[Zikula Application Framework]::.. ..::[SEO-Blog]::.. ..::[CMS Sicherheit]::..
