Getting in Touch

Join our Google Group
We have set up a discussion group openATTIC Users on Google Groups, and we'd like to invite you to join the conversations. If you have a question or problem, just ask! Google Groups offers a forum-like web frontend and can also be used as regular mailing list.

You can subscribe to it via the web page, or via email, by sending an empty message to, using the email address that you want to use to exchange messages with this group (no Google account required).

Chat with us on IRC
visit the #openattic IRC channel on

openATTIC on social networks

Send us an e-mail for further information about openATTIC (no support questions, please):

Need professional support?
Take a look at our support offerings.

Follow our blog

Send us Feedback

Found a bug? Missing a feature? Please let us know!
If you want to help, you don’t have to be a developer. Reporting bugs or inconsistencies also helps!

We have set up a public issue tracker (based on Atlassian Jira). We appreciate any kind of feedback like comments, enhancement requests, bug reports, or code contributions!

Before submitting a bug report or feature request, make sure it’s not already known. If you're unsure, feel free to get in touch with us via IRC or the Google group first, so we can discuss your request beforehand.

Contribute Code or Patches

You have coding experience in Python (Django) or JavaScript (AngularJS, Boostrap) and would like to contribute to openATTIC? Or you found a bug and want to propose a fix? Excellent!

Please join our IRC channel or Google Group — it will help us to get to get to know you better and how we can collaborate. Coordinating our work will allow us to achieve the best results.

The openATTIC source code is available as a Mercurial repository on BitBucket.

First off, start by Setting up a Development System. Then code away, implementing whatever changes you want to make. See Contributing Code to openATTIC for details on how to submit your changes to the upstream developers. Follow the openATTIC Contributing Guidelines to make sure your patches will be accepted.

To improve tracking of who did what, we use the “sign-off” procedure introduced by the Linux kernel. The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch.