[Cabal] AOL

[Kevin M Stange]

Sean Egan wrote:
> This is what we expect AOL to agree to.
> 

How does this apply to the API going forward?  I see mention of the fact
that we are to be permitted to continue to use the name Gaim in the
following context:

"AOL does not object to uses of the term “Gaim” as it appears in the
computer code, supporting files and accompanying documentation written
by you prior to the date of this agreement."

This seems to assert that any new code will have to be namespaced as
pidgin_* or purple_* (or technically anything that isn't gaim_*).  Is
that correct?  If so, will we be re-namespacing the entire codebase
before 2.0.0 goes final?  If we keep the gaim_* namespacing but are no
longer allowed to use it for new code, my concern is that we'd end up
with versions such as 2.1.0 that contain a mix of the two different sets
of namespaces.

Kevin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://pidgin.im/cgi-bin/mailman/private/cabal/attachments/20061220/daefe373/attachment.pgp