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

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.
  • ...and someone else is going to start up a new list...

    That someone is me. After some discussion with Tony, he's happy for me to run a new list. Sadly he's said that he doesn't feel able to participate but hopefully there will be enough of us around to help out, and be helped.

    Head over to [] to sign up.


  • So Tony unsubscribed him for a week to cool down.

    I made two rude comments and got temp-banned, no problem, but Tony never told me about it!
    The conversation i posted is really everything.
  • threatening legal action over something so trivial makes me think Tony is behaving like a bit of a dick. There *are* ways of banning people, even if his chosen mailing list software, just like the one I use, doesn't make it easy. For instance, configure the MTA to not communicate with particular servers or netblocks.
    • Yeah I sat there thinking I must be missing something. This bloke is threating legal action because he doesn't like the fact that someone keeps resubscribing to his mailing list? Oh good grief (/me rolls eyes).
  • I really thing the ball is in Sebastian's court to patch things up, if it's still possible. Swallow your pride and make things good again. This is for the good of the community. Gavin.
    Fancy a Just ask!!!
  • Reading the email archives I was reminded of something I saw happen before in another online community of which I was a member. We had a member who was enthusiastic, presumably well-intentioned, but stubborn, and he had an agenda that was not exactly the same as the community's. He thought he was always right, was repetitive, and always wanted to have the last word. In the end, this guy was kicked out. Luckily, it was not as easy to resubscribe, no one threatened to call the police and the community wasn't
  • in situations like this is the gradeschool teacher sends both children to the corner and denies recess for a week. Everyone wants to tattle and tell the teacher how Graham's code is closed or how Tony's an asshole all while maintaining an aura of innocence with a patina of self-righteous indignation without getting painted with the same bush. It doesn't work that way.
  • At this point Sebastian created a journal on use.perl to post up his side of the story.

    And what an eye-opener that turned out to be. Threatening legal action over something as insignificant as resubscribing to a mailing list struck me as being a little, er, bizarre.
  • The biggest issue I have with this whole thing is that the technical discussion that was occurring between Matt S Trout, Schwern, Perrin and a couple others was excellent. The insight that I gained by reading their discussion on multiple inheritance, delegation and plugins, I haven't been able to find anywhere else. By simply ignoring the mail from Sebastian and for the most part Tony I was able to focus on the technical discussion at hand.

    Unfortunately the list has been shutdown and the thread will not

    • I was sad to see it too. Unfortunately, there are real world consequences when people stop being civil and "raise their voices" on mailing lists. Politeness might seem like an antiquated notion to some people, but it is the thing that allows us to disagree without causing a body count, and when it goes out the window, things like this happen.
  • OK, I can understand Tony closing the mailing list. He was taking a fair amount of abuse on the list, and I can understand reaching the breaking point and calling it quits (i.e. closing the mailing list).

    But killing the CDBI Wiki? That just wasn't very cool. The vast majority of the content on the Wiki was created by the CDBI community, not by Tony. I sincerely hope Tony can be persuaded to either bring it back online or at least give the content to someone else for them to host. Has anyone looked into that
  • I note that Sebastian's journal has now been opened for comments.

    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • In these cases (we all ended up in one at least once in our online lives) there comes a point where the right solution is: UNPLUG. Forcibly, if necessary. But unplug it. Do not multiplicate blogs about this. A little bit is ok, but then eventually: UNPLUG.
      Someone has to be "virile" enough to accept of being right without the full recognition of his or her own right.

      Unplug it :-).

      Alberto []