Difference between revisions of "Infrastructure Requirements"
(Infrastructure Requirements taken from mtg's comments on the infrastructure_problems page) |
(requirements) |
||
Line 1: | Line 1: | ||
− | + | The following list contains the major functionalities expected from the | |
+ | OpenOffice.org infrastructure. The bullte points have been collected with focus on | ||
+ | software developerment but are also applicable for user oriented needs. | ||
− | + | == Prioritized Item List == | |
− | + | 1) Framework | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | 1a) lightweight role / user administration / SSH key management | |
+ | [incl. authorization / authentication interfaces for cmdline / web | ||
+ | based apps] | ||
+ | |||
+ | 1b) structuring/projects/categories/namespaces | ||
+ | f. tools like bugzilla, wiki, ... | ||
+ | |||
+ | 2) Version Control System for source code | ||
+ | [for web publishing and documentation see CMS] | ||
+ | CVS [svn/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, ...] | ||
+ | |||
+ | 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) | ||
+ | [scriptable / workflow] | ||
+ | |||
+ | 5) 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 | ||
+ | |||
+ | 6) Audit | ||
+ | |||
+ | === Unprioritized === | ||
+ | |||
+ | ?) localization of UI parts (bugtracking, webpages, ...) | ||
+ | and process for new locales | ||
+ | ?) reporting / stats / logfiles | ||
+ | ?) Search? use 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, ...) | ||
+ | |||
+ | SLA | ||
+ | + availability / uptime | ||
+ | + upgradable by component (not only as a whole) | ||
+ | + scalability / firewalled / distribution of services | ||
+ | + OS and software security patches | ||
+ | + helpdesk / response times on issues | ||
+ | + backup / restore | ||
+ | + bandwidth / transfer volume / | ||
+ | + disk space | ||
+ | + roadmap for enhancements / DIY | ||
+ | |||
+ | Migration | ||
+ | + CVS content (incl webcontent from <project>/www?) | ||
+ | + IZ data | ||
+ | + mailing list subscriptions / mail archive | ||
+ | + docs & files | ||
+ | + DNS | ||
+ | + user data |
Revision as of 03:49, 4 April 2006
The following list contains the major functionalities expected from the OpenOffice.org infrastructure. The bullte points have been collected with focus on software developerment but are also applicable for user oriented needs.
Prioritized Item List
1) Framework
1a) lightweight role / user administration / SSH key management
[incl. authorization / authentication interfaces for cmdline / web
based apps]
1b) structuring/projects/categories/namespaces
f. tools like bugzilla, wiki, ...
2) Version Control System for source code
[for web publishing and documentation see CMS] CVS [svn/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, ...]
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) [scriptable / workflow]
5) 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
6) Audit
Unprioritized
?) localization of UI parts (bugtracking, webpages, ...)
and process for new locales
?) reporting / stats / logfiles ?) Search? use 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, ...)
SLA + availability / uptime + upgradable by component (not only as a whole) + scalability / firewalled / distribution of services + OS and software security patches + helpdesk / response times on issues + backup / restore + bandwidth / transfer volume / + disk space + roadmap for enhancements / DIY
Migration + CVS content (incl webcontent from <project>/www?) + IZ data + mailing list subscriptions / mail archive + docs & files + DNS + user data