Talk:Foss.in

One of the primary aspects that we should be focusing upon is that OO.o as an application is not only consumed by the Small Office Home Office population who have access to it through distributions. OO.o is also something that is used strategically by:

   * organizations doing Information and Communication Technologies for Development
   * deployments at places like Judiciary and related citizen centric services by the Government of India

If localization is of paramount importance it is because of:

   * the work around the effort by local groups
   * acceptance of ODF and L10n into Government policy

One of the reasons that contributions to OO.o as a project (as well as an application) is really low is that there is a perceived high barrier to entry. This is accentuated by the lack of core developer guidance and documentation.

The objective of the OO.o PD and the subsequent OO.o BoF was to discuss ways and means of addressing the following:

  * Lowering barriers for entry
      o have defined and documented means of entry into OO.o Project (with perhaps using stories)
      o provide documentation and mentoring towards contribution
  * Extend functionality of OO.o as an application
      o ensure a larger number of relevant extensions (eg templates of local language forms,letters) are available
      o encourage extension creation
      o encourage macro creation towards helping migration cases
  * Use OO.o Project resources
      o provide access to Build-Test-Release framework that would allow building,testing and releasing using OO.o infrastructure
      o have "Tech Days" with the intention of "showing how to use the components" as opposed to current "telling how cool it is"
  * Evangelize
      o business opportunities around OO.o
      o policy framework around OO.o and ODF