I want to submit an asset to the Asset Store which includes an open source library to parse YAML. It is released under the terms of The Code Project Open License (CPOL), as stated here.
This license permits commercial and derivative works.
My question is how to best handle including a third party open source library. Can I add a header to the library files like the following:
// -----------------------------------------------------------------------------
// FileName.cs
// Author: Liu Junfeng
// Source: http://www.codeproject.com/Articles/28720/YAML-Parser-in-C
// License: The Code Project Open License (CPOL)
// -----------------------------------------------------------------------------
…or do you think this would be rejected, or what are the guidelines that I should follow?
In the CPOL:
“…You must include a copy of, or the Uniform Resource Identifier for, this License with every copy of the Executable Files or Source Code You distribute and ensure that anyone receiving such Executable Files and Source Code agrees that the terms of this License apply to such Executable Files and/or Source Code.”
To sum up, you need to somehow make the user accepts the license as part of using your tech. This appears to be in direct contrast with the licensing section of the Asset Store’s Submission Guidelines:
“Please do not include your own license terms in your offering.”
I recommend hitting up the Asset Store’s Twitter account, which I’ve found to be incredibly responsive in the past - many script related projects need to rely on OSS libraries, so I imagine they’d have some ways to work with you.
I realize this perhaps is not an actual answer, but a means to get one. Perhaps you could post your findings back here?