[kepler-dev] breaking off a kepler-docs repository
jones at nceas.ucsb.edu
Fri Aug 5 06:36:24 PDT 2005
One thing I like about using CVS for document management is being able
to travel with everything and access all of the docs even when I am not
network connected. I find I often need access to powerpoint files and
word files in particular when I am on airplanes, and so I think whatever
solution we choose should allow a simple mechanism for downloading the
whole repository to local systems for offline access.
Otherwise, I would be fine with separating out a document repository.
Shawn Bowers wrote:
> I think it is a good idea to *not* include the various publications and
> presentations concerning Kepler in the code repository (cvs).
> I wonder, however, if having a separate cvs for documents is the way to
> go. Instead, maybe we should consider using a more traditional approach
> like a document management system? I'm sure there are a number of
> open-source/free ones out there (e.g., zope and plone are popular ones,
> the stanford publication server is an older one). Perhaps there are
> also extensions of the wiki for this?
> Chad Berkley wrote:
>>As I sit here checking out kepler (again), waiting forever for the docs
>>directory to finish, it occured to me that it might be ok to have a
>>different cvs repository for kepler docs. there's no reason why a
>>developer should have to checkout out a myriad of .doc and .ppt files
>>everytime you need a new version of kepler. It seems to me that docs
>>that actually go with the kepler software should stay in the kepler
>>repository, but publications, reports and the like could be stashed
>>somewhere else. Anyone have any reasons why this would be a bad idea?
>>Kepler-dev mailing list
>>Kepler-dev at ecoinformatics.org
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
More information about the Kepler-dev