Development Team
m (Protected "Development Team": Official Team page. Protected to prevent vandalism [edit=sysop:move=sysop]) |
m (→What Development Environment Does DareNET Use?) |
||
| Line 16: | Line 16: | ||
| ircd-darenet 1.2.0 | | ircd-darenet 1.2.0 | ||
|} | |} | ||
| + | |||
| + | === Why Don't You Use <insert your favorite wizz-bang feature here>? === | ||
| + | |||
| + | There is always a temptation to use the newest operating system features as soon as they arrive. We resist that temptation. | ||
| + | |||
| + | First, we support several operating systems, so any new feature has to be well established before we will consider it. Second, most new wizz-bang features don't provide dramatic improvements. Third, they usually have some downside, such as decreased reliability or additional code required. Therefore, we don't rush to use new features but rather wait for the feature to be established, then ask for testing to show that a measurable improvement is possible. | ||
| + | |||
| + | So, we are not ignorant of new features. It is just that we are cautious about their adoption. | ||
=== What Development Environment Does DareNET Use? === | === What Development Environment Does DareNET Use? === | ||
Revision as of 06:38, 10 December 2008
Welcome to the Development Team's section of the wiki. This page is intended to provide you with information regarding the team and its various projects. We can also be found in #Dev on the network.
IRCd-DareNET
We currently use a modified version of Nefarious IRCu. We decided that rather than always downloading and modifying the source whenever new versions of Nefarious IRCu are released, to instead fork and maintain our own source tree, since the amount of changes we've already made are quite significant.
Current Version
| Current Release: | ircd-darenet 1.2.0 |
| Required Release: | ircd-darenet 1.2.0 |
Why Don't You Use <insert your favorite wizz-bang feature here>?
There is always a temptation to use the newest operating system features as soon as they arrive. We resist that temptation.
First, we support several operating systems, so any new feature has to be well established before we will consider it. Second, most new wizz-bang features don't provide dramatic improvements. Third, they usually have some downside, such as decreased reliability or additional code required. Therefore, we don't rush to use new features but rather wait for the feature to be established, then ask for testing to show that a measurable improvement is possible.
So, we are not ignorant of new features. It is just that we are cautious about their adoption.
What Development Environment Does DareNET Use?
IRCd-DareNET is developed mostly in the C programming language. The source code is targeted at most of the popular Unix platforms.
Most developers run a Unix-like operating system and use an open source tool chain with GCC, GNU Make, GDB, Autoconf, and so on. If you have contributed to open source software before, you will probably be familiar with these tools.
The complete list of required software to build ircd-darenet can be found in the installation instructions.
How Do I Get Involved With DareNET Development?
If you are interested in contributing to DareNET's various development projects (e.g. ircd-darenet, services-darenet, web development, etc) please send e-mail to dev@darenet.org. If you are involved with other projects, please note this in your e-mail and possibly provide links to their project pages.
