incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: Access to wiki
Date Sun, 07 Aug 2011 17:50:13 GMT

One clarification.  

Moving the Wiki onto Apache infrastructure is not the same as moving it onto an Apache domain.
 We have the possibility of sustaining http://* (sub)-domains which have community
and participatory focus, with movement of other materials to locations that reflect
their incorporation in the release structure.  While we might need to adjust the administration,
clean out accounts, etc., we can minimize disruption by preserving that which already works
and has no need to be changed.

 - Dennis

-----Original Message-----
From: Eike Rathke [] 
Sent: Sunday, August 07, 2011 03:21
Subject: Re: Access to wiki

Hi Rob,

On Saturday, 2011-08-06 21:05:49 -0400, Rob Weir wrote:

>  It is much more than just 2 categories, official or unofficial doc.
> Looking around I see things like:
> a) Official doc (current)
> b) Official doc (obsolete)
> c) Doc in progress (active)
> d) Doc in progress (abandoned)
> e) Project planning docs
> f)  Pages related directly to the development of the product, e.g.,
> build instructions, architecture notes, coding standards, etc.
> g) Marketing and event related pages
> h) Pages related to the governance of the project, e.g., minutes from
> engineering steering committee meetings, etc.
> i) Biography/home pages for project volunteers
> j) And probably many other categories

Given this list I see the following categories:

A) Apache OOo committers only, with comments/discussion enabled for
   everyone with a wiki account.
B) Contributed 3rd party material, unsure which edit rights those should
   be assigned.
C) Community wiki editable for everyone with a wiki account under AL2 or
   a permissive license.
D) Museum, read-only pages that can be revived and moved to one of the
   other categories.
E) Dump. Pages that were contributed under licenses that are not
   permissive in an Apache project.

Material of categories:

A: a, e, f, h
B: TBD, e.g. the ODFAuthors documentation
C: c, g, i, j
D: b, d

> 1) Migrate the wiki off of Oracle and on to Apache machines.  But
> pending further consensus, keep it read-only except to committers.
> 2) At the same time, make the Oracle-hosted version be read-only.
> 3) Figure out the minimal number of changes necessary for the PPMC to
> have consensus that Oracle can shut down their server and switch the
> domain to point to the Apache version. This might include things like
> branding, license, policies, appointment/confirmation of
> admins/moderators, etc.
> 4) Prepare notification to community about the new website.
> 5) Go live, along with notification to community

Sounds like a plan. Though for 1) consensus should be reached quickly to
not put contributors off.


 PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication.
 Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3  9E96 2F1A D073 293C 05FD

View raw message