The IRCv3 working group is chartered to prototype, develop, test and specify further extensions to the IRC client protocol. It does not define any other aspect of an IRC network, such as IRC services, or the server-to-server protocol, although the changes it develops may require cooperation from vendors in both areas.
These extensions are published on this website through backwards-compatible specifications.
The direction of these specifications is led by the technical board. The board consists of a broad range of IRC software and specification authors that reflect the community at large. The board will seek to make all decisions by consensus.
Nominations for new members of the board will be considered once the following pre-requisites are met:
In general, candidates who meet any of the following criteria will be given more consideration
We’re seeking representation from as many members of the IRC community as possible. If you or your project would be a good candidate for representation, please contact the board. The current members of the board are:
|dan-||DanielOaks||ircdocs / Ergo|
|dx||dequis||bitlbee / irssi|
|jess||jesopo||Libera.Chat / BitBot|
|justJanne||justjanne||Quassel / Quasseldroid|
|Sadie||SadieCat||Anope / InspIRCd|
The chair has ultimate responsibility for moving discussions forward and will make decisions in cases where consensus isn’t possible, including returning proposals to the drawing board where necessary.
The main project resources are:
Contributions are welcome from anyone in the IRC community; including users, developers, operators, administrators. Feel free to start a discussion on IRC or on the issue tracker if you’d like to contribute.
Failure to follow our code of conduct when participating may result in immediate removal from the project resources.