This is an excerpt from Rick Moen's Version-Control and SCMs for Linux document in regard to the problems that were encountered in the BitKeeper Gratis License. (which was end-of-lifed as of April 2005)
Was encumbered by mandatory "Open Logging" of your metadata (privacy loss) if used with multi-user access.
Had a history of gaining more restrictive conditions over time. E.g.: The licence initially provided that, if the company's Open Logging servers ceased to function for 180 days, the software would convert to GPL, but that provision was later withdrawn. Source code access was also withdrawn. The non-compete clause was added. A provision was added (and later removed) to allow BitMover to terminate the licences of any individuals or groups whose usage is deemed to have cost BitMover over US $20,000 in support costs.
Consequently: (1) Publicly posted comments about BitKeeper were often outdated. (2) It was recommended to download the program and read its current licence agreement. (See slightly outdated licence analysis, copy 1 2, for which the author was unfortunately threatened with litigation.)
Was subject to mandatory upgrading, per the licence's requirement, when new versions come out. There are compelling technical reasons why BitMover required this. However, it should be noted that replacement versions often introduced new licensing containing novel restrictions, such as the no-compete clause. (The point was not to portray this as somehow sinister: It was to prevent people from assuming they could keep using older versions, if they didn't like newer ones' terms of use.)
Was encumbered by non-compete clause, http://lwn.net/Articles/12120/. If you or your employer develops, produces, or [re]sells a "substantially similar" competing product, you may not use it. BitMover sometimes waived this restriction for particular users. BitMover had advised some Linux kernel developers that they may not use the gratis-usage version, given their work on other SCMs. (They would have been obliged to buy the commercial version.)
Required in latter versions that the the hosted repositories' source code contents be available (on BitMover request) via the BitKeeper access protocol.
Was announced to be end-of-lifed in a company press release of April 6, 2005.