Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

jonasbn (1153)

  reversethis-{gro.napc} {ta} {nbsanoj}
AOL IM: BJonasN (Add Buddy, Send Message)

Perl Programmer located in Copenhagen, Denmark. Active member of Copenhagen Perl Mongers.

Author of:

  • Business::DK::CPR
  • Business::DK::CVR
  • Business::DK::PO
  • Business::OnlinePayment::CashCow
  • Date::Holidays
  • Date::Holidays::Abstract
  • Date::Holidays::Super
  • Date::Pregnancy
  • Games::Bingo
  • Games::Bingo::Bot
  • Games::Bingo::Print
  • Module::Info::File
  • Module::Template::Setup
  • Test::Timer

and maintainer of:

  • Tie::Tools
  • XML::Conf
  • Workflow

Journal of jonasbn (1153)

Wednesday June 25, 2008
03:03 AM


[ #36771 ]

The other night I was contacted by mst on IRC, I received a torrent of words, but I just leaned back and read on.

My journal entry entitled "Burden of Proof", had upset a few people.

I had offended the person (bricas) whom had attempted to follow-up on the RT ticket and I was told my mst that I had been too hard on him.

So I told mst that I would apologize to him, I felt there was not reason to go into a discussion about this.

I contacted bricas right away and apologized, since it had never been my intent with the journal entry to offend anybody. We talked back and forth with bricas and I think we worked things out.

After this I sat back with a feeling that I had experienced this before and I had. Well the roles where just different. So I dug up a journal entry - where I had been offended on some comments on one of the CPAN modules I am maintaining.

I was somewhat ashamed and saddened by the fact that I had offended bricas and that I had actually been in bricas situation and had still been so stupid as to attack his efforts and work, when I knew what it felt like to be attacked like that.

My intent of the journal was actually to address the problem of head-less bug squishing and lacking test and the problem of not processing bug reports when fresh. But I had still gone after the messenger and this was never the intent but still a fact.

So an apology was in order, no question about that.

Yesterday bricas was so kind to inform me that the issue I originally had reported had been addressed and fixed.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I feel like we were able to work through whatever misunderstandings we had. I think it's easy to see that either side can feel invested in the issue and how a person can get upset if things aren't handled properly.

    I'm just really glad the bug has been resolved! :)