Channels
doorman
infrastructure
random
zercurity
community-feeds
fleet-dev
code-review
queryhub
apple-silicon
carving
tls
fim
goquery
zentral
aws
querycon
golang
zeek
file-carving
fuzzing
auditing-warroom
linen-dev
fleetosquery
plugins
jobs
arm-architecture
darkbytes
process-auditing
uptycs
android_tests
selfgroup
vendor-feeds
fleet
eclecticiq-polylogyx-extension
ebpf
website
core
general
macos
kolide
osctrl
extensions
foundation
sql
officehours
linux
windows
Title
t
terracatta
03/31/2020, 1:10 PMwhen you issue a Pull Request into the repository you will be automatically asked to sign a CLA before the code can be accepted into the project
I believe the corporate CLA text can be found here if you wish to review it prior to submitting a Pull Request https://github.com/osquery/foundation/blob/master/CCLA.pdf
a
Amol Khare
03/31/2020, 1:30 PMGreat. Thanks. Will check it out before submitting pull request. One general question was about are there any concerns if we change the existing schema (by adding new columns, not touching the existing ones), mainly related to consumers of the existing schema ?
t
terracatta
03/31/2020, 2:26 PMadditive changes are generally fine
a
Amol Khare
03/31/2020, 3:29 PMThanks Jason !
s
seph
03/31/2020, 4:35 PMI think the workflow for a corporate CLA is a bit weird. It might be https://docs.linuxfoundation.org/easycla/ccla-managers-and-ccla-signatories
a
Amol Khare
04/02/2020, 4:22 PMThanks seph for the link. We are reaching out to find who do we need to sign the CCLA.
s
seph
04/02/2020, 8:09 PMIf you run into issues with the CCLA, feel free to ping me on slack. Though, obviously, I can’t with your employer