Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Deleting doc wiki spaces
From: Andrus Adamchik <andrus@objectstyle.org>
In-Reply-To: <4E90FFCA.9040803@maniatis.org>
Date: Sun, 9 Oct 2011 11:19:46 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <38CAAC2F-40B2-406D-A423-F2DA689E8ACC@objectstyle.org>
References: <4924AAB8-2327-4B2F-8661-DD2D708679F8@objectstyle.org>
 <640DF9E1-87F9-486C-A3BC-0BBAEEE80B38@objectstyle.org>
 <4E90FFCA.9040803@maniatis.org>
To: dev@cayenne.apache.org


On Oct 9, 2011, at 4:58 AM, Aristedes Maniatis wrote:

> . Confluence website (maybe one day Apache CMS, but that's another =
issue)
> 2. docbook docs
> 3. javadocs
>=20
> (3) used to be built out of my p.a.o account, but recent changes there =
has meant that is no longer building

Is it our changes in the Maven build? Or something that infra has done?

> (2) needs some automated mechanism to build and publish. Should that =
be jenkins (not the most reliable!) and then a p.a.o script to publish =
to www?


> (1) continues to tick another as is, until I have time to spend on =
learning Apache CMS, navigating a bunch of obscure Perl, etc.
>=20
>=20
> As for old CAYDOC, I don't see why we'd want to delete old =
documentation. That is still useful.

We have 4 versions of the documentation with the wiki process - (a) =
dynamic on Wiki, (b) autoexported on wiki (cwiki.apache.org), (c) cloned =
from (b) to our site, (d) - specially formatted version of (a) in SVN. =
My suggestion is to remove (a) and (b) as we don't need them, but keep =
the (c) and (d).=20

> Google rankings are something else again and easily solved with a =
robots.txt in our root. I just did that now, wait 60 minutes for it to =
publish.

http://cayenne.apache.org/robots.txt - this is cool. We do need that =
(although maybe allow 30 for now). But I was thinking more about this =
one: https://cwiki.apache.org/robots.txt (if we delete the autoexported =
garbage, we won't care about it anymore though).


> As soon as the new docbook contains all the documentation from the =
current Confluence docs, then sure, let's replace the trunk =
documentation with docbook. We'll figure out if infra want us to publish =
using Jenkins, p.a.o or something else. I'll go ask there now.

My point is that we no longer need (a) and (b) above, but can keep (d) =
as long as we are doing the transition for 3.1 and indefinitely for 3.0 =
and earlier.=20

Does it make sense?

Andrus=