Skip to end of metadata
Go to start of metadata

Rice Collaboration

Recently Updated


The Kuali Rice Collaboration group is open to implementers, contributors, and anyone who is interested in implementing Kuali Rice in support of implementations of Kuali applications (KFS, KC, KS, etc) and for developing custom applications that leverage Kuali Rice.

This group meets regularly by teleconference as a venue for community engagement related to Kuali Rice efforts.

Below you can find resources for joining the community mailing list and this wiki. Additionally, you can find the agendas of past and upcoming collaboration group meetings.

Getting Involved

You will need to create a KIS account before you can join the mailing list, so that you can receive collaboration group emails, post comments, and add attachments.

  • Instructions for how to get a KIS account:
    • Go to and click on the "create account" link at the top of the page.
    • Fill out the requested information and then click submit.
    • After filling in all of the pages of information, you will be asked to check the email inbox for the account used to create your KIS account.  In this email will be a link to create your password for Kuali.  This password will work for all systems in Kuali, so make it one you will remember.
    • Follow the directions for creating your Kuali password.
    • At this point, it will ask you to log out.
  • Instructions for adding yourself to the Rice collaboration emailing list:
    • Log into KIS (see the login at the top)
    • Click the "Collab Support" link on the left
    • Click the "Kuali Rice - Technical Collaboration" link
    • Click the green "Add self to group" button

If you also want to be able to log bugs against Kuali project code, you will also need to get a Jira and Confluence account (this can be done at any time later).  See instructions at Getting Started with Kuali.

If you'd like to contribute code to the Kuali community, see Kuali Contributions Home page.

Learning and Troubleshooting

Collaboration Topics



You should always specify the version of Rice you are using, and any related information about your environment and customizations. You should always take the following steps before sending a support request, and include any pertinent information about your results in your request...

  • Verify that the issue exists, i.e. it is not the result of a misconfiguration on the part of the institution
  • Verify that the issue exists in the test environment, i.e. it still needs to be worked on
  1. Send an email to the collaboration group, asking for input. Provide a reasonable deadline, e.g. "please get back to me by Friday at 2 if you have any insight on this issue". (* See note below if you are beta testing the 2.0 version of Rice!)
  2. If you receive a response that helps to answer your question or resolve the issue and it is something that should be updated in the documentation, or if you do not obtain resolution to your issue via the collaboration list, enter a and reply to your collaboration list inquiry with a link to the issue.
  3. The Rice Team will...
    • Create an issue in the appropriate internal queue, so that the team can evaluate and schedule the work
    • Set the fix version appropriately on Jira issue, once the work has been scheduled for a release
    • Resolve the Jira issue when the fix is completed, and close it when the version is released

Collaboration Meetings

Conference Dial-in Number: (218) 844-0850
Participant Access Code: 429965#
Recurrence: Second Monday of every other Month, 3:00 - 4:00 PM Eastern Time

Collaboration Working Groups

During the course of the larger collaboration meetings there may be a smaller group of participants that want to dive deeper into a particular topic. This is where the collaboration working groups are formed.

The larger group can follow the work of these groups via the Wiki and the groups can reports back any interesting findings to the larger group.


The Kuali Foundation Contribution Model is evolving and each project is piloting the model to see how it works for them. Visit the Kuali Sharing space for information on contributing tangible items like code, documentation, features, or bug fixes. Contact us if you have any questions or would like to contribute developer time or other resources.

  • No labels