Hey Michael, here's my best to answer your questions: > Is there specific existing documentation on this subject I've > somehow missed, which would obviate the need for a more complex > answer? Have you seen our feature's pages? https://github.com/features/projects
> My intuition is that a personal account creates an organization, and > within that organization are teams. Teams seem like a collection of > permissions applied to private collaborators. Is this accurate? Yes. > Do repositories belong to the organization, or to an account? That > is to say, (for example) would there need to be a company account to > which the repositories belong, plus an organization? Or just the > organization? The organization in effect becomes an account that's managed by one/many personal accounts. The company would be an organization. Repositories belong to the organization. > Does the creation of an organization mean that for any given private > repository, there are an unlimited number of collaborators allowed (is > this what "unlimited teams" means)? Yes. There are no collaboration limits within organization owned repositories. > Do employees still have their own GitHub accounts (I assume > otherwise "normal" accounts owned by them), but are also then granted > access to the company's repositories? That's correct. > If employees already have their own personal account associated to > their personal email address, is adding another email address to the > account (i.e., their company email address), combined with some local > git configuration on their workstation the right way to segregate > their own personal work on their own repositories from the work they > do on a company repository? That's definitely one way. They can add many email addresses to connect commits to their GitHub accounts and edit the git config in individual repositories, or the global git config on their workstation. Alternatively, many people simply commit to work repositories using their personal email address. This is really all up to you and your organization — GitHub will support pretty much any workflow you choose for identifying commits locally. -- Kyle Neath http://github.com/kneath On Sunday, February 20, 2011 at 11:39 AM, Michael Wehner wrote: > I'm attempting to stage a small coup at my company by switching our > version control system from subversion to git. I've decided that the > best way to do this is to make the switch for one new project I'm > spearheading, hopefully making it a model that our other existing > projects can follow. > > Before I can commit resources to this, I need to better understand the > relationship between teams, collaborators, and accounts on GitHub. > I've searched around a fair bit for more information on the topic of > teams and organizations, but am coming up short. > > To that end, here are a few questions I have, but as I'm mainly just > trying to understand the overall relationships and workflow, they can > be ignored in favor of a better explanation than the answers might > afford. > > * Is there specific existing documentation on this subject I've > somehow missed, which would obviate the need for a more complex > answer? > > * My intuition is that a personal account creates an organization, and > within that organization are teams. Teams seem like a collection of > permissions applied to private collaborators. Is this accurate? > > * Do repositories belong to the organization, or to an account? That > is to say, (for example) would there need to be a company account to > which the repositories belong, plus an organization? Or just the > organization? > > * Does the creation of an organization mean that for any given private > repository, there are an unlimited number of collaborators allowed (is > this what "unlimited teams" means)? > > * Do employees still have their own GitHub accounts (I assume > otherwise "normal" accounts owned by them), but are also then granted > access to the company's repositories? > > * If employees already have their own personal account associated to > their personal email address, is adding another email address to the > account (i.e., their company email address), combined with some local > git configuration on their workstation the right way to segregate > their own personal work on their own repositories from the work they > do on a company repository? > > Thanks in advance for any assistance with my questions. > > - Michael Wehner > > -- > You received this message because you are subscribed to the Google Groups > "GitHub" group. > To post to this group, send email to github@googlegroups.com. > To unsubscribe from this group, send email to > github+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/github?hl=en. > -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to github@googlegroups.com. To unsubscribe from this group, send email to github+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/github?hl=en.
