I don't have a problem with John's proposals at first glance.
However, if we're still planning to follow the
https://github.com/dbsrgits/dbix-class/blob/devrel/GOVERNANCE process that Matt
set up to the letter, we're going to have to address this sentence in that file:
"This document is currently in bootstrap phase, and as such no merges will be
made to master or blead until this sentence is removed."
By the letter of the rule of law under which Matt took over the official
DBIx::Class namespace, we can't implement John's first proposal without at
minimum first removing that sentence.
So my zeroth proposal to the governing committee is that, now that there's been
over a year to think about it and/or see how things shook out with PAUSE perms,
update the GOVERNANCE doc to reflect what you actually intend to happen, this
change presumably also carrying a vote of the list members.
Otherwise we'll have a failure of the constitution right out of the gate.
-- Darren Duncan
On 2018-01-12 8:25 AM, John Napiorkowski wrote:
Two proposals for the governing committee
First proposal:
Haarg proposed a small and obvious fix here =>
https://github.com/dbsrgits/dbix-class/pull/114
I think it should be merged.
Second proposal:
Anyone with comaint or first come should be able to merge and release as needed
trivial or obvious patches (such as the one Haag proposed), documentation
improvements, or fixes required immediately because of security issues or
problems with upstream dependencies. In those cases we can allow to skip voting
and merge / release code at once.
Regards,
John Napiorkowski
_______________________________________________
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
