Apply for prefix reservation on NuGet

[fredericDelaporte]

See prefix reservation documentation, we should apply for the NHibernate prefix reservation on NuGet with the NHibernate organization as an owner of the prefix.

But we should before that decide whether we let the prefix be public, allowing other package owners to publish with the NHibernate prefix, but without the visual hint of prefix ownership, or not, which would prevent new NuGet package names with the NHibernate prefix to be published outside of the NHibernate organization. (Already published packages can still be updated without owning the prefix.)

[bahusoid]

whether we let the prefix be public, allowing other package owners to publish with the NHibernate prefix, but without the visual hint of prefix ownership

See no reasons to forbid using this prefix. Custom libraries for NHibernate should be allowed to have NHibernate prefix.

[hazzik]

While we were deciding on the option, it just became the only option.

[hazzik]

I've applied. Got confirmation. They'll promised to come back to me in 3 days.

[hazzik]

Reserved

[fredericDelaporte]

According to the prefix documentation, the default behavior is to reject push from people outside of the organization having reserved the prefix. So @hazzik if they were not letting you choose to be public or not, it means our reservation is not public and forbid newcomers to publish a package with the NHibernate prefix.

Still the same documentation does write about public registration, to be asked at the time of reserving. So either it has came back or the documentation is outdated.

I cannot find more information about what kind of prefix reservation do we have on the NuGet site. Maybe we need to ask account@nuget.org about this.

We need to know for #3250, and eventually changing the reservation kind if needed and possible.

[dennis-gr]

We need to know for #3250, and eventually changing the reservation kind if needed and possible.

Any news on this?

[dennis-gr]

Anyone? @hazzik @fredericDelaporte