Contributing

Should I contribute?

The core of Webbit Server is deliberately minimal and a goal of the project is to keep it that way. Many of the value-add features will reside in different projects built on top of Webbit. This allows the core of Webbit to move independently from the features layered on top of it.

Examples of good contributions to Webbit Server

• Performance and memory improvements
• Bugfixes
• Better support for HTTP and WebSocket specifications
• Improvements to serving static content
• Core API changes

Examples of features that would be better off as independent projects

• Higher level APIs
• Language specific bindings
• Reflection driven web frameworks

Contributing to Webbit Server

If it's a small change, Fork the project on GitHub, make your changes and create a Pull Request.

For larger changes, it's best to discuss them first on the mailing list.

If you have repeated contributions accepted, you may be granted commit access to the main repository.

By contributing code to Webbit, you agree to pass ownership to Joe Walnes under the BSD License.

Creating an independent project

For most contributions, it probably will make more sense to start a new project. So what are you waiting for?

When you're ready to announce it, or just want feedback, feel free announce it on the Webbit mailing list and add it to the Projects page.