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 cer

  • I once saw an early attempt fail, in large part because managers got their hands on the front-page and used it to post management screeds and exhortations (e.g., reminders for people to use meaningful contents when checking in files). Useful content got pushed off into the archives. It didn't take long before people decided it wasn't worth the trouble to even look.

    This was before there were well-developed blogging tools (and the expectations that developed along with them).

  • Not really a blog though some entries have a clear blog feel (a lot of us spend a lot of time meeting people abroad -- W3C, DVB, TV Anytime, MPEG, DAB, etc... -- and we add entries about those very bloggishly. A lot of the ongoing research stuff is there, lots of crackfueled ideas that are either progressively worked into specs (at which point they drop off the Wiki and turn into a pointer to a more manageable & multidevice XML document -- you want those specs on the Zaurus ;) or into "DON'T GO THERE

    --

    -- Robin Berjon [berjon.com]

  • I have integrated blosxom and bugzilla (and CVS too, although somewhat intermittedly) on one of our internal servers.

    We use it for some project tracking stuff like

    • releases to different servers
    • CVS commits (when I get loginfo to work with N different ways people connect to CVS)
    • Bugs fixed, and added
    • Interesting news and articles
    It has proved fairly useful so far, and I plan to automate a load more with some simple perl scripts.

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
  • We (still!) use the Wiki I talked about at the first YAPC for our project management. I'm looking at integrating it with RT or Bugzilla to make it simpler to do the problem tracking.