> That's exactly why I don't want comments. If comments are used to ask 
> for information, it won't happen anytime soon. I think we need to use 
> the right tool for the job:
> 
> * questions/support: mailing-list
In my experience, mailing lists have the problem of not being as popular
or accepted as they should be. I think this is mainly because most of
the time they are not very well integrated into the other tools used for
a project. For example, this list is hosted provided by google. To take
the full out of the web frontend, you need yet another account from
google. To put it simpler, people are used to stuff like forums and
tools that look pretty.

> * issues/bugs/enhancements: bug tracker
Yes, I would support bug tracker(s) for plugins. Developing a larger
tool without a bt is quit painful and besides that, a bt is always a
good indicator for project activity.

> * documentation/more information about the plugin: wiki
Wikis are a great tool for any kind of community documentation, +1 for that.

> For now, we don't have specific ML or bug tracker for plugins, and I 
> don't know if we need to add all these to the plugin management system. 
> Suggestions welcomed.

As I already mentioned, I believe the question is not about tools but
about strategy. People submit plugins on a "fire and forget" thought and
nobody seems to really care. If you are working on a professional
project, symfony as a framework is great, but using plugins is just to
risky. Tools will not solve this problem. Yes, a comment system can help
to separate the "good" from the "bad", but then I have to ask myself:
why even have bad? Who would be interested in not deployable, not
documented and not maintained plugins? I guess, the answer is no one.
What symfony is really missing on the plugin side is a strong user base
that cares for plugin development and maintenance as much as for the
core elements and we need good quality standards to be able to draw a
real benefit from community developed plugins. In short, symfony needs a
guided community process for plugin development.

Chris


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

Reply via email to