@fmanco what will it look like for someone outside FB to build osquery from source

Basically something like

buck build osquery:osqueryd

is it a local build? does it need remote hosts?

There might be some setup required as we're not going to package the toolchain as a dependency anymore. We'll provide scripts to setup the host, but if you have a toolchain that should also work.

will you guys write up how to do that?

We'll update the provisioning scripts. It might not all be done with the first commit but we'll work with the community to try to support at least the major OSes/distros.

Okay

So to correct my answer above is more like

./tools/provision.sh

and then buck

happy to help with figuring out what breaks once you push the commits to the repo

Awesome, that will be helpful.

@fmanco one last question. the phabricator instance, is it public? can we see your code review there?

Unfortunately our Phabricator instance isn't public, so you won't be able to see our code review. Visibility into our code review is something we discussed and would like to give but currently don't have a solution for. To keep a good level of transparency we'll ensure that the commit messages are descriptive, and that we'll still do Blueprints for discussing major changes.

how does discussion work, with github

Ah, for PRs we will do the review fully on GitHub, so the current process will basically remain.

how do we give you feedback on changes you make? are you opening PRs too? or are we going to start seeing commits which we were not able to review

On the individual commits there won't be a chance to give feedback. At least initially. For major changes we'll open Blueprints and feedback is given on the issue on GitHub.