<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Proposal A<br>
</p>
<br>
<div class="moz-cite-prefix">On 05/12/16 06:15, David Golden wrote:<br>
</div>
<blockquote
cite="mid:CAOeq1c9CTnuc2Q1=ez-cAudUFEJWwsE2AcJ+8b+=p7M7--tgtg@mail.gmail.com"
type="cite">
<div dir="ltr">Thank you to everyone who has been participating in
or just reading the various governance discussions since my
initial email to the DBIC list of Oct 3. [1]<br clear="all">
<div><br>
</div>
<div>It's time to bring this to a conclusion.<br>
<br>
</div>
<div>Peter suggests that the question to consider is merely
which fork gets the "DBIx::Class" namespace indexed on CPAN.
While that may be all he cares about, I feel it trivializes
the discussions the community has been having and the decision
the community is being asked to make.<br>
<br>
</div>
<div>Without restating all the history to date, here are the
facts of the case that I think are most relevant to consider
in understanding the proposals at hand:<br>
<br>
</div>
<div>* Peter's original plan that started the dispute could be
summarized as "Peter takes sole control of the DBIx::Class
namespace and does X", where at that time the plan appeared to
be "freeze and park permissions with an unknown owner".<br>
<br>
</div>
<div>* The dispute process clearly indicated that Peter didn't
have the support of existing maintainers or the community for
such a plan sufficient to disregard his prior permissions
agreement with Matt.<br>
</div>
<div><br>
* Matt proposed a mechanism for the community to self-govern
the DBIC namespace and development, sharing power between
maintainers and the mailing list. (Revised proposal is linked
as [2])<br>
</div>
<div><br>
* Peter revealed that his new employment situation allows him
to continue development. [3]<br>
</div>
<div><br>
* Given Peter's track record and renewed availability, some in
the community wanted to see an alternative proposal where
Peter continued DBIC and the community took forward "DBIC2";
Andrew Beverl formalized a proposal [4]. In response to
concerns about the proposal, Peter volunteered to clarify the
alternative proposal.<br>
</div>
<div><br>
</div>
<div>* Peter delivered an alternative proposal that could be
summarized as "Peter takes sole control of the DBIx::Class
namespace and does X", where at this time the plan appears to
be "kickstart a DBIx::Class fork free of community bias". [5]<br>
</div>
<div><br>
</div>
<div>Unfortunately for the community's deliberations, Peter has
consistently provided minimal details on his plans,
particularly regarding succession should he no longer be able
to or wish to continue development. After Andrew Beverl's
proposal, Peter said he would clarify by Nov 1 [6]. This
target date then slipped to Nov 5 [7], was pushed back again
on Nov 7 [8], and pushed again to Nov 17 or else Thanksgiving
[9]. On November 10, in the middle of this sequence of
delays, I started a private email thread with Peter asking if
there was anything I could do to help him formalize his
proposal, but the thread stalled on the Nov 14. On November
26, I received a separate private email telling me I could set
a deadline of Dec 1, if needed [10]. In our continuation of
the stalled thread at that point, Peter and I briefly
discussed what ultimately became his final proposal of Dec 3.<br>
<br>
</div>
<div>I think some details in those private emails are relevant
to the decisions at hand, so now that Peter has released his
proposal and because Peter originally insisted that all
discussions about DBIC be public anyway, I am now posting the
content of that private email thread in full. [11]<br>
</div>
<div><br>
Specifically, I want to call attention to Peter's description
of the future of DBIC as "two forks developed in parallel, by
noncooperating, openly adversarial teams" which I think is
more indicative of the stakes and situation than the simpler
question of "where does the DBIx::Class namespace point".
What an adversarial fork means for the future of the
repository, mailing list, bug trackers, module ecosystem, and
community itself, etc. is undefined and community members may
wish to consider that in their decision process.<br>
<br>
</div>
<div>Given Peter's stated intent to launch a "fork free of
community bias", it's clear there is no governance alternative
for the community on the table. Matt's original proposal had
enough support to be adopted outright [12], has been amended
with generally good feedback, and has provisions for future
self amendment. I consider it operative in its amended form
as soon as this vote is concluded, with the only missing piece
being what specific namespaces it governs.</div>
<div><br>
</div>
<div>The question thus comes down to whether the community feels
"official" DBIC is best developed going forward by a
self-governed community or by a single individual with
absolute control (with both the good and ill that comes of
that). The community may wish to consider the track record
and personalities of everyone involved for both scenarios in
weighing a decision.<br>
<br>
As there has been more than enough time spent on these topics
and/or waiting for clarification already, and since the
options on the table aren't materially altered from their
earlier forms, I don't believe further discussion, debate or
new alternatives will provide better or clearer options for
the future of DBIC. It is time for this dispute to be
resolved so everyone can move forward.<br>
<br>
</div>
<div>Therefore, I submit to the list the following two
proposals:<br>
<br>
</div>
<div>* PROPOSAL A: Primary permissions for DBIx::Class and
related namespaces shall be managed under the amended DBIC
community governance structure proposed by Matt Trout.
Decisions about the future development of the project,
including but not limited to stability policy, new
development, branching and freezing shall be governed by the
community under the same terms. The community will choose
whether/how to continue active development of DBIC under that
name or a separate name. Peter will choose whether/how to
fork DBIC to a new namespace for independent development.<br>
</div>
<div><br>
</div>
<div>* PROPOSAL B: Primary permissions for DBIx::Class and
related namespaces shall be managed solely by Peter Ribasushi
until he transfers it to another of his choosing or appears
permanently incommunicado (whether by choice, accident or
death). Decisions about the future development of the
project, including but not limited to stability policy, new
development, branching and freezing shall be made at Peter's
sole discretion. Peter will choose whether/how to continue
active development of DBIC under that or a separate name. The
community, under the governance proposal, will choose
whether/how to fork DBIC to a new namespace for independent
development.<br>
<br>
</div>
<div>List members should reply to this email with an email body
indicating clearly "Proposal A" or "Proposal B". Other
responses, such as "+1" or "me, too" replies to others' votes
will be disregarded.<br>
<br>
</div>
<div>Voting will close 72 hours after this email is sent.<br>
<br>
I will tally and announce results shortly thereafter. I will
be sole arbiter of any voting irregularities. Once announced,
I will transfer namespace permissions accordingly and consider
the matter resolved.<br>
<br>
</div>
<div>Regards,<br>
</div>
<div>David<br>
</div>
<div><br>
[1] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/IMPORTANT-A-discussion-of-DBIC-governance-and-future-development-td7578987.html">http://dbix-class.35028.n2.nabble.com/IMPORTANT-A-discussion-of-DBIC-governance-and-future-development-td7578987.html</a><br>
[2] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/PROPOSAL-Governance-and-sustainability-td7579228.html">http://dbix-class.35028.n2.nabble.com/PROPOSAL-Governance-and-sustainability-td7579228.html</a><br>
<div>[3] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/IMPORTANT-A-discussion-of-DBIC-governance-and-future-development-tp7578987p7579158.html">http://dbix-class.35028.n2.nabble.com/IMPORTANT-A-discussion-of-DBIC-governance-and-future-development-tp7578987p7579158.html</a><br>
[4] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579175.html">http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579175.html</a><br>
</div>
[5] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/Decision-time-which-fork-inherits-the-existing-DBIx-Class-namespace-tp7579255.html">http://dbix-class.35028.n2.nabble.com/Decision-time-which-fork-inherits-the-existing-DBIx-Class-namespace-tp7579255.html</a><br>
[6] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579184.html">http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579184.html</a><br>
[7] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579208.html">http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579208.html</a><br>
[8] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579225.html">http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-tp7579168p7579225.html</a><br>
[9] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/An-answer-and-a-question-tp7579248p7579250.html">http://dbix-class.35028.n2.nabble.com/An-answer-and-a-question-tp7579248p7579250.html</a><br>
[10] <a moz-do-not-send="true"
href="https://gist.github.com/xdg/836e6341b757df8b67cf26f02b6899d6">https://gist.github.com/xdg/836e6341b757df8b67cf26f02b6899d6</a><br>
[11] <a moz-do-not-send="true"
href="https://gist.github.com/xdg/955519bee08658f9b60c6219a51fd0dd">https://gist.github.com/xdg/955519bee08658f9b60c6219a51fd0dd</a><br>
</div>
<div>[12] <a moz-do-not-send="true"
href="http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-td7579168.html">http://dbix-class.35028.n2.nabble.com/GOVERNANCE-Aggregation-and-conclusion-td7579168.html</a><br>
<br>
</div>
<div>-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>David Golden <<a moz-do-not-send="true"
href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a>>
Twitter/IRC/GitHub: @xdg</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
List: <a class="moz-txt-link-freetext" href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class</a>
IRC: irc.perl.org#dbix-class
SVN: <a class="moz-txt-link-freetext" href="http://dev.catalyst.perl.org/repos/bast/DBIx-Class/">http://dev.catalyst.perl.org/repos/bast/DBIx-Class/</a>
Searchable Archive: <a class="moz-txt-link-freetext" href="http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk">http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk</a></pre>
</blockquote>
<br>
</body>
</html>