Thanks for the response. By the limited response I guess no one has had to get one of these disclaimers before for boost. I am proposing to use the following which is basically the GNU one you linked to: Yoyodyne, Inc., hereby disclaims all copyright interest in the "Boost.GAL C++ Library" (which provides a library of tools for audio representation, processing and IO) written by Brendon Costa. <signature of Moe Ghoul>, 1 April 1989 Moe Ghoul, President of Vice Do you think this is suitable? I wanted to make the exemption more generic to cover the entire Boost C++ Libraries so I could contribute to other boost projects as necessary, however I am Not A Lawyer and a lot of things in the above broke attempting that. For example: Yoyodyne, Inc., hereby disclaims all copyright interest in the "Boost C++ Libraries" (which provide assorted libraries for use in C++ coding). <signature of Moe Ghoul>, 1 April 1989 Moe Ghoul, President of Vice * I would have to remove the "written by" as I did not write all the Boost Libraries (Which I think this exemption needs to have my name in it somewhere) * The description is redundant really here "which provide assorted libraries for use in C++ coding" On Monday, 6 May 2013, John Bytheway wrote:

On 2013-05-05 21:09, Brendon Costa wrote:

...

I am looking into asking the company I work at for an official written "release" on the copyright for work I with to contribute to boost as per the description at:

http://www.boost.org/development/requirements.html

I will be developing this in my own time outside of work hours but I will need this release due to clauses in my contract and the relationship that the proposed library would have to my normal work.

Are there any examples of what this release should look like for boost to accept it?

I think having a sample release available on the page I linked to above would be really useful.

I'm not sure about the Boost requirements, but there's an example for GNU here: http://www.gnu.org/licenses/gpl-howto.html

John Bytheway

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

I wanted to make the exemption more generic to cover the entire Boost C++ Libraries so I could contribute to other boost projects as necessary, however I am Not A Lawyer and a lot of things in the above broke attempting that. For example:

Yoyodyne, Inc., hereby disclaims all copyright interest in the "Boost C++ Libraries" (which provide assorted libraries for use in C++ coding).

<signature of Moe Ghoul>, 1 April 1989 Moe Ghoul, President of Vice

* I would have to remove the "written by" as I did not write all the Boost Libraries (Which I think this exemption needs to have my name in it somewhere) * The description is redundant really here "which provide assorted libraries for use in C++ coding"

How about: Yoyodyne, Inc., hereby disclaims all copyright interest in contributions made by Brendon Costa to the Boost C++ Libraries. <signature of Moe Ghoul>, 1 April 1989 Moe Ghoul, President of Vice IANAL, of course. Regards, Nate

Yoyodyne, Inc., hereby disclaims all copyright interest in contributions made by Brendon Costa to the Boost C++ Libraries.

<signature of Moe Ghoul>, 1 April 1989 Moe Ghoul, President of Vice

That does sound better. About the whole idea of protecting an employer from an employee submitting some of the employers code to boost using the exemption, I don't think any statement can really cover that unless it is completely unrelated to your work. Even with the more restrictive statement I specified earlier about "audio processing, representation and io", this statement covers maybe 50% of what we do at work so the problem of submitting an employers source code exists with this as well. My plan is to submit my source to someone at work to review first to ensure that I am not disclosing anything that is considered as belonging to my employer. The exemption then could probably be signed off on that block of work. Maybe even generating a hash of the source I will submit and having exemption sign-off on that. Tedious but probably the safest. I guess I have an idea of possible statements now. Its time to speak with my employer. Thanks, Brendon.