On May 3, 7:45 pm, "R. Rajesh Jeba Anbiah"
<[EMAIL PROTECTED]> wrote:
> On May 3, 8:59 pm, nate <[EMAIL PROTECTED]> wrote:
>
> > Also, for as quaintly egalitarian as your "no authority" clause is, it
> > doesn't fly in the real world. Even if "developers aren't morons,"
> > that doesn't mean that you won't get n00bs who only think they know
> > what they're doing, or people who's opinions differ from yours.
>
> > And you plan to handle this by branching? What does that leave you
> > with? Subtilely different versions of the same code, which fall into
> > a state of atrophy over time as they diverge from the core codebase
> > and from each other, and as developers lose interest, which tends to
> > happen on smaller projects.
>
> > If you really think you can do this, hey, more power to you, but so
> > far this plan doesn't even sound good in theory.
>
> I think, we can't conclude the future at this point of time; you
> may be right or wrong with your opinion on the openness of the
> project. But, I'm quite positive about the power of openness.
Good luck with your efforts. If you
avoid making changes to the cake core*
make use of overriding
make use of externals/vendor branching
You would have a fighting chance (IMHO) of succeeding and not having a
project that (might) look ok at the outset and quick stagnate.
Cheers,
AD
*By which I mean
3. Remove scaffolding. Replace with UIMS ->
don't remove things just for the sake of it
6. Remove Session, Cookie, XML, Configure wrappers. Todo: find a
better solution
especially in the absence of an alternative and when the things you
want to replace are configurable
7. Change dispatcher to make the default URL scheme to /foos for
index, /foo/id for view, /foo/edit/id for edit, /foo/add for add
actions
or when you can just change your default routes or use mapResources
or otherwise with simple bootstrap code.
10. Remove debugger. Or move to vendor (xdebug seems better)
or when just by defining DISABLE_DEFAULT_ERROR_HANDLING in your
webroot index disables what you want to remove
13. Remove plugins. Replace with new "mods" architecture
or when the change suggested potentially stems from a
misunderstanding
n. I think, modifying core is necessary evil. To bend it for the UIMS,
it's extremely necessary
any changes *at all* planned for core classes that could be
overridden ( controller/model/view/helper/data source/etc.) imply
change for the sake of change - and that's gonna hurt if you want to
keep up to date.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
