Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorganizing teams #7

Open
cameronmcefee opened this issue Jul 24, 2013 · 14 comments
Open

Reorganizing teams #7

cameronmcefee opened this issue Jul 24, 2013 · 14 comments

Comments

@cameronmcefee
Copy link

cc @CoderDojoSF/owners @CoderDojoSF/mentors

I'd like to do some restructuring of this org's teams to optimize our permission stuff a bit so that more people can be involved in the admin processes.

  • Make the owner team (full admin) down to GitHub personnel only since this org represents GitHub itself. If anyone objects, feel free to voice your concern.
  • New "Organizers" team. This team will have access to a private repo which will contain details for admin stuff like email/social accounts, as well as process docs for keeping the dojo running. This one will be limited to only people who have committed to helping out. This will help:
    1. Keep a limited number of people accountable for specific tasks.
    2. Limit the number of people with access to sensitive info at a given time.

In an effort to keep things moving along, I'm going to make these changes now. If there are any concerns regarding this issue, we can address them as they come.

@donjo
Copy link
Member

donjo commented Jul 24, 2013

👍

@mikefowler
Copy link

Approve.

@KartikTalwar
Copy link
Member

👍 If you want to create a repo, you'd have to proxy the request to an admin. Which makes sense?

@cameronmcefee
Copy link
Author

Oh hmm… I'll need to look into that. I'd hate to stall people by preventing them from creating repos. Mostly I just want to restrict access to admin login type data to only the people that need it.

@KartikTalwar
Copy link
Member

Yeah, and the same goes for editing existing public repos. You'd have to fork it to your personal account and send a PR

@cameronmcefee
Copy link
Author

Hmm that sucks. Alright, let me see if I can figure out a better solution.

@cameronmcefee
Copy link
Author

How does GitHub even work? Ok, I think I've got it set up so people in @CoderDojoSF/mentors should be able to create repos. If you aren't able to, let me know.

@KartikTalwar
Copy link
Member

Yup, @CoderDojoSF/mentors can now create repos but, they don't have access to public repos

@cameronmcefee
Copy link
Author

Wat? @KartikTalwar so you can create repos but you can't push/pull to existing repos?

@KartikTalwar
Copy link
Member

@cameronmcefee yeah, because the mentors team is restricted to mentor-tickets repo

@cameronmcefee
Copy link
Author

Ugh, right. Ok, let me fix that too. If you create a new repo, do only you get access to it, or do all mentors, I wonder.

@KartikTalwar
Copy link
Member

I believe all team members with push and pull access do.
On Jul 24, 2013 11:09 AM, "Cameron McEfee" [email protected] wrote:

Ugh, right. Ok, let me fix that too. If you create a new repo, do only you
get access to it, or do all mentors, I wonder.


Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-21504341
.

@cameronmcefee
Copy link
Author

Alright, all the repos are part of the mentors team now. Sorry if you got notifications for each of them. Hopefully this resolves things. If not, give me a shout and I'll see if we can improve the process further.

@KartikTalwar
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants