CinelerraReview

Revision 4 as of 2007-02-13 01:19:01

Clear message

CinelerraReview

Reviewing the licence of the Cinelerra source tree.

Scope

We need to review the Cinelerra-CV sources that muzzol has pushed to bzr. The branch can be seen at [https://code.launchpad.net/~ubuntustudio-dev/+branch/ubuntustudio/cinelerra], and there are instructions there for pulling it.

Use Cases

  • Bob wants to use Cinelerra and Ubuntu to edit his video, and doesn't want to use a non-free equivalent. However, he is unable to, nor does he want to, build Cinelerra himself.
    • We need to get Cinelerra into the repository. This cannot happen unless all licence issues are sorted, and thus the purpose of this spec.

Design

The task could be done in either of two ways, both of which I will outline below.

1. We each create, on Launchpad, a branch of ~ubuntustudio-dev/ubuntustudio/cinelerra (thus becoming ~<user>/...). Each branch has the file, say, ./LICENCES in it, where each reviewer keeps a note of the licence of every source file they have reviewed. When the reviews have finished, all the personal branches are merged back into ~ubuntustudio-dev.

2. We each pull from and push to the ~ubuntustudio-dev branch. Each reviewer has their own file in which they update their list of files and licences. This file could be called something like ./LICENCES.<reviewer>. When the reviews are complete, these files can be merged into one file, ./LICENCES, or debian/copyright.

Implementation

As the source tree is 438MiB at last clone (268MiB used up by bzr), the first method seems like too much uploading - to create new branches for each of us, and then make a merge at the end. It would almost double the amount of up/down traffic we need. As a result, I suggest we choose to follow method 2.

However, either way we will need to decide how to split the 72030 files in the source tree between the team. It does indeed look a daunting task, but if divided up properly, it can be made much easier. It may be possible to have a system of locking, where we each check each others' LICENCES files, where it would be specified which files have been and will be done.We could also have a page like UbuntuStudio/ToPackage, where we divide up and allocate the sources. Either way, we cannot waste time stepping on toes.

Comments


CategorySpec