You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: