Contribution Guide

Introduction

Thank you for considering contributing to InspIRCd. This guide will hopefully make it easy for you to contribute. If you have any questions feel free to ask on IRC.

Getting started

Read the project rules

All contributors are required to comply with the project rules. Most of these rules are common sense so you shouldn't need to worry too much but you should read it just in case.

Join the development channel

As well as our support channel #inspircd we also have #inspircd.dev where the latest development commits are announced. Joining this channel allows you to take part in discussions about the development of InspIRCd.

Tasks we need help with

Testing

Testers are currently needed for the master branch as large changes have been made. If you have a test network or small network you are okay with being down when bugs appear of please consider running v5 to help find any bugs which have been missed during development.

Packaging

If you use an operating system or distribution that we do not currently have an up-to-date package for then you can help out by packaging InspIRCd for it. Advice for packagers is available here.

If you find that your system requires patches to get InspIRCd working we are happy for you to upstream them regardless of system popularity providing they do not require massive changes (e.g. Haiku support required under 10 lines),

Development

Help with bug fixes and small features is always appreciated. Pick a bug from our issue tracker and ask if anyone is already working on it in the development channel. If nobody is working on it do what you can and send us a pull request.