Detailing my workflow

[Manoj Srivastava]

Hi,

        I have been meaning to write this up for a long time now, since
 I vaguely made a promise to do so last Debconf. I have also been
 wondering about the inefficiencies in my work-flow, but I kept
 postponing my analysis since there were still large gaps in my
 packaging automation since I moved off Arch as my SCM of
 choice. However, recently I have taken a sabbatical from Debian, so
 I've had time to complete bits and pieces of my package building
 framework, enough so that I could no longer justify putting off the
 analysis. I tried writing it up, but the result confused even me; so I
 instead recorded every shell command during a recent series of
 packaging tasks, and converted that into a nice, detailed, activity
 diagram that you see over here. This is as efficient a work-flow as I
 have been able to come up with.

   http://www.golden-gryphon.com/blog/manoj//blog/2009/02/25/A_day_in_the_life_of_a_Debian_hacker/

        Along with a git commit hook script, that parses the commit log
 and adds pending tags to bugs closed in the commit, the figure above
 represents my complete work-flow -- down to the details of every /cd/
 command I executed. I think there are too many steps still.

        Feedback and commentary would be appreciated, as well as any 
 suggestions to improve efficiency.

        manoj

ps: I updated http://vcs-pkg.org/index.html to add a link to this blog
    post. I must figure out how to enable comments on my blog
-- 
An optimist is a man who looks forward to marriage. A pessimist is a
married optimist.
Manoj Srivastava <srivasta at acm.org> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C