2013-07-01 scrum call
Attending
- Benn Oshrin
- Marie Hunyh
- Scott Koranda
Items covered for this sprint
Scruminess
- What have you done since the previous call?
- Marie: closed out a bunch of tickets, finished everything in sprint16
- Scott: on vacation
- Benn: working on CO-283 (default values for enrollment flows); about 2/3 done at this point; note that there are two ideas that are covered under "default values for enrollment flows" - are we prepopulating with identity we already have (account linking model) but having an enrollment flow have a hardcoded value for something like "student" is a different kind of default - Benn needs to write some documentation on this
- What are you planning to do between now and the next call?
- Marie:
- Scott: working on getting the gwastrony.org instance updated to the trunk and using it for a particular use case (see Questions section)
- Benn: continue working on CO-283
- Any impediments/stumbling blocks?
- Marie: not sure what else to do with the test scaling ticket? not seeing anything else that is UI related (that we don't otherwise have tickets for already) - need to add this to our F2F discussion next week
- Scott: haven't talked about it yet
- Benn: javascript regular expression
Question
- "using the current trunk for a "pre-production" exercise"
- Scott proposses that he updates gw-astronomy.org to the trunk, create a LIGO-KAGRA CO, then take a list of about 50 KAGRA users and add them to the CO (name, email, ePPN) by hand; would also configure the COmanage deployment so that the info about the CO people is put in the view in the database that grouper could consume as its subject information (that's been documented in our install instructions); this would allow a grouper deployment that would let Scott create a group appropriate to his needs - the idea is to have a Shib IdP also on that same box but configured as an attribute authority, look up in LDAP provisioned by group
- Purpose of this exercise is to make available to a particular application via a SAML assertion the list of KAGRA individuals in a group
- will also need to have these users in LDAP
- main question: with the current trunk, can Scott get the info about the ePPN in to LDAP in some way so that he can have the group membership also go out? (Benn) yes, if you store ePPN in the identifiers table (this might be in 0.8, but go ahead and use trunk which will also get you Marie's work and a few other things); this is part of the LDAP provisioner; make sure to update the database schema if you aren't starting from scratch (there will be a schema change for what Benn is doing right now, but that won't impact what Scott needs right now)
- UI should also be fine - no commits in the past week should be problematic
- Need to determine what should be on Marie's list for the remainder of the week
CO-472, CO-608, CO-475, CO-222, CO-567, CO-619; also look at 0.9 for a potential source of things to do
- changing variable names = proposal: start a new variable name convention for all newly added variables, and changing older (un-conventional) variable names when we have to
- concern - variables cross many files, and when we do want to change them, we have to do some extensive work to find all the places those variables might be hidden
- counter - the readability of the new code makes it worth it; at the point we do decide to refactor (which we really should do someday) it will be worth investing in a good IDE and let the IDE do it
- the big wildcard is the cake 3 framework; at that point, there are a significant number of under-the-hood changes; if we stay on the cake framework when 3 comes out, there will be a significant amount of rewriting of code
2013-07-03 scrum
Attending
- Benn Oshrin
- Marie Hunyh
- Scott Koranda
Items covered for this sprint
Scruminess
- What have you done since the previous call?
- Benn: no change since last call
- Marie: worked on CO-222, making good progress
- Scott: no significant progress, but given some thought to ePTID; add to the agenda next week (will need to look for ePPN instead of ePTID)
- What are you planning to do between now and the next call?
- Benn: no change since last call
- Marie: will continue to work on CO-222
- Scott:
- Any impediments/stumbling blocks?
- Benn: no change since the last call
- Marie: none
- Scott: time
Dev business
F2F agenda bash and logistic review - see Dev 2013-07 Milwaukee