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

Drop technical requirements for all team members #2581

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jameshochadel
Copy link
Contributor

Changes proposed in this pull request:

Team members without technical or compliance roles do not need to review technical documentation. They also may not have contingency plan roles.

Questions for @pburkholder and friends:

  • Is it safe to totally drop the CP requirement, or is it possible that non-(compliance, engineering) team members will have a CP role? For instance, the director.
  • Do non-technical team members need GitHub access at all? If not, we can remove the step in which they're added to the organization.
  • Is IR training required of all team members? (I'm assuming nonpublic information still is.)
  • I left "read security policies and procedures" in, since business unit may be subject to some controls. Is that right?
  • I left "read delivery process" in, but I'm not sure other teams (biz, program, eventually outreach?) use GitHub to track their work, so is it necessary for all team members to read?

security considerations

We must ensure that changes to this onboarding are in line with our practices as detailed in our SSP.

@markdboyd markdboyd requested a review from a team December 19, 2023 16:17
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

Successfully merging this pull request may close these issues.

1 participant