@@ -174,16 +174,6 @@ quickstart examples and usage details.
174
174
See also the combined [ changelog for all ReactPHP components] ( https://reactphp.org/changelog.html )
175
175
for details about version upgrades.
176
176
177
- ## Documentation
178
-
179
- Superficial documentation can be found in the README files of the individual
180
- components. See ` vendor/react/*/src/README.md ` .
181
-
182
- ## Community
183
-
184
- Check out #reactphp on irc.freenode.net. Also follow
185
- [ @reactphp ] ( https://twitter.com/reactphp ) on twitter.
186
-
187
177
## Tests
188
178
189
179
To run the test suite, you first need to clone this repo and then install all
@@ -208,6 +198,45 @@ they can simply be skipped like this:
208
198
$ php vendor/bin/phpunit --exclude-group internet
209
199
```
210
200
201
+ ## Support
202
+
203
+ Do you have a question and need help with ReactPHP? Don't worry, we're here to help!
204
+
205
+ As a first step, check the elaborate documentation that comes with each
206
+ component (see links to individual documentation for each component above).
207
+ If you find your question is not answered within the documentation, there's a
208
+ fair chance that it may be relevant to more people. Please do not hesitate to
209
+ file your question as an issue in the relevant component so others can also
210
+ participate.
211
+
212
+ Check out ` #reactphp ` on ` irc.freenode.net ` . You can use the
213
+ [ Webchat] ( http://webchat.freenode.net/?channels=%23reactphp ) if you don't
214
+ already use an IRC client. Many of us are available in this channel, so many
215
+ questions get answered in a few minutes to some hours. We also use this channel
216
+ to announce all new releases and ongoing development efforts, so consider
217
+ setting up an IRC client and idling in this channel for a little longer.
218
+
219
+ Also follow [ @reactphp ] ( https://twitter.com/reactphp ) on Twitter for updates.
220
+ We use this mostly for noteworthy, bigger updates and to keep the community
221
+ updated about ongoing development efforts. You can always use the ` #reactphp `
222
+ hashtag if you have anything to share!
223
+
224
+ We're a very open project and we prefer public communication whenever possible,
225
+ so that more people can participate and help getting the best solutions available.
226
+ At the same time, we realize that some things are better addressed in private.
227
+ Whether you just want to say * thank you* , want to report a security issue or
228
+ want to help sponsor a certain feature development, you can reach out to the
229
+ core team in private by sending an email to ` support@reactphp.org ` . Please keep in
230
+ mind that we're a small team of volunteers and do our best to support anybody
231
+ reaching out.
232
+
233
+ Do you want to support ReactPHP? Awesome! Let's start with letting the the world
234
+ know why you think ReactPHP is awesome and try to help others getting on board!
235
+ Send a tweet, write a blog post, give a talk at your local user group or
236
+ conference or even write a book. There are many ways you can help. You can
237
+ always reach out to us in private and help others in our support channels.
238
+ Thank you!
239
+
211
240
## License
212
241
213
242
MIT, see LICENSE.
0 commit comments