This site is deprecated; docs have moved to docs.inspircd.org!
Contributing to InspIRCd
How to Contribute
The InspIRCd project is quite open to all contributions, large and small. Whether you're a coder, docs writer, tester or <insert role here>, we're sure you will help out in a useful way.
This page documents a bit of how we work internally as a project, so that you can better fit in and help out if you want.
The structure of the development team is of a loosely connected core of developers, supported by a large number of contributors, all working and collaborating on things they want to see done. We don't really assign work to anyone, they find stuff to work on on their own generally.
You can find repositories on GitHub.
If you wish to contribute to development, feel free. To get started, you're probably best off speaking to a developer in #inspircd, or just checking out repositories and sending us patches via git diff. The issue tracker is a good place to put diffs.
Not everyone who can code is stellar at writing things up in a clear, easy to use way - this is where people can help out quite often, by making our numerous features easy to understand. Alternatively, perhaps you are interested in helping to translate our documentation into the language of your choice. Most of the action in this department takes place here on our wiki.
The docs team is managed by SaberUK. To contribute, speak to him or join #inspircd.dev, and talk it over.
Support is a largely informal area, provided by other users and team members. To help out, hang around in #inspircd (we don't mind idlers!) and answer questions if you know what it's about. We're all quite friendly.
If you think you can help out in other ways, get in contact with Attila, Adam, or SaberUK on IRC.