On Sun, Dec 28, 2008 at 5:50 PM, Iain Duncan <iaindun...@telus.net> wrote:
>
> On Sat, 2008-12-27 at 16:51 -0800, Mike Orr wrote:
>>
>> On Sat, Dec 27, 2008 at 12:48 PM, Iain Duncan <iaindun...@telus.net> 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.
>>
>> Numerical ratings are probably useless except in a voting system, but
>> a comparative chart of packages with comments about how suitable they
>> are for beginners and how well documented they are, could be made on
>> the wiki.
>
> Yeah, that's sort of what I meant. Something that just provides a heads
> up for people about the different components, much like what gets seen
> on the list occasionally.

Book #2?  Pylons Cookbook?

>
> Iain
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to