Marvin Humphrey wrote:
> The code bases are already divergent and it would be very difficult to
> reconcile them. To make Apache OOo "upstream" from LO would mean one
> of two things
OK, let's clarify for sensibility: Apache would be upstream (licensing
acting as a diode), but not THE upstream.
As for how to do that, that's something that would have to be worked out
between the project and other stakeholders, e.g., TDF. The greater the
extent of the upstream work, the greater the code sharing.
Charles Schulz wrote:
> Instead of spending hours and keystrokes pondering on the ability
> of the Apache OpenOffice project to execute or to become LibreOffice's
> upstream
OK, can we put to rest the idea that code sharing only flows in one
direction due to the licensing, and that is the sole implication of the word
"upstream"? :-)
> I would like to rephrase or reframe Simon's proposal:
> - rename the project to Apache ODF suite
That's up to the project.
> - this project not the office suite that competes with LibreOffice but
> make it the meeting point of development efforts for specific purposes
> and ODF).
Again, this is up to the project and the needs of its participants. But you
appear to be ignoring the need for a permissively licensed product codebase
on behalf of some members of the proposed community.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
