Subj : Re: Tools for software-developement
To   : comp.programming
From : Phlip
Date : Sat Oct 08 2005 03:44 pm

Christof Köhler wrote:

> Phlip schrieb:
>
>> Google wiki.
>
> I don't think that a programmer only uses a wiki.
>
> But i thought you could give me some names of working solutions you have
> heared about or that you are using yourself.

Not sure if you will pride honesty, but I'm using a wiki. Maybe we need 
more; I don't know yet.

I also just installed Doxygen, but I only use it so far to link out from my 
wiki. For example, I configure my wiki to format a RemoteLink of DoxyGen to 
point into the DoxyGen web site, and then I

The rules here are "start simple" and "travel light". I have seen teams use 
 >deep breath< DevTrack (issue tickets), AlienBrain (content version 
control), Perforce (source version control), OpenWiki (knowledge base), and 
an extensive in-house tools system.

The hand-made tools put daily builds onto a build farm, and uploaded their 
results into new pages in OpenWiki. Of course nobody read those, but of 
course the effort of doing it rewarded everyone with more control over the 
build tools. You could stop and start a build remotely, for example.

When a team starts by adding all those tools up front, I wonder if they 
missed opportunities to simplify by leaving out some. (AlienBrain and 
Perforce were widely regarded as redundant, and DevTrack was very 
user-hostile, for example.) So if a team starts with very few tools and adds 
them at need, they might right-size their tool chain.

I said "Google wiki", not "use a wiki".

-- 
  Phlip
  http://www.greencheese.org/ZeekLand  <-- NOT a blog!!!

.