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

why does each repo, and not just each organization need to be listed? #5

Open
alanswx opened this issue May 7, 2015 · 1 comment
Open

Comments

@alanswx
Copy link

alanswx commented May 7, 2015

This is confusing:
"Each project published on a GitHub repository must be recorded in the DOC Social Media Application Tracking System."

It isn't using the vernacular of github, so it is confusing. I am assuming this meant:
"Each repo published on a GitHub organization must be recorded in the DOC Social Media Application Tracking System."

This would be much better:
"Each organization published on GitHub must be recorded in the DOC Social Media Application Tracking System."

The best would be that each GitHub organization needs social media approval. From there it would be easy for DOC to find all repos under that organization.

Making each repo go through approval is a bad idea for a few reasons:
1 - it is unnecessary extra work
2 - adding unnecessary work for people to create a repo is almost always bad for software design. It needs to be quick and easy, so that people share code, open it up, and keep it in source control. ie: some people I have talked to have wanted to open up and move dozens of projects in the first few weeks

@ianjkalin
Copy link
Collaborator

I personally don't consider Github to be a social media application, not in this work-related context. So I will need to investigate why this requirement exists.

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

2 participants