On 11/02/2016 10:07 AM, Paul Mooney wrote:
> On 02.11.2016 09:02, Dave Cross wrote:
>> Quoting Matthias Zeichmann <matthias.zeichm...@gmail.com>:
>>
>>> On Tue, Nov 1, 2016 at 10:45 PM, Charlie Garrison <garri...@zeta.org.au>
>>> wrote:
>>>
>>>> On 1 Nov 2016, at 19:48, Thomas Klausner wrote:
>>>>
>>>> > I think a fork will not work. The "old" DBIC will stagnate, the "new"
>>>> > will not gain traction. Everybody loses.
>>>>
>>>> Agreed. Another,
>>>>
>>>
>>> same here
>>>
>>> -1 for forking, +1 for the original proposal
>>
>> Mee too.
>>
>> +1 Matt's proposal (new project team)
>> -1 Andrew's proposal (forking)
>
> Same here:
>
> +1 Matt's proposal
> -1 to forking
>
+1 Matt's proposal
+1 to forking
I think we should at least give interested developers a chance to play
with DBIx::Class and test out new features.
It can just live on Github and not on CPAN until something useful
emerges out of it. In case that doesn't happen, the repo can
be closed.
Regards
Racke
>
> _______________________________________________
> 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
>
--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration.
_______________________________________________
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
