Community
Channels for help, ideas, and contribution.
GitHub Discussions
github.com/Deiamor/flowgl/discussions
| Category | Use when |
|---|---|
| Q&A | You have a question that isn't a bug. "How do I…", "Is this a good fit for…", "What's the difference between…". |
| Ideas | Feature ideas that aren't quite ready to be a feature request issue yet. Half-formed is fine — that's what discussion is for. |
| Show & Tell | Projects, demos, blog posts, talks. We feature these on the showcase page. |
| Announcements | Release notes, deprecation notices, maintainer updates. Read-only for users; maintainers post. |
Discussions are the right channel when the answer is "let's talk about this" rather than "let's track this to completion". An idea that crystallizes in Discussion often becomes a feature request issue (with your use case attached). A question with a recurring answer often becomes a Cookbook recipe.
Issues
github.com/Deiamor/flowgl/issues
For specific actionable items — bugs, feature requests, documentation fixes. The issue templates ask for the minimum info needed to act on the report.
The flow:
- Bug? Use the bug template. Reproductions get fixed faster.
- Feature? Use the feature template. Start with the use case, not the proposed API.
- Documentation? Open a plain issue — or just send a PR; docs PRs are almost always merged without a separate issue.
- Security? Do not open a public issue. File a Security Advisory — see SECURITY.md.
Pull requests
github.com/Deiamor/flowgl/pulls
Read CONTRIBUTING.md first. The PR template walks through the verification checklist that mirrors what reviewers will look for.
First-time contributor? Look for the good first issue label — these are scoped down enough that you can land your first PR without needing to know the whole architecture.
Sponsoring
flowgl is MIT-licensed and not commercially sold. If your team uses it and would like to keep maintenance moving, the GitHub Sponsors button on the repo funds the maintainer's time spent on docs, releases, and reviewing external PRs.
No tier gates any feature behind sponsorship — see the roadmap § "Won't / Will-not".
Code of conduct
CODE_OF_CONDUCT.md — Contributor Covenant 2.1. Enforcement via the same channel as security reports.
Maintainer
Currently solo-maintained by @Deiamor. If the project grows enough that a single maintainer becomes the bottleneck, the Contributing guide will be updated with the co-maintainer onboarding flow.