Home
License
Download
Quickstart
Documentation
Support
Miscellaneous
Links
If you still have questions after reading the [Documentation], you can reach out to the community via the forum. Since we had spam problems, you need a Sourceforge account to post. Having such an account is not that bad actually: SF protects your email address, and you can get notification emails when an item on a project changes (new forum post, new wiki page, ...).
If you have found a bug, please report it via the tracker. Make sure to give a precise description and instructions so that the error can be reproduced. This includes the version of Calimero that you are using, but probably also other relevant components in the system (e.g., your KNXnet/IP interface).
If you have posted to the forum or the tracker, use the "subscribe to updates" feature provided by Sourceforge so you do not miss replies or follow-ups that arrive later than you expected.
Don't be angry if there is no answer to your post. Nobody gets paid to answer questions or fix bugs here. You may want to read How To Ask Questions The Smart Way before posting on the forum if you are not offended by straight talk (note that the authors of this FAQ have nothing to do with Calimero, so do not contact them about it). When you are making a good comment or reporting a bug, this is a valuable contribution even if it may only result in a reaction at a much later point in time. If you want to get involved in the project - please see below!
In general, please stay friendly. Inappropriate or offensive posts are not appreciated and will be removed.
There are many ways to help, including:
Regarding the last point: Currently, Calimero is maintained on a "whenever there's some time between all those other things to do" basis. This means that, except during some lucky periods, there is nobody who has a good overview of the Calimero codebase and design AND, at the same time, an agenda free enough to respond to code-related issues or requests on a short time frame (for example, follow up on bug reports, but not least: perform quality checking of submitted bugfixes or extensions and integrate them into the codebase). If you feel you could do this - while showing respect for previous contributions - and have access to the KNX specifications, contact the core team (you know who we are).
If you don't want to bother with all that, feel free to fork - as long as you keep to the rules (= license). It's the beauty of open source that you can!