Revise the Initial Contribution Process
In the past, we required that project teams provide a ZIP file containing a snapshot of their repository to the IP Team for review via IPZilla. The team was then "on hold" until the IP Team granted their approval to "check-in"; with that approval, the project team could then work with the IT team to move/create repositories.
With the changes in the IP Policy, we have an opportunity to improve this experience.
The short version is this:
- Complete the proposal process and creation review;
- Project team and EMO works with IT Team to move existing repositories (or create new ones) in EF GitLab or EF-managed GitHub;
- EMO will initiate the intellectual property review of the default branch of all repositories;
- The EMO IP Team will inform the EMO when the reviews are complete.
Note that the overall process likely takes the same amount of time with these revisions as it did in the past. The perception and general experience should, however, be better for the committer teams involved.
We need to take special care to ensure that project teams understand that when we move repositories under management of the EFs, the repositories will become immediately subject to our system's management of project roles. Write access to repositories will, for example, be limited to committers who are listed on the project proposal and have signed the necessary agreements.
That is, some committers may lose access during the transition period, so care should be taken with regard to timing of the move. It is a best practice, therefore, to wait until a critical mass of committers have been onboarded before starting to move any repositories.
Note that the process is basically the same when a repository of existing code is added to a running project. We can likely do something similar with pull requests that require review (more investigation required).