Working Group is an hour
1. Spring I2 meeting (6 functional weeks)
- what are we demo'ing? review demo script
Goal is = 50% shiny, 50% function
- UI work that Marie did must be in the code base = (both) - MUST
- Grouper integration = NICE for I2, MUST for LIGO
- CO and COU has to be reflected in to Grouper
- replace CO groups controller
- enrollment workflow demo = (both) - MUST - Need at least 1 real, complete LIGO flow
- process by which someone gets added to COmanage database
- approval
- notifications (NICE)
- provisioned via OpenLDAP via SQL, showing a wiki (I2)
- provisioned via OpenLDAP directly and in Grouper, Kerberos (LIGO)
- COmanage Directory
- real-time reconciliation match ("search as you type" functionality) (I2 - NICE and SHINY)
- COmanage Web Directory/White Pages = (more for LIGO) NICE
- editable COmanage registry entry
- Date-based off-boarding = (I2 = Very NICE)
- Embedded Discovery Service (CO-219) = (NICE and SHINY)
After April (Backlog) :
- Audit History (will be partly handled by integration with Grouper 2.1 and its own real-time auditing)
- Person expiration and full de-provisioning workflow
- Search box
- Unit testing
- De-duplication/Merging of user info
- Photos
- Federated Groups
...
Summary of MUSTs, assignments and timelines
- finish necessary provisioning for demo = Benn
- UI work that Marie did must be in the code base = Marie, 2 weeks
- Enrollment - add to DB = Benn, 1 day
- Enrollment - OpenLDAP, wiki, Directory = Benn, 1 day
- Approval = Benn, 5 weeks
- Grouper - CO and COU = Scott, 4 weeks
- Grouper - replace CO groups controller = Scott, 2 week
- CO/COU document - Heather, 1 week
If we have time between now and April:
- real-time reconciliation - Benn
- date-based provisioning - Benn
- notifications
- OpenLDAP, provision, Kerberso
- Directory
- Directory link to registry
- Deprovisioning
- EDS - Scott
Will need a doc that explains CO versus COU, a stock slide and a full doc describing the difference between the two
"Isn't the CO / COU distinction just different groups? No, it's groups WITH workflows; it's assurance levels, it's management of data and processes at a certain level"
2. Mapping COmanage Registry v.5, v.6
- .5 is going to be feature-add; .6 will be cleanup
(over lunch) Reconciliation workflow vs LIGO
Vocabulary
- we have a tendency in COmanage and I2 to use very precise language, which makes it harder for mere mortals to understand; products like Globus Collaborate overloads terms, to the comfort of their primary audience
- In having a CO/COU document, we still need to consider more broadly how we're going to simplify language to market to non-IT communities
Monday for Proj Mgr:
- Reconcilation workflow v. LIGO requirements
- what to announce to the community list (as related to I2SMM)
- Petition templates for common enrollment patterns
- Is adding an additional role just another petition? If so, how does it vary from the current model (if at all)?
- COmanage Directory v0.2
- COmanage Demo 3 / demo.co.internet2.edu
- GUI design
- Switching to div layouts from table layouts
- What goes in a URL? (See background, below)
- And, relatedly, CO-247 (CO selector - persistence of selected CO)
- Rationalization of the REST request and response structures
- CO-261 and strategy for fixing validation issues after CakePHP upgrade
- svn vs git, continued
- Silver requirements as they relate to/impact LIGO/COmanage decisions
- Org identities, reconciliation, and deletions