My apologies if this proposal is out of place on either list, but I think it's worth thinking about
early. Obviously I speak for neither Apache nor TDF but I have a deep concern for OpenOffice.org
and am very keen to see the community healed.
Given that:
* both LibreOffice (October, Paris) and Apache (November, Vancouver) have conferences in the
second half of the year,
* between them cover both Europe and North America,
* plenty of people will be travelling anyway to attend them,
* it's much easier to co-operate with people you've met
I would like to suggest to both TDF and Apache that they host an "OpenOffice.org Unity Summit" (or
some less cheesy name if you prefer!) at both conferences, inviting everyone associated in any way
with the overall OpenOffice.org community (open source projects like LibreOffice or the proposed
Apache project, their direct downstreams like NeoOffice, their commercial derivatives like
Symphony) to attend, preferably without charge.
The event would need a neutral Chair/Organiser and a suitably egalitarian agenda, naturally. Is
this worth exploring?
S.
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [tdf-discuss] OpenOffice.org Summit Proposal · Simon Phipps
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.