>>> Pourquoi ne pas faire un seul projet avec Go-OOo plutôt que de forker OOo?
Y'a un article de LWN qui vient de paraitre là-dessus : http://lwn.net/Articles/407339/ (réservé aux abonnés pour le moment).
Michael Meeks parle de Go-OOo:
It is a distinct piece of code from go-oo for several reasons, most importantly being that we don't want to maintain patches anymore. Go-oo was maintained as patches, such that features could be enabled per-platform or per distribution simply by not applying them but this brings maintenance, and development problems of its own.
Instead with LibreOffice we will have several flat git repositories, such that the git diff output will be your patch, and committing is as simple as a git push. Of course many of the go-oo features have been merged, some are still pending review, and going forward go-oo will be obsoleted by LibreOffice.
[^] # Re: Apport de Go-OOo
Posté par patrick_g (site web personnel) . En réponse au journal LibreOffice. Évalué à 6.
Y'a un article de LWN qui vient de paraitre là-dessus : http://lwn.net/Articles/407339/ (réservé aux abonnés pour le moment).
Michael Meeks parle de Go-OOo:
It is a distinct piece of code from go-oo for several reasons, most importantly being that we don't want to maintain patches anymore. Go-oo was maintained as patches, such that features could be enabled per-platform or per distribution simply by not applying them but this brings maintenance, and development problems of its own.
Instead with LibreOffice we will have several flat git repositories, such that the git diff output will be your patch, and committing is as simple as a git push. Of course many of the go-oo features have been merged, some are still pending review, and going forward go-oo will be obsoleted by LibreOffice.