2. I definitely think that this would have to be something new. Like you
say, they have different purposes and it should be kept that way.
3. I think that using the apache SVN for this will be near impossible as
commit permissions would have to be given to everyone that commits to
the book. There has been talk in the past about creating sub-projects
under the Tapestry umbrella each with it's own permission scheme and all
that this idea never went into practice.
4. Like i suggested before, if we could find somewhere to host a Docbook
Wiki(http://doc-book.sourceforge.net/homepage/) i think it could work
quite well. Even without hosting, hand editing Docbook files isn't that
hard and there are tools to help get the job done.
There's also another possibility. Using Confluence with this plugin
(http://confluence.atlassian.com/display/CONFEXT/PDF+Documentation+Generator)
for generating the printable version. I never used the plugin but it
looks like it could get the job done. If it does, i think this could
definitely be a way to go.
Alex Kotchnev wrote:
This is great, we have at least a bunch of people who would like to
contribute. Any comments on the last couple of questions from my post :
2. Is there an existing place where this effort can be channeled
better,
instead of creating something new ?
I still don't know the answer to this question. One option would be to
try to enhance the existing docs, but it seems that the two will have a
slightly different purpose. The docs try to deliver as much punch as
possible within a couple of pages, whereas the book will probably have to be
a little bit more explanatory.
3. If this could be a new effort (e.g. a project tapestry-doc,
maybe??),
what are any additional requirements for doing it (in addition to some
of
the ones listed above).
Would it be an option to have an SVN component in the Tapestry
repository, or would this be harder than necessary (e.g. overhead of
Tapestry being an apache project) ? Any comments on using Google code for
this ( they already have a wiki and an issue tracker for each project) ?
4. If this is to be done, what's the best way of doing it ? I'll
research
to
see if I can find out how Django did their, but general feedback &
ideas
on
the technicalities would be very useful. E.g. how do people
collaborate
best
on writing a book ? Is there an existing service that might make this
easier
Has anyone written a book or collaborated with a couple of other people
in writing one (other than Howard :-) ). Do you know personally anyone who
has such experience ( I plan to ping Geertjan Wielenga from the NetBeans
community to see if he can give me some advice) ? Any ideas of how we can
handle the code in the book (to make sure it always works) ?
Would the user list be the best place to keep the discussion going or
would this be an annoyance to everyone else ?
I guess the easiest start would be to post some kind of outline of the
book table of contents on the T5 wiki. While we're coming up with that we
should probably figure out the answers to the questions above, as I don't
think the wiki is the ultimate place to keep this.
Cheers,
Alex Kotchnev
