symfony framework forum: Documentation => Developer for documentation?
Home » development » Documentation » Developer for documentation?
I am not sure, but I don't think so. You could always ask on the dev mailing list for the best course of action; you could submit patches, which might be more likely to be applied than manual fixes, or eventually you may even get svn access and apply the changes yourself.
There is a small group that contributes to the documentation, but mostly by means of translations and fixing grammatical errors etc.
When the changes require more of a "decision" then it seems to be no more than a few people.
As halfer suggests, submitting a patch is a great start, also change your trac entry to start with [patch] if there is one. This is much more likely to get looked at first.
I can see that one of your bug reports was fixed by Fabien a few months ago, I'll have a quick look at the other now.
Thanks, I hadn't noticed that one of the patches had been fixed recently, I don't think I got a notification email which I would have expected.
I will try and submit patches in future - the first time I submitted a documentation ticket I hadn't used Subversion much so I had no idea how to submit a patch, but now I'm far more comfortable with it. The barrier of checking out the documentation, altering it and then creating and upload a patch just to fix a spelling mistake is also a bit of a high one if it's your first bug report on a project.
Presumably for changing the Practical Symfony book I'd be looking here?
With documentation patches, if you are not comfortable with submitting a patch, and the changes are relatively small, just submitting the necessary snippet of Markdown or plain-text should be sufficient.
It's much easier for the team to change something in the documentation if the bug report comes with exact details and a suggested fix, either in the ticket - or in a patch which provides all the necessary info.