www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: License for the other works of a product
Date Sun, 05 Jun 2016 14:00:07 GMT
To summarize the arguments against:

- other projects don't do it
- nobody has said that it is critical and documented policy
- one committer doesn't like having a commit that adds the headers

The argument for seems to be:

- it is good to clarify the license status of documents and config files
- somebody has already done the work (not that adding headers to docs is
such a huge task)

To me, the argument that documents should have clear licensing is
reasonably strong. We see questions about the status of diagrams, we see
large chunks of documentation being copied into commercial books with no
attribution and it would help if the source material were marked somehow to
make clear the status.

On the other hand, config files are typically so short it doesn't make much
sense to put a copyright header on them. If the config files ever get as
long as the copyright notice itself, then I think that there are bigger
problems than just the presence or absence of a copyright header. A note in
the config directory isn't a big deal.

The issue does have a tinge of bike-shedding unless the documentation
becomes much more substantial than most of our projects have. That would be
lovely, of course, but it isn't common.

On Sun, Jun 5, 2016 at 11:07 AM, Pierre Smits <pierre.smits@gmail.com>

> Hi all,
> A discussion has started in the ponymail podling regarding the license to
> be used for the other works of the project (meaning documentation,
> examples, explaning pages, etc).
> The viewpoints posted in the comments of
> https://github.com/apache/incubator-ponymail/pull/56 are opposing, so it
> seems we need some guidance from this forum. Informative pages of the ASF
> seem to be unclear on the subject.
> The question basically is:
> Do the other works (as mentioned above) of a project require (to
> reference) a license and if so, which one is it?
> Best regards,
> Pierre Smits
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/

View raw message