> >Well, IMHO =) I think the decision should be up to the TC4
> >committers (i.e.
> >people who will deal with the build, edit the docs, etc.).
>
> There is commiters in tomcat area which are not just TC4
> commiters, TC 3.2/3.3 teams, JTC team, Jasper34 team.
For sure, I was just thinking that the people who will ultimately deal with
the consequences of the vote (TC4 developers and TC4 active documentation
authors) should have the most say in how the TC4 docs are developed. That
is unless of course we start talking about a big unified documentation
project, etc. etc. which opens up all the cans of worms that I don't think
anyone will want to stick around long enought to deal with =)
> >They seem to
> >have already decided.
>
> Who decided what ? I didn't recall about a VOTE on that area.
What I meant was that the TC4 developers have already decided on Anakia for
TC4, as in, "that's what they're using now."
> The pre-proposal was about having a separate tomcat subproject,
> jakarta-tomcat-doc, where redactors could have access to this
> particular CVS even if they don't have access to code CVS.
>
> I'd like to see the same organisation in J-T-D (jakarta-tomcat-doc)....
I'm not a committer, but FWIW I don't think this is such great idea. Like I
mentioned in a previous post - the more time and effort spent on such an
undertaking will most likely not get enough people active and on-board to
make it worth while.
Documentation management can be as complicated as anyone likes. You'll have
to correct me if I'm wrong, but I was pretty sure Pier mentioned that there
wasn't much overlap, if any at all, between 3.x and 4.x. I don't think
spending a huge amount of time just to centralize docs benefits us in
significant manner.
My thought is that until now, we've been unable to produce what many agree
is a quality batch of documentation. Once we've proven to ourselves that we
can perform that one 'small' task =) then I would feel more comfortable
complicating things.
- r
