I think we shouldn't split the plugin list, actually I don't think we should create one at all. For people that are known to symfony the way our support lists are organized seems quite straightforward but I'm pretty sure that it isn't that great of a setup for new symfony users. New users should have as little as possible to choose from in my opinion (they always doubt, sorry if this isn't the place to post this but.... I know I do when I'm new to a community). Besides I agree with the cross pollination argument of Jacob. The only thing I would like to make an exception for is when there is an issue that is related to the core of the framework. For example I recently ran into an issue with logging from the PluginConfiguration class with the event dispatcher. Perhaps I should have asked first in the user list but to me it really seemed like a question for the dev list since it is related to the very core of the framework. Filing a ticket straight away when it is actually not a bug creates an unnecessary flow of new tickets in trac...
I guess we should just keep everything as is. Post in the user list first, with complicated core related questions one could ask on the dev list later when no answer was obtained in the user list and file bugs in trac if it simply is left unanswered. That way we keep active lists and prevent an awful amount of invalid tickets in trac. Kind regards, Marijn On Feb 3, 2009, at 4:52 PM, Jacob Coby wrote: > > I don't think there is enough traffic on either list to warrant > splitting out the plugins into their own lists. Having a slow main > list and a dead plugin list doesn't seem like an advantage. > > On top of that, you lose the "cross-pollination" of ideas as people > discuss issues with plugins (either development or usage). Seems like > a lose-lose idea. > > Just my $0.02. > > On Feb 3, 2009, at 10:38 AM, Fabien Potencier wrote: > >> >> Tom Boutell wrote: >>> We'll have the same issue of distinguishing plugin development from >>> plugin use, though. People will want to post their "how do I use >>> sfGuardUser" questions to the plugin-devs list. We might want to >>> add a >>> plugin-users list as well so there's a clear place for them. >> >> Right, as for the main mailing-lists, we need two of them. >> >>> >>> I'm tempted to comment further on the names of the mailing lists, >>> but >>> the fact is that you can only say much in a few characters. A clear >>> description of the list's purpose in a signature at the bottom of >>> each >>> message would help more. >> >> I would rather use the same name as we have for the symfony MLs to >> avoid >> confusion. >> >> Fabien >> >>> >>> -Tom >>> >>> On Tue, Feb 3, 2009 at 9:59 AM, Pablo Godel <[email protected]> >>> wrote: >>>> On Tue, Feb 3, 2009 at 9:57 AM, Fabien Potencier >>>> <[email protected]> wrote: >>>> >>>>> It is always better to discuss a problem in the MLs before >>>>> creating a >>>>> ticket. It you are unsure about the problem, ask the question to >>>>> the >>>>> user mailing-list. >>>>> >>>>>> And where do plugin related questions belong? On the dev list or >>>>>> the >>>>>> user list? >>>>> That's a very good question. Perhaps it is time to create a >>>>> plugins >>>>> mailing-list. What do you think? >>>> I second the idea of a list for plugin development. >>>> >>>> Pablo >>>> >>> >>> >>> >> >>> > > -- > Jacob Coby > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
