...in no time, with 300+ variations. This is what I hate about OSS. The moment someone isn`t too happy, they get the fork off and duplicate the work and dilute any chance of completing the damn thing, rather than working things out.
The moment someone isn't too happy? Read the history! Developers have been ranting about the closed shop that surrounded the copyright assignments required for contributing to the OO.o tree for years. The go-oo fork was set up as a rational way to keep track of contributions from people who weren't happy to give their copyrights over to Sun, and I think it's fair to say that most open-source contributors were more comfortable with Sun than Oracle. Forking a project this big is not something that developers take lightly and it takes extreme situations to make one happen.
There are plenty of examples of successful forks out there. Because OO.o version 3.x is LGPL v3.0, and I assume that TDF will stay with the same license, TDF will be able to take whatever OO.o adds, at least while the forks stay close together. However, unless OO.o starts taking code without copyright assignments, the reverse is not true. It is entirely probable that LibreOffice will be become the preferred product, at which point Oracle is going to have to make a call on whether it wants to work with TDF properly, or watch OO.o wither.