COmanage Developers List

[Heather Flanagan <>]

Thanks for the feedback, Scott.  It has been incorporated.

You wrote a CO vs. COU vs. Group doc a while back.  Should that be kept in 
the child pages?  If so, either that doc or my doc needs to change its name.

-Heather 

----- Original Message -----
From: "Scott Koranda" 
<>
To: "Heather Flanagan" 
<>
Cc: "comanage-dev" 
<>
Sent: Sunday, April 22, 2012 5:36:22 AM
Subject: Re: [comanage-dev] updated CO vs COU doc

Hi,

> Hi all -
> 
> As mentioned on the dev call today, here's the latest CO versus COU draft, 
> incorporating feedback from Ann and Tom B.
> 
> https://spaces.internet2.edu/display/COmanage/CO+vs.+COU
> 

My apology for taking so long to get back to you.

I think this looks good. In particular I like this:

If you have an organization with common goals and common
policies, and yet within that understanding you have unique
requirements that the different groups will have different
paths to joining and participating in those groups, you have a
CO that contains COUs.  If you have one, common set of
policies that define how individuals are added or removed from
the CO, then you do not have COU even though you may have
groups for simple access control.

I have only minor comments:

- I would remove the opening phrase "Within the COmanage
  terminology..." and just start with "This document clarifies
  the difference between a CO and a COU and why a COU is..."

- I would change "combined with workflows" to be more
  specific by saying "combined with enrollment and
  de-enrollment workflow" or "combined with onboarding and
  offboarding workflows"

I made one edit myself, changing "gravitation waves" to
"gravitational waves"--this is an important difference to
anyone in our field. 

Thanks,

Scott