There is a public community repo with contributor guidelines

[izgeri]

AC:

• Populate the repo with the contributor license agreement, guidelines on contributing, info on how to get started finding issues, software quality standards and expectations, the process for submitting work and getting it merged
• Update existing repositories to refer to the central community repo as appropriate

[izgeri]

AC:

• [ ] The community repo has a README that:
  • [x] Introduces CyberArk Commons and has a "Welcome to CyberArk Commons" message
  • [x] Refers to Discourse, conjur.org, blogs.conjur.org
  • [ ] Talks about the three primary groups that have software in the cyberark GitHub org, and links to READMEs in separate folders for those three groups. There should be a bullet for each group that is involved - CyberArk Labs, CyberArk Conjur, and CyberArk Cloud Solutions - and the bullets should each link to a README in a folder for each group (eg labs, conjur, and cloud).
• [ ] We'll ask PMM for feedback on the main community README, and alert the cloud and lab teams to let them know to add content to their folders
• [ ] In the Conjur folder, there needs to be:
  • [x] A README for Conjur Open Source that refers to the content below and talks about how to file GitHub issues
  • [x] A folder for style guides (eg Ruby, Golang, Bash) that is linked to from the README - use existing style guides when possible, and if none exists pull existing content from the about-X channel in Slack and craft at minimum a simple style guide that links to others that we try to follow
  • [x] A CONTRIBUTING file with:
  • [x] Info on looking for CONTRIBUTING.md in other repos
  • [x] Info on contribution guidelines (eg fork, change, PR, etc)
  • [x] Guidelines on using the DCO (for MIT / Apache / BSD licensed repos) vs the CLA
  • [x] Special git-flow guidelines that we use, that community users should know about
  • [x] General info on typical testing patterns / how to run tests
  • [x] A copy of the CLA