Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • We're using elogs [sourceforge.net] Logbooks to keep stream-of-consciousness work notes.

    We share contacts, project approaches, problem fixes, development ideas, etc. etc. All in a system that is very very simple and easy to maintain.

    We can attach emails (or various documents) to our notes, which are uploaded through a standard file dialog to give additional context. The logbooks are fully searchable.

    We're supposed to use a Monstrous Problem Ticket/Change Request system for this, but sheesh, it would take at a minimum 3

    • Very interesting! Thanks for sharing this. How many people are collaborating this way? Are you all in the same building?

      --Nat

      • Like I said, we're a small group.

        The 'pilot' is 2 people. We have adjoining cubicles. There is me and an associate who just started late last year, I've been here almost 5 years. I'm the the more experienced worker, not just here, but overall.

        There's a lot to learn on this job. We do 2nd level help desk support troubleshooting for our customer base and development. My associate is trying to learn the ropes, but there's so much work to do that we can't work together on everything. He's taken over certain tasks that the guy he replaced was primarily responsible for, which keeps him busy.

        So, I thought that if we documented all the tasks we do in a log like this, along with our approaches, we could look over each other
        's shoulders virtually. This allows us to work on dual paths and also benefit from reviewing each others work in a convenient time-shifted fashion. I could review what he's doing to offer up my experience and he can review what I'm doing to get up to speed on those tasks that I perform.

        The original logs involve the tasks of 2 people, but we're letting management in on it too. They'll be able to read and offer perspectives, as necessary.

        Others in our larger group are interested in this trial and we may open this concept up in the future. If we do, I envision a group of 7 all sharing logs. eLog support separate logbooks served from the same server and I'm thinking making several logbooks that serve various overlapping groups share. Then, there is a larger group that involves an addition 5 people who are 2000 miles away.

        One concern is that if top management finds out and realizes that we aren't using THE BIG PROBLEM TRACKING/CHANGE CONTROL TOOL that they'll stop us and make us use that instead. So, we're keeping it pretty quiet.

        Well! I'm just posting it to the Internet! I'm fairly confident that nobody here reads use.perl.org... Except me!