On Tue, Jul 22, 2014 at 12:50 PM, Sara Golemon <poll...@php.net> wrote: > This document is meant for PHP, and PHP should be the steward of it > going forward, so we (as in PHP) should start looking at good ways to > keep it up to date and revise it over time. > Some folks in IRC asked for clarification of this point.
FB isn't looking to just throw this over wall saying "HERE'S THE FINAL DOCUMENT, HAVE A NICE DAY, GOOD BYE!". What we're planning to release next week is more like a pre-1.0 draft which will probably need a lot of work before anyone is willing to call it final, and of course the document will need to be updated over time to reflect changes in the language's syntax (e.g. return typehint rfc). We're happy to setup the framework for curating that document (probably as a github project), but don't want to be all controlling with it, so if the PHP Group as an organization wants to own it and manage updates to it over time, all the better. If that means FB sets it up then hands it over, that's an option too. This is the discussion I'd like to start now, so that we can work out a strategy for what that looks like. If folks have comments on the one chapter I uploaded, I'd say start with emails to the list or me directly and I'll pass them on. That should be considered a short-term solution though. Ideally we'll have something in a collaborative format next week that folks with existing karma can contribute to more directly. -Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
