Matt Feifarek wrote:
1. remove all non-core "kits" like middlekit, comkit, taskkit, userkit, etc. When there is a dependency on one of them for Webkit, fix the dependency. To the extent that these projects have interest (like MiddleKit) spin them into their own projects.
Can't agree more!
Myself and probably many others get away with just WebKit - this is a basis and all other kits are optional and [should be] pluggable. Hence it's quite naturally to develop them independently.
3. Choose one (1) templating option (maybe PSP) if it's deemed essential to get the php/asp crowd comfortable. If we can't agree on one (1) then ditch it, and include *prominent* links to the contenders, and how to install them.
If there is a community interest, I could contribute an adapter that integrates Cheetah nicely into WebKit.
[ other good thoughts are skipped ]
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
