DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Where we are today
The Apache OpenOffice project maintains the following web properties today:
Property |
Technology |
Content size |
Usage level |
|---|---|---|---|
www.openoffice.org |
Static pages, mainly HTML, some MDText. |
19,697 html pages |
Top page (download/index.html) receives 3.5 million visits/month. |
openoffice.apache.org |
Static pages mainly MDText. |
49 mdtext pages |
155K total page views/month |
cwiki.apache.org/confluence/display/OOOUSERS/ |
Confluence Wiki |
~180 pages |
Unknown, but mainly active project members, not end-users, though permissions permit public editing. |
cwiki.apache.org/confluence/display/OOODEV/ |
Confluence Wiki |
1 page |
Unused |
wiki.openoffice.org |
Media Wiki |
11,281 pages |
~900K page viewers per month |
forum.openoffice.org |
phpBB |
? |
? |
extensions.openoffice.org |
? |
? |
? |
templates.openoffice.org |
? |
? |
? |
What is working well today
- We've successfully migrated and preserved a huge amount of content (over a decade's worth) and brought it over to Apache.
- The CMS mechanism allows us to quickly push out page changes to the website, including site-wide template changes. The most common site-wide changes can be made efficiently, without touching every page, an important consideration for a website of this size.
- MediaWiki user interface is well-known and accepted by its users.
- Site-wide integration of Google Analytics has enabled us to track how our sites are being used and provides concrete data for decision making.
What is not working so well today
- Redundancy of services, in particular the multiple wikis. This fragments content and causes confusion.
- UI inconsistency between our web properties.
- Inconsistency within individual properties, e.g., within the www.openoffice.org website, especially with the NL websites.
- Inconsistency at the markup level as to what HTML version is being targeted, what encodings are used, whether document is even well-formed. In other words, all the liabilities of human-authored HTML.
- In general lack of a consistent information taxonomy that allows the user (or the content author) to know where a given topic belongs on the website(s).
- Perception that website is "tired" and lacks freshness and modern appeal.
- Large amounts of outdated content on website and wiki.
- Lack of consistent, documented best practices and techniques for maintaining NL websites. What is translated and how?
- Skill mismatch between what translators know and what is actually needed to maintain an NL website. (Translators are not HTML designers and certainly not CMS experts)
- Similar for potential content authors, the skill level needed to maintain an HTML-based website with the CMS exceeds that of most potential volunteers.
- Sustainability concerns due to our use of unsupported applications (from Apache Infra perspective), including phpBB and MWiki and reliance on a very small number of system admins.