I will talk to the author about committing the changes to the documentation. I know he (and we) are very interested in sharing the enhanced version of the docs, I'm just not sure of his availability to commit the changes himself. What would our next step be if he does have time? I'm also happy to help, so perhaps he and I could both help. And just so I'm clear, there are no issues with us publishing the enhanced version of the docs with his book (we definitely will be encouraging people to check the official docs for the most up-to-date information, of course).
Thanks,
Beth

On 9/19/2012 2:27 PM, Philip Olson wrote:
On Sep 19, 2012, at 11:34 AM, Elizabeth Tucker Long - Treeline Design, LLC 
wrote:

Is there any certain person in charge of the SPL documentation? We are 
publishing an SPL book, and the author spent a lot of time going through and 
updating the existing documentation with in-depth explanations and examples. I 
wanted to talk with someone about getting this information into the online SPL 
docs, if that's of interest to them, and see what their thoughts are about us 
publishing this enhanced version of the documentation (because we do not want 
to overstep and publish anything that shouldn't be published if it's too close 
to the existing documentation that was written by someone else).
Greetings Beth,

The manual is open to all and doesn't really have maintainers for specific
parts.

Your plan sounds great as a win-win for everyone. Ideally the author would
commit the SPL changes so would you like to pursue that option? It'd mean
gaining SVN access and making the commits. If you'd rather not do that
and/or would prefer sharing non-DocBook suggestions then I (or anyone else)
could help you do that. Etienne and Peter are our resident SPL experts
though so they would make a better choice than me :)

Whatever the case, let's move this to the PHP Documentation list.

Regards,
Philip



--
Beth Tucker Long
Treeline Design, LLC
807 Arbor Vitae Place
Verona, WI 53593
608-770-6677
http://www.TreelineDesign.com

Reply via email to