We have a variety of communication tools that the Foreman Community uses to get work done. The guidelines below apply in general when interacting with other Foreman users & developers:
There are also a few extra medium-specific guidelines, listed with each type of support below.
Should you need to speak with someone about another Foreman member’s behaviour, email the Community Lead, Greg Sutcliffe (greg.sutcliffe at gmail.com). You may also CC or email Ohad Levy (ohad.levy at gmail.com). We’ll do our best to listen to your issue fairly and take appropriate action.
To get appropriate support, you need to provide sufficient information about your operating system, environment and setup. You can utilize the foreman-debug tool - for more info see the manual.
The issue tracker (Redmine) should be used to check for existing issues or to file a new issue. First, find the project and then use the Issues tab to view bugs and feature requests. Use the search feature at the top of the issue list to filter by Category to narrow down the results.
When filing a new issue, check that the correct project is selected, then click the New Issue link in the header. Try to set the Category, Found in release and include as much information as possible, including log files and screenshots. For support requests, please use one of the other options below.
Mailing lists are available via Google Groups. For help or support with Foreman problems, questions and answers or general discussion, post to the foreman-users list:
For discussions about developing Foreman or plugins, use the development list:
There is also a low-traffic list dedicated to release and security announcements:
In addition to the general guidelines above, we also have a few email-specific guidelines:
(Credit to the Fedora Mailing List Guidelines as a source of ideas, under the Creative Commons Attribution-ShareAlike 3.0 Unported license)
Ask questions about how to use Foreman on Server Fault, so anyone can benefit from the answers. Tag your questions with ‘foreman’.
A great place to get real-time help with The Foreman is our IRC channel:
There are usually many helpful people there in addition to some of the Foreman developers. For discussions about the intricacies of developing Foreman or plugins, use the development channel:
Please read and understand this fantastic guide to getting help for open-source projects on IRC before diving in. All of the points there apply to #theforeman, especially “Don’t repeat yourself”, “Don’t ask to ask”, and “Stick around”. #theforeman in particular has concentrations of people in Europe (CEST) and East-coast US (EST), so asking your question when those time zones are in business hours is more likely to get a good result.
Be aware that the IRC channel is not an official support channel, it’s an ad-hoc group of people (some of whom work on Foreman for a living) self-organizing to help each other out. If you do not receive an answer to your question, (especially if you have not followed the getting help on IRC best practices!), that doesn’t mean you are out of options; the software may have a bug, the docs may be lacking, or it’s possible Foreman doesn’t yet support your use case. It just means you need to keep troubleshooting to find out which.
In addition to the general guidelines above, we also have a few IRC-specific guidelines:
(Thanks to the Puppet Labs IRC Guidelines for the original document)
Please subscribe to our YouTube channel. We regularly upload deep dives on Foreman features, screencasts to learn how to use the different features and plugins of Foreman, discussions and much more.
Our Google+ community regularly hosts live hangouts on a variety of topics. Become a member of the community and you will be notified about these events, so you can ask questions to the presenters and join the conversation.
A new bug fix release for Foreman 1.14 is available. See the Foreman 1.14.1 release notes for more details.
Foreman 1.14.0 is now available, featuring new automatic IPv6 support, LDAP and template enhancements, and easier email configuration. Read about all of the changes in the release notes, and follow the quick start to install it.