• You can get support from the Orbeon Forms community on the ops-users mailing list. The ops-users mailing list is the hub of the Orbeon Forms community, and this is the best place to ask questions, share you experience, or post issues and requests for enhancements. Also see:

  • How can I subscribe to the Orbeon Forms mailing list?

  • How to report issue in the Orbeon Forms mailing list?

  • Where are the Orbeon Forms mailing list have archives?

• Orbeon can provide professional support for your company. Orbeon has two types of plans: Production Support plans are the most appropriate when your application is in production, while Development Support plans also covers issues during development, feature enhancements, and training. For more information contact Orbeon at info@orbeon.com.

1. To subscribe, send an email to: ops-users-subscribe@ow2.org. You can leave the subject and body of your email empty.

2. You will receive a message asking you to confirm that you want to subscribe to the list. Confirm by following the instructions in that message. If you don't receive this message in an hour or so, you might want to check if it went to your spam folder.

3. You should then start receiving messages from the list in the next few hours. You might receive 10 to 30 messages a day, so you might want to setup your mail client to automatically move those messages in a particular folder, so they don't all show up in your inbox.

4. To unsubscribe, send an email to: ops-users-unsubscribe@ow2.org from the email address you used to subscribe. You can leave the subject and body of your email empty.

If you are having any problem subscribing to the list, please contact at info@orbeon.com.

Since July 2009, the source code has migrated from the older CVS repository to the git repository on github. More information on the wiki: Orbeon Source Code Repository.

More information on the wiki: Orbeon Source Code Repository.

How often do you release new versions of Orbeon Forms?

We generally have one major release a year. Historically:

• 3.9: May 15, 2011
• 3.8: May 14, 2010
• 3.7.1: June 1, 2009
• 3.6: December 7, 2007
• 3.5: February 20, 2007
• 3.0: January 17, 2006
• 2.8: March 10, 2005

We may provide Orbeon Forms PE customers with stable point releases between major versions.

More historical releases for the curious:

• 2.7: January 21, 2005
• 2.6: November 18, 2004
• 2.5: July 13, 2004
• 2.2: November 17, 2003
• 2.1: September 16, 2003
• 2.0: July 10, 2003
• 1.5: March 17, 2003

• The bug has been reported by a support customer and has been evaluated as high priority.
• It is very easy to implement, so we just implement it along the way to make everybody happy.
• We have put it on our roadmap and scheduled it because we think it is a crucial feature for Orbeon Forms. 
• We need it for a project we are currently working on.
• Somebody sponsors it.
• Somebody sends a patch for it.

The key to effectively reporting an issue is to post in the ops-users mailing list a message with:

• A reproducible test case, attached to your message
• How to run this test case
• What is the behavior you observe when you run the test case
• What is the behavior you expect

But why a reproducible test case? The alternative is to describe the issue in plain English with maybe the help of code snippets. The problem with this approach is that it requires of people who will be helping you on the mailing list to understand the context of your problem, which might be trivial to you, but can be hard to grasp quickly for someone else.

You can provide two types of test cases:

• An XHTML+XForms file that runs in the XForms sandbox - This is by far the preferred way of submitting a test case. Most problems with XForms can be shown in one single XHTML+XForms file. If you need the XForms to call a service with an <xforms:submission>, you can simulate this by placing an XML file that contains the response from that service on a public web site, and changing the<xforms:submission> to point to that file. If you don't have a server of your own that you can use for this, a free hosting service like GeoCities will work.

• An application - An Orbeon Forms application is stored under resources/apps. Assuming you have your application under resources/apps/foo, it can be accessed by going tohttp://localhost:8080/ops/foo/. If you can't create a test case that runs in the XForms sandbox, create a simple standalone application under directory foo, zip the content of that directory, and attach it to your email in the mailing list as foo.zip.

In both cases:

• Make your test case as simple as possible. Remember that people who will be helping you on the list often don't have much time, and you are more likely to receive feedback that is useful if your test case only contains the minimum amount of code required to reproduce the issue.

• Keep your post focused on a single issue. If there are more issues you would like to report, post them in separate threads, or post the first one and wait to get that one resolved before you post the next one in another thread.

• At Nabble.

• At OW2. This is the primary archive but has an older user interface.

You can help by:

• Subscribing to the ops-users mailing list, and helping other people in community.

• Contributing to the open source effort. If you have a feature in mind and think it would benefit Orbeon Forms, you can implement it and contribute it. The best place to get started is to discuss your idea on the ops-users mailing list.

• Get a Support Plan with Orbeon. If Orbeon Forms is what it is today, it is in great part thanks to companies who have financially supported Orbeon, allowing Orbeon developers to be paid to work on Orbeon Forms and make it a better product. For more information, see Support and Service or contact Orbeon at info@orbeon.com.

Your support is greatly appreciated!

Yes. You find it on the OW2 site:

• Issues by highest priority (9 is highest - we use levels 9, 7, 5, and 3)

• Recently open issues

• Recently closed issues

Note that we put bugs and requests for enhancement (RFEs) in the same tracker category, and just prefix RFE descriptions with the string "RFE:".

In general, we recommend you do not add bugs or RFEs in the tracker yourself, as we may miss them, and you may introduce duplicates. Please discuss bugs or issues on the Orbeon Forms mailing-list first.

Yes! In fact we have two:

• A legacy wiki on the OW2 site.

• New documents on Google Sites. We are migrating documents from the OW2 site to Google Sites, as we prefer the WYSIWYG approach of Google Sites.

Feel free to add or make changes to the contents there. You can do so after creating a user (anonymous changes are not allowed). But please be considerate. You may want to discuss changes on the mailing-list first.

You can find information about the latest Orbeon Forms development on:

• Twitter
• the ops-users mailing-list
• the XForms Everywhere blog
• the wiki

In addition, the entire list of commits is available on github.