Skip to end of metadata
Go to start of metadata

What about the Rice framework would you like to see improved to make it even easier to adopt and learn?

  1.  Installation:

    1. Better installation instructions
      1. several copies appear to be online without obvious way to know which is the latest
      2. Links bring up glossary first!
      3. Searching for Rice "help" with error messages (in Google) leads to old message boards and old documentation (current message board and docs are somewhat "hidden" in the KIS site).
    2. Simpler process:
      1. Downloadable VM image.  See
      2. Simple command-line process to get Rice up and running quickly
      3. Embedded database.
      4. See example from Min-It Rice at Example extract is below:
        1. The min-it Rice platform goal is to significantly reduce the installation time associated with getting the Kuali Rice framework up and running for both evaluation and development and provide a distribution platform for XO tools and extensions in the future. 
        2. Quick steps to install & run min-it Rice
          1. Click here to download the and extract to your c: drive
          2. From the file explorer click c:\xorice\start_server.bat
          3. From your browser address bar type {*}http://localhost/\* (http://localhost/*) - you'll see the XO home page
          4. For help check the \xorice\readme.txt.  To log into the Rice Portal use the "admin" user.  (This could be expanded to include sample apps, and perhaps Kuali Apps.)
      5. UI tools to help with data migration and management
      6. a more dynamic “portal” framework where client apps like KC and KFS can customize the kuali portal w/o essentially copying all the rice ui components
    3. Message board shouldn't be "behind" a KIS account - can't think of one mainstream software company that I have to register for to see a message board.  Google searchers should find the content and not require sign-in to see it (error message info).
  1.  Development

    1. Code generation tools
    2. self documented code/settings
    3. Better developer documentation
      1. Google searches bring up mostly old documentation! 
      2. never enough of it
      3. more intuitive
      4. “cookbook” for examples - how tos: create an edoc lite, create a simple workflow, create a KRMS agenda / rules
      5. What Rice tables are required for standalone app DB schema?
      6. wiki information cleaned up and posted to web site (being done in the “docbook” now/soon?)
    4. Build the UI without having to touch the XML, forms designer applications or other tools for building the apps without requiring a bunch of XML to be typed in
  2. Project Creation

    1. Update project generation tool
      1. needs to be updated for KRAD
    2. Project artifacts and conventions 
    3. Better integration and consistency between KRAD and eDocLite applications
    4. easy to use visual tools for basic users to create, update, and deploy eDoc lite documents
    5. Project module generation tool
    6. Document generation tool
      1. Doc files
      2. Roadmap item exists for this: KRRM-129 for KRAD
        1. at least one tool exists to help with this, but its old and command-line only
        2. KC has a tool that does this reading from a DB table
        3. Rice has a tool for generating objects for services
  3. Deployment

    1. Guidelines/suggestions for production environment
      1. UC Davis example -  
      2. worth considering a survey of active schools per project?
    2.   Easy to use visual tools for basic users to create, update, and deploy eDoc lite documents
    3. Performance issues and information?
  4. Other

    1. Rice test drive
      1. - updated daily
      2. being done for 2.0 - jira: 
    2. (Doesn't have to do with the Rice framework, but employing a technical evangelist would help!  Technical evangelists publish articles, tutorials, and little projects that they've created to help people get started, and show people the value they can get by adopting the product.  See for example, the adobe flex evangelist's blog:
    3. Brainstorm input from the Rice developers
  • No labels