Model ownership at team and org levels

[jeremiak]

Per issue #7, we want to model the notion of ownership a bit differently. Specifically, we want to make sure that we can capture the notion of an organization and a team within that organization.

Some keys have also been renamed:

• name has been renamed to id
• full_name has been renamed to name

[mbland]

This particular PR has greater ramifications than the others split out from #12. I'm hoping to get a chance to take a concentrated look a little later today, but I just remembered I've a couple perf reviews to do, so it may be Monday before I take a peek.

[mtorres253]

The idea behind this might be a good one. Lets discuss what these terms mean? We have asked the question in #data channel. Are teams part of organizations or vice versa?

[ultrasaurus]

Not sure I understand what problem we're solving here... could this issue be renamed "When looking at a repo, I would like to know who has responsibility for it" ? -- wouldn't that always be 18F? or are we saying that if we are writing code on behalf of agencyX that agencyX is the "owner" of that repo? or are we talking about the person or group of people at 18F who are responsible for moving it forward (which might include a hand-off to agencyX in the future)? seems like we have a lot of projects which might be started for agencyX but have multiple uses (which is actually our intent for a lot of the little libraries and tools we create).

Maybe there's a clearer way to express the problem....?

[mtorres253]

Still no response from #data. So, we believe that the use case here is that there are times when we (anyone at 18F who has questions about a repository or project) will want to know the organization that is responsible for the project repo (18F for example). By responsible we mean whichever organization is currently maintaining the repo. Then we would also want to know the individual or group within the organization that is actively working in that repo. If we agree to this use case, we can fill out the details of the user story and move forward.

[arowla]

We need to keep in mind here that repos can also be owned by individuals or groups of individuals, and are not always owned by a team. This is especially the case for a lot of older 18F repos that sprang to life independent of a partner project/team, and before working groups existed.