Hello everyone.

Today I am officially announcing the start of the async working group.
Anyone may join the group without restrictions.
However, the discussion will follow a clear flow and will be divided
into several stages.

The discussion moderator will help keep the conversation on the right
track, separating secondary questions from the more important ones.
Anyone may propose a candidate for the role of moderator, and until
then I will fulfill this role.

https://github.com/true-async/php-true-async-rfc/discussions/8

Please note that this discussion is not tied to the RFC, is not a
continuation of it, and is essentially a discussion starting from
scratch. At this stage, PHP may choose any direction, as long as it
receives support.
The discussion stages will be finalized through voting and will also
be documented in the form of theses.

It is possible that some stages will need to be approved by the
broader PHP community. I am not yet sure how this should be done, but
I hope for support from the PHP Foundation.

In addition to the main discussion, anyone may create an independent
topic, which will be reviewed.
I also intend to bring this discussion to the attention of the
maintainers of PHP frameworks, because these changes are of primary
importance to them.
For RFC developers, it is important to identify the parts of the code
that will not work, or to understand how the code should be adapted so
that it functions correctly in asynchronous mode.
This is why collective discussion is so important.

For the developers of Swoole and FrankenPHP, this discussion is
equally important. Asynchronous execution makes little sense if PHP
does not have its own built-in web server. A built-in web server with
workers is the foundation for everything. Releasing Async without a
server is possible, but almost meaningless. This is why there is great
hope and attention directed toward your work.

Please share this message with anyone who may be able to help the project.

----
Best regards, Ed

Reply via email to