Difference between revisions of "Infrastructure Requirements"
From Apache OpenOffice Wiki
(requirements) |
(some numbers.) |
||
Line 1: | Line 1: | ||
The following list contains the major functionalities expected from the | The following list contains the major functionalities expected from the | ||
− | OpenOffice.org infrastructure. The | + | OpenOffice.org infrastructure. The bullet points have been collected with focus on |
− | software developerment but are also applicable for user oriented needs. | + | software developerment but are also applicable for the user oriented needs. |
== Prioritized Item List == | == Prioritized Item List == | ||
− | 1) | + | # Framework |
+ | ## lightweight role / user administration / SSH key management<br>[incl. authorization / authentication interfaces for cmdline / web based apps] | ||
+ | ## structuring/projects/categories/namespaces<br>for tools like bugzilla, wiki, ... | ||
+ | # Version Control System for source code<br>[for web publishing and documentation see CMS] | ||
+ | #* CVS | ||
+ | #* [[SVNMigration|Migration to SVN]] planned | ||
+ | #* [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?) | ||
+ | #* [bonsai, lxr, fisheye / CIA, ...] | ||
+ | # Bug Tracking System (Bugzilla) | ||
+ | #* central configuration | ||
+ | #* export [/ import] interface | ||
+ | # Wiki (CMS) | ||
+ | #* for webcontent | ||
+ | #* allow branding | ||
+ | #* [localized UI] | ||
+ | #* versioned | ||
+ | #* namespaces | ||
+ | #* reuse of content (templates, server-side-include) | ||
+ | # Mailing Lists | ||
+ | #* different types (moderated, private) | ||
+ | #* non-site-member subscription | ||
+ | #* Archive | ||
+ | #* SPAM / Virus protected | ||
+ | #* [RSS] | ||
+ | #* [webbased forums] | ||
+ | #* NNTP | ||
+ | #* attachment stripping | ||
+ | #* customizable headers, footers, robot replies | ||
+ | #* Audit | ||
− | + | === Unprioritized === | |
− | + | ||
− | + | ||
− | + | * 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, ...) | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | == Key Numbers == | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | Per day the main site (actualy 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. | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |
Revision as of 20:38, 8 April 2006
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
- Framework
- lightweight role / user administration / SSH key management
[incl. authorization / authentication interfaces for cmdline / web based apps] - structuring/projects/categories/namespaces
for tools like bugzilla, wiki, ...
- lightweight role / user administration / SSH key management
- Version Control System for source code
[for web publishing and documentation see CMS]- CVS
- Migration to SVN planned
- [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?)
- [bonsai, lxr, fisheye / CIA, ...]
- Bug Tracking System (Bugzilla)
- central configuration
- export [/ import] interface
- Wiki (CMS)
- for webcontent
- allow branding
- [localized UI]
- versioned
- namespaces
- reuse of content (templates, server-side-include)
- Mailing Lists
- different types (moderated, private)
- non-site-member subscription
- Archive
- SPAM / Virus protected
- [RSS]
- [webbased forums]
- NNTP
- attachment stripping
- customizable headers, footers, robot replies
- Audit
Unprioritized
- 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, ...)
Key Numbers
Per day the main site (actualy 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.