Perhaps we need a set of well-defined community engagement policies just as we have well-defined licenses or copyright policies, e.g.: - patches/pull requests

Perhaps we need a set of well-defined community engagement policies just as we have well-defined licenses or copyright policies, e.g.: - patches/pull requests welcome or not - paid consulting available or not (obviously with a right of refusal on architectural changes) This would go a long way towards managing expectations and avoiding mismatch. Tooling matters. Github doesn't have a way for a project to specify they won't accept pull requests for instance (e.g. thet's SQLite's policy, one I fully support, but then SQLite doesn't use GitHub or even git for that matter).