No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

For folks getting started with Pulumi, we have an “IaC Recommended Practices” series that discusses a lot of different topics with regard to how to use Pulumi. This includes things like where to store your Pulumi code, how to use Git branches, using per-developer stacks, structuring Pulumi projects (when to use one project versus multiple projects), and more. You can find the first post in the series here: <https://www.pulumi.com/blog/iac-recommended-practices-code-organization-and-stacks/>

&gt;  Who is responsible for maintaining the code? If the application code and the Pulumi code are managed by different teams, then using separate repositories may be the best approach.
Seems too quick to rule out mono-repo approaches, they have a lot of advantages

There are lots of variables; each approach has advantages and disadvantages. You could definitely consider a monorepo; in fact, the fictional company in the series started out with a mono-repo. Nothing wrong with that, if it satisfies your requirements.