As per offline discussion with @inferno-chromium and @jonathanmetzman

https://google.github.io/oss-fuzz/getting-started/new-project-guide/#prerequisites

1. there are unnecessarily many examples, we can remove some of them

2. we should add project using libprotobuf-mutator and FuzzedDataProvider to the lis (e.g. one project using each of these) with a comment like `(note how this project

Current docs here.

When reading the SciPy docs on structured arrays. I discovered that array dtypes / record dtypes / structured dtypes (we should probably mention those other terms in the docs...) can have a title as well as a fie

https://google.github.io/clusterfuzz/setting-up-fuzzing/blackbox-fuzzing/ is probably the best page to add it.

This is particularly helpful for blackbox fuzzers with custom launchers, as the logs from the launcher scripts aren't visible unless FUZZ_LOGS_BUCKET is specified.

Dirsearch has an option that will force the use of hostname and by default it search by IP. I think it should be the opposite. It should search by hostname by default and an option could be used to search by IP.

This behavior is not expected by user that briefly read the help and this may result in not finding files or directories on server using vhost.

Topics that need to be covered:

• how to write good Fuzz functions (checking for logical bugs, cross checking different implementations, examining as much code as possible, testing functions that require more complex inputs and not just []byte)
• how to use several Fuzz functions in a single package
• corpus collection

The dashboard app doesn't have much documentation - it took me a while to figure out I needed to install the Google Cloud SDK to do anything with it. It would be nice to have some basic setup instructions documented.

similar to how https://docs.rs/ndarray/0.12.1/ndarray/doc/index.html has a documentation module, I think this is a nice place to keep the docs in a more properly version-controlled place.

fast-check is a very nice library. It would be even better if we could use it with Facebook's ReasonML instead of Typescript!

It might be possible to use https://github.com/rrdelaney/ReasonablyTyped to make the conversion easier.

So while I was debugging another issue, I came along the enormous list of parameters in the Session class. I feel that some of them should be moved to more appropriate locations, and I'd argue that this should be a breaking change. Benefits: better documentation, easier to understand.

In particular:

• ignore_connection_reset, ignore_connection_aborted, `ignore_connection_issues_when_sendin

I've created some example code and scripts in the wiki, they could be in the repo and either useful documentation or tests for the testsuite.

https://github.com/googleprojectzero/halfempty/wiki/Examples

In common/src/config.rs

https://github.com/AngoraFuzzer/Angora/blob/1940eb560201f3705afcdde5f3a720addb1df528/common/src/config.rs#L41

This value is used to ignore those seed files larger than 15000 bytes. https://github.com/AngoraFuzzer/Angora/blob/1940eb560201f3705afcdde5f3a720addb1df528/fuzzer/src/depot/sync.rs

This is something that hasn't been super clear to me, and I haven't really seen it discussed anywhere ever.

The corpus

• can end up getting sizable (see also #163)
• often isn't human readable

Committing it to the project-being-fuzzed's repo seems like it could add a bunch of git overhead and even make merges difficult.

But, it is needed to "pick up where you left off" when doing time

Since we support much more modern Python 3.x builds, we should use static type checking with our Python codebases. By making our types explicit and more absolute, this should not only improve code clarity, but also reduce any runtime TypeErrors (or any other type-related exceptions) that may happen as a result of having looser typing.

Pyre and [mypy](http://mypy-lan