On Tue, Jun 16, 2009 at 10:15 AM, Matthew Wilson<m...@tplus1.com> wrote: > Hi -- > > > I've been working on a distributed, flat-file-based issue-tracking > system named pitz. The idea is to keep issues in the same source > control system as the related code. > > Essentially, you use an IPython session to read and write your issues. > Each issue is a subclassed dict with some utility methods, including > a way to write itself out to a yaml file. > that sounds really interesting. It looks awfully familiar to a project I have been discussing with the author http://dvdev.org/
I'll take a look at this (for my stuff) thanks. > You would really help me out to try it out and either tell me why it > is not a good match or even adopt it. Right now, I"m using pitz for > my own projects and I like it, but I'd love to get other people's > remarks. > > A stale version is on the cheese shop. I update code fairly often > here http://github.com/mw44118/pitz/tree/master. > > Docs available at http://pitz.tplus1.com. > > > -- > Matthew Wilson > m...@tplus1.com > http://tplus1.com > > > _______________________________________________ > Fab-user mailing list > Fab-user@nongnu.org > http://lists.nongnu.org/mailman/listinfo/fab-user > _______________________________________________ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
