What's holding ooo-build back?

What's holding ooo-build back?

Posted May 1, 2008 13:46 UTC (Thu) by janneke (subscriber, #15012)
In reply to: What's holding ooo-build back? by edschofield
Parent article: Sun and corporate open source

Surely rancour over the need to fork belongs to the bad old days of 
centralized revision control systems.

ooo-build is already a fork with some 800 patches. The question is: should ooo-build now work hard to fork the community? There's something to say for working with SUN instead of against them.

Why doesn't ooo-build use git/hg/bzr with a branch to track the upstream 
OpenOffice CVS and go go go?

OpenOffice.org is big, even for git. Kendy has been doing some grand git testing and profiling the past year and has been submitting patches to git to up cloning performance. Then, there are discussions about what to do with the ~800 patches in ooo-build. As most of these should go "upstream" (read: to SUN), one feature a time, should we have 800 branches? And how to manage these? Scripts, new git features?

We could all be using ooo-build in a few months if it were the more 
dynamic project.

It already is the more dynamic project, esp. for developers and we already *are* all using ooo-build. Well, technically maybe not if you're still using Fedora (has its own fork, taking their own set of patches from ooo-build, hysterical raisins), but all other distros are working with Novell and ooo-build.

Ah and of course it's not "go go go", but rather GO-OO ;-)

---

(Log in to post comments)