COmanage Developers List

[Heather Flanagan <>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Attending
Benn
Scott
Arlen
Heather

Notes:

1. Outreach discussions
   - Géant: went well; Mandeep offered good feedback on documentation
improvements (we have a reference manual, but what we need is an
introductory tutorial that describes the simplest use case), and
overall it seems to be a good fit for COmanage
   - NIH: f2f meeting planned for the end of this week


2. QA and Release Planning
We need to do better.  Suggest following a functional testing plan and
follow something like a Release Candidate set of release.  Team will
schedule a QA meeting after team returns from Japan. Maybe have a day
of QA at the I2GS


3. Provisioning identifiers into LDAP
How do we take application specific identifiers and provision them
into LDAP?
If we need those, then specific attributes holding them may be
reasonable.  But why do we need app specific instead of platform
specific that an application can use?  Because different apps have
different constraints on what they expect in an identifier.
Team needs to discuss the use cases a bit more to figure out what to
do net.
There is a one-to-one relationship between CO's and LDAP servers and
applications can't source from multiple LDAPs.
We need to make sure we know how to help those use cases (LIGO, Géant)
that come up against this.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJU2Nf1AAoJEBTitMubYA+RJ+MIALXU0Hbqlwvu2B5m5X86pRAU
7voojpFEyetX/qIxmWqWtaKcxcc2Wpqci3DcmxEGm5fl1KJO1YEkVpQlgOdzOnHg
ZUVbYd1TvAdAPZTfENuhSHUufdCoRaj8J1wePoQUPWW2mmj0aVj/LLjbryE4dQK3
kbWf4SBnOYrS5xFaZ+Mx4qwlA2rWyVJd392i1Xp8vWm0zmklHzAyS45vXVxiSDNE
Yh4qIWdqWXjlAXS96S2xSyYcdomCFUt8fZLTQ+TdQ7woI19QIvV6JwJyPmSnK/uj
dz+mge576o3BW7MUCKfe/vnYx9pMdUGy6nCF2d6MIZs5KsYIa6LyufLB6GLy0VI=
=W9oD
-----END PGP SIGNATURE-----