I have been working on a project that is hosted on GitHub in a private repository. The repo has three directories, call them frame, private1, private2. The frame directory is framework code used by private1 and private2, which both contain image assets and html content that make use of the code in frame. Currently, after a build process, private1 and private2 are deployed as publicly viewable websites.
I would like to change this GitHub repo from private to public, making frame (and some other files) reusable under MIT license, but retaining copyright protection on private1 and private2.
I read this related question:
So, if I create a LICENSE file in the root directory of the repo with the following content, would this be a correct solution:
This code repository contains some open source and some copyrighted content. All of the content under the directories named private1 and private2 has been made available to this project by XYZ Corp and is copyrighted; permission to use those files is not granted. All other parts of this repository are made available under the standard MIT License: Copyright (c) 2017 XYZ Corp Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.