On Mon, 14 Aug 2000, Josh Lucas wrote:
> Jason van Zyl wrote:
> >
> >
> > No, all documentation would move into a new branch. The
> > turbine documentation is our website.
> >
> > Three reasons:
> >
> > 1. I would like to be able to use whatever tools, scripts
> > for building the docs without worrying about bloating
> > the base turbine. I'm using StyleBook, which requires
> > Xalan, and I want to write some python scripts to
> > make a skin maker.
> >
> > 2. I have found someone who take care of the turbine
> > docs. Though he is technially proficient he isn't
> > a programmer (which is good for the docs!) and I
> > think it would be best to keep him out of the
> > base turbine. He knows someone who is interested
> > in helping out. So if we actually get a couple
> > non-programmers doing docs then it's probably
> > best to keep them out of the main branch.
> >
> > 3. Sometime this week the TDK will be finished, and
> > it will combine turbine, tomcat, and all the docs.
> > So I don't think it matters if the docs and
> > base turbine are separated, because they will
> > be recombined in the TDK which, hopefully will
> > become the first thing that potential turbine
> > developers will see.
> >
> > What's the policy anyway for going ahead with
> > something? How many votes do I need? Something
> > to add to the docs!
>
> I'm not totally sold on this because I feel we should have *something*
> in a checkout of the base module. I realize that the TDK will take care
> of many things but some users/developers will want some docs.
>
> An idea which might work would be to add an Ant target for the docs so a
> developer could run './build-turbine.sh docs' and the relevant module
> would be checked out of CVS and any files that need to be built would be
> generated. An echo message could alert the developer that a sizable
> download was going to be taking place just to make sure there aren't
> complaints about that.
Sure, or we could just put a copy of resultant html in the docs
directory, and update it with a cron job. The resultant html
doesn't take up much room. That would be fine with me.
So how about that, we'll make a separate documentation
project, and put a copy of the resultant html in the
turbine/docs directory.
jvz.
--
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
