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

You have the flexibility to do either, or a 3rd option, to share the `package.json` but also put [most of] the pulumi stuff in a subdir.

It really depends on your use case.

For simplicity, the majority of our stacks have chosen to streamline it and use option 3, sharing the `package.json` using `devDependencies` which is usually just 2-3 pulumi packages.  The Pulumi files go into `deploy` so any IaC solution can be expected in a sub dir there.

`Pulumi.yaml` then looks something like:
```name: some-service
description: Some service
main: deploy/pulumi
stackConfigDir: deploy/pulumi
runtime:
  name: python
  options:
    virtualenv: venv```