HI! I am not a symfony developer (involved in symfony code i mean), but i am thinking that would be nice to have a "FAQ" / "Knowlegde base" system ... to get different things that we can see that are repeating into the mail list or in the irc ...
last night someone asked on the IRC a thing related about a symfony best practice: "I need to save several objects that came from a single form. Where do i need to do that save stuff ? " - an the user was a little bit concern that he is doing a bad thing by saving the form inside the action ... I guess that it would be good to provide a "transactions" example (doctrine and propel) ... and i think we could look into list and we could see that there at least 5 topics related to the same issue (i have to look to give a good example )... A Knowledge base system i guess it would help the users to find their problems more quickly ... Also ... i guess it should be written a tutorial about migrating the apps from 1.2 to 1.3 ... it seems that noone reads the change log ... I know 2 people that had same problems in 1 week time period ... the yml conversion from "on/off" to "true/false" thing If you would like, i could buy a domain and make that symfony-faq website ... What do you think about it ? Alecs On Mon, Nov 2, 2009 at 11: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. > > regards, > Lukas Kahwe Smith > [email protected] > > > > > > > -- As programmers create bigger & better idiot proof programs, so the universe creates bigger & better idiots! I am on web: http://www.alecslupu.ro/ I am on twitter: http://twitter.com/alecslupu I am on linkedIn: http://www.linkedin.com/in/alecslupu Tel: (+4)0748.543.798 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
