See sprint 17 in Jira
Dates for Sprint 18
- Start August 12 2013
- Ends September 6 2013
Priorities
- KAGRA deployment (7 tickets open)
- 0.8.2 release (26 tickets open; release date revised from 29 August 2013 to 6 September 2013)
General discussion
- Grouper discussion
- Agenda planning for NYC F2F
- webinar screencast
Action items
- ask Dean about whether we should use adobe connect for screen cast
------
Scrum - 12-August-2013
What have you done since the previous scrum?
- Scott: grouper provisioner plugin; group membership (mostly) working, with a few questions to ask
- Marie: continue working on CO 645 and CO 643
- Benn: sponsorship is now available in enrollment flow and looks like all the other attributes; cut some enhancement tickets for sponsorship enhancements; CO-485
What are you planning to do between now and the next scrum?
- Scott: depends on grouper discussion
- Marie: continue to work on CO 643
- Benn: started work on debugging CO-640 and hope to have that resolved
What are your blockers?
- Scott: the provisioning infrastructure doesn't work as expected
- Marie: waiting to hear back from Benn on a code question
- Benn: no
------
Scrum - 15-August-2013
What have you done since the previous scrum?
- Benn: closed out a few small tickets and going through the 0.8.2 backlog and doing things in priority order
- Scott: continuing to work on the grouper provisioner plug in; has the first cut of provisioning memberships done, but the status isn't hooked yet
- Marie: committed changes for CO-645; sent out the screenshots to the list
What are you planning to do between now and the next scrum
- Benn: CO-311 and CO-577
- Scott: vacation
What are your blockers?
- Benn: no
- Scott: time
- Marie: Benn had some comments; need to discuss on call to know next steps
Dev topics
- Screen shots from Marie
I've been working on the layout of the CO People index page and it looks something like this:
I'll keep working on it. Multiple people's boxes can be expanded at once. I like having the admin buttons on the closed bar for easy access. Thoughts? Anything obviously missing you want included?
- final comments: would like this view to make it easy to look for a person in a population, visually and quickly identify that it it is the correct person (and so it has just enough identifying data), and having gotten that far, click to get to a page that has all of his details
- name, email, and maybe some extended attributes, but NOT the validity dates, NOT the created/approved parts
- other groups may find different information identifiable - maybe make this configurable?
- this also suggests we need to move search up higher in the priority list (functional roadmap adjusted)