<div dir="ltr">Yep thats something that will need to be done. In which case.... Lets get this ball rolling</div><br><div class="gmail_quote"><div dir="ltr">On Fri, 12 Jan 2018 at 21:02 Darren Duncan <<a href="mailto:darren@darrenduncan.net">darren@darrenduncan.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I don't have a problem with John's proposals at first glance.<br>
<br>
However, if we're still planning to follow the<br>
<a href="https://github.com/dbsrgits/dbix-class/blob/devrel/GOVERNANCE" rel="noreferrer" target="_blank">https://github.com/dbsrgits/dbix-class/blob/devrel/GOVERNANCE</a> process that Matt<br>
set up to the letter, we're going to have to address this sentence in that file:<br>
<br>
"This document is currently in bootstrap phase, and as such no merges will be<br>
made to master or blead until this sentence is removed."<br>
<br>
By the letter of the rule of law under which Matt took over the official<br>
DBIx::Class namespace, we can't implement John's first proposal without at<br>
minimum first removing that sentence.<br>
<br>
So my zeroth proposal to the governing committee is that, now that there's been<br>
over a year to think about it and/or see how things shook out with PAUSE perms,<br>
update the GOVERNANCE doc to reflect what you actually intend to happen, this<br>
change presumably also carrying a vote of the list members.<br>
<br>
Otherwise we'll have a failure of the constitution right out of the gate.<br>
<br>
-- Darren Duncan<br>
<br>
On 2018-01-12 8:25 AM, John Napiorkowski wrote:<br>
> Two proposals for the governing committee<br>
><br>
> First proposal:<br>
><br>
> Haarg proposed a small and obvious fix here =><br>
> <a href="https://github.com/dbsrgits/dbix-class/pull/114" rel="noreferrer" target="_blank">https://github.com/dbsrgits/dbix-class/pull/114</a><br>
><br>
> I think it should be merged.<br>
><br>
> Second proposal:<br>
><br>
> Anyone with comaint or first come should be able to merge and release as needed<br>
> trivial or obvious patches (such as the one Haag proposed), documentation<br>
> improvements, or fixes required immediately because of security issues or<br>
> problems with upstream dependencies. In those cases we can allow to skip voting<br>
> and merge / release code at once.<br>
><br>
> Regards,<br>
><br>
> John Napiorkowski<br>
<br>
_______________________________________________<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-bin/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/repos/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/dbix-class@lists.scsys.co.uk</a></blockquote></div>