* FreeBSD is an example of an organization that successfully uses Perforce to manage its source code. Keep in mind, however, that the copyright is owned by a single legal entity, The FreeBSD Project (in turned backed by the FreeBSD Foundation.) PCC's copyright is spread among many contributors, meaning that each active contributor would have to agree to Perforce's terms and submit a signed EULA to them in order to access the repository.

* Perforce's licenses must be renewed on a yearly basis. Making each active contributor send their renewals to Perforce would be an unneeded burden.

* Perforce would still be at liberty to change its licensing terms at any time. Anybody who remembers the Linux/BitKeeper fiasco knows exactly what I mean.

I like Rockbox's development process. Each contributor owns the copyright to their code, but they all agree to use the GPL. They currently use SVN.

We can take this discussion offline to discuss the merits of SVN vs. Git vs. Mercurial vs. etc.