incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Re: License/Notice/Disclaimer file location in tree and modifcations of License headers in contributed files
Date Fri, 10 Aug 2012 11:31:45 GMT
There is still one open questions here, let me summarize it again:

OCAD[1] contributed files via JIRA[2] to the ASF,
Those files already had a license header (GPL) example: [3].

What is the correct way to handle that?
Replace license header with Apache license header and put some credits to
initial contributors in Readme ?



2012/8/5 <>

> Hi,
> we maintain some plugins at the podling Apache OpenMeetings for
> various 3th party applications.
> Those plugins have a fixed folder structure where the actual module is
> sometimes nested in the structure.
> Do we always need to put the files LICENSE, DISCLAIMER, NOTES,
> CHANGELOG, README in the root dir of the source and binary packages?
> For example:
> There is just a build.xml in the root, the actual "module dir" (those
> files that will be imported and copied by Drupals plugin installation
> hook) are situated at:
> I could not find any strict rule for the place of LICENSE, et cetera
> files in the docs. However is there any?
> Modifications of License headers:
> Additionally we did receive some contributed files at:
> The OCAD team contributed the files to the ASF so that our student/we
> can distribute this plugin at the Apache Foundation.
> However those source files already contained a license header.
> Can we just replace that license header with an Apache License header
> and put a note in the Readme to give some credits to the initial
> contributors or?
> Thanks!
> Sebastian
> --
> Sebastian Wagner

Sebastian Wagner!/dead_lock

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message