Community and contribution
frei0r is maintained in public. Use the channel that matches the conversation.
Telegram discussion
Talk with developers and users about effects, integrations and contribution ideas.
GitHub repository
Read source, follow changes, inspect releases and fork the project.
Issue tracker
Report reproducible defects and missing documentation.
Pull requests
Submit plugin, build, test and documentation changes.
Discuss an idea
Use t.me/frei0r for exploratory questions, plugin ideas, host-integration design and help narrowing down a problem.
GitHub also provides repository discussions when a topic benefits from a durable threaded record.
Report a problem
Open a GitHub issue and include:
- Operating system and architecture
- frei0r release or commit
- Host application and version
- Plugin name and parameters
- Exact reproduction steps
- Relevant console output or crash report
Security-sensitive reports should follow any private reporting method configured in the GitHub repository rather than being posted publicly.
Contribute code or documentation
- Build and test the current branch.
- Keep each change focused and preserve the small API's compatibility.
- Add or update tests for changed behavior.
- Check plugin metadata and unusual frame/parameter boundaries.
- Open a pull request.
New effect authors should begin with the plugin development guide. Website contributors should use the source map in docs/content-sources.md to avoid restoring obsolete information.
Releases and project activity
License
frei0r is free software. The repository's COPYING file contains the GNU General Public License, and individual source files identify their applicable GPL or compatible terms. Preserve copyright and license notices when reusing code.
Legacy discussion archive
The project previously used a public mailing list. Its searchable archive remains useful for historical research, but new discussion should use Telegram or GitHub.