"Serving the core values of higher education"

The Kuali community shares a set of strong values that guides how we work:

Open Source Licensing - Kuali values free information, and distributes its software under the Educational Community License, Version 2.0 so that anybody can download and use Kuali software without paying any licensing fees whatsoever.

Community Source Development Model - Kuali software is developed using a community source model to coordinate development efforts. This practice allows both large universities and small colleges to have an opportunity to impact software development, insuring that both big and small players can have an influence over Kuali projects.

Collaboration - The Kuali Community's success comes from the members' ability to collaborate, which entails a number of underlying values including listening, introspection, objectivity and thoughtful communication.

Transparency - To a large degree, Kuali's communications and collaboration infrastructure is open to the public. Although certain information may be protected for various reasons, Kuali strongly values making as much information publicly accessible as possible.

Modularity - Kuali aims to produce module software, allowing adopters to pick and choose the functionality they require

Scalability - Kuali values scalability, and produces software that can serve both small and large user groups.

Distributed Software - Kuali's software architecture is guided by the principal of distribution, resulting in loosely-coupled components that allow for flexibility and a more rapid response to changes in business needs

Re-usability - the Kuali community works hard to identify common needs between different Kuali applications, and produce assets that can be easliy re-used throughout the community.

Accessibility - Kuali strives to produce software that is accessible to people who use screen-reader technologies, and is associated with the The Fluid Project.

Functionally-Driven Projects - Kuali's projects are driven by the functional needs of the potential adopters of the software, usually through governance groups caslled Functional Councils.