search

async-interop / event-loop

An event loop interface for interoperability in PHP.
MIT License
170 stars 9 forks source link

List participating projects in README #83

Closed kelunik closed 7 years ago

kelunik commented 8 years ago

I guess it would be fine having them listed in the README. Suggestion comes from https://www.reddit.com/r/PHP/comments/4t6ggs/first_draft_version_of_the_eventloop/d5ezhqg

bwoebi commented 8 years ago

I wouldn't say the projects participated, but individuals.

For example for react, Cees-Jan is heavily involved, but he's not the main maintainer… Thus, I wouldn't distinguish by project here.

AndrewCarterUK commented 8 years ago

Most of my work here is motivated by PHPFastCGI - but I'm not sure if that counts as a participating project?

WyriHaximus commented 8 years ago

The title could be Projects with participating members, as @bwoebi points out the projects are not participating per se their members are. Honestly I'm in doubt about this

jmalloc commented 8 years ago

If you're interested in an outsider's two cents, I think it would be more useful to prospective users and implementors to list projects that adhere to the interfaces, rather than contributing projects, and I believe this is the original intent of @mnapoli's Reddit comment.

If you're reluctant to include such a list in the README file - which is understandable, as it will hopefully grow considerably :) - then perhaps taking a leaf out of ReactPHP's book and offering a user-editable wiki page could be useful?

mnapoli commented 8 years ago

Well now that the project has a release, it might be interesting to list projects that are compatible with this standard (either as provider or as consumer).

For example the list in container-interop: https://github.com/container-interop/container-interop#compatible-projects

kelunik commented 8 years ago

@jmalloc @mnapoli The number of projects implementing the Loop will probably not grow. Amp will get a version 2.0, React will work with an adapter of Amp 2.0 probably, don't know what will happen to Icicle, @trowski?

So it seems we're rather aiming at a common implementation not only a common interface currently.

bwoebi commented 8 years ago

@kelunik Don't know what will happen with React yet… and perhaps Guzzle will also have their own loop implementation … We'll see what future brings.

WyriHaximus commented 8 years ago

We'll see what future brings.

Exactly! I'll start writing a bidirectional adapter for react first. As a member and not the leader I can't guarantee anything. But this is an initiative I personally consider to be hugely beneficial for the async php community, so yeah I intend to get it to react one way or the other. The adapter is way one and hopefully the first step :smile: .

mnapoli commented 8 years ago

@kelunik right but projects will use this? If so, it seems interesting to list them? This discussion make it sound complicated :)

bwoebi commented 8 years ago

Sure, will. But we have no released versions of projects actually using it. amphp/amp v2 will probably get some release (or pre-release at least) in not too distant future I guess.

Then we can add it ;-)

mnapoli commented 8 years ago

:+1:

trowski commented 8 years ago

@kelunik Icicle will be abandoned in favor of Amp v2. The APIs are nearly identical at this point, no use having two competing projects offering almost the exact same thing.

kelunik commented 7 years ago

We have the implementations and compatible packages listed now. The spec is written by individuals, not projects. I'll close this one now. If someone wants to see more in the README, just respond or reopen.