Wiki

Development Information

Git repository

The current development state is stored in a Git repository.
To check out the latest development version use the following command. If this code does not compile it's probably a known issue and you should not complain about that.

After "cloning" the repository you will need to generate the automake and autoconf files. You can do this using the build.sh script found in the root directory of the repository.

Users of github can also use our github mirror.

Bugtracking system

We're in the process of setting up a bugtracking system for collectd. It's in an early test phase, but hopefully it will stabilize quickly. Please help to improve it by using it and pointing out problems.
Unfortunately you have to sign up to post bugreports, because otherwise the system will not be usable within a year due to spam. We regret this, but there's no way around it.

Development articles

• collectd's plugin architecture
  A technical overview of the functions that should be in a plugin and what they do.
• collectd's build system
  Some hints how you integrate a new plugin in the autotools-based build-system.
• Submitting patches
  A few words on how you best generate patches.
• A few words on coding style
  A guidline to write, what we consider, "good code".
• Roadmap
  Some ideas of future development and a rough order in which we plan to implement them.

The collectd Contribution Appreciation Program

In order to attract developers and other contributors to collectd, I, octo, am giving away free t-shirts to people who have contributed to the project in whatever form. You can read the details in the news entry. So far, t-shirts have gone to:

• Sebastian Harl
• Richard Shade
• Peter Holik
• Richard W. M. Jones
• Stefan Hacker
• Oleg King
• Michał Mirosław
• Alessandro Iurlano
• M. G. Berberich
• Michael Stapelberg
• Luke Heberling
• Bruno Prémont
• Doug MacEachern
• Fabian Linzberger

Thanks, guys :)