<div dir="ltr">On Tue, Oct 11, 2016 at 1:23 PM, Peter Rabbitson <span dir="ltr"><<a href="mailto:rabbit+dbic@rabbit.us" target="_blank">rabbit+dbic@rabbit.us</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/09/2016 06:35 AM, David Golden wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Further, Peter's prior agreement with Matt at the time of the initial<br>
transfer calls into question whether Peter can, in fact, claim an<br>
exclusive, unilateral privilege to name a successor.<br>
</blockquote>
<br>
David, to use your own language from <a href="mailto:modules@perl.org" target="_blank">modules@perl.org</a>[1]:<br>
<br>
> Saying it repeatedly will not make it true.<br>
<br></blockquote><div><br></div><div>Note: "calls into question" means there is an unresolved question. You may believe there is no question, but the consensus of PAUSE administrators is that there is. This is true by construction. As soon as we wonder what the right outcome is, the question has been called.<br><br>Specifically, we didn't think this situation was clear cut for *either* side, which is why we wanted discussion among affected parties to inform the outcome rather than deciding peremptorily in favor of either party in the dispute.<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I presented ample evidence to supports my claim, culminating with the following exchange[2] on 2015-12-07 (which *was* also mentioned in [3]):<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">[snip]<br><div>
mst_20151208.log:[16:44:55] <mst> so, basically "giving warning would stop it being the not-orderly thing you have in mind, but while you're trying to make a splash, you're going to do so without causing carnage" or so?<br>
mst_20151208.log:[16:45:31] <ribasushi> I promise you no carnage.<br></div></blockquote></blockquote><div><br></div><div>Speaking personally, I read that entire exchange in the context of your post about leaving CPAN entirely and thus about *all* your modules, not DBIC specifically. Again, speaking personally, I consider kicking out all co-maintainers a form of "carnage". So I don't see in that exchange any sort of prior approval for the course of action you appear to have intended.<br><br>I think it's unfortunate that you didn't feel you could be more open about your intentions earlier as much misunderstanding would have been avoided.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div></div></blockquote>In other words, to make it as clear as possible: the PAUSE admins' taking a side in mst's 11th-hour scramble for relevance placed in limbo the following:<br>
<br>
~/devel/dbic$ git diff -C -w --shortstat 6a0bca69f dc7d89911<br>
516 files changed, 13941 insertions(+), 4547 deletions(-)<br>
<br></blockquote><div><br></div><div>That sounds like a threat. Is that what you intended?<br></div><div><br></div><div>Regards,<br></div><div>David<br><br></div></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>David Golden <<a href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a>> Twitter/IRC/GitHub: @xdg</div></div></div></div></div>
</div></div>