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

Yeah. We can help make that happen :grinning:

I'll try and write some docs on the process. But we can work through it together first?

<@UKHFQ233Q> me and <@UCU9C7W73> are owners of the `pulumiverse` github organization. If you transfer your repo to one of us, we then transfer it to the Github organization. In this process, you will retain your access rights to the repository. Once in place, we can start the collaboration!
Thanks already for your contribution! :tada:

image.png

<@UK4HNFLCB> no problem. What user name(s) shall I put in here?

<@UCU9C7W73> Thanks for the quick onboarding of the provider to Pulmiverse :thumbsup::skin-tone-3: I'll update the provider configuration accordingly with a PR. Or am I allowed to push directly to master?

<@UCU9C7W73> shall I integrate the "standard" `.github/workflows` for Pulumi Providers into this repository or will providers published differently from Pulumiverse?

LOL .. I know I know... Didn't find a better wording. Thus in quotes :wink: SO? :grin: Adding `.github/workflows` or not?

Tend to use the stuff from `pulumi/pulumi-azure` because <@UHTP242EB> keeps it up to date

<@UKHFQ233Q> I'm working on a number of reusable GitHub workflows so that all providers can leverage this effort.

Okay. Great to hear. But how will (can) the time provider published in the meantime?

We could use Dagger and provide an acation for this. <@UK4HNFLCB> :grinning: