openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: Structure of the CWiki?
Date Thu, 18 Jul 2013 14:50:05 GMT
On Thu, Jul 18, 2013 at 10:33 AM, janI <> wrote:
> On 18 July 2013 15:29, Rob Weir <> wrote:
>> We have the opportunity to restructure the pages on our CWiki.    When
>> looking over the current structure it looks like we've been taking two
>> entirely different approaches to organizing the information:
>> 1) A team-oriented approach, where at the top organizational level
>> there are parent pages for each team, dev, qa, doc, l10n., etc.
>> 2) A release-oriented approach, where the top level is a specific
>> release, like AOO 3.4.1 or 4.0, and subpages are used for status and
>> plans for functional groups.
>> These two approaches look like they are both being used, but not
>> consistently.
>> I wonder if would be worth being more consistent, and doing something like:
>> 1) Have a top-level page for each functional group, for tracking
>> release-independent information, e.g., links to useful other pages,
>> lists of volunteers, "how to" information.  The stuff that does not
>> change from release to release.  It is information about the team and
>> what they do, not information about tasks for a specific release.
>> 2) Then have top-level release-specific pages, where we store plans
>> and status reports, dashboards, etc., associated with a release.
>> I think this is not so far from what the CWiki was evolving toward.
> If we anyhow think about restructuring, why not also think of a merge with
> does not seem correct that we need all these flavours of wiki,
> and it do cost maintenance.

Restructuring is just drag and drop in CWiki.  Migration would be more
effort, but we could restructure while migrating.  But a non-trivial
effort unless there is a tool that automates page conversion, moving
images, etc.


> rgds
> jan I.
>> -Rob
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message