i think the big issue is about marketing and critical mass, and less about the exact details of functionality.
I think a lot of concerns could be solved in two steps: 1. getting a "Framework :: Pyramid" classifier, which has been requested 2. having a page/module on the Pyramid site that does this: table 1: official pyramid plugins table 2: community plugins grid based view that shows in alphabetical order [ name ][ pypi page][ homepage(bitbucket/github/site) ][ description ] everything in the grid would be auto-updated based on the "Framework :: Pyramid" classifier. it's one huge list. the opencomparison engine is a nice bell/whistle -- but one of the big things that got the django community moving was that there were many huge lists of packages early on. there are a 2700 packages referencing django on pypi and 220 for pylons. the best way to show that pyramid is a vibrant community is to make all the activity going on around it look as substantial as it really is. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
