I really don't understand the point of resetting it
if there is not a clear understanding of what roll it will serve
within the organization moving forward and a recommended path
for how projects will interact with it.
If it is only going to be a proxy for maven
central, then that is fine and you should go for it, but if
you're planning on having projects actually deploy to it
and/or build out the story for syncing to maven central then
all of that should be ironed out ahead of time and wired up
accordingly.
Maven repositories are meant to be durable and
exist forever, unlike orbit repositories that are transitory
and exist for small windows of time. If you screw something
up with Orbit then no biggy, it will eventually just disappear
and problem solved. With a maven repository once it is
released it is locked away for time eternal, which is why I am
such a strong proponent of having staging repositories so upon
release you can give things a pre-flight check before
releasing it and locking it down.
Once you set this up and take ownership of it you
are making a contract with anyone that uses it that you will
support the stuff in there from that point on. None of this
disappearing repository stuff where you check out an old tag
and some repository you built against is now missing and
perhaps replaced with a different version of some dependency.
cheers,
jesse