Community Support
Questions and discussion are on the infrastructures mailing list or IRC channel:
- infrastructures list
- #infrastructures IRC channel at irc.infrastructures.org; most activity on the channel tends to be 1900-0700 UTC, weekdays.
Bugs should be submitted as a ticket rather than as email messages on the infrastructures list; this way they don't get lost. If you have a patch, it's better to attach it to the ticket as a patch file rather than include the entire file.
You don't want to email the developers directly -- they need to be able to post their answers on the list, to reduce the number of repeat questions. You'll tend to get more answers from other list members anyway.
Commercial Support
ISconf is designed to be easy to use and easy to understand. Commercial support is entirely optional. But if you need a site visit, training, dedicated support, telephone support, or fast turnaround on feature requests, then you probably want a commercial support contract. We do this already, billing via our TerraLuna LLC incubator. Contact Joyce Cao to get the process started.
Expect a standard consulting contract -- boilerplate contract, statement of work, etc. Pricing depends on your needs, but see http://www.stevegt.com/dgp/rates for representative examples. Code developed under contract should remain under a GPL license so we can include it in the ISconf code base and manage it with this Trac site -- if we need to protect confidential portions, or if you require that we use your internal version control repository, then your costs will be towards the high end of the range.
