Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

  • Attendees (Lisa, Brian, Scott, Jon, Thomas(phone))
  • Issues Summary:
  1. If we don't have any issues, then it may not be worth other's time to discuss any.
    • Brian
    • 0 votes
  2. Created functional spec for Samigo, sent to Kirk and Sandra for review. This will be sent out to us soon, also. She needs help setting up MySQL, to look at the Samigo tables.
    • Lisa
    • 0 votes* *Scott will help her set up MySQL locally
  3. What is the formal process for giving feedback from these XP meetings? Do we give them directly to Kirk, set up JIRA's, etc?
    • Scott
    • 0 votes, however resolved this issue by comments from the group (see below)
  4. Samigo import/export validation chokes on white spaces (e.g. cannot have html syntax in questions). Thomas wants to look more into this.
    • Thomas
    • 0 votes
  5. Wanted to know more about how to follow-up on the results of these meetings, and how we can put efforts into changes in the Sakai API's so that the framework group may know about them (e.g. Gradebook student id vs username issue)
    • Jon
    • 0 votes
  • Covered all issues, however none got votes because they were mostly non-issues or any that needed further discussion.

**RESOLUTION(s)
There were several decisions made by the group with respect to the XP meeting format. They include:
a. Each programmer does not have to have an issue each meeting. This will allow us to discuss the important issues in detail, rather than spending the earlier part of the meeting trying to decide on all issues.
b. We will have a process for submitting issues beforehand, so that everyone has the ability to comment on and look at the issues beforehand. This will allow more time dedicated to the meetings to solving the issues, and thinking about them. The process described above will be similar to the following:
1. Each programmer will add their problems in Confluence (as comments), so that everyone can look at them.
2. Issues that are not resolved during meetings, and/or need to be bubbled up we should make the necessary people aware (e.g. Kirk and/or Tom)
3. JIRA entries will come out of this process, without an assignee, to track the issues that come out of the XP meetings.

  • No labels