Difference between revisions of "Infrastructure Requirements"

Revision as of 15:23, 16 September 2007

The following list contains the major functionalities expected from the OpenOffice.org infrastructure. The bullet points have been collected with focus on software developerment but are also applicable for the user oriented needs.

Prioritized Item List

1. Framework
   1. lightweight role / user administration / SSH key management
      [incl. authorization / authentication interfaces for cmdline / web based apps]
      (e.g. LDAP directory, could be placed on the SVN/CVS server)
   2. structuring/projects/categories/namespaces
      for tools like bugzilla, wiki, ...
2. Version Control System for source code
   [for web publishing and documentation see CMS]
   • CVS
   • Migration to SVN planned
     (NB. auth for SVN usually done using HTTPS or SSH)
   • [svk/distributed later?]
   • admin access for cvsroot manipulation, deletion, move
   • cvsup, anoncvs, viewcvs, notification mails, ...
   • simple permission system (s. 1)
   • authenticated access via SSH tunnel (and/or direct?) Using svn we can be secure, yet not need the use of a tunnel, thus reducing the barriers to participation.
   • Preferrably sudo root access for selected admins
   • [bonsai, lxr, fisheye / CIA, ...]
3. Bug Tracking System (Bugzilla)
   • central configuration
   • export [/ import] interface
4. Wiki (CMS)
   • for webcontent
   • allow branding
   • [localized UI]
   • versioned
   • namespaces
   • reuse of content (templates, server-side-include)
5. Mailing Lists
   • different types (moderated, private)
   • non-site-member subscription
   • Archive
   • SPAM / Virus protected
   • [RSS] for easy syndication of new from various parts of the site, including the home page and mac port pages.
   • [webbased forums]
   • NNTP
   • attachment stripping
   • customizable headers, footers, robot replies
6. Audit

Unprioritized List

• localization of UI parts (bugtracking, webpages, ...) and process for new locales
• reporting / stats / logfiles
• Search via Google, Yahoo, ...
• mail forwarding (xxx@openoffice.org)
• IP / domain blocking
• blog / planet
• download, documents & files structured in folders
• surveys / votes / polls
• general open-ness for integration of scripting (PHP, Perl, ...)
• MySQL databases
• provide SSL logon for security reasons
• rise the limit for mail attachments from 2 MB to 10 MB

Key Numbers

Per day the main site (actually the accelerators) receives 4-6M hits / 100,000 - 150,000 visits and sends 40-60GB. In peaks like the OpenOffice.org 2.0 launch there were > 16M hits per day with more than 400,000 visits.

The mail server has to be prepared to handle 50 msg/sec and 300 parallel sessions when the rising tide flows in.

See also

• Infrastructure_Overview
• Infrastructure_Problems