Mailing list readme

[krisnova]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind flaky-test

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area engine

/area rules

/area deployment

/area integrations

/area examples

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[poiana]

@kris-nova: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[poiana]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kris-nova

If they are not already assigned, you can assign the PR to them by writing /assign @kris-nova in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[poiana]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• e00181d Merge pull request Merging for 0.5.0 #174 from draios/dev
• d1b6b2b Merge pull request Merging for 0.6.0 #229 from draios/dev
• b0ae29c Merge branch 'dev'
• 809d20c Merge pull request Merging for 0.7.0 #246 from draios/dev
• 74556e5 Merge branch 'dev'
• e8aee19 Merge remote-tracking branch 'origin/dev', 0.8.1
• 3ee7663 Merge branch 'dev'
• 94df00e Merge branch 'dev'
• 2a0911d Merge branch 'dev'
• b496116 Don't make driver compilation fail when kernel is compiled with CONFIG_ORC_UNWINDER or CONFIG_STACK_VALIDATION. (Don't make driver compilation fail when kernel is compiled with CONFIG_ORC_UNWINDER or CONFIG_STACK_VALIDATION #362)
• 6acb13e Merge branch 'dev'
• 4707103 Merge remote-tracking branch 'origin/dev'
• 5e38f13 Merge remote-tracking branch 'origin/dev'
• ff299c1 Merge remote-tracking branch 'origin/dev'
• bd7a973 Merge branch 'dev'
• ddf55d3 Merge remote-tracking branch 'origin/dev'
• 62c1a04 Merge remote-tracking branch 'origin/dev'
• 44e88f2 Merge remote-tracking branch 'origin/dev'
• e546555 fix k8s install issue (fix k8s install issue #506)
• f4b0b3c falco.yaml: change default program_output action (update program_output example #507)
• 36a095c Merge remote-tracking branch 'origin/dev'
• db41945 Merge remote-tracking branch 'origin/dev'
• 807c00b Merge remote-tracking branch 'origin/dev'
• ff376d3 Merge remote-tracking branch 'origin/dev'
• 194a017 Merge remote-tracking branch 'origin/dev'
• 75b816d Merge remote-tracking branch 'origin/dev'
• 670736d Merge remote-tracking branch 'origin/dev'

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[poiana]

@kris-nova: There is not a label identifying the kind of this PR.
Please specify it either using /kind <group> or manually from the side menu.
In case you do not know which kind this proposal is please mention the maintainers using @team/maintainers.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.