Dirbuster

[ThatEidolon]

Another graphical tool; need to figure out how to document.

[WebBreacher]

How about for all graphical tools you: 1 - note they are graphical; 2 - note how they are launched?

[ThatEidolon]

That could work. The other thing I was thinking is include descriptions for the various sourceforge / github pages describing how the tool is used.

I will make a second pass with the graphical tools and close out the issues I am opening

[WebBreacher]

hey. instead of making another issue for each graphical tool, how about making 1 issue with them all?

[ThatEidolon]

Having separate issues allows for easier closing, as someone can come in
and fix one tool, and close one issue.

What might be a better way of tracking is to create milestone roll-up of
the graphical tools, and then create sub-milestones to track each
individual tool. This is similar to the way giga has each menu setup, and
allows for easy tracking.

On Sun, Apr 20, 2014 at 11:28 AM, WebBreacher [email protected]:

hey. instead of making another issue for each graphical tool, how about
making 1 issue with them all?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/69#issuecomment-40897170
.