[Dbix-class] GOVERNANCE: Aggregation and conclusion

[Matt S Trout]

(this message bcc'ed to modules at perl.org for the record, not cc'ed in the
hopes of minimising the odds of unintended cross-list reply carnage)

So, everything seems to've settled down. I've just gone back through and
attempted to extract votes out of the various threads, possibly imperfectly,
and in the case of my proposal considering people who said "yes, but" to be
simply against it in the name of fairness.

Here's the summary:

Governance+core team proposal:

Tue Oct 18:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012331.html

Updated Wed Oct 19 by:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012365.html

In favour:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012336.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012339.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012340.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012342.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012343.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012345.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012348.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012350.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012355.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012359.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012360.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012362.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012366.html

Against:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012332.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012357.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012358.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012360.html

13 for, 4 against, for a total of +9.

DBIC/DBIC2 proposal:

Sun Oct 23:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012370.html

In favour:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012371.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012374.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012378.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012379.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012389.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012390.html

Against:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012383.html
http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012388.html

6 for, 2 against, for a total of +4.

Combine these numbers with the fact that the objections to the governance
proposal were primarily of the form of "this needs to be tweaked" and the
boostrap phase update I made gives us time to do so, whereas the objections
to the alternative were outright, I believe the overall will of the
community is at this point relatively clear.

For those of you who think a two stream release system is a good idea in
general ... it's entirely possible it could be, and I think a discussion
of that later would be a good idea, but I expect that for the first few
months we'll primarily be getting settled and handling bugfixes and figuring
out what potential future features we even want, and I'd rather not second
guess plans that aren't made as yet. So, basically, "let's definitely come
back to that, but let's wait until we have a concrete basis from which to
discuss it before doing so". Plus even an untweaked version of the governance
document means (intentionally) I can't stop you forcing a vote on it at any
point you want to.

As such, I hereby call upon the PAUSE administration to adjust the permissions
for all namespaces within the DBIx::Class distribution in accordance with:

http://lists.scsys.co.uk/pipermail/dbix-class/2016-October/012365.html

Once this is done, I intend to commit the GOVERNANCE document to master and
we can enter the bootstrap phase to thrash the governance system into a shape
people are actively happy with.

Peter, if you have any remaining code to push, shout and I'll be happy to
defer committing the governance document for a few days since it's pretty
uncontested that you know what you're doing and I can't see how that can't
be a net positive.

Ladies, gentlemen, and mongers, thank you for bearing with us through this
process and I look forward to working together going forwards.

-- 
Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue

http://shadowcat.co.uk/blog/matt-s-trout/   http://twitter.com/shadowcat_mst/

Email me now on mst (at) shadowcat.co.uk and let's chat about how our CPAN
commercial support, training and consultancy packages could help your team.