seeking an elegant solution, somewhat OT

[John Sgammato]

Seeking some creative input, or maybe a success story...
The products that I write about use a variety of open source and other
licenses. There is a thicket of rules surrounding attribution of them. I am
looking for a way to assemble this the first time, and then to maintain it
after that.

I have a list of about 300 software components that need different handling
according to their licenses.


   - Some (MIT, BSD) require no attribution.
   - Some (Apache) require us to reproduce a "NOTICE" file from the
   original distribution.  These vary from vendor to vendor.
   - Some (GPL) require us to include a copyright statement, a statement of
   the terms under which the code is distributed, and instructions on how to
   obtain the sources used to build the component.
   - There are others that have more unique requirements.

I'd appreciate any thoughts on the subject,
and Happy Thanksgiving to all our USA list-members!

-- 

<http://www.actifio.com/>    *John Sgammato, Documentation Architect*
*e* john.sgammato at actifio.com  *c* 508.927.2083
*t* @actifiodocs <http://twitter.com/actifiodocs>

333 Wyman Street, Waltham, MA 02451
<http://twitter.com/actifio>    <http://www.linkedin.com/company/399246>
<https://plus.google.com/102870897962348937868/posts>
<http://www.youtube.com/user/actifio>    <http://www.actifio.com/>

*Radically simple copy data management *

*.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20141126/fbe2f3f4/attachment.htm>