Welcome to the newly renamed Kuali Student Insider. This entry covers blog changes, documentation, Kuali Reference University, Kuali Days, and team highlights. Future updates will include KS news from the campuses. Note: Most links require login to KS wiki.
Project News
Blog Changes
Kuali Student Insider, formerly titled Kuali Student @ Berkley, will remain focused on project news and become a platform for news from participating institutions. Thank you to Tim (Berkeley) for his diligent and continuing work on this blog. Please share your thoughts on how this blog can meet your KS information needs.
Documentation with Doc-to-Help
Brian (CMU) has introduced his plans for KS’s documentation, including printable documentation, online documentation and JavaHelp context-sensitive online help (where appropriate in the system). Like Kuali Coeus and Kuali Financial System, KS is expected to use DocToHelp, a single-source Help authoring tool.
Kuali University (KuU) is now Kuali Reference University (KRU). The name change will be reflected in all new documentation moving forward, while the KRU team of Sarah (UMCP) and Audrey (UBC) will reflect this change in existing documentation as quickly as possible. All team documentation should also be updated.
Additionally, Sarah and Audrey are working with Scott S. (UMCP) to alter the KRU presence on the wiki. Soon, KRU will include a status dashboard and finalized documents will be in wiki format, in addition to MS Office documents for download.
Next Kuali Days: Nov 2009
There will not be a Kuali Days event in the spring of 2009 due to multiple projects resource constraints and restricted travel expectations for the industry. The next Kuali Days is scheduled for November 2009. KS will still be planning an in-person board meeting and possibly another Leadership Team planning session in the spring.
Team Highlights
Within the Functional Team, the Application Design Team has been developing a set of common Apps Design Guidelines, which will be reviewed first by the Services Team, followed by Use Case and UX and then moving on to Development.
The Services Team has re-released the LU Service. The team has been meeting with Application Design and Use Case to narrow operations and features of different services to be in R1 vs. R2.
On the Technical side, Leo (UBC) is getting started with team members on Reporting Architecture. A kick-off meeting is tentatively scheduled for Feb 10. A LU Development workshop was held this week in Berkeley (see live and archived streaming at http://ustream.tv/channel/kuali-student/). This will be a critical workshop to the development of the LU module. Members from UX, ADT, and Services were in attendance to address design questions, but Dev Team 1 spent afternoons coding.
Full Status Reports for the Functional Team and Technical Team are available on Confluence for those who would like more detail on daily activities.
Calendar
Jan
26-30 – LU Development Planning II – Berkeley
Feb
16-20 – LU Requirement Rules – Vancouver
Mar
16-20 – Technical Integration - TBA
1 comment:
Like the links to the people mentioned, that for that addition.
Post a Comment