On 05.10.2010, at 08:09, Lukas Kahwe Smith wrote: >> >> A wiki might be helpful, but I feel it could easily get stale very quickly. >> The best method of documentation would likely be contributing to the >> official Symfony2 docs, which have their own Git repository. > > I think a wiki would still be a good idea. Submitting a doc addition just > because I think something is a best practice doesnt seem viable. Multiple > people have to agree and the ideas should mature a bit more before they > should be added to the official docs. As for the risk of going stale .. any > page that doesnt get toched for a few weeks means its probably not a best > practice. Anything that is a best practices will eventually make it into the > docs (at which point the wiki page should be updated).
thought about it some more .. in order to stay uptodate with things we should let code speak (supported with tests). so i think i will spend a bit of time on the sandbox adding some more things which i consider best practices. hopefully we can all do the same and then collaborative expand the sandbox to cover more ground. i especially want to make sure that all aspects are unit tested, which should also be very helpful to find out if things change in core. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
