+1 I also think that it wold be great that the knowledge generated in the forums could be structured in some way.
On Mon, Nov 2, 2009 at 1:58 PM, Pablo Godel <[email protected]> wrote: > On Mon, Nov 2, 2009 at 4:09 AM, Lukas Kahwe Smith <[email protected]>wrote: > >> >> >> On 02.11.2009, at 10:06, Fabien Potencier wrote: >> >> > >> > Lukas Kahwe Smith wrote: >> >> >> >> On 02.11.2009, at 08:32, Sid Bachtiar wrote: >> >> >> >>> I agree, we don't need any more mailing list! Just post on symfony- >> >>> users. >> >> >> >> >> >> i think right now it can be said definitively that these messages get >> >> lost in the noise and the two emails i listed both had a clear prefix >> >> in their subjects. so far i have not seen much reaction to the post >> >> that have been made (aside from read blog post xyz ..). >> >> >> > >> > I have definitely read your question, and have no answer... yet. >> > Basically, this is not possible, but should be. I'm working on a patch >> > to make it possible. I should probably have responded to say so, but >> > did >> > not. Sorry about that. >> >> Yeah .. that would have made me feel less desperate. >> Also I can help with writing a patch if I know its really not yet >> possible :) >> >> >> also questions about components that haven't been released yet, tend >> >> to have very listers "users" and most questions tend to end up being >> >> development questions. >> >> >> >> as for fragmentation .. >> >> if the components are supposed to be used by non symfony developers >> >> as >> >> well, then making them bare all the symfony specific noise will be a >> >> serious issue. >> > >> > You are right, that is a very valid point. So, do we need one >> > mailing-list for all components? Or one per component? Because, if >> > someone is only using the YAML component for instance, he will have a >> > lot of noise from other components. >> >> >> I think right now the chances are low that there will be too much >> noise. So I would start of with a single mailinglist and if necessary >> split it up later on. > > > I would go with one list for all components. If things pick up then they > can get split up. > > Pablo > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
