We definitively need to make things clear between Pyramid and higher- level stuff and the site must provide that information unambiguously; by words, by content organization, by layout, etc...
We also need to make a distinction between projects developed by The Pylons Project and by third parties, not to create confusion and have a cohesive collection. I think Pyramid must be associated with something like a «core» or a «base» framework and it's why we must not use a name including Pyramid for an higher-level framework based on it, it's just too confusing. A plugin or extension like pyramid_beaker makes sense because it plugs another lib to extend the core framework, but «gears» will define policies, rules and opinions so it needs to be self defined. Pyramid is not called Paste Pyramid or WebOb Pyramid because it uses them to provide functionalities. It's not an easy task... Blaise -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
