On Sun, Dec 28, 2008 at 9:48 AM, Iain Duncan <[email protected]> wrote: > >> > >> > 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.
Almost like a parts kit catalogue, but populated with information from a community of users. I bet some of the stuff from the collective intelligence book would come in handy. Maybe this would actually be a good google app engine project actually.... > > 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 -~----------~----~----~----~------~----~------~--~---
