OSSRH namespace issue

[Mark Raynsford]

Hello!

I've been publishing to Central since (I think) 2012.

Between oss.sonatype.org and s01.oss.sonatype.org, I either have
ownership of, or permission to, publish to all of the following namespaces:

com.io7m
net.adoptopenjdk
one.irradia
one.lfa
org.dyn4j
org.immutables
org.jogamp
org.librarysimplified
org.lwjgl.osgi

I've been trying to get support for a publishing issue, but haven't had
a response. I attempted to log in to the new
https://central.sonatype.com to see if there were other support options,
but I discovered that I needed to create an account.On logging in, a
dialog popped up telling me that I needed to verify a namespace. I tried
entering com.io7m (as that's my main namespace) but it claimed that it
was already registered as an OSSRH namespace.

Is there some kind of phantom account out there that I have access to
via s01.oss.sonatype.org that's not tied to central.sonatype.com? How is
this all supposed to work?

--
Mark Raynsford | https://www.io7m.com

[Brian Fox]

Hi Mark, 

Where were you trying to get assistance? We recently cutover to a new support system and that should ensure a timely response. You can access that by emailing 

mailto:central...@sonatype.com

If you have and that isn’t working, I definitely want to know.

For your second question, the new publishing at central.sonatype.com is meant for new signups only at the moment. Eventually everything will move there but the team is still working on the backend to integrate auth etc to make this as seamless as possible. This is why when you sign up here it’s not recognizing your existing namespaces.

--
You received this message because you are subscribed to the Google Groups "OSSRH Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ossrh-users...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/ossrh-users/30aebee2-a626-465e-867f-08d872fe03f8%40io7m.com.

[Mark Raynsford]

On 22/02/2024 13:03, Brian Fox wrote:

> Hi Mark,
>
> Where were you trying to get assistance? We recently cutover to a new
> support system and that should ensure a timely response. You can access
> that by emailing

> mailto:central...@sonatype.com <central...@sonatype.com>

>
> If you have and that isn’t working, I definitely want to know.

Hello! I was emailing that address. I got an automated response, but I
guess I'm kind of spoiled by the sub-millisecond response times that
support tickets got on issues.sonatype.org. :)Having not heard anything
for two days, I assumed something had broken.

> For your second question, the new publishing at central.sonatype.com is
> meant for new signups only at the moment. Eventually everything will move
> there but the team is still working on the backend to integrate auth etc to
> make this as seamless as possible. This is why when you sign up here it’s
> not recognizing your existing namespaces.

OK, thanks. Should I assume that there'll be some way to tell it about
my existing namespaces in the future? Not sure if I've just complicated
matters by setting up an account...

[Joel Orlina]

Hi Mark,

First off, I wanted to thank you for your patience as we work through changes to our support process as we incorporate new team members and tools.  I was primarily responsible for support tickets on issues.sonatype.org, and, while I appreciate that I was usually able to get to your tickets fairly quickly, I feel like "sub-millisecond" response might be a bit generous ;)

I did respond to the ticket you created via central...@sonatype.com today, and I'm glad Brian was able to provide a little bit of clarity.  To reiterate, central.sonatype.com is where we'd like new projects to sign up.  If you publish on oss.sonatype.org and s01.oss.sonatype.org, your credentials there will continue to work as should whatever build process you already have that target those hosts.  What has changed is the way you get support for those hosts.  We've already turned off the ability to create new issues on issues.sonatype.org, and in the coming weeks, we will retire the site entirely.  E-mailing central...@sonatype.com is the proper channel for raising support requests with the team, and, as the team gets more comfortable with processing support requests for our legacy publishing services, the response times should improve.

And don't worry about the new account you've created on central.sonatype.com.  It's in our plans to migrate all of our users there at some point, and, at the worst, we may have to do some account merging on our side when that happens.

If you've got any remaining questions, please add them to the email thread you started with central...@sonatype.com.

Thanks again,

Joel

--

Joel Orlina Engineering Manager

[Mark Raynsford]

Hello!

On 22/02/2024 22:06, Joel Orlina wrote:

> Hi Mark,
>
> First off, I wanted to thank you for your patience as we work through
> changes to our support process as we incorporate new team members and
> tools. I was primarily responsible for support tickets on
> issues.sonatype.org, and, while I appreciate that I was usually able to get
> to your tickets fairly quickly, I feel like "sub-millisecond" response
> might be a bit generous ;)

The generosity is well-deserved. The level of support you guys offer for
free is well above the quality and timeliness of support I've seen from
some companies that charge money for it.

> I did respond to the ticket you created via central...@sonatype.com
> today, and I'm glad Brian was able to provide a little bit of clarity. To
> reiterate, central.sonatype.com is where we'd like new projects to sign
> up. If you publish on oss.sonatype.org and s01.oss.sonatype.org, your
> credentials there will continue to work as should whatever build process
> you already have that target those hosts. What has changed is the way
> you get support for those hosts. We've already turned off the ability to
> create new issues on issues.sonatype.org, and in the coming weeks, we will
> retire the site entirely. E-mailing central...@sonatype.com is the
> proper channel for raising support requests with the team, and, as the team
> gets more comfortable with processing support requests for our legacy
> publishing services, the response times should improve.

Yep, thanks! The problem was also fixed (and was my fault). :)

> And don't worry about the new account you've created on central.sonatype.com.
> It's in our plans to migrate all of our users there at some point, and, at
> the worst, we may have to do some account merging on our side when that
> happens.

Got it.

Mark Raynsford | https://www.io7m.com