Red Hat's "default to open" ethos is one such strategy. It turns out, that beyond a certain point, sharing information within a company is actually harder than just sharing it with the world at large. So Red Hat pairs up its products with a community project, and we have community projects for many of our internal tools as well.
On the community side, it doesn't matter that much what your official job title is - it's all about ability and the investment of time, and that applies even if you have "@redhat.com" in your email address.
On the product side, we try to provide a far more streamlined experience, as we aim to provide customers with a clearer picture of what's going on in the more free-wheeling upstream communities, and which parts are actually relevant to them, and which parts they don't need to worry about (at least for now).