<br><br><div class="gmail_quote">On Sun, Sep 13, 2009 at 10:48 AM, Kamil Dworakowski <span dir="ltr"><<a href="mailto:kamil@dworakowski.name">kamil@dworakowski.name</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br>
</div></div>Good point that notification is the week point of this method of<br>
communication. I think the reason for the wiki page was simply that it<br>
was hard to follow the thread, especially that there was mentioning of<br>
some off the list discussion and that at some point the title changed.<br>
I was also not helping by repeatedly replying just to the author<br>
omitting the list. I think I have this impulse already under control<br>
and now that we have all the current context on the wiki we might<br>
continue the discussion on the mailing list. Anyway, I am happy either<br>
way, though wiki might have more latency obviously. I shall try to<br>
follow irc too.<br></blockquote><div><br></div><div>My reply is going to be a fair bit off topic now, but after I sent that message, I realized that a good hybrid-compromise would be a bug tracker built on top of darcsit, as long as it had a good bug tracking interface. Here are some things it could excel at:</div>
<div>1) Distributed and offline usage</div><div>2) (optional for users) Integration with CLI tools</div><div>3) (optional for users) Web interface</div><div>4) History</div><div>5) Good searching</div><div>6) Support for local customizations</div>
<div><br></div><div>I marked 2 & 3 and optional meaning, I would like it offer both and let the user decide which to use.</div><div><br></div><div>Not a project I want to start, but I could see it being popular.</div>
<div><br></div><div>Jason</div></div>