That's a great idea, except that--in this instance--the motivation for this CakePlus fork seems more about "fixing" parts of Cake which the OP disagrees with rather than fixing outstanding bugs. Unless the core devs were to agree to these changes being made they aren't going to be in Trac for anyone to deal with.
I think some of them (though not all) would be very worthwhile, btw. On Mon, May 5, 2008 at 1:05 PM, Sliv <[EMAIL PROTECTED]> wrote: > > Personally I'd prefer to see all of this "energy" go into helping to > close tickets by writing tests, patches, documentation and offering > time/resources to join initiatives that need the help (i.e. > cookbook). I just find that helping is superior to forking for > everyone in the community, unless you've tried to help and run into a > wall of some sort. > > To use a personal example, I had thought of trying to fork a docs > initiative to concentrate on usage examples (less verbose than the > cookbook, more verbose than the API). That may or may not be a good > idea, but instead, at least for now, I've been working on fixing a > checkout of the bakery, helping with Trac "cleanup" and (up until > recently) helping manage this google group. > > I figure fixing existing issues by helping is better than starting > something else and leaving the community starving for assistance... > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
