geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Kirby" <>
Subject Re: Update on documentation progress of Geronimo v2.2
Date Fri, 14 Nov 2008 17:05:32 GMT
I "fixed up" some of the references to GEP pages.  There is some
duplication of GEP info between two sets of pages:  "Development
environment" and "How to install Geronimo Eclipse Plugin".  A couple
of months ago I removed the installation instructions from the former,
and replaced them with a link to the latter.  The idea is to keep this
information in one place.  You can follow the gory details of this
work in GERONIMODEVTOOLS-461.  The plan is that there will be a "How
to install Geronimo Eclipse Plugin" page for each release.  Old and
new releases are children of this page.

The design of "Development environment" page seemed to be to put
everything on one big page.  I don't think this is a good approach.  I
think pages should be shorter and more focused.  For example, breaking
out the installation information.

Hopefully, we can all by in sync moving forward.  I think the GEP doc
needs some work in terms of integrating it into the overall G doc, and
eliminating duplication.  Hopefully this can occur in G 2.2 and

Ted Kirby

On Fri, Nov 14, 2008 at 1:13 AM, chi runhua <> wrote:
> Hi all,
> We just created a page with one table of content to track progress of
> Geronimo 2.2 documentation. In this table, we highlighted some topics to be
> updated based on G 2.2 release roadmap. We believe that not every topic was
> included so far. Therefore, don't hesitate updating the table if you have
> new discoveries or topics. We also encourage everyone in this community to
> adopt topics and contribute more to the success of Geronimo.
> Here is the linkage for your reference.
> What we are planning to do next are:
> 1. Moving pages to their appropriate parent so that the structure will be
> more like a "tree";  ---> Ongoing
> 2. Keep the consistency between different topics including subject, wording
> and phrases;
> 3. Keep migrating topics from previous documentation and update them if
> capable;
> 4. Refine the granuality by dividing unique topics into pages, in this way,
> contibutors can include existing pages while writing a new topics instead of
> introducing basic concepts again and again. (might be difficult, but I hope
> it's the right direction);
> We are expecting to receive as much as feedback and opinions about
> documentation so that we can make it better and better.
> Thanks alot.

View raw message