§01CONTACT
Write to
a human.
They'll write back.
§02 · CHANNELS
GH
GitHub Issues
bugs · feature requests · public discussion
DS
GitHub Discussions
questions, show & tell, ideas
GH
Maintainer
@hoootan · Hootan Moradi
SEC
Security
private vulnerability report via GitHub
BEFORE YOU WRITE
- → Read the docs — most questions live here
- → Search GitHub Issues — someone else may have asked
- → Skip the
“hope this is the right place”intro. It is. Get to the point.
§03WHERE I AMOne city.
One city.
One shared terminal.
Amsterdam BASE
UTC+1 · Netherlands
SetupRemote · by appointment
Team1 engineer
Best reachGitHub issues
§04BEFORE YOU ASK
Questions we already have answers for.
How fast will I get a reply?
Usually within 48 hours on weekdays. GitHub issues are the fastest path — they land right next to the git log. FlowForge is maintained by one person, so weekends are best-effort.
Can I get a demo or onboarding call?
Yes — pick “Working together” on the form. Please have FlowForge running locally first so the call is productive. 30–45 minutes, screenshare, actual code.
I found a security issue. Where do I send it?
Open a
private security advisory on GitHub. Please don't file a public issue — we'll coordinate a fix and disclosure together.How can I contribute?
Pick an open issue or file a new one to discuss the change first. Small PRs land quickly; larger ones are easier to review when there's context. The repo is
github.com/hoootan/flowforge.— or just start building
The fastest way
to a reply is a
working prototype.
$ pip install flowforge
$ flowforge init hello-world
$ flowforge dev
→ ready on :8288 · 3 example flows loaded