Details
-
Type:
Rice Enhancement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Unspecified Future Release
-
Labels:None
-
Rice Theme:Ease of Implementation
-
Priority Score:0
-
Priority - KFS:No Priority
-
Priority - KC:Low
-
Priority - KS:No Priority
-
Priority - Rice:No Priority
-
Theme:Development Ease of Use, Ease of Implementation
-
Effort Estimate:Low ~ 200 hrs
Description
Below are a couple of recommendations on improving the configuration of Rice.
1) Better error checking and reporting on configuration issues. Possibly a standalone tool that can be ran for validation
2) Make it easier for a client application to switch from using Rice "bundled" to integration with a shared standalone server
These are two older recommendations, we should spend some time (possibly in the KTI) revising this list and JIRA to better reflect what's needed today.
Attachments
Issue Links
- Trackbacks
-
![[Confluence: Kuali Rice]](/images/icons/generic_link_16.png "[Confluence: Kuali Rice]")
Copy of Roadmap Draft 2 - Hampton
Timelines The team is currently developing Rice 2.0. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2.0 Milestones. See details on our release cycles, i.e. frequency of major, minor,...
-
Kuali Rice Roadmap 2011
Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.1, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Kuali Rice Roadmap 2012
Draft Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.2, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Roadmap Draft 2
Timelines The team is currently developing Rice 2.0. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2.0 Milestones. See details on our release cycles, i.e. frequency of major, minor,...
Activity
Doesn't seem related to KRAD to me. The 4th bullet is the least compelling to me and mine.
Some of this (part of 2 and 3) will start to be addressed by KRAD, but not all. Items 1 and 4 would be need to be addressed later.
With the arrivial of KRAD this JIRA needs to be updated a bit. The KNS parts have been removed and on the Improved configuration of Rice bits remain. For historical purposes, the original description is provided here...
"From the KNS working group some recommendations to improve configuration of the KNS and Rice:
1) Better error checking and reporting on configuration issues. Possibly a standalone tool that can be ran for validation
2) Reduce amount of configuration by eliminating duplicate information and providing defaults where possible
3) Look into using convention more in the KNS so that configuration is unnecessary (look to Grails for ideas)
4) Make it easier for a client application to switch from using Rice "bundled" to integration with a shared standalone server"
removing myself as assignee
how relevant is this, given the work on KRAD? The 4th bullet seems the most compelling. This item could use a more holistic description with more context on the problem that is being solved.