From judofyr at gmail.com  Wed Oct  1 16:18:04 2008
From: judofyr at gmail.com (Magnus Holm)
Date: Wed, 1 Oct 2008 22:18:04 +0200
Subject: [ditz-talk] Gitz - Gash-powered Ditz
Message-ID: <391a49da0810011318y58d29a47x85b43b0ee9e9f46c@mail.gmail.com>

Hiya!

I'm thinking of combining Gash[1] and Ditz in order to make it more
"streamlined" for Git-users. So all your issues live in the bugs-branch,
which isn't really checkout out anywhere (Gash can easily read/commit
without checking out the branch). The gitz-command will work just like ditz,
but will read the issues from the bugs-branch and commit if needed. There
should also be a gitz-shell when you need to run several commands (only
loading the issues once).

I'm only throwing ideas around (haven't written a single line of code) and
am wondering if it's actually possible:

1) How easy is it to switch from file-based to hash-based storage of issues?
2) How easy is it to mimic the ditz-command?
3) Could it be done with a plugin, or would a seperate project be better?


[1]http://judofyr.net/posts/its-a-gash-gash-gash.html
-- 
Magnus Holm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20081001/c257630e/attachment.html>

From wmorgan-ditz at masanjin.net  Wed Oct  1 19:32:34 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Wed, 01 Oct 2008 16:32:34 -0700
Subject: [ditz-talk] Gitz - Gash-powered Ditz
In-Reply-To: <391a49da0810011318y58d29a47x85b43b0ee9e9f46c@mail.gmail.com>
References: <391a49da0810011318y58d29a47x85b43b0ee9e9f46c@mail.gmail.com>
Message-ID: <1222903294-sup-3689@entry>

Reformatted excerpts from Magnus Holm's message of 2008-10-01:
> [1]http://judofyr.net/posts/its-a-gash-gash-gash.html

Very cool stuff.

> I'm thinking of combining Gash[1] and Ditz in order to make it more
> "streamlined" for Git-users. So all your issues live in the
> bugs-branch, which isn't really checkout out anywhere (Gash can easily
> read/commit without checking out the branch)

Sounds like a good idea. Although I do think the optimal way of using
Ditz is usually to maintain a separate database on a per-branch basis,
maintaining the issues on a per-project basis is useful for some
projects and I'd like to keep supporting it.

> 3) Could it be done with a plugin, or would a seperate project be
> better?

You could implement it as a separate command, but I think a plugin would
be better. Then the interface stays the same. Doing this the right way
will probably require adding some new plugin infrastracture, e.g.  the
ability to change the storage mechanism, which I believe is hardcoded
in bin/ditz right now.

> 1) How easy is it to switch from file-based to hash-based storage of
> issues?

I would guess reasonably easy. I abstracted away all file access into
the FileStorage object, but there are a few remaining file-specific
behaviors that may have to be tweaked (or disabled). Things like 'ditz
archive', for example. I've also never actually implemented another
storage mechanism, so you might find dependencies I didn't think about
as you start doing it.

> 2) How easy is it to mimic the ditz-command?

Again, reasonably easy, should you chose to go that route. Basically you
just need to call methods on the Operator class. If you look at bin/ditz
you'll see it's basically just loading configuration files, parsing
commandline arguments, and pretty-printing any errors.

This sounds like a pretty cool idea. Let me know if you have more
questions!
-- 
William <wmorgan-ditz at masanjin.net>

From matt at tplus1.com  Fri Oct  3 14:26:59 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Fri, 3 Oct 2008 14:26:59 -0400
Subject: [ditz-talk] How do I see the debugging statements?
Message-ID: <f6f643a20810031126m25b8af91ha764590e3b19cc70@mail.gmail.com>

I see in the bin/ditz code lots of stuff like:

  Ditz::debug "loading config from #{$opts[:config_file]}"

What do I need to do to see those statements?

Matt

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com

From matt at tplus1.com  Fri Oct  3 14:43:22 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Fri, 3 Oct 2008 14:43:22 -0400
Subject: [ditz-talk] How do I pass in the ignore_case option to ditz grep?
Message-ID: <f6f643a20810031143y33204a50ud071054dc6730973@mail.gmail.com>

I'm reading the code in lib/ditz/operator.rb, and it seems like the
grep command / operator supports case-insensitive searches.

I can't figure out what to type at the command-line to enable
ignore_case in the code.  Any ideas?

Here's (I think) the relevant code from lib/ditz/operator.rb:

  operation :grep, "Show issues matching a string or regular
expression", :string do
    opt :ignore_case, "Ignore case distinctions in both the expression
and in the issue data", :default => false
  end

  def grep project, config, opts, match
    run_pager
    re = Regexp.new match, opts[:ignore_case]
    issues = project.issues.select do |i|
      i.title =~ re || i.desc =~ re ||
        i.log_events.map { |time, who, what, comments| comments
}.join(" ") =~ re
    end
    puts(todo_list_for(issues) || "No matching issues.")
  end

Matt

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com
216-470-6058

From wmorgan-ditz at masanjin.net  Fri Oct  3 14:46:52 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Fri, 03 Oct 2008 11:46:52 -0700
Subject: [ditz-talk] How do I see the debugging statements?
In-Reply-To: <f6f643a20810031126m25b8af91ha764590e3b19cc70@mail.gmail.com>
References: <f6f643a20810031126m25b8af91ha764590e3b19cc70@mail.gmail.com>
Message-ID: <1223059587-sup-6740@entry>

