<!-- /* Font Definitions */ @font-face {font-family:"Times New Roman"; panose-1:0 2 2 6 3 5 4 5 2 3; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:50331648 0 0 0 1 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman";} table.MsoNormalTable {mso-style-parent:""; font-size:10.0pt; font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->Bostong Sakai Conference EVALSYS BoF
July 8, 2009\\
Attendees:
Sean DeMonner\\ \\
1. Coordination of build process across institutions
\- UMD, UCT, U-M, Cambridge, rSmart (?)
\- Process:
\- post to list to make changes
\- monthly meetings
\- services layer testing; code path testing\\
2. Decision making around changes to trunk
\- branches should be short term
\- do features need to run locally before going to trunk
\- demoathon of various\\
3. Coherent user design process (Stephen)
\- Aaron playing backend lead
\- Front end is suffering\\
4. Sakai 3 migration plans\\
5. Response rates\\ \\ \\
Action Items:\\
\- Sean: report to group on U-M findings
\- Sean: Set up monthly technical review
\- branch merges, Sakai 3 migration (RSF .73; service layer, tool itself)
\- Ellen & Stephen: coordinate UI discussion
\- Stephen: get resource to document current functionality and use; gaps
\- All: demoathon Thurs night |