Saturday, July 24, 2010

OpenOffice.org Lessons Learned

Link to OSCON page.

openoffice.org

  • at first most considered openoffice.org a minor annoyance

    • wasn't popular at Sun as it undercut StarOffice

  • an alternative to a life of licensed software

  • focus on end-users

  • changing legacy software mindset

    • move away from monolithic structure

      • “let's cram as much crap into our software as possible”

      • difficult to refactor

    • focus on open data formats

    • ODF standard

      • make open source/standards/formats more palatable to governments and corporations

  • focus on extensions

    • allow non-core development


creating a community

  • requires a central focus

    • the easiest way is to have a common enememphasize the virtues of what you're doing

  • develop a product strategy

    • how do we encourage adoption

  • lower the bar of entry for contributing

    • don't just focus on developers

  • face-to-face meetings

  • architecture shapes community participation

    • monolithic structure limits participation

      • getting new developers is difficult

    • modular structure encourages participation

  • ecosystems

    • created around extensions, services, and support

  • education

    • need new developers

    • new developers need to be taught how to code and how to contribute

      • not a bunch of untrained developers slowing the process

      • the mythical man-month (throwing more developers at a project does not decrease development time)

No comments:

Post a Comment