Existing Jasig projects, like uPortal and CAS, will need to transition from their current licensing process to this new process. This must be handled carefully to make sure future intellectual property problems are not created in the process. For each project, there will be two major steps to this process: 1) moving the committers to the new policy and then 2) moving the codebase to the new policy. The project steering committees are responsible for ensuring this process is executed properly. The goal here is to conform to the new Jasig process for Implementing the Licensing Policy, while still adhering to the conditions of contributions that were previously made before the new policy was put into effect.

Committers

First, the project has to make a transition with all the committers. Before the project can change over a codebase to use the new license or issue any releases under the new license, it must get all the current active committers to complete at least an ICLA, and optionally a CCLA.

Getting organizations to complete the CCLA is encouraged, but optional. Individuals are encouraged to get their organization to complete the CCLA since it provides them with better protection for their contributions. But the ICLA is sufficient to provide Jasig and adopters with the protections Jasig is seeking from this process.

Institutions who have previously made meaningful contributions are highly encouraged to complete a CCLA and to specifically include a grant of all previous contributions within the CCLA.

The steering committee will run this process and set a deadline by which active committers must complete an ICLA. Once that deadline is reached, anyone who has not completed an ICLA will have their commit privileges suspended. These privileges will be restored as soon as the ICLA is completed.

Codebase

Second, the project has to make a transition with the codebase. Once the active committers have all completed an ICLA, the project can then make the transition of the codebase to the new license. There are still some important details for how this needs to be done that are different from how Jasig would handle a new project.

All the requirements for the LICENSE and NOTICE files still apply, so those files should be set up accordingly. See Implementing the Licensing Policy for more information on these.

However, Because all of the preceding contributions to Jasig projects were done under the New BSD License and there were no Contributor Agreements in place, Jasig must continue to honor the terms of the New BSD License under which Jasig has rights to the current codebase. Fortunately, the requirements of the New BSD License and the Apache License 2.0 that Jasig is adopting are fully mutually compatible. The Apache Software Foundation itself considers New BSD licensed projects fully compatible with the Apache License and appropriate for inclusion within Apache projects. See the ASF's Legal FAQ for more details on this, specifically the reference to the "Category A list" of licenses.

To continue to honor the terms of the New BSD License, projects simply need to include its required statements in the NOTICE file included with each project. So, the NOTICE file for these projects should contain the following:

Copyright <Year>, JA-SIG, Inc.
This project includes software developed by Jasig.
http://www.jasig.org/

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at:

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

===========================================================================

Requirements for sources originally licensed under the New BSD License:

Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions
are met:

- Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.

- Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

- Neither the name of JA-SIG, Inc. nor the names of its contributors may be
used to endorse or promote products derived from this software without
specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

===========================================================================

[additional contributor copyright notices]

===========================================================================

[third-party legal notices as required]

Any additional notices required from third-party sources should then be added to the bottom of the NOTICE file.

The source header needs to be added to every source file in the codebase. See Implementing the Licensing Policy for details. This header should replace any existing header that may already be in the file. If there are copyright notices present in the source files, those should be moved to the NOTICE file and should be placed after the text listed above, but before the third-party notices (which should stay at the end of the file).

Once the LICENSE and NOTICE files are properly in place and all the source headers have been modified accordingly, the codebase is now ready for a first release under the new license.