Re^4: Someone take control of Magnet.

[EvanCarroll]

in reply to Re^3: Someone take control of Magnet.
in thread Someone take control of Magnet.

Someone other than mst obviously owns the domain perl.org. Someone other than mst also has the right to remove him from ops on freenode. One capable individual that comes to mind is "thrig", one organization that comes to mind is http://www.perlfoundation.org/ or any release manager of perl5.

And, one of the things I expect to come out of this would be bogus nonsense claims of passive-aggressive forking -- like the claim you just made to cease. I'm banned from an official medium that can provide feedback, and my contributions are obstructed by one person's very personal desire to continue an age old vendetta. It isn't passive aggression: it is necessity:

1. I'm sick of making contributions where the official forum is infested with a moderator that keeps me klined, and shit talks about me behind my back.
2. I'm sick of not getting prompt feedback because I'm blocked to the official medium.

[zek152]

I'm sure that the logs are available. If you linked (or posted) enough context then we could better see your side of things. I personally give people the benefit of the doubt when they are not present to defend themselves when there is no real evidence provided.

As my friend would quote "Screenshot or it didn't happen?

[chromatic]

... one of the things I expect to come out of this would be bogus nonsense claims of passive-aggressive forking -- like the claim you just made to cease...

Libel is only libel if it's false. See MooseX::Types::DateTime::ButMaintained and, I quote:

When I want to contribute but I'm klinned from irc.perl.org, and #perl on irc.freenode.net you can just about expect me to fork.

As far as I care to tell, you submitted a patch, complained, had it applied within some six hours, and can't connect to IRC, so you've come to an unrelated forum to beg for someone else to revoke the server administration privileges of someone who owns one of the physical machines, and if it doesn't happen, you absolutely cannot be expected not to fork code, because six hours is just too long to wait for a patch to be applied.

I knew about none of this before, and I'm not impressed.

[EvanCarroll]

That's presumptuous and foolish, and wrong the patch that resulted in MooseX::Types::DateTime::ButMaintained was originally submited more than 4 months before the fork -- the truth must hurt.
• MooseX::Types::DateTime didn't remove DateTimeX::Easy until version 0.05, on 24 Aug 2009. The original patch was submitted 25 Mar 2009 a full FOUR MONTHS earlier.
• MooseX::Types::DateTime::ButMaintained on the other hand was released 05 April 2009 without the dependency for DateTimeX::Easy (making Date::Manip a non-requirement). It now also uses M::I the build system of most MooseX modules, and it also outs the database into the external Olson::* dist which other DateTimeX::Format modules use.
And, I don't understand what you're getting at, this quote is certainly not passively aggressive.

When I want to contribute but I'm klinned from irc.perl.org, and #perl on irc.freenode.net you can just about expect me to fork.

That's like saying if (a) I need to write to my grandma, and (b) if I'm out of paper, then (c) you can just about expect me to call. It is certainly not aggressive. I'm making an argument from necessity - if you don't view access to the official mediums of communication as a necessity then argue that. But, stop trying to confuse the readers with propaganda.

[chromatic]

... if you don't view access to the official mediums of communication as a necessity...

Without access to the so-called "official mediums of communication", you managed to submit a bug report, submit a patch, and get it applied within six hours. That seems fairly reasonable to me. Whining in an unrelated forum that the administrator of a server doesn't like you and won't let you use his service and thus you absolutely cannot accomplish what you want to do and it's his fault after all that you're forced to fork software, and isn't he a horrible person because forking is so bad is ... well, you don't think that's passive aggressive, but whatever it is, I find that argument silly.