Comply is a community of security, infrastructure and engineering experts who set out to make SOC2 compliance easier to achieve. Whether it’s fixing bugs, improving features, contributors help make Comply the most convenient compliance tool.

How to get involved in the Comply community

Together, we can support a framework that allows you to efficiently prepare for SOC2 compliance. Here are a few ways to get involved in the Comply community.

DOCUMENTATION

Make Comply even easier to use

SLACK

Share insights, advice or questions with peers

CODE

Add a new feature or improve an existing one

GOT QUESTIONS?

Join Comply's Slack channel to swap notes with peers.

FEATURED CONTRIBUTORS

These are just a few of the people who help build Comply

michael_dasilve_headshote

MICHAEL DASILVA

YEXT | INFOSEC MANAGER

jonathan_hunt_invision

JONATHAN HUNT

INVISION | VP INFOSEC

tom_miller_braze

TOM MILLER

BRAZE | INFOSEC MANAGER

danny_graves

DANNY GRAVES

SPLUNK | SR MANAGER INFOSEC POLICY

justin_mccarthy

JUSTIN MCCARTHY

STRONGDM | CTO

david_aderonpe

DAVID ADERONPE

SPLUNK | SR MANAGER SECURITY RISK ASSURANCE

HOW TO CONTRIBUTE

To contribute, help resolve 10 issues on our GitHub page. Any comment or code that helps resolve an issue counts. After 10, we'll send you a pair of Comply SOCks to say thanks! And yes, we know we're bad at puns.

If an issue appears to be a bug, make sure that authors provide at the very least the following:

  • A snippet of code or a link to code available that causes the issue to occur. This could include a link to:
    • The production website that experiences this issue

When answering questions the following things are very useful:

  • Providing snippets of code that help fix the issue (i.e. new HTML markup, CSS rules, JS code, etc)
  • Linking to external blog posts, articles, Stack Overflow links that address the issue
  • Putting together a pull request (PR) that fixes the issue and linking to it in the issue it helps to fix.