FAQ: Submitting Code to comply with RCL Licence Terms|OPC UA Implementation: Stacks, Tools, and Samples|Forum|OPC Foundation

Any member company that uses the OPC-F code and needs to comply with their obligations under the RCL licence should do the following:

1. Create a fork on the appropriate OPC-F GitHub repo;
2. Add your fixes;
3. Compile and test (Changes that do not compile are not acceptable);
4. Document (Explain why the changes were made and when they are needed);
5. Create a pull request.

Your obligations are fulfilled once the pull request exists, all files compile, documentation exists and the changes are accessible to all. 

When deciding what changes need to submitted the rule of thumb should be: if you change a file distributed by the OPC-F then that change must be given back. If you extend the library with subclasses or helper functions then that does not need to be given back unless the changes require your new code to be compiled into the same library as the OPC-F code. If the latter then the new code is too tightly coupled to be considered a true extension and must be given back.