> > > > Last but not least this is pylons, over here everything is optional. > > No one told you to use any of them. > > One thing that might be nice with Pylons, is if each optional > component had a rating system that included attributes such as: > > difficulty to learn: > full test coverage: > documentation: > downloads/popularity: > > It seems like a community rating system could help communicate to both > the author of the component, and the potential developer what is going > on. Like an ebay of sorts.
I think a rating system is going to be deceptive, because beginner friendly components will always get more ratings, so they will be rated higher. This doesn't really match the Pylons targeted user. However, I like the idea of some kind of directory that would give opinions on who would want the component and for what. Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
