The reasons will stay between the other core developers and me, so please don't ask for details.
Thanks to Adam Kennedy who did a great job negotiating and good luck to the remaining Catalyst developers.
You may want to join #woodstock on irc.perl.org if you like talking about web framework design.;)
There are still some design ideas and code from Catalyst but not that much, atm it looks like Woodstock is going to be a fusion between Catalyst and Jifty.
It's all in the early stages (even though we have a running prototype).
So everything is still open, and anyone can join #woodstock to discuss and influence the development.
I sent this to the list as well. I must say, for a dev/team/software dispute, this was handled quite professionally with the help of Adam. That says a lot about the people/project involved imho.
I think it was in pretty much everyone's mind that regardless of the result from a technical angle, it was encumbant on everyone to calm down and deal with it in a reasonable manner, because if nothing else Class::DBI demonstrated that if you are scared that the project leader is going to flip out and threaten to sue people, many users simply do not care about the technical result and will walk regardless.
Woodstock (Score:1)
Will it be a fork or something from the ground up?
Re:Woodstock (Score:1)
There are still some design ideas and code from Catalyst but not that much, atm it looks like Woodstock is going to be a fusion between Catalyst and Jifty.
It's all in the early stages (even though we have a running prototype).
So everything is still open, and anyone can join #woodstock to discuss and influence the development.
I agree (Score:1)
Re:I agree (Score:1)
Re:I agree (Score:1)