The openATTIC project has entered maintenance mode. New feature development has been discontinued in favor of enhancing the upstream Ceph Dashboard.
See this blog post for details.
There are multiple resources available for you to get help, in case you have questions or run into problems when using openATTIC.
Getting in touch
There are many ways for you to get in touch with us. We prefer having conversations on our public channels like the mailing list or IRC, as this makes it easier for other users to chime in and to contribute to the discussions. It also allows new users to read up on previous topics and learn about know issues and workarounds.
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 email@example.com, using the email address that you want to use to exchange messages with this group (no Google account required).
Before asking a question, please consider searching the group's archive and consult our public issue tracker - maybe the issue you are observing has already been reported.
Also see How To Ask Questions The Smart Way by Eric S. Raymond and Rick Moen for some more guidance on how to yield the best results when posting a request for help.
Chat with us on IRC
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!
Before submitting a bug report or feature request, please spend some time on make sure it’s has not been reported already. 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
If you're looking for some easy task to get started, we have created a list of relatively easy tasks that would be suitable for new developers to become familar with the code base and processes involved. We've collected them on a dedicated Wiki page titled Low hanging fruit tasks. If you're looking for something to hone your skills and expertise, these might be a good start.
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 in the form of a git 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 require you to sign your patch contribution. 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.