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 may want to take a look at <https://github.com/pulumi/pulumi/issues/2039>.  We actually plan on moving to a more explicit hierarchy of &lt;org&gt;/&lt;project&gt;/&lt;stack&gt; to make this more clear/explicit.

Hmm, so I don’t know that I fully understand the questions, but I find it helpful to think of the TS/JS/Python code of a Pulumi application to be _a description of desired cloud resources_ — this, in turn, is driven by the `pulumi` CLI, which can re-use those resource descriptions in multiple _stacks_. So hopefully that’s a helpful start.

Thank you <@UB3BGTV63>, so it seems stack names will be scoped to pulumi projects. Then I guess I could have a convention that in projects with a single stack I could name it `default` (or similarly).

So resources are managed Pulumi, in the context of these _stacks_. As luke says, these two have a hierarchy that is relevant to the organization that uses those resources. org, project, stack, etc.,

<@UBAJ7TD53> one of the issues I have is the usage of _pulumi program_ in one places of the docs and _pulumi project_ in others. I am lost if they describe the same thing :slightly_smiling_face:

Is it possible to have one pulumi project that contains more than one pulumi program?

see luke’s response, he pretty much covers it.

&gt; Is it possible to have one pulumi project that contains more than one pulumi program?

No.  A project is a Pulumi.yaml file, and that file specified the `runtime` and `main` entrypoint of the program to execute for the deployment of the project.

&gt; one of the issues I have is the usage of _pulumi program_ in one places of the docs and _pulumi project_ in others. I am lost if they describe the same thing :

Yes - it does look like we are a little loose in using the word "program" in some places we should use "project".  Technically, these are 1:1, so it doesn't really matter - and in many cases the prose really is referring to the program that a project will run, vs. the project itself.  But I do see a few cases where we should be crisper here.

I’m still learning Pulumi so I might misunderstand some of the concepts and how they are related with each other - all these answers make it very clear now.