- Foundation Repository -- https://github.com/osquery/foundation
- osquery repository -- https://github.com/osquery/osquery
- 1Password Team Account -- https://osquery-foundation.1password.com
This is owned by the Linux Foundation
The NS is AWS and the zone is managed within Route53 by the osquery account.
This is available to the TSC and provides [email protected] inboxes.
The [email protected] inbox is a inbox-like-group that forwards to all TSC members.
This manages API keys, GPG keys, etc.
The users and owners include the osquery TSC.
Usage is free via a yearly check-in here: https://github.com/1Password/1password-teams-open-source
We have a phone number in Twilio, it forwards places.
Essentially this repo and all osquery foundation managed code.
The organization admins are the members of the TSC and the linuxfoundation management account.
This is managed within the Linux Foundation's EasyCLA tool.
Members of the Linux Foundation can help with changes. There is a installed GitHub app called CommunityBridge: EasyCLA.
Help with this is best obtained through https://jira.linuxfoundation.org/servicedesk
This is maintained by Trail of Bits.
It requires integration into the osquery GitHub org.
This is maintained by the osquery AWS organization (osquery-storage). The content is 100% public.
It contains dependencies for the build, in some cases pre-built dependencies.
It hosts the content for package (RPM, PKG, etc) releases as well as the content for YUM and APT repositories.
https://pypi.org/project/osquery/
The owners include the osquery TSC, managed through the PyPI website.
The code is managed in the osquery/osquery-python repo.
Updating requires bumping osquery/__init__.py's __version__ field. And optionally tagging a release on GitHub.
https://osquery.readthedocs.io/en/stable/
The admins include the osquery TSC, managed through the RTD website.
The content is hosted within the osquery/osquery repo, in the /docs folder.
Anyone submitting PRs to osquery can update the documentation.
Unused, it existed to route notifications for Jenkins in 2014.
We have a dashboard page setup at https://scan.coverity.com/projects/osquery
Various members of the TSC are project owners.
There is the Slack workspace, admins include the osquery TSC.
There is a auto-inviter (slackin) configured within a Droplet at https://osquery-slack.herokuapp.com
This twitter account is configured to grant various TSC members posting permissions in TweetDeck. You should be able to login and use it.
The underlying credentials are in 1password.
osquery exists on communitybridge's funding platform -- https://funding.communitybridge.org/projects/osquery In theory any members of the TSC can file expense in that. seph (@directionless) is probably the entry owner.