<div dir="ltr">Proposal A</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><table cellspacing="0" cellpadding="0" width="410" style="font-family:'Times New Roman'"><tbody><tr><td colspan="2"><p style="font-family:Arial;font-size:12px;line-height:20px;margin:0px;color:rgb(45,92,136)"><strong>Martin Renvoize</strong></p></td></tr><tr><td colspan="2"><p style="font-family:Arial;font-size:12px;line-height:20px;margin:0px;color:rgb(45,92,136)">Development Manager</p></td></tr><tr><td colspan="2"><p style="font-family:Arial;margin:0px"><br></p></td></tr><tr><td colspan="2"><p style="font-family:Arial;margin:0px"> </p></td></tr><tr><td><p style="font-family:Arial;font-size:12px;line-height:20px;margin:0px;color:rgb(45,92,136)"><strong>T:</strong> +44 (0) 1483 378728</p></td></tr><tr><td><p style="font-family:Arial;font-size:12px;line-height:20px;margin:0px;color:rgb(45,92,136)"><strong>F:</strong> +44 (0) 800 756 6384</p></td></tr><tr><td><p style="font-family:Arial;font-size:12px;line-height:20px;margin:0px;color:rgb(45,92,136)"><strong>E:</strong> <a href="mailto:martin.renvoize@ptfs-europe.com" style="color:rgb(45,92,136);text-decoration:none" target="_blank">martin.renvoize@ptfs-europe.com</a></p></td></tr><tr><td><p style="font-family:Arial;font-size:12px;line-height:20px;margin:0px;color:rgb(45,92,136)"><a href="https://www.ptfs-europe.com" style="color:rgb(45,92,136);text-decoration:none" target="_blank">www.ptfs-europe.com</a></p></td></tr><tr><td><p style="font-family:Arial;margin:0px"> </p></td></tr><tr><td colspan="2"><p style="line-height:20px;margin:0px"><a href="https://www.ptfs-europe.com" border="0" target="_blank"><img src="https://www.ptfs-europe.com/wp-content/uploads/2014/09/ptfs_logo1.png" width="" height="" border="0"></a></p></td></tr><tr><td><p style="font-family:Arial;margin:0px"><br></p></td></tr><tr><td><p style="font-family:Arial;margin:0px"><br></p></td></tr></tbody></table><table cellspacing="0" cellpadding="0" style="font-family:'Times New Roman';border-top-width:1px;border-top-style:solid;border-top-color:rgb(194,194,194);padding:20px 0px 0px;margin:0px"><tbody><tr><td><p style="font-family:Arial;font-size:12px;color:rgb(45,92,136);margin:0px">Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30</p><br><p style="font-family:Arial;font-size:12px;color:rgb(45,92,136);margin:0px">The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at <a href="mailto:info@ptfs-europe.com" target="_blank">info@ptfs-europe.com</a></p></td></tr></tbody></table><span style="font-size:12.8px"><br></span></div></div><div dir="ltr"></div></div></div></div></div>
<br><div class="gmail_quote">On 5 December 2016 at 16:44, Sam <span dir="ltr"><<a href="mailto:perl@net153.net" target="_blank">perl@net153.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Proposal A<div><div class="h5"><br>
<br>
On 12/05/2016 12:15 AM, David Golden wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Thank you to everyone who has been participating in or just reading the<br>
various governance discussions since my initial email to the DBIC list<br>
of Oct 3. [1]<br>
<br>
It's time to bring this to a conclusion.<br>
<br>
Peter suggests that the question to consider is merely which fork gets<br>
the "DBIx::Class" namespace indexed on CPAN. While that may be all he<br>
cares about, I feel it trivializes the discussions the community has<br>
been having and the decision the community is being asked to make.<br>
<br>
Without restating all the history to date, here are the facts of the<br>
case that I think are most relevant to consider in understanding the<br>
proposals at hand:<br>
<br>
* Peter's original plan that started the dispute could be summarized as<br>
"Peter takes sole control of the DBIx::Class namespace and does X",<br>
where at that time the plan appeared to be "freeze and park permissions<br>
with an unknown owner".<br>
<br>
* The dispute process clearly indicated that Peter didn't have the<br>
support of existing maintainers or the community for such a plan<br>
sufficient to disregard his prior permissions agreement with Matt.<br>
<br>
* Matt proposed a mechanism for the community to self-govern the DBIC<br>
namespace and development, sharing power between maintainers and the<br>
mailing list. (Revised proposal is linked as [2])<br>
<br>
* Peter revealed that his new employment situation allows him to<br>
continue development. [3]<br>
<br>
* Given Peter's track record and renewed availability, some in the<br>
community wanted to see an alternative proposal where Peter continued<br>
DBIC and the community took forward "DBIC2"; Andrew Beverl formalized a<br>
proposal [4]. In response to concerns about the proposal, Peter<br>
volunteered to clarify the alternative proposal.<br>
<br>
* Peter delivered an alternative proposal that could be summarized as<br>
"Peter takes sole control of the DBIx::Class namespace and does X",<br>
where at this time the plan appears to be "kickstart a DBIx::Class fork<br>
free of community bias". [5]<br>
<br>
Unfortunately for the community's deliberations, Peter has consistently<br>
provided minimal details on his plans, particularly regarding succession<br>
should he no longer be able to or wish to continue development. After<br>
Andrew Beverl's proposal, Peter said he would clarify by Nov 1 [6].<br>
This target date then slipped to Nov 5 [7], was pushed back again on Nov<br>
7 [8], and pushed again to Nov 17 or else Thanksgiving [9]. On November<br>
10, in the middle of this sequence of delays, I started a private email<br>
thread with Peter asking if there was anything I could do to help him<br>
formalize his proposal, but the thread stalled on the Nov 14. On<br>
November 26, I received a separate private email telling me I could set<br>
a deadline of Dec 1, if needed [10]. In our continuation of the stalled<br>
thread at that point, Peter and I briefly discussed what ultimately<br>
became his final proposal of Dec 3.<br>
<br>
I think some details in those private emails are relevant to the<br>
decisions at hand, so now that Peter has released his proposal and<br>
because Peter originally insisted that all discussions about DBIC be<br>
public anyway, I am now posting the content of that private email thread<br>
in full. [11]<br>
<br>
Specifically, I want to call attention to Peter's description of the<br>
future of DBIC as "two forks developed in parallel, by noncooperating,<br>
openly adversarial teams" which I think is more indicative of the stakes<br>
and situation than the simpler question of "where does the DBIx::Class<br>
namespace point". What an adversarial fork means for the future of the<br>
repository, mailing list, bug trackers, module ecosystem, and community<br>
itself, etc. is undefined and community members may wish to consider<br>
that in their decision process.<br>
<br>
Given Peter's stated intent to launch a "fork free of community bias",<br>
it's clear there is no governance alternative for the community on the<br>
table. Matt's original proposal had enough support to be adopted<br>
outright [12], has been amended with generally good feedback, and has<br>
provisions for future self amendment. I consider it operative in its<br>
amended form as soon as this vote is concluded, with the only missing<br>
piece being what specific namespaces it governs.<br>
<br>
The question thus comes down to whether the community feels "official"<br>
DBIC is best developed going forward by a self-governed community or by<br>
a single individual with absolute control (with both the good and ill<br>
that comes of that). The community may wish to consider the track<br>
record and personalities of everyone involved for both scenarios in<br>
weighing a decision.<br>
<br>
As there has been more than enough time spent on these topics and/or<br>
waiting for clarification already, and since the options on the table<br>
aren't materially altered from their earlier forms, I don't believe<br>
further discussion, debate or new alternatives will provide better or<br>
clearer options for the future of DBIC. It is time for this dispute to<br>
be resolved so everyone can move forward.<br>
<br>
Therefore, I submit to the list the following two proposals:<br>
<br>
* PROPOSAL A: Primary permissions for DBIx::Class and related namespaces<br>
shall be managed under the amended DBIC community governance structure<br>
proposed by Matt Trout. Decisions about the future development of the<br>
project, including but not limited to stability policy, new development,<br>
branching and freezing shall be governed by the community under the same<br>
terms. The community will choose whether/how to continue active<br>
development of DBIC under that name or a separate name. Peter will<br>
choose whether/how to fork DBIC to a new namespace for independent<br>
development.<br>
<br>
* PROPOSAL B: Primary permissions for DBIx::Class and related namespaces<br>
shall be managed solely by Peter Ribasushi until he transfers it to<br>
another of his choosing or appears permanently incommunicado (whether by<br>
choice, accident or death). Decisions about the future development of<br>
the project, including but not limited to stability policy, new<br>
development, branching and freezing shall be made at Peter's sole<br>
discretion. Peter will choose whether/how to continue active<br>
development of DBIC under that or a separate name. The community, under<br>
the governance proposal, will choose whether/how to fork DBIC to a new<br>
namespace for independent development.<br>
<br>
List members should reply to this email with an email body indicating<br>
clearly "Proposal A" or "Proposal B". Other responses, such as "+1" or<br>
"me, too" replies to others' votes will be disregarded.<br>
<br>
Voting will close 72 hours after this email is sent.<br>
<br>
I will tally and announce results shortly thereafter. I will be sole<br>
arbiter of any voting irregularities. Once announced, I will transfer<br>
namespace permissions accordingly and consider the matter resolved.<br>
<br>
Regards,<br>
David<br>
<br>
[1]<br>
<a href="http://dbix-class.35028.n2.nabble.com/IMPORTANT-A-discussion-of-DBIC-governance-and-future-development-td7578987.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/IMPORTANT-A-discussion<wbr>-of-DBIC-governance-and-<wbr>future-development-td7578987.<wbr>html</a><br>
[2]<br>
<a href="http://dbix-class.35028.n2.nabble.com/PROPOSAL-Governance-and-sustainability-td7579228.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/PROPOSAL-Governance-<wbr>and-sustainability-td7579228.<wbr>html</a><br>
[3]<br>
<a href="http://dbix-class.35028.n2.nabble.com/IMPORTANT-A-discussion-of-DBIC-governance-and-future-development-tp7578987p7579158.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/IMPORTANT-A-discussion<wbr>-of-DBIC-governance-and-<wbr>future-development-tp7578987p7<wbr>579158.html</a><br>
[4]<br>
<a href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579175.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/GOVERNANCE-Aggregation<wbr>-and-conclusion-tp7579168p7579<wbr>175.html</a><br>
[5]<br>
<a href="http://dbix-class.35028.n2.nabble.com/Decision-time-which-fork-inherits-the-existing-DBIx-Class-namespace-tp7579255.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/Decision-time-which-<wbr>fork-inherits-the-existing-<wbr>DBIx-Class-namespace-tp7579255<wbr>.html</a><br>
[6]<br>
<a href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579184.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/GOVERNANCE-Aggregation<wbr>-and-conclusion-tp7579168p7579<wbr>184.html</a><br>
[7]<br>
<a href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579208.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/GOVERNANCE-Aggregation<wbr>-and-conclusion-tp7579168p7579<wbr>208.html</a><br>
[8]<br>
<a href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579225.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/GOVERNANCE-Aggregation<wbr>-and-conclusion-tp7579168p7579<wbr>225.html</a><br>
[9]<br>
<a href="http://dbix-class.35028.n2.nabble.com/An-answer-and-a-question-tp7579248p7579250.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/An-answer-and-a-questi<wbr>on-tp7579248p7579250.html</a><br>
[10] <a href="https://gist.github.com/xdg/836e6341b757df8b67cf26f02b6899d6" rel="noreferrer" target="_blank">https://gist.github.com/xdg/83<wbr>6e6341b757df8b67cf26f02b6899d6</a><br>
[11] <a href="https://gist.github.com/xdg/955519bee08658f9b60c6219a51fd0dd" rel="noreferrer" target="_blank">https://gist.github.com/xdg/95<wbr>5519bee08658f9b60c6219a51fd0dd</a><br>
[12]<br>
<a href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-td7579168.html" rel="noreferrer" target="_blank">http://dbix-class.35028.n2.nab<wbr>ble.com/GOVERNANCE-Aggregation<wbr>-and-conclusion-td7579168.html</a><br>
<br>
--<br></div></div>
David Golden <<a href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a> <mailto:<a href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a>>> Twitter/IRC/GitHub: @xdg<span class=""><br>
<br>
<br>
______________________________<wbr>_________________<br>
List: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class" rel="noreferrer" target="_blank">http://lists.scsys.co.uk/cgi-b<wbr>in/mailman/listinfo/dbix-class</a><br>
IRC: <a href="http://irc.perl.org#dbix-class" rel="noreferrer" target="_blank">irc.perl.org#dbix-class</a><br>
SVN: <a href="http://dev.catalyst.perl.org/repos/bast/DBIx-Class/" rel="noreferrer" target="_blank">http://dev.catalyst.perl.org/r<wbr>epos/bast/DBIx-Class/</a><br>
Searchable Archive: <a href="http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk" rel="noreferrer" target="_blank">http://www.grokbase.com/group/<wbr>dbix-class@lists.scsys.co.uk</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<wbr>_________________<br>
List: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class" rel="noreferrer" target="_blank">http://lists.scsys.co.uk/cgi-b<wbr>in/mailman/listinfo/dbix-class</a><br>
IRC: <a href="http://irc.perl.org#dbix-class" rel="noreferrer" target="_blank">irc.perl.org#dbix-class</a><br>
SVN: <a href="http://dev.catalyst.perl.org/repos/bast/DBIx-Class/" rel="noreferrer" target="_blank">http://dev.catalyst.perl.org/r<wbr>epos/bast/DBIx-Class/</a><br>
Searchable Archive: <a href="http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk" rel="noreferrer" target="_blank">http://www.grokbase.com/group/<wbr>dbix-class@lists.scsys.co.uk</a><br>
</div></div></blockquote></div><br></div>