Loren Bufanu
Browser engine, Servo integration, compatibility, and the public evidence trail.
- GitHub
- @lolren ↗
Contact
Write to a person, not a form.
There is no support desk and no shared alias. The main address lands with all three of us. If you know which part of the project you mean, the direct lines and the public repositories below go straight to the right hands.
Main address
One address, all three of us.
Project questions, press, bug reports, and ideas. It lands with the whole team, and we reply in the order we read it.
Direct lines
The right pair of hands.
Know which part of the project you are writing about? Write the person who works on it.
Ionel Silviu Ghimpau
Browser chrome, product engineering, quality, and delivery.
- GitHub
- @Silviu3369 ↗
Manuel Ionasel
Development, contributor coordination, and the work between an idea and a merge.
- GitHub
- @ionaselmd ↗
The code, in public
Where the work actually happens.
The repositories, the discussions, and the source of this site — the same places we use ourselves.
github.com/GalileoBrowser/GalileoEngine ↗ — the engine, the browser, the feature matrix, and the release ledger.
github.com/GalileoBrowser/GalileoExtensions ↗ — the extension packages and the MV2/MV3 runtime.
github.com/GalileoBrowser/GalileoEngine/discussions ↗ — questions, debates, and feature requests.
github.com/GalileoBrowser/galileoengine-site-v2 ↗ — the source of the pages you are reading.
Where to say what
Short version.
A missing page or a bug → an issue on GalileoEngine ↗. A question or a debate → the discussions ↗. Anything about the project as a whole → contact@galileobrowser.com. We read all of it.