Download Firefox: WindowsMac OS X
logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: Keeping track of stdlib documentation, and more: msg#00023

Subject: Re: Keeping track of stdlib documentation, and more
Regarding keeping records of what stage the rdoc'ing of
various files is up to, I agree that it would be a good idea
to have this centrally located.  I wonder, though, whether a
simple webapp wouldn't be better than a file in CVS?  Could
it even be done as a wiki page or pages?  I'd be happy to
put in any development time that was required.

As for RImport/rj, I'm not familiar enough with them to
really comment (I hope to make myself more familiar soon,
though).  I agree that putting it up on rubyforge is also a
good idea.

I'm doubtful about combining the stdlib documentation
project records with the RImport/rj project files, because
they seem to me fundamentally different types of objects,
and I'm also doubtful about putting the stdlib documentation
project records up on rubyforge by themselves, as they are
not a piece of software nor yet the documentation that is
the goal of the project, but rather administrative material
of a project whose productions are appearing somewhere else
(namely, the main ruby CVS repository).

William




<Prev in Thread] Current Thread [Next in Thread>