Rating system would be great. And some way to categorize plugins would be great too. If I could tell whether or not a plugin has test cases and documentation at a glance that would be awesome.
However, I think we should avoid making a fundamental distinction between libraries, plugins, and modules on a technical level. If all of these different kinds of things can be handled by one system... that's a great feature, and keeps things simple. It also lets a trivial "library" grow into a more sophisticated "plugin" through a gradual, evolutionary process without any artificial barriers being created. On Dec 11, 2007 3:12 PM, mozey <[EMAIL PROTECTED]> wrote: > > well!, perhaps we can further divide plugin types. So instead of just > a good old plugin you have either a: > > - Library: just like the blueprintcss example, just expand it and use > its functions. > - Plugin: Actual functional something or other, WITH test cases, this > and that AND documentation. > - Module: Almost like an application, WITH test cases, AND sample > data, AND proper documentation. > > Where all of these types of components have a set of things that is > expected to accompany them, like the test cases, documentation, etc. > This would improve on the over all quality of the code, and i there > are TWO plugins that does one thing, III would chose the one which > comes with test cases for instance!. > > Ontop of that!, a rating system based on: > > - usability: > - downloads: > - etc etc > > so same idea different fields?!? > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
