What happened to the "Symphony Forge" effort? As can be seen on http://www.symfony-forge.com/frontend_dev.php, it was supposed to include: - a link to a wiki page for the plugin, - a dedicated svn and trac repositories, - a rating system, and a list of "most popular" plugins.
BTW, if we really want to rely on a Wiki to describe and comment the plugins, let's not use Trac's wiki. There are tons of excellent tools out there, so why settle for one of the worst? And what about the list of "Official Proposed Plugins" on http://trac.symfony-project.org/wiki/OfficialProposedPlugins ? It seems that this discussion has already taken place, maybe more than once. Sorry, all this might have obvious answers for those who have been following Symfony for longer that I have. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sid Bachtiar Sent: Tuesday 03 March 2009 09:25 To: [email protected] Subject: Re: Re : [symfony-devs] Re: Do we need plugin comments? >> * documentation/more information about the plugin: wiki > Wikis are a great tool for any kind of community documentation, +1 for that. You know, I think if we could just have a wiki page link for each plugin, that'll be the same as having comments feature. People can then share about their findings and experience in using particular plugin. > 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? That's the reason why we need some sort of medium (comment, wiki page, etc) linked to each plugin. So people can share their experience and knowledge about particular plugin. And other people can find out quickly if they should use the plugin or not. And it is also a way for plugin users to share things not yet written in the readme of the plugin. At the moment we got none of that. > 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. So give the tool, so people can start sharing their knowledge about the existing plugins. On Tue, Mar 3, 2009 at 8:37 PM, Chris <[email protected]> wrote: > > >> 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 > > > > > -- Blue Horn Ltd - System Development http://bluehorn.co.nz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
