Improve contributor experience

[BradleyBoutcher]

• Added several clarifications and high-level descriptions to make navigating our docs easier, and their purpose clearer

[izgeri]

Here are some notes from going through this branch right now:

• In the main README:

  • [x] We shouldn't have "CyberArk Commons" at the top of the TOC - it means everything else on the page is a sub-bullet, and truthfully that first bullet doesn't matter. Can you remove it and revise the TOC to start with a top-level "Welcome to the CyberArk Commons" bullet?
  • [x] In "Communicating" we should either write out the discourse link (and have it be a link) or just have the Discourse link - but we shouldn't have both
  • [x] In "Contributing" - it would be valuable to say a bit more about what to find in that doc. I like how Kubernetes does it here - where they have succinct bullets with what's in that doc, and each bullet links to the doc section. Can we do something like that too?
  • [x] We can remove Cloud Solutions for now - I'm still working with them on this, but they don't have their content ready yet so we will add them back once they are ready.

• In the main CONTRIBUTING

  • [x] The TOC here would also benefit from having its top level be "Where do I start?"
  • [x] "Reporting an issue" makes more sense before "Finding issues to work on", since the latter topic is closely related to the next one

• In the Conjur README

  • [x] The main "CyberArk Conjur" heading should not be a link
  • [x] The discourse bullet at the bottom should have a link to discourse

• In the Conjur CONTRIBUTING

  • [x] The TOC top level should be "Before you get started"
  • [x] The "Sign the CLA" bullet would be better reworded as "Review the contributor license agreements"
  • [x] "Find an issue you'd like to work on using this guide." could just be "Find an issue you'd like to work on" where Find an issue links to the writing on that (it's not really a guide)
  • [x] bullets 3 and 4 in "Find something to work on" could be merged. They could instead be something like:

    Locate the project's CONTRIBUTING.md file, which documents contribution guidelines and in particular details the steps required to run, build, and test the project. There are usually development prerequisites in these guides that are important for getting set up. Can't find a project's CONTRIBUTING.md? Please create an issue or submit a PR to create one!

  • [x] "Before you get started" should just contain "Review the contributor license agreements" and "Read the code of conduct"
  • [x] "Start contributing" should have a section on "Reporting an issue" and a section on "Contributing to code" that includes "Find something to work on" and "Working on issues". The "Reporting an issue" section can have more information about how an important way to contribute is to report an issue or to add your own experience to an existing issue, and interacting with us this way is strongly encouraged. The current text under "Start contributing" can be moved under "Working on issues" and revised a bit to work under there.
  • [x] The "Git-flow guidelines" and "Open source guidelines" can be in an "Appendix" section, so it's clear by the time someone has reached them they're at the end of the main document
  • [x] All sentences should end with a period.

• Misc

  • [x] We don't have any notes about how we use the issues in this repo (eg https://github.com/cyberark/community/issues) - I've been logging issues in here for community initiatives that we're doing to improve the community UX, so it's a good place for community members to watch to see what we're planning. It might be worth putting info about that somewhere too (any idea where?)

[BradleyBoutcher]

@izgeri For the note on how we use issues in this repo - I added a section in the contributing doc for it. In the readme, we briefly mention that many projects are open to contributions, even this on, and link to the contributing doc. I think that's a natural place for it to sit.