2014-07-01 Meeting Notes

Samigo Working Group

July 1 2014

Meeting Information

Day/Time: Monthly, Tuesdays 11am PT / Noon MT / 2-3 ET / 18:00 UCT

Phone number: +1 812 856 7060; when prompted to "Enter the number you wish to dial," enter 2285713#

Titanpad notes: http://titanpad.com/samigo

Adobe Connect Room (for screen sharing when needed): http://breeze.iu.edu/samigo

Sign In:

Stanford: Keli,Karen

Jim Mezzanotte (ANI)

J Mariano Luján y Raúl Sanchez (Universiad de Murcia)

Neal Caidin (Apereo / Sakai)

Bryan Holladay (Longsight)

Archive of Samigo-team list

http://collab.sakaiproject.org/pipermail/samigo-team/

Agenda

I) What is the future of this working group? See end of this presentation (https://docs.google.com/presentation/d/1O5213_Wtw2cNbSNfZwZN6xDizBhrmMw71iZUP-j7sIc/edit?usp=sharing)

--Neal talks about dev/commits being taken over by core team

--T&L could have sessions set aside for design review. Not a place to drive an issue to get accepted, but a place to get input. Lessons is trying a kickstarter-like model.

--Samigo Team workflow: demo and get user feedback--useful. Meet to shepard things--maybe T&L meeting, then core team (10 Am eastern Sakai core team call or dev-list?) Discussion at call, decision on list. Right now it's in a transition point, so this needs to be worked out--Lydia and Karen can get looped in if core team needs their expertise. Anyone can add agenda item to etherpad prior to Thurs. Neal seeds the agenda, but if you have something, put something on agenda then attend the call to represent your issue.

2) do we need a separate mailing list from samigo-team? Its an extra list--it's a cc line. Keli will float idea of retiring it.

3) if need conference line, switch to Cauliflower? (Moot)

4) Potential work for 11--see slide 24 for JIRAS in

Also, SAM-2315 for new jQuery datepicker

--Jim thought it was some nice design work on settings but can't commit to taking it up

--Mariano and Spanish universities always worried about doing work but not having it adopted. So nice to know if Karen or Lydia will be available for help.

5) Neal says Sakai is probably going to move to GitHub in the next month. Git is control system, GitHub is front end. Workflow is different. Still a handful of committers, but easier to get visibility for contrib. Now you open a JIRA ticket, patch added is a tag that you add, core team filters for that tag. With Git, it should be more visible. Commit is associated with who generated code, rather than the committer; more traceable. Opens it up beyond Sakai community.

6) Maybe Keli will try to give UX feedback via T&L calls to get that part of workflow,