Reformatted excerpts from Matthew Wilson's message of 2008-10-03:
> What do I need to do to see those statements?

-v
-- 
William <wmorgan-ditz at masanjin.net>

From wmorgan-ditz at masanjin.net  Fri Oct  3 15:16:06 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Fri, 03 Oct 2008 12:16:06 -0700
Subject: [ditz-talk] How do I pass in the ignore_case option to ditz
	grep?
In-Reply-To: <f6f643a20810031143y33204a50ud071054dc6730973@mail.gmail.com>
References: <f6f643a20810031143y33204a50ud071054dc6730973@mail.gmail.com>
Message-ID: <1223061336-sup-932@entry>

Reformatted excerpts from Matthew Wilson's message of 2008-10-03:
> I'm reading the code in lib/ditz/operator.rb, and it seems like the
> grep command / operator supports case-insensitive searches.
> 
> I can't figure out what to type at the command-line to enable
> ignore_case in the code.  Any ideas?

If you do "ditz grep --help" it will give you a mini-help. In this case
it's -i or --ignore-case.
-- 
William <wmorgan-ditz at masanjin.net>

From matt at tplus1.com  Fri Oct 10 11:23:06 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Fri, 10 Oct 2008 11:23:06 -0400
Subject: [ditz-talk] Why add a comment when adding a new issue?
Message-ID: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>

I don't see why I would ever put anything in the comment field when
I'm creating a ditz issue.  I put my long-winded explanations in the
description section, then (theoretically) I would use the comment
field later as I remark on progress made.

Is there a way to configure ditz so that it doesn't ask me for a
comment during issue creation?

Matt

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com
216-470-6058

From nate at natemurray.com  Fri Oct 10 11:42:17 2008
From: nate at natemurray.com (Nate Murray)
Date: Fri, 10 Oct 2008 08:42:17 -0700
Subject: [ditz-talk] Why add a comment when adding a new issue?
In-Reply-To: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
References: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
Message-ID: <9c1993f20810100842k14604ff5v1f7fe66108055b7b@mail.gmail.com>

+1 on this opinion

On Fri, Oct 10, 2008 at 8:23 AM, Matthew Wilson <matt at tplus1.com> wrote:
> I don't see why I would ever put anything in the comment field when
> I'm creating a ditz issue.  I put my long-winded explanations in the
> description section, then (theoretically) I would use the comment
> field later as I remark on progress made.
>
> Is there a way to configure ditz so that it doesn't ask me for a
> comment during issue creation?
>
> Matt
>
> --
> Matthew Wilson
> matt at tplus1.com
> http://tplus1.com
> 216-470-6058
> _______________________________________________
> ditz-talk mailing list
> ditz-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ditz-talk
>

From nicolas.pouillard at gmail.com  Fri Oct 10 16:00:31 2008
From: nicolas.pouillard at gmail.com (Nicolas Pouillard)
Date: Fri, 10 Oct 2008 22:00:31 +0200
Subject: [ditz-talk] Why add a comment when adding a new issue?
In-Reply-To: <9c1993f20810100842k14604ff5v1f7fe66108055b7b@mail.gmail.com>
References: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
	<9c1993f20810100842k14604ff5v1f7fe66108055b7b@mail.gmail.com>
Message-ID: <1223668826-sup-8695@ausone.local>

Excerpts from Nate Murray's message of Fri Oct 10 17:42:17 +0200 2008:
> +1 on this opinion
+1

> On Fri, Oct 10, 2008 at 8:23 AM, Matthew Wilson <matt at tplus1.com> wrote:
> > I don't see why I would ever put anything in the comment field when
> > I'm creating a ditz issue.  I put my long-winded explanations in the
> > description section, then (theoretically) I would use the comment
> > field later as I remark on progress made.
> >
> > Is there a way to configure ditz so that it doesn't ask me for a
> > comment during issue creation?
> >
> > Matt
> >
> > --
> > Matthew Wilson
> > matt at tplus1.com
> > http://tplus1.com
> > 216-470-6058
> > _______________________________________________
> > ditz-talk mailing list
> > ditz-talk at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/ditz-talk
> >

-- 
Nicolas Pouillard aka Ertai

From wmorgan-ditz at masanjin.net  Fri Oct 10 16:27:22 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Fri, 10 Oct 2008 13:27:22 -0700
Subject: [ditz-talk] Why add a comment when adding a new issue?
In-Reply-To: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
References: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
Message-ID: <1223670247-sup-2612@entry>

Reformatted excerpts from Matthew Wilson's message of 2008-10-10:
> Is there a way to configure ditz so that it doesn't ask me for a
> comment during issue creation?

I don't want too much configuration. I'd rather disable it entirely for
add, since I also don't use it. Any strong objections to that?
-- 
William <wmorgan-ditz at masanjin.net>

From mitch at cgarbs.de  Fri Oct 10 17:16:35 2008
From: mitch at cgarbs.de (Christian Garbs)
Date: Fri, 10 Oct 2008 23:16:35 +0200
Subject: [ditz-talk] Why add a comment when adding a new issue?
In-Reply-To: <1223668826-sup-8695@ausone.local>
References: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
	<9c1993f20810100842k14604ff5v1f7fe66108055b7b@mail.gmail.com>
	<1223668826-sup-8695@ausone.local>
Message-ID: <20081010211635.GC23092@cgarbs.de>

On Fri, Oct 10, 2008 at 10:00:31PM +0200, Nicolas Pouillard wrote:
> Excerpts from Nate Murray's message of Fri Oct 10 17:42:17 +0200 2008:
> > +1 on this opinion
> +1
+1

Regards,
Christian
-- 
....Christian.Garbs.....................................http://www.cgarbs.de

Hilfe! Ich werde in einer Signaturfabrik gefangengehalten!


From matt at tplus1.com  Fri Oct 10 19:13:44 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Fri, 10 Oct 2008 19:13:44 -0400
Subject: [ditz-talk] How can I remove a release?
Message-ID: <f6f643a20810101613n31d52079mec3a9b5dafcd2754@mail.gmail.com>

So, after I create a release, how can I remove it, if I decide I'm not
going to do that release?

Matt

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com

From wmorgan-ditz at masanjin.net  Sat Oct 11 14:59:09 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Sat, 11 Oct 2008 11:59:09 -0700
Subject: [ditz-talk] How can I remove a release?
In-Reply-To: <f6f643a20810101613n31d52079mec3a9b5dafcd2754@mail.gmail.com>
References: <f6f643a20810101613n31d52079mec3a9b5dafcd2754@mail.gmail.com>
Message-ID: <1223751524-sup-6156@entry>

Reformatted excerpts from Matthew Wilson's message of 2008-10-10:
> So, after I create a release, how can I remove it, if I decide I'm not
> going to do that release?

There's no drop-release command (though that's a good idea). You can
edit project.yaml directly and just remove the relevant YAML block.
-- 
William <wmorgan-ditz at masanjin.net>

From matt at tplus1.com  Sat Oct 11 15:44:43 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Sat, 11 Oct 2008 15:44:43 -0400
Subject: [ditz-talk] Comment on ditz-113
Message-ID: <f6f643a20810111244gff62fccoc957a811299b9e56@mail.gmail.com>

Is this the right way to add comments on issues?

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Ditz-issue-99b1878684a8bd55d1f06e70a9f2c4f6da257fd5.patch
Type: text/x-diff
Size: 1153 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20081011/67eb7713/attachment.bin>

From nicolas.pouillard at gmail.com  Sat Oct 11 15:45:30 2008
From: nicolas.pouillard at gmail.com (Nicolas Pouillard)
Date: Sat, 11 Oct 2008 21:45:30 +0200
Subject: [ditz-talk] Why add a comment when adding a new issue?
In-Reply-To: <1223670247-sup-2612@entry>
References: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
	<1223670247-sup-2612@entry>
Message-ID: <1223754312-sup-8772@ausone.local>

Excerpts from William Morgan's message of Fri Oct 10 22:27:22 +0200 2008:
> Reformatted excerpts from Matthew Wilson's message of 2008-10-10:
> > Is there a way to configure ditz so that it doesn't ask me for a
> > comment during issue creation?
> 
> I don't want too much configuration. I'd rather disable it entirely for
> add, since I also don't use it. Any strong objections to that?

That's fine for me.

-- 
Nicolas Pouillard aka Ertai

From xbenlau at gmail.com  Sat Oct 11 23:14:11 2008
From: xbenlau at gmail.com (Ben Lau)
Date: Sun, 12 Oct 2008 11:14:11 +0800
Subject: [ditz-talk] Why add a comment when adding a new issue?
In-Reply-To: <1223754312-sup-8772@ausone.local>
References: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
	<1223670247-sup-2612@entry> <1223754312-sup-8772@ausone.local>
Message-ID: <f9a7555e0810112014u4ac21779x4575b98f3f27f04c@mail.gmail.com>

On Sun, Oct 12, 2008 at 3:45 AM, Nicolas Pouillard
<nicolas.pouillard at gmail.com> wrote:
> Excerpts from William Morgan's message of Fri Oct 10 22:27:22 +0200 2008:
>> Reformatted excerpts from Matthew Wilson's message of 2008-10-10:
>> > Is there a way to configure ditz so that it doesn't ask me for a
>> > comment during issue creation?
>>
>> I don't want too much configuration. I'd rather disable it entirely for
>> add, since I also don't use it. Any strong objections to that?
>
> That's fine for me.

+1

From wmorgan-ditz at masanjin.net  Mon Oct 13 13:37:49 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Mon, 13 Oct 2008 10:37:49 -0700
Subject: [ditz-talk] Why add a comment when adding a new issue?
In-Reply-To: <f9a7555e0810112014u4ac21779x4575b98f3f27f04c@mail.gmail.com>
References: <f6f643a20810100823y53d55b21h38d5fe5c7258398d@mail.gmail.com>
	<1223670247-sup-2612@entry> <1223754312-sup-8772@ausone.local>
	<f9a7555e0810112014u4ac21779x4575b98f3f27f04c@mail.gmail.com>
Message-ID: <1223919271-sup-2635@entry>

I've created issue c4b03e19.
-- 
William <wmorgan-ditz at masanjin.net>

From wmorgan-ditz at masanjin.net  Mon Oct 13 13:54:02 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Mon, 13 Oct 2008 10:54:02 -0700
Subject: [ditz-talk] Comment on ditz-113
In-Reply-To: <f6f643a20810111244gff62fccoc957a811299b9e56@mail.gmail.com>
References: <f6f643a20810111244gff62fccoc957a811299b9e56@mail.gmail.com>
Message-ID: <1223920399-sup-5992@entry>

Reformatted excerpts from Matthew Wilson's message of 2008-10-11:
> Is this the right way to add comments on issues?

A patch or a merge request, at least until I get off my ass and set up a
sheila.
-- 
William <wmorgan-ditz at masanjin.net>

From xbenlau at gmail.com  Mon Oct 20 09:29:31 2008
From: xbenlau at gmail.com (Ben Lau)
Date: Mon, 20 Oct 2008 21:29:31 +0800
Subject: [ditz-talk] Simple Ditz GUI Frontend
Message-ID: <f9a7555e0810200629l7bf02553vac0822ce50915939@mail.gmail.com>

Hi,

I just wrote a very simple GUI frontend for Ditz. I call it Ditz
commander (v 0.1)

Features:
- Integrate HTML browser and terminal in a single UI window
- Short cut to ditz commands like "add" , "edit" , "comment" and "html"
- Auto determine the Issue ID of loading page for ditz commands like
"edit" and "comment". No need to copy & page issue ID from HTML page.

Prerequisites:
- python-vte  (Linux only?)
- python-gtk2
- python-gtkmozembed

Usage
$ Commander.py path_to_ditz_issue_repository

Screenshot:
http://picasaweb.google.com/xbenlau/Blog#5259216573926229058

Remarks:

- You may change the path of ditz issue repository after the program
launched by click the "Open" button.

- Why write in Python instead of Ruby?

I think Ditz is good but I don't know Ruby... and I need this kind of
GUI application. So I make this prototype. I don't mind if other takes
over the project and rewrite in Ruby.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Commander.py
Type: text/x-python
Size: 5465 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20081020/c98e5b48/attachment-0001.py>

From wmorgan-ditz at masanjin.net  Mon Oct 20 11:48:21 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Mon, 20 Oct 2008 08:48:21 -0700
Subject: [ditz-talk] Simple Ditz GUI Frontend
In-Reply-To: <f9a7555e0810200629l7bf02553vac0822ce50915939@mail.gmail.com>
References: <f9a7555e0810200629l7bf02553vac0822ce50915939@mail.gmail.com>
Message-ID: <1224517547-sup-2538@entry>

Reformatted excerpts from Ben Lau's message of 2008-10-20:
> I just wrote a very simple GUI frontend for Ditz. I call it Ditz
> commander (v 0.1)

Looks very cool.

> - Why write in Python instead of Ruby?
> 
> I think Ditz is good but I don't know Ruby... and I need this kind of
> GUI application. So I make this prototype. I don't mind if other takes
> over the project and rewrite in Ruby.

Seems like a perfectly fine choice to me.
-- 
William <wmorgan-ditz at masanjin.net>

From matt at tplus1.com  Mon Oct 20 12:04:46 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Mon, 20 Oct 2008 12:04:46 -0400
Subject: [ditz-talk] Simple Ditz GUI Frontend
In-Reply-To: <1224517547-sup-2538@entry>
References: <f9a7555e0810200629l7bf02553vac0822ce50915939@mail.gmail.com>
	<1224517547-sup-2538@entry>
Message-ID: <f6f643a20810200904h20edb5c5k2267dcf89247fe54@mail.gmail.com>

On Mon, Oct 20, 2008 at 11:48 AM, William Morgan
<wmorgan-ditz at masanjin.net> wrote:
> Reformatted excerpts from Ben Lau's message of 2008-10-20:
>> I just wrote a very simple GUI frontend for Ditz. I call it Ditz
>> commander (v 0.1)
>
> Looks very cool.
>
>> - Why write in Python instead of Ruby?
>>
>> I think Ditz is good but I don't know Ruby... and I need this kind of
>> GUI application. So I make this prototype. I don't mind if other takes
>> over the project and rewrite in Ruby.
>
> Seems like a perfectly fine choice to me.

Since ditz uses yaml, it seems like it should be possible for people
to use any language possible to write clients / plugins / extensions.

I've been experimenting with using python to parse the yaml files.  It
felt strange at first to use python to parse yaml tags named stuff
like !ditz.rubyforge.org,2008, but I got it to work eventually.  Once
I have something interesting, I'll post it to the list.

Am working on a view that shows claimed issues for every member of a team.

Does ditz need some kind of locking mechanism?  I might use the
command-line client in a terminal to start editing a file and then
forget about it, and then use some fancy gui to edit the same issue.

Sure, since I use git to track the ditz files, I could revert to the
beginning, but I would still probably end up wasting a little time.
Maybe something as simple as vim's .swp files would be good enough.

Matt

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com

From wmorgan-ditz at masanjin.net  Wed Oct 22 11:04:46 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Wed, 22 Oct 2008 08:04:46 -0700
Subject: [ditz-talk] Simple Ditz GUI Frontend
In-Reply-To: <f6f643a20810200904h20edb5c5k2267dcf89247fe54@mail.gmail.com>
References: <f9a7555e0810200629l7bf02553vac0822ce50915939@mail.gmail.com>
	<1224517547-sup-2538@entry>
	<f6f643a20810200904h20edb5c5k2267dcf89247fe54@mail.gmail.com>
Message-ID: <1224687474-sup-172@entry>

Reformatted excerpts from Matthew Wilson's message of 2008-10-20:
> Am working on a view that shows claimed issues for every member of a
> team.

Have you tried 'ditz claimed'?

> Does ditz need some kind of locking mechanism?  I might use the
> command-line client in a terminal to start editing a file and then
> forget about it, and then use some fancy gui to edit the same issue.

It might be better to just have 'ditz edit' check to make sure the
underlying issue file hasn't changed between reading it and writing it.
Most reasonable editors can detect when the file has changed underneath
them, so this would fix the other half of the potential overwrite
problem. (Since 'ditz edit' doesn't actually edit the file itself, but a
temp file containing portions of it, which it then translates to changed
on the original issue file.)
-- 
William <wmorgan-ditz at masanjin.net>

From xbenlau at gmail.com  Wed Oct 22 12:09:25 2008
From: xbenlau at gmail.com (Ben Lau)
Date: Thu, 23 Oct 2008 00:09:25 +0800
Subject: [ditz-talk] Simple Ditz GUI Frontend
In-Reply-To: <1224517547-sup-2538@entry>
References: <f9a7555e0810200629l7bf02553vac0822ce50915939@mail.gmail.com>
	<1224517547-sup-2538@entry>
Message-ID: <f9a7555e0810220909h42bd893fn33c20bf23057a151@mail.gmail.com>

On Mon, Oct 20, 2008 at 11:48 PM, William Morgan
<wmorgan-ditz at masanjin.net> wrote:
> Reformatted excerpts from Ben Lau's message of 2008-10-20:
>> I just wrote a very simple GUI frontend for Ditz. I call it Ditz
>> commander (v 0.1)
>
> Looks very cool.
>
>> - Why write in Python instead of Ruby?
>>
>> I think Ditz is good but I don't know Ruby... and I need this kind of
>> GUI application. So I make this prototype. I don't mind if other takes
>> over the project and rewrite in Ruby.
>
> Seems like a perfectly fine choice to me.

Great.

I have created a project page in Google Code and released v0.2

http://code.google.com/p/ditz-commander/

ChangeLog

Release 0.2

 * New executable name : ditz-commander
 * Implemented "Assign" , "Close" & "Start" command
 * Added quotes to the target path of "cd" command
 * Auto grab focus to terminal
 * Added setup.py for distutils

From wmorgan-ditz at masanjin.net  Sun Oct 26 22:05:45 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Sun, 26 Oct 2008 19:05:45 -0700
Subject: [ditz-talk] experimental sheila running
Message-ID: <1225072582-sup-4686@entry>

Hi ditzers,

I've finally gotten Sheila to the point where you can add issues and
comments, and they're autocommitted to a git repo.

Since it's now basically minimally functional, I'm going to run it for a
while and see how long it takes before I need to add CAPTCHA. :) So if
you have ditz issues or comments to add, you can try it at:
http://masanjin.net:9000.

Issues submitted via the web are added to a separate repo, and I'll pull
them in periodically into the mainline one.

If you want to run it yourself, you'll need the latest camping and my
sheila (on Github, not Gitorious):
http://github.com/wmorgan/sheila/tree/master
-- 
William <wmorgan-ditz at masanjin.net>

From ngty77 at gmail.com  Mon Oct 27 07:52:21 2008
From: ngty77 at gmail.com (Ng Tze Yang)
Date: Mon, 27 Oct 2008 19:52:21 +0800
Subject: [ditz-talk] Hyperlink for commit details
Message-ID: <4905AB75.1070602@gmail.com>

Hi Guys,

I've just started using ditz, and is using the plugin 'git'. i'm 
experiencing problem with getting the desired html for 'ditz commit' . I 
believe ditz is working fine, just that i've probably missed something.

Using an example from 
http://ditz.rubyforge.org/ditz/issue-2f1ba961b0945536b511a2b1cc00c5313359f099.html, 
under <COMMITS FOR THIS ISSUE>, we see:

"
  2008-07-29 00:38 GMT  William Morgan <wmorgan-ditz at ...>       add 
INSTALL with gem and non-gem install instructions [f0954fc]
  2008-07-29 00:19 GMT  William Morgan <wmorgan-ditz at ...>       ignore 
rubygems library if not found [5d1f52f]
  2008-07-29 00:18 GMT  William Morgan <wmorgan-ditz at ...>       added 
trollop library directly in lib/ [b73fa89]
  2008-07-29 00:18 GMT  William Morgan <wmorgan-ditz at ...>       added 
setup.rb for tarball installation [7f4f4ba]
"

At the end of each line, we have [...] which is a hyperlink to the 
details of the commit. How do we get [...] to become a hyperlink ?

TKS

--
http://ngty77.blogspot.com


From wmorgan-ditz at masanjin.net  Mon Oct 27 11:37:43 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Mon, 27 Oct 2008 08:37:43 -0700
Subject: [ditz-talk] Hyperlink for commit details
In-Reply-To: <4905AB75.1070602@gmail.com>
References: <4905AB75.1070602@gmail.com>
Message-ID: <1225121716-sup-9784@entry>

Reformatted excerpts from Ng Tze Yang's message of 2008-10-27:
> At the end of each line, we have [...] which is a hyperlink to the 
> details of the commit. How do we get [...] to become a hyperlink ?

It's a little hacky right now, but if you set these two configuration
variables in your .ditz-config, you'll get links: (shown here with the
values I use for ditz itself)

  git_commit_url_prefix: http://gitorious.org/projects/ditz/repos/mainline/commits/
  git_branch_url_prefix: http://gitorious.org/projects/ditz/repos/mainline/logs/

Hacky because the links are constructed by appending the commit id to
these prefixes, which works for Gitorious and Github, but probably not
for other things.
-- 
William <wmorgan-ditz at masanjin.net>

From wmorgan-ditz at masanjin.net  Mon Oct 27 11:40:13 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Mon, 27 Oct 2008 08:40:13 -0700
Subject: [ditz-talk] experimental sheila running
In-Reply-To: <1225072582-sup-4686@entry>
References: <1225072582-sup-4686@entry>
Message-ID: <1225121999-sup-2009@entry>

Reformatted excerpts from William Morgan's message of 2008-10-26:
> http://masanjin.net:9000.

Ok, now it's really up.
-- 
William <wmorgan-ditz at masanjin.net>

From matt at tplus1.com  Mon Oct 27 10:55:35 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Mon, 27 Oct 2008 10:55:35 -0400
Subject: [ditz-talk] Anyone else want ditz to auto-commit after make a new
	issue?
Message-ID: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>

I'm using git.  After I make a new ditz issue, I do this:

$ git add ditz/issue-12431234
$ git commit -m "Just added issue 12341234"

Since I do this *every single time* it seems like there oughtta be a better way.

Is there?

Is it possible to write a plugin to do this?

ditz is awesome, by the way.  It saves me a lot of time because I
don't use my mouse and browser to track issues.

Matt

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com

From nate at natemurray.com  Tue Oct 28 12:40:11 2008
From: nate at natemurray.com (Nate Murray)
Date: Tue, 28 Oct 2008 09:40:11 -0700
Subject: [ditz-talk] Anyone else want ditz to auto-commit after make a
	new issue?
In-Reply-To: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>
References: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>
Message-ID: <9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>

+1

additionally, i often keep my bugs in their own git repo, not part of
a bigger project.

On Mon, Oct 27, 2008 at 7:55 AM, Matthew Wilson <matt at tplus1.com> wrote:
> I'm using git.  After I make a new ditz issue, I do this:
>
> $ git add ditz/issue-12431234
> $ git commit -m "Just added issue 12341234"
>
> Since I do this *every single time* it seems like there oughtta be a better way.
>
> Is there?
>
> Is it possible to write a plugin to do this?
>
> ditz is awesome, by the way.  It saves me a lot of time because I
> don't use my mouse and browser to track issues.
>
> Matt
>
> --
> Matthew Wilson
> matt at tplus1.com
> http://tplus1.com
> _______________________________________________
> ditz-talk mailing list
> ditz-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ditz-talk
>

From nicolas.pouillard at gmail.com  Wed Oct 29 04:56:20 2008
From: nicolas.pouillard at gmail.com (Nicolas Pouillard)
Date: Wed, 29 Oct 2008 09:56:20 +0100
Subject: [ditz-talk] Anyone else want ditz to auto-commit after make a
	new issue?
In-Reply-To: <9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
References: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>
	<9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
Message-ID: <1225270550-sup-5462@ausone.inria.fr>

You can easily do that using hooks, see my attached file.

Excerpts from Nate Murray's message of Tue Oct 28 17:40:11 +0100 2008:
> +1
> 
> additionally, i often keep my bugs in their own git repo, not part of
> a bigger project.
> 
> On Mon, Oct 27, 2008 at 7:55 AM, Matthew Wilson <matt at tplus1.com> wrote:
> > I'm using git.  After I make a new ditz issue, I do this:
> >
> > $ git add ditz/issue-12431234
> > $ git commit -m "Just added issue 12341234"
> >
> > Since I do this *every single time* it seems like there oughtta be a better way.
> >
> > Is there?
> >
> > Is it possible to write a plugin to do this?
> >
> > ditz is awesome, by the way.  It saves me a lot of time because I
> > don't use my mouse and browser to track issues.
> >
> > Matt
> >
> > --
> > Matthew Wilson
> > matt at tplus1.com
> > http://tplus1.com
> > _______________________________________________
> > ditz-talk mailing list
> > ditz-talk at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/ditz-talk
> >

-- 
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ditz-SCM-hooks.rb
Type: application/octet-stream
Size: 1658 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20081029/7ca7b39f/attachment-0001.obj>

From xbenlau at gmail.com  Wed Oct 29 14:19:46 2008
From: xbenlau at gmail.com (Ben Lau)
Date: Thu, 30 Oct 2008 02:19:46 +0800
Subject: [ditz-talk] Simple Ditz GUI Frontend
In-Reply-To: <f9a7555e0810220909h42bd893fn33c20bf23057a151@mail.gmail.com>
References: <f9a7555e0810200629l7bf02553vac0822ce50915939@mail.gmail.com>
	<1224517547-sup-2538@entry>
	<f9a7555e0810220909h42bd893fn33c20bf23057a151@mail.gmail.com>
Message-ID: <f9a7555e0810291119y2660ad55r8ce455add855b1ff@mail.gmail.com>

On Thu, Oct 23, 2008 at 12:09 AM, Ben Lau <xbenlau at gmail.com> wrote:
> On Mon, Oct 20, 2008 at 11:48 PM, William Morgan
> <wmorgan-ditz at masanjin.net> wrote:
>> Reformatted excerpts from Ben Lau's message of 2008-10-20:
>>> I just wrote a very simple GUI frontend for Ditz. I call it Ditz
>>> commander (v 0.1)
>>
>> Looks very cool.
>>
>>> - Why write in Python instead of Ruby?
>>>
>>> I think Ditz is good but I don't know Ruby... and I need this kind of
>>> GUI application. So I make this prototype. I don't mind if other takes
>>> over the project and rewrite in Ruby.
>>
>> Seems like a perfectly fine choice to me.
>
> Great.
>
> I have created a project page in Google Code and released v0.2
>
> http://code.google.com/p/ditz-commander/
>
> ChangeLog
>
> Release 0.2
>
>  * New executable name : ditz-commander
>  * Implemented "Assign" , "Close" & "Start" command
>  * Added quotes to the target path of "cd" command
>  * Auto grab focus to terminal
>  * Added setup.py for distutils

Hi,

v0.3 is released!

http://code.google.com/p/ditz-commander/

Changelog:

    * Added new Tool buttons : Go back & Go forward
    * Added extra command list for non-common command
    * Implemented commands : "add-release" , "add-component" ,
"set-component" , "Unassign" , "Stop" , "Raw Edit"
    * Added "Recently opened folder" menu
    * Raw Edit Command - Launch $EDITOR (default is vim) and open raw issue file
    * Bug Fix - It is now able to handle relative path as input
argument of command "ditz-commander"
    * Change window title according to the current loading page

From matt at tplus1.com  Wed Oct 29 12:13:51 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Wed, 29 Oct 2008 12:13:51 -0400
Subject: [ditz-talk] Anyone else want ditz to auto-commit after make a
	new issue?
In-Reply-To: <1225270550-sup-5462@ausone.inria.fr>
References: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>
	<9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
	<1225270550-sup-5462@ausone.inria.fr>
Message-ID: <f6f643a20810290913o6cefe4ado231b58651ae440bf@mail.gmail.com>

Thanks!  I'll study that script.

Matt

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com

From matan.nassau at gmail.com  Tue Oct 28 17:37:19 2008
From: matan.nassau at gmail.com (Matan Nassau)
Date: Tue, 28 Oct 2008 17:37:19 -0400
Subject: [ditz-talk] Anyone else want ditz to auto-commit after make a
	new issue?
In-Reply-To: <9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
References: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>
	<9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
Message-ID: <2958d6390810281437v5d5c1baet4911a37aaaecdd7f@mail.gmail.com>

+1

i also think there must be a better way of +1ing a feature-request.

On Tue, Oct 28, 2008 at 12:40 PM, Nate Murray <nate at natemurray.com> wrote:
> +1
>
> additionally, i often keep my bugs in their own git repo, not part of
> a bigger project.
>
> On Mon, Oct 27, 2008 at 7:55 AM, Matthew Wilson <matt at tplus1.com> wrote:
>> I'm using git.  After I make a new ditz issue, I do this:
>>
>> $ git add ditz/issue-12431234
>> $ git commit -m "Just added issue 12341234"
>>
>> Since I do this *every single time* it seems like there oughtta be a better way.
>>
>> Is there?
>>
>> Is it possible to write a plugin to do this?
>>
>> ditz is awesome, by the way.  It saves me a lot of time because I
>> don't use my mouse and browser to track issues.
>>
>> Matt
>>
>> --
>> Matthew Wilson
>> matt at tplus1.com
>> http://tplus1.com
>> _______________________________________________
>> ditz-talk mailing list
>> ditz-talk at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ditz-talk
>>
> _______________________________________________
> ditz-talk mailing list
> ditz-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ditz-talk
>



-- 
Matan Nassau

From wmorgan-ditz at masanjin.net  Tue Oct 28 14:12:52 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Tue, 28 Oct 2008 11:12:52 -0700
Subject: [ditz-talk] Anyone else want ditz to auto-commit after make a
	new issue?
In-Reply-To: <9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
References: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>
	<9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
Message-ID: <1225217305-sup-3414@entry>

Weird, I didn't seem to get the original email.

On Mon, Oct 27, 2008 at 7:55 AM, Matthew Wilson <matt at tplus1.com> wrote:
> I'm using git.  After I make a new ditz issue, I do this:
>
> $ git add ditz/issue-12431234
> $ git commit -m "Just added issue 12341234"

Hooks! See http://hackety.org/2008/06/26/gitHooksForDitz.html.

You'll also want to add an update hook:

  Ditz::HookManager.on :after_update do |project, config, issues|
    issues.each do |issue|
      `git add #{issue.pathname}`
    end
  end
-- 
William <wmorgan-ditz at masanjin.net>

From martindemello at gmail.com  Wed Oct 29 21:57:41 2008
From: martindemello at gmail.com (Martin DeMello)
Date: Wed, 29 Oct 2008 18:57:41 -0700
Subject: [ditz-talk] ditz -h should mention ditz help
Message-ID: <f93a6bcc0810291857j4e9d050ai1fb3f78fe2164664@mail.gmail.com>

ditz should either have a ditz --commands that does the same thing as
ditz help, or ditz --help should mention ditz help; as it stands, man
ditz is empty, and there's no indication that ditz --help isn't all
the help there is.

martin

From matt at tplus1.com  Thu Oct 30 11:28:58 2008
From: matt at tplus1.com (Matthew Wilson)
Date: Thu, 30 Oct 2008 11:28:58 -0400
Subject: [ditz-talk] Does ditz need some kind of relational DB or searching
	/ indexing engine?
Message-ID: <f6f643a20810300828j37b76a24gf34eee4f88e7abdf@mail.gmail.com>

I've been using ditz for about a month now, and I have big pile of
ditz issues.  Now I want to search through them and organize them, and
I feel like I'm writing SQL queries except with long chains of greps
and pipes.

For example, I want to find all issues associated with a release that
are assigned to a particular employee, filtered to just the issues
that have a particular phrase in the description.

Another example is that I decided to rename a release from 3.5.1 to
"long-run".  Since all the issues use the release-name in their own
issue file, all the issues that were assigned to 3.5.1 were now
orphaned.

A local sqlite database might solve a lot of these problems, but maybe
there are other solutions as well, like just building index files.
Also, I think it might be nice to use something like UUID to make
unique identifiers for each issue, release, component, etc, and then
use those IDs for references between them.

Or if sqlite is no bueno, what about using one of those newfangled
document databases like couchdb for storing issues?

-- 
Matthew Wilson
matt at tplus1.com
http://tplus1.com

From nolan at thewordnerd.info  Thu Oct 30 18:56:55 2008
From: nolan at thewordnerd.info (Nolan Darilek)
Date: Thu, 30 Oct 2008 17:56:55 -0500
Subject: [ditz-talk] Does ditz need some kind of relational DB or
 searching / indexing engine?
In-Reply-To: <f6f643a20810300828j37b76a24gf34eee4f88e7abdf@mail.gmail.com>
References: <f6f643a20810300828j37b76a24gf34eee4f88e7abdf@mail.gmail.com>
Message-ID: <490A3BB7.5000808@thewordnerd.info>

I think that SQLite would be out of the question since it's a binary 
format, and Ditz needs to rely on textual mergingg for conflict-resolution.

I wonder, though, if something like http://stone.rubyforge.org would be 
a good fit? It provides a DM-like view onto a simple YAML datastore, 
supporting searching and such. For that matter, I think DM has a 
YAML-based storage layer that would likely accomplish the same thing.

This actually dovetails with a thought I've been having recently: 
RESTful Ditz. Instead of a bunch of commands, make the structure more 
REST-like. So you'd have "ditz issue add", "ditz release drop," etc. 
Then alias a few shortcuts, so "ditz add" and drop would reference 
issues, thus making the common case more quick. This would likely make 
it easy to spot gaps in command coverage, like the missing command to 
drop a release for instance. :)


On 10/30/2008 10:28 AM, Matthew Wilson wrote:
> I've been using ditz for about a month now, and I have big pile of
> ditz issues.  Now I want to search through them and organize them, and
> I feel like I'm writing SQL queries except with long chains of greps
> and pipes.
>
> For example, I want to find all issues associated with a release that
> are assigned to a particular employee, filtered to just the issues
> that have a particular phrase in the description.
>
> Another example is that I decided to rename a release from 3.5.1 to
> "long-run".  Since all the issues use the release-name in their own
> issue file, all the issues that were assigned to 3.5.1 were now
> orphaned.
>
> A local sqlite database might solve a lot of these problems, but maybe
> there are other solutions as well, like just building index files.
> Also, I think it might be nice to use something like UUID to make
> unique identifiers for each issue, release, component, etc, and then
> use those IDs for references between them.
>
> Or if sqlite is no bueno, what about using one of those newfangled
> document databases like couchdb for storing issues?
>
>    


From wmorgan-ditz at masanjin.net  Fri Oct 31 16:02:18 2008
From: wmorgan-ditz at masanjin.net (William Morgan)
Date: Fri, 31 Oct 2008 13:02:18 -0700
Subject: [ditz-talk] Anyone else want ditz to auto-commit after make a
	new issue?
In-Reply-To: <2958d6390810281437v5d5c1baet4911a37aaaecdd7f@mail.gmail.com>
References: <f6f643a20810270755w5071a9c7j8b94983e16dcf8d6@mail.gmail.com>
	<9c1993f20810280940u4a16c531oca310937270a375e@mail.gmail.com>
	<2958d6390810281437v5d5c1baet4911a37aaaecdd7f@mail.gmail.com>
Message-ID: <1225483200-sup-1500@entry>

Reformatted excerpts from Matan Nassau's message of 2008-10-28:
> i also think there must be a better way of +1ing a feature-request.

You can also comment on issues via Sheila.
-- 
William <wmorgan-ditz at masanjin.net>