Contribution Guide

Bug Reports

To encourage active collaboration, Socialstream strongly encourages pull requests, not just bug reports. Pull requests will only be reviewed when marked as "ready for review" (not in the "draft" state) and all tests for new features are passing. Lingering, non-active pull requests left in the "draft" state will be closed after a few days.

However, if you file a bug report, your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix.

Remember, bug reports are created in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the bug report will automatically see any activity or that others will jump to fix it. Creating a bug report serves to help yourself and others start on the path of fixing the problem. If you want to chip in, you can help out by fixing any bugs listed in our issue trackers. You must be authenticated with GitHub to view all of Socialstream's issues.

If you notice improper DocBlock, PHPStan, or IDE warnings while using Socialstream, do not create a GitHub issue. Instead, please submit a pull request to fix the problem.

The Socialstream source code is managed on GitHub.

Which Branch?

All bug fixes should be sent to the latest version that supports bug fixes (currently 5.x). Bug fixes should never be sent to the main branch unless they fix features that exist only in the upcoming release.

Minor features that are fully backward compatible with the current release may be sent to the latest stable branch (currently 5.x).

Major new features or features with breaking changes should always be sent to the main branch, which contains the upcoming release.

Security Vulnerabilities

If you discover a security vulnerability within Socialstream, please send an email to Joel Butcher at [e-mail]. All security vulnerabilities will be promptly addressed.

StyleCI

Don't worry if your code styling isn't perfect! StyleCI will automatically merge any style fixes into the Socialstream repository after pull requests are merged. This allows us to focus on the content of the contribution and not the code style.

Code of Conduct

The Socialstream code of conduct is derived from the Ruby code of conduct. Any violations of the code of conduct may be reported to Joel Butcher ([e-mail]):

• Participants will be tolerant of opposing views.

• Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.

• When interpreting the words and actions of others, participants should always assume good intentions.

• Behavior that can be reasonably considered harassment will not be tolerated.