New effort...
Christoph Zwerschke
(posted at the TG group). I'm currently a bit busy, but generally I'm
ready and interested to help with this effort.
Not sure whether we should aim at the TG 1.1 branch or current trunk
based on Pylons. I'd prefer the latter, but in the last time work on the
TG trunk seems to have stalled. Or should we take this as an opportunity
to revive that as well?
-- Chris
Kevin Horn
It might also be a good way to promote TG2, as a "real app" to show off its capabilities.
While it may be a while before I can manage to start work on this, there's no reason we can't start planning now (and I think we should). I've been working on some design notes, which I'll post here before too long, a few days at most.
If there are any features, etc. you'd like to see in Docudo, now would be a good time to speak up!
Kevin Horn
Mark Ramm
> based on Pylons. I'd prefer the latter, but in the last time work on the
> TG trunk seems to have stalled.
I've been swamped with work reciently, but TG 2 mostly just needs to
be pulled up to the latest changes in Pylons. We'll still have to
work out some things, but I think lots of progress on this will happen
over the next 3 to 4 weeks.
> Or should we take this as an opportunity to revive that as well?
I'd love to have some more eyes on the trunk, and I'm definitely
trying to get the trunk in shape fror a preview as soon as we can.
Having some work on Docudo happen against trunk would help a lot in
terms of flushing out what might still need to be finished.
--Mark
Kevin Horn
I'd love to have some more eyes on the trunk, and I'm definitely
trying to get the trunk in shape fror a preview as soon as we can.
Having some work on Docudo happen against trunk would help a lot in
terms of flushing out what might still need to be finished.
--Mark
One thing to be sure you provide when the TG2 preview comes out is instructions on how to set up a dev environment (on multiple platforms...*nux, OS X, Win32). I'm sure you've already considered this, but I thought I'd mention it, just in case. I do most of my development on Windows, mostly because I need it for other things, and I've occasionally had trouble with the dev instructions on Win32 (though granted, I haven't looked at it in a loooong time now, it may have already improved).
John Lavoie
requires PySVN, which can be difficult to install/build on certain
platforms.
If Docudo is to be an example of how to create a TG application, it may
be a good idea to remove PySVN so that other users can pull the source
be up and running quickly.
John
Kevin Horn
At one point during the original development of Docudo, it was not necessary to have a subversion repository, and you could optionally store your docs in a simple local file structure. I think this option needs to return, but expanded.
I'd like the New Docudo to have support for multiple storage backends, which would be available as eggs. I think this would help people get started using it, and also help with development, since then people wouldn't necessarily have to have a SVN repository available to test with.
It might even mean that we could have 2 subversion storage backends. One based around PySVN, and one based around the Subversion Python bindings. I haven't looked at the Bindings in any great detail, so I don't know whether this would actually work, but it may be possible.
Kevin Horn
Mark Ramm
> would be available as eggs. I think this would help people get started
> using it, and also help with development, since then people wouldn't
> necessarily have to have a SVN repository available to test with.
Bazaar is a pure python version control system, so it might be a
candidate for one of the early back ends too.
--Mark
Ian Bicking
Bazaar or hg are probably easier to distribute, and does the particular
backend matter that much so long as it is versioned?
OTOH, creating a local svn repository is fairly trivial for testing,
just do "svnadmin create /path" and "file:///path" is your repository.
It's easy to do for local testing.
--
Ian Bicking : ia...@colorstudy.com : http://blog.ianbicking.org
: Write code, do good : http://topp.openplans.org/careers
Kevin Horn
Kevin Horn
Bazaar or hg are probably easier to distribute, and does the particular
backend matter that much so long as it is versioned?
No, it doesn't really matter, but I think SVN support is crucial for groups that already have a large doc base in some kind of repository. Also, it has a much larger user base than Bazaar or others. People will recognize SVN.
That said, SVN doesn't need to be the default backend, nor does it need to be the first one we support. As I said, I want to support multiple storage backends.
Of course, if we use something else, it will mean more of a learning curve for me personally, since SVN is what I use for my projects. :(
Kevin Horn
OTOH, creating a local svn repository is fairly trivial for testing,
just do "svnadmin create /path" and "file:///path" is your repository.
It's easy to do for local testing.
This was until recently less than trivial on Windows. It's gotten better now.
Mark Ramm
http://gazdemo.ygingras.net/wiki/Index/hist
This gives you 3 way merge, some cool options for branching the docs
for new software versions, and may be a good way to go for Docudo2 ;)
I'm less concerned about having multiple versioned backends than
having one working version of Docudo. Multiple backends will come if
Docudo is successful, but not the other way around ;)
--
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog
Kevin Horn
I was mostly interested in just setting up the code so that the storage backend was pluggable. My intention (and I think most people will agree) is to have one "sensible default", but with enough forethought in the design to allow OTHER PEOPLE to write additional backends. I certainly don't care to write (or support) them all myself. :)
And thanks for the link, Mark, I will definitely try to check that out.
Kevin Horn