For general support and development enquirines we recomment joining the rspec mailing list / google group. There are many experienced rspec developers on this list who are normally only to happy to help solve your development woes.
See: https://groups.google.com/forum/#!forum/rspec for more information.
If you prefer, you can join the `#rspec` channel on freenode, there are often people willing to help hanging around, although the core team do not monitor this continuously they are often around to help out.
If you encounter a bug in rspec itself you are encouraged to open up an issue on the appropriate repository on GitHub.
- For bugs with rspec-rails: https://github.com/rspec/rspec-rails
- For bugs with rspec-core: https://github.com/rspec/rspec-core (runner, configuration, etc)
- For bugs with rspec-mocks: https://github.com/rspec/rspec-mocks (doubles, spies, etc)
- For bugs with rspec-expectations: https://github.com/rspec/rspec-expectations (matchers)
- For bugs with rspec-support: https://github.com/rspec/rspec-support (string encoding, failed expectation diffing, Ruby feature detection, etc)
- For bugs with rspec-dev: https://github.com/rspec/rspec-dev (tools for developing rspec)
Please note we prefer you don't open general support requests on GitHub.