Contribute to Gosub

Where we are

Gosub is young, and we'll be honest: we don't yet have a fully structured onboarding process for new contributors. That doesn't mean you can't get involved - quite the opposite. Even if you don't jump straight into coding like you might in a more mature project, there are plenty of areas where your input will be genuinely valuable.

Where help is needed most

• Documentation for getting started - documenting how to compile and run the current components, so the next contributor has an easier time than you did.
• Documentation review - reviewing and refreshing existing documentation for accuracy as the codebase evolves.
• Project structure - helping establish roadmaps and define coding standards for the project.
• Code, testing, and bug reports - the engine itself always needs hands. Check the status page for components in active development.

Who we're looking for

Building a browser engine takes far more than writing a parser. We're looking for experienced developers, new and aspiring developers, browser specialists, security researchers, designers, writers, and people who can help organise and promote the project. You don't need browser experience, and you don't need to understand the entire engine - most contributors work on one particular part of the system.

We also want to establish small focus groups around specific areas of the engine, such as security and process isolation, rendering and graphics, networking, and scripting. Read the full story in our blog post Join the crew.

Where to find us

Development happens in the open on GitHub, and the developers collaborate day-to-day in our Zulip chat. Drop in, say hello, and tell us what you'd like to work on - we'll help you find a good starting point.