Hello perhaps a silly question but what is the current recommended naming convention for Community packages currently. I know it used to be Our.Umbraco.{package} but had a feeling that it changed recently to Umbraco.Community.{package} - obviously any name is fine but was just curious what the general concensus was currently

Historically it has been

Our.Umbraco.*

- partially because packages were released through the Our Umbraco site. But probably since Umbraco 9+ packages live on NuGet instead, the old prefix doesn't make as much sense as it did in the past. NuGet allows reversing a prefix, so Umbraco has reserved

Umbraco.*

. This previously meant that you couldn't release a package on NuGet starting with

Umbraco.*

. At some point Umbraco opened up so that the community can use

Umbraco.Community.*

while

Umbraco.*

in general is still reserved. TL;DR -> if you're starting a new package, and wish to use a community prefix,

Umbraco.Community.*

is the recommended prefix now.

Amazing, thank you Anders. That's a perfect explanantion

@Hooky If interested, the backstory for the

Our.Umbraco.

prefix: https://dev.to/leekelleher/history-of-our-umbraco-package-names-34f2 (yup, it's kinda my fault) 😉 I'm all for

Umbraco.Community.

prefix now! (I'm partly to blame for that too) 😉