On 9/11/2013 1:14 PM, Charles Steinkuehler wrote:
> Thanks for looking through the files! Several of them are mine, and I
> just missed adding the license header. I'm willing to license the
> files GPLv2+ or whatever works best for the project, including public
> domain or even something like MIT/BSD.
That makes a lot of sense to me. From my viewpoint a sample config file
is provided as an example / teaching starting point.
I personally don't see any need to have the GPL copy left aspect apply
to a K9 Hal config or a DTS/DTO file.
It seems to me that if everyone that made a change to those *had* to
contribute it back (due to GPL), we'd just get a bunch of patches from
multiple users that would be likely to conflict. Nor am I much worried
about the corner case of missing a sample file bug fix because the file
was not marked GPL.
For the K9 / Shapeoko example files I did, I'm happy with the (3-clause)
"New BSD License" (which I think does not cause any problem to LCNC, but
if someone thinks it does, let me know and we'll figure out plan b).
The FSF preferred name for that lisc is "Modified BSD License".
The files I did were whipped up wearing using a corp hat, so the correct
(c) holder name for them is: Copyright (c) 2013 Calypso Ventures, Inc.
To save you the trouble of finding the text, here is a paste of it with
the CVI corp name replacing the meta tokens in the BSD template:
---------------------
Copyright (c) 2013, Calypso Ventures, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of Calypso Ventures, Inc. nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL CALYPSO VENTURES, INC. BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------
Rather than my making a patch to send to you , and you sending it on to
Michael, and he sends it to LCNC repo etc., I'd appreciate it if
someone farther up the git food chain would insert the lisc headers for me.
>> = configs/ARM/BeagleBone/BeBoPr-Bridge/BB-LCNC-BEBOPRBR-00A0.dts
>> = configs/ARM/BeagleBone/K9/Device_Tree_Overlays/BB-BLACK-LCNC-K9-00A0.dts
>> = configs/ARM/BeagleBone/K9/Shapeoko/temp/LCNC-BBB-K9S-00A0.dts
Hum, I don't remember the shapeoko temp dir - maybe a temp dir got
tagged for git inclusion when it didn't need to be?
(I could easily have made that mistake when creating the Arm config tree
structure.)
Do not contain license declaration. Are these generated files or are
they all hand-written?
> They are written, not generated. I'll add license headers.
>
Dave
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
