[samigo-team] Got an issue or a patch to propose for SAMigo 2.10 inclusion? Send it to this list.

[Keli Sato Amann]

Hello all,
Since 2.9 is nearing code freeze, after the last meeting, Lynn and I brainstormed about next steps for 2.10. We'd like to propose something fairly decentralized; to use the analogy of the newspaper classified section:

1) FIND A PARTNER: Do you have the same interests as someone else? We clustered people's top 3 issues so people could see if others were concerned about the same things. If you suspect someone else is interested in a fix (sometimes it's hard to tell because these were very high-level descriptions), start that conversation on this list. We started some of that conversation in the meeting, but on-list might be more inclusive for those who can't attend.

2) ADVERTISE YOUR WARES: Do you have a local fix for SAMigo that you think others might be interested in? It may not be in their top three issues, but might still be useful. If so,  send a note to this list. Those fixes should be captured in a JIRA item eventually and posted to the Proposed 2.10 page.

3) PROPOSE AGENDA ITEM: If someone wants to either talk about an issue (1) or about a patch (2) or something else (such as finishing up 2.9) during our bi-weekly meeting, send it to the list. We should probably send a note out a week before each meeting and if no one responds during a given week, we can cancel the meeting.

Thoughts? In the meantime, we'll start doing as we suggest--Lynn's planning on describing some work IU has done. About a week ahead, start sending agenda items, if none, we'll cancel by Monday. 

And no, we don't know when 2.10 will come out. If this entire team were working in an Agile method, we would concentrate on just a few key issues and take them from start to finish every month or so (maybe this is 2.9.1, 2.9.2, etc.). Perhaps that should go on the agenda.

Keli Amann
User Experience Specialist
Academic Computing Services, Stanford University