Benn: working on 226 (petitions on hold for the moment)
Marie: worked on CO-234, found other bugs while trying to reproduce this one
Scott: was working on CO-229, then distracted by trying to reproduce Marie's problem, but in doing so discovered CO-261
What are you planning to do between now and the next call?
Benn:
Marie:
Scott:
Any impediments/stumbling blocks?
Benn: functional problem, and now a topic for dev
Marie: needs input from Benn regarding text/screenshot of bug he found doc'd in 234
Scott: none
Development
a COU admin should be able to see CO people, so they can be added to the COU, but you should not be able to edit (remove or change their membership in other COU) them or their name
ignoring org people entirely, when a person is in both COU (of the 2 COU in a CO), can the name be changed? Yes
what we're trying to do is tease out the assumptions in CO versus COU; does the existence of a COU as part of a CO imply something about the collaborative relationship and associated priv's available?
any COU admin has read access to the entire CO, but write access to only their COU
CO-261: the user that goes to edit the CO identity will receive an error to recheck their submission; sort of related to CO-242, an add method having a similar problem