Contribute where the work is public.
Start with a bounded issue, reproduce the failure, and attach the evidence. The GalileoBrowser organization ↗ is the home of the public repositories.
Get involved / open source
There is more than one way to move a browser forward.
Code matters. So do reproducible failures, patient testing, documentation, thoughtful discussion, and the infrastructure that keeps the work running.
Test the edges.
Try real sites, extensions, media, profiles, keyboard navigation, and accessibility flows. A precise failure report gives the team something concrete to fix.
Ask, challenge, and document.
Join the public project discussions ↗, or follow maintainer updates in the Newsletter.
Support development.
Funding will eventually cover compute, CI, reference hardware, testing, and release engineering. We will open a payment channel only after its rules and reporting are public.
What funding would cover
A browser costs more than code.
The team currently pays the development costs directly: compute, CI, storage, reference hardware, and the environments needed to reproduce failures. Writing code is only part of the work; testing, evidence, packaging, and maintenance carry their own cost.
When funding opens, it will buy engineering capacity rather than influence over the roadmap. Spending and priorities will be reported publicly.
Funding status
We are not accepting money yet.
GitHub Sponsors and the organization payout route are still pending. We will publish the channel, reporting rules, and legal owner before accepting financial support. Until then, code, careful feedback, documentation, and discussion are the useful ways to help.
When funding opens
Fund the work without buying control.
Money should buy more measurement and maintenance, not a louder promise.
Compute and infrastructure
CI capacity, development compute, test environments, artifacts, and storage for retained evidence.
Compatibility work
Reference hardware, media testing, accessibility checks, and the time needed to investigate failures properly.
Release engineering
Packaging, signing, security response, updates, documentation, and long-term maintenance.