Upgrade to Pro — share decks privately, control downloads, hide ads and more …

GreekFOSS Athens

GreekFOSS Athens

Italo Vignoli

August 16, 2012

More Decks by Italo Vignoli

Other Decks in Technology


  1. IANAD I am not a developer IAAOMGAYSNTAOM G I am

    an old marketing guy and you should never trust an old marketing guy
  2. Background July 19, 2000: Sun Announces an Open Source StarOffice

    October 13, 2000: OpenOffice.org Launched May 1, 2002: OpenOffice.org 1.0 Released October 20, 2005: OpenOffice.org 2.0 Released October 2, 2007: Go-OO Announced October 13, 2008: OpenOffice.org 3.0 Released January 27, 2010: Oracle Acquires Sun
  3. Ten Years After Ten years after the promise of a

    foundation ... “a foundation is a great idea... the time is not yet ripe... perhaps in three years”, etc. Patience is a virtue, but not an inexhaustible resource. Some truly fantastic “opportunities” for improvement Vendor neutrality / no copyright assignment barrier
  4. LibreOffice An idea – whose time has finally come ...

    A beautiful, Office suite we can be proud of (in due course) backed by a real, open community Shipping on Windows, Mac, GNU / Linux, *BSD, etc. ODF enables trivial migration with your data ...
  5. Vendor neutral, no code ownership aggregation A real Free Software

    / hackers project Volunteers + RedHat + Novell + Debian + Canonical + Google … FSF + OSI + boycott Novell support, etc. Freedesktop hosting LGPLv3+ / MPL for new code ... Doing It Right
  6. Last Eight Months September 28, 2010: The Document Foundation and

    LibreOffice 3.3 Beta are announced January 25, 2011: LibreOffice 3.3 Stable Released End of May 2011: LibreOffice 3.4
  7. Easy Hacks removing pointless comments porting from Java → python

    and Java → C++ kill 3 of 4 duplicate base64 impls remove dead / un-called code fix cppcheck warnings remove obsolete macros remove thousands of multi-second sleeps from QA tooling help thread the spreadsheet re-calculation engine write unit tests stop battery sapping timer leaks improve localization tooling
  8. What Users Can Do File good bugs Clear description: i.e.

    not “it doesn't work” Sample documents: should exist, and be minimal i.e. what is the smallest possible bug document Bug triage: hunting duplicates, poking “bad” bugs Help us out: we have some wonderful QA guys Test team Downloading and testing release candidates Using the latest snapshots, running QA testtool
  9. Build LibreOffice Find tasks to be solved Write code and

    patches that go into the software Experiment with and implement ideas Code
  10. Perform testing on the software Find and report bugs Review

    patches Help improve the quality of the software QA
  11. Translate the project in your local language Help the software

    reach out to a Non-English-Speaking audience too Localization
  12. Design buttons and icons Design web banners Design badges and

    stamps Make it just work, and look great, too! Graphics
  13. Help write technical documentation for the project Write technical “how

    to’s” for all the member applications Write User Guides Documentation
  14. Marketing Learn how to compete with the best marketing organization

    in the software environment, without a budget Work with the oldest and less enjoyable marketing guy in the free software world
  15. What Are We Doing Code Bug fixing New features: SmartArt,

    improved interoperability GNU-make completion & cross-compile for Windows During-build unit tests & improved QA process Moving bottom up ... clean code → clean UI → features Polish ... making it usable and pretty: i.e. Ctrl-F to find Governance Incorporation: raised 100k Euro for setting the legal entity http://wiki.documentfoundation.org/CommunityBylaws Membership process bootstrapping, ESC setup, etc.