On Fri, 2011-06-10 at 10:04 +0000, toki wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 09/06/2011 21:38, Jean Weber wrote: > > > I don't know what this will mean for us in the OOo and LibO docs groups, > > but I am concerned about the potential for further fragmentation of a small > > group of docs people into working on several > projects. > > If The Apache Software Foundation does what they normally do with > projects, there will not be a binary release of Apache OpenOffice.org. > There will only be a source code release. > > The onus will be on third parties to deliver binaries. > > Given the history of third party distribution of OOo binaries, I suspect > that tracking the third parties that deliver binaries that are either > based upon, or exclusively Apache OpenOffice.org code to non-trivial. > > I don't see typical OOo end-users grabbing the Apache OpenOffice.org > source code, and compiling it for their system. > > > We really need to work on better ways to reuse material without time > > consuming rebranding > > +1 > > OTOH, I'm not sure how much material will be reusable. > In updating _OOo in a Multi-Lingual Environment_, my original theory was > to include OOo4Kids, and OOoLight. Due to the differences between those > programs, and OOo, I had to either write: "This can not be done using > OOo4Kids" or else write a completely different set of instructions. > Instructions that, as often as not, did not work with either OOo, or LibO. > > > by automating everything we can and choosing not to do some > non-essential things that can't be automated. > > The practical issue is: > * Which existing OOo derivatives/variants should the Documentation > Project track; > * What criteria should be used, to determine which new > derivatives/variants should be tracked; > > Existing OOo derivatives/variants are: > # FLOSS: > * GO-Oo; > * BrOffice; > * LibreOffice; > * OOo4Kids; > * OOoLight; > * OpenOffice.org; > * OxygenOffice; > > # Proprietary: > * 602Office; > * Co-Create Office; > * EuroOffice; > * KaiOffice; > * MagyarOffice; > * MyOffice 2007; > * NeoOffice; > * NextOffice; > * OfficeOne; > * OpenOffice Pro; > * OpenOffice UX PL; > * OpenOffice PL; > * RedOffice; > * StarOffice/Oracle OpenOffice; > * Symphony; > * ThizOffice; > * UPOffice; > * WPOffice; > > I put that list together, based on various pages on the web. Not all of > those programs are still distributed. > > > jonathon > - -- > If Bing copied Google, there wouldn't be anything new worth requesting. > > If Bing did not copy Google, there wouldn't be anything relevant worth > requesting. > > DaveJakeman 20110207 Groklaw. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJN8ewkAAoJEERA7YuLpVrV8HEH/RukCJDYCR5T7WteFqAu0Iw3 > Udp2F49WQynqzsr/B4dFTX17PwL/oDVZDLqtNgpDykcyqK1nOVRB4X8KUt9Vf8y9 > GOyVOBAQjp9Tc3zxbsp8UdPbErSVfkBD4Nwvy7Ht+WDZkGy35xqgINS/MkvE50E7 > XM2ZNbojVUNLrF609mgPLZddKEReB4+aKaPZa+vijuC+vdPAlTIz6FsBBOpARbEg > WiaihWK8s9sDKfpuad1Q5TJOqZ5vMd7pfqfnhnEZC/gHEav9vVQcOMWdT6fjyf21 > 8o1Zab0SwXD95hN/4FHfVMWF9rH1fhMoNWLnT+q2AH9xBO9AzNvkatSvoTNiJvY= > =F9A9 > -----END PGP SIGNATURE----- >
Do we want to track KOffice and Calligra as well? They have some interesting ideas that we should probably look at. -- Jay Lozier [email protected] -- Unsubscribe instructions: E-mail to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
