From bad0864796cfcaaadad59dd878f1f7e9eafa684b Mon Sep 17 00:00:00 2001 From: Stefano Bonicatti Date: Tue, 3 Dec 2024 19:53:42 +0100 Subject: [PATCH] Update expired Slack invite --- .../2017-10-24-monitoring-macOS-hosts-with-osquery.md | 2 +- .../blog/posts/official_news/2017-11-16-building-community.md | 2 +- .../posts/official_news/2020-09-10-linux-arm64-beta-support.md | 2 +- src/pages/Home/Home.js | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/data/blog/posts/community_articles/2017-10-24-monitoring-macOS-hosts-with-osquery.md b/src/data/blog/posts/community_articles/2017-10-24-monitoring-macOS-hosts-with-osquery.md index 5c88ee6..9d41aed 100644 --- a/src/data/blog/posts/community_articles/2017-10-24-monitoring-macOS-hosts-with-osquery.md +++ b/src/data/blog/posts/community_articles/2017-10-24-monitoring-macOS-hosts-with-osquery.md @@ -42,7 +42,7 @@ The official package includes osqueryd, osqueryi, and a launchd agent that maint ## Getting Help -Documentation is available at [osquery.readthedocs.io](http://osquery.readthedocs.io). An active Slack community is available for discussion and support, request an [auto-invite](https://join.slack.com/t/osquery/shared_invite/zt-1wi6cdgf7-zR2wt7FZ0ClHj6tEym6KFQ). +Documentation is available at [osquery.readthedocs.io](http://osquery.readthedocs.io). An active Slack community is available for discussion and support, request an [auto-invite](https://join.slack.com/t/osquery/shared_invite/zt-1wipcuc04-DBXmo51zYJKBu3_EP3xZPA). ## Exploring Host Internals with osqueryi diff --git a/src/data/blog/posts/official_news/2017-11-16-building-community.md b/src/data/blog/posts/official_news/2017-11-16-building-community.md index 6c79518..f702bc3 100644 --- a/src/data/blog/posts/official_news/2017-11-16-building-community.md +++ b/src/data/blog/posts/official_news/2017-11-16-building-community.md @@ -24,7 +24,7 @@ We passed 10,000 GitHub stars, passed over 1000 users in Slack, and have 172 con ## What could improve our community and how can you be involved -* The best way to contribute is to [join our Slack](https://join.slack.com/t/osquery/shared_invite/zt-1wi6cdgf7-zR2wt7FZ0ClHj6tEym6KFQ) and ask good questions and help others. Be kind, assume good intent, and share your knowledge. Double check assumptions and skim the [documentation](http://osquery.readthedocs.org/en/stable/) to guide others to reference materials when available. +* The best way to contribute is to [join our Slack](https://join.slack.com/t/osquery/shared_invite/zt-1wipcuc04-DBXmo51zYJKBu3_EP3xZPA) and ask good questions and help others. Be kind, assume good intent, and share your knowledge. Double check assumptions and skim the [documentation](http://osquery.readthedocs.org/en/stable/) to guide others to reference materials when available. * Capture your insight and experiences! Create good issues that go beyond bookmarking a feature request, bug, or user experience flaw. Here's an [example](https://github.com/osquery/osquery/issues/3764) of me 'bookmarking'. While it is concise and I understand what needs to be done, it does not help anyone else who may be having the same issue, or anyone who many want to help fix the issue. Here is an [issue](https://github.com/osquery/osquery/issues/3920) that is well documented, discoverable, shares an experience, and is actionable (even though it is hard to fix, or may not be fixable). * We need code reviews badly, this is the #1 way we can land code faster and with less bugs. Unfortunately there are two blockers, first there is a requirement for C++ fluency and second the test infra is a gray box. If you fork our repo you need to run tests manually. If we did not have customized test infra the experience may be improved. If you have any C++ experience, please *please please*, leave some notes on the [pull requests](https://github.com/osquery/osquery/pulls), make some nits, we promise to assume the best intent and we do value your time and advice. * Share your deployment experiences and the use cases you are solving. We would like to solve security and detection use cases with osquery, as well as inventorying, vulnerability management, compliance, performance monitoring, and many more. The more open we are about the 'edges' of the use case solutions the better we can all be at planning to address those. diff --git a/src/data/blog/posts/official_news/2020-09-10-linux-arm64-beta-support.md b/src/data/blog/posts/official_news/2020-09-10-linux-arm64-beta-support.md index ec0f9d2..66a32d6 100644 --- a/src/data/blog/posts/official_news/2020-09-10-linux-arm64-beta-support.md +++ b/src/data/blog/posts/official_news/2020-09-10-linux-arm64-beta-support.md @@ -22,7 +22,7 @@ We would like to announce beta support for Linux arm64/aarch64. We are working d They should follow the same portability expectations as x86, and work on any Linux distribution released since 2011. -Bugs and incompatibilities should be filled as GitHub [issues](https://github.com/osquery/osquery/issues) on the osquery repository. Questions, comments, and discussions are taking place in the Slack channel `#arm-architecture` ([request an invite!](https://join.slack.com/t/osquery/shared_invite/zt-1wi6cdgf7-zR2wt7FZ0ClHj6tEym6KFQ)) +Bugs and incompatibilities should be filled as GitHub [issues](https://github.com/osquery/osquery/issues) on the osquery repository. Questions, comments, and discussions are taking place in the Slack channel `#arm-architecture` ([request an invite!](https://join.slack.com/t/osquery/shared_invite/zt-1wipcuc04-DBXmo51zYJKBu3_EP3xZPA)) And of course, if you would like to build osquery for aarch64 yourself, please follow our [building](https://osquery.readthedocs.io/en/latest/development/building/) guide. But use the [aarch64](https://github.com/osquery/osquery-toolchain/releases/download/1.1.0/osquery-toolchain-1.1.0-aarch64.tar.xz) version of our toolchain. diff --git a/src/pages/Home/Home.js b/src/pages/Home/Home.js index 2bcbf4e..8905bb2 100644 --- a/src/pages/Home/Home.js +++ b/src/pages/Home/Home.js @@ -462,7 +462,7 @@ class Home extends Component {
} > Join the osquery Slack