Thanks for the feedback. It might be helpful to add this requirement to the Package upload page, instead of only displaying it after a failed upload. On Thu, May 4, 2023 at 4:23 AM Merijn Verstraaten wrote:

Unlike the "long time ago", when everyone would immediately get upload rights upon account creation, you now need to be manually added to the Uploaders group by mailing the hackage admin address. This due to spammers abusing hackage and uploading packages consisting solely of linkspam/advertisements.

Cheers, Merijn

...

On 4 May 2023, at 08:23, Henning Thielemann < lemming@henning-thielemann.de> wrote:

On Thu, 4 May 2023, Dominick Samperi wrote:

...

I just tried to upload a new Haskell package and ran into some difficulties. If I just try to upload, it fails and says I need to contact somebody in the trustees group to be added to the Uploaders group. If I try to upload a package candidate instead, it says Forbidden, No access for this resource.

You need a Hackage account for both candidate upload and final release.

...

Also, I have a Hackage account and I can get to the account management page, and generate an auth key, but I don't know what I can do with that.

It's a long time ago that I registered my account, but maybe your account must be added to a special group, the group Uploaders.

I do not need an auth key for uploading, just user name and password. I use 'cabal upload' for Hackage releases.

...

It seems the package candidate feature is the way to go, since direct uploads are irreversible and more difficult to manage.

right

You can watch and check the appearance of your package candidate at Hackage before publishing. You can even use the uploaded candidate temporarily in your project by adding its tarball URL to cabal.project.local or stack.yaml. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

There must be a backlog of requests for uploading rights as I have not heard back for some time. On Mon, May 8, 2023 at 3:38 AM Merijn Verstraaten wrote:

If I recall correctly, the account creation page mentions needing to mail the hackage admins, but I don't know if there's any further reminders afterwards.

Cheers, Merijn

...

On 4 May 2023, at 17:32, Dominick Samperi wrote:

Thanks for the feedback. It might be helpful to add this requirement to the Package upload page, instead of only displaying it after a failed upload.

On Thu, May 4, 2023 at 4:23 AM Merijn Verstraaten < merijn@inconsistent.nl> wrote: Unlike the "long time ago", when everyone would immediately get upload rights upon account creation, you now need to be manually added to the Uploaders group by mailing the hackage admin address. This due to spammers abusing hackage and uploading packages consisting solely of linkspam/advertisements.

Cheers, Merijn

...

On 4 May 2023, at 08:23, Henning Thielemann < lemming@henning-thielemann.de> wrote:

On Thu, 4 May 2023, Dominick Samperi wrote:

...

I just tried to upload a new Haskell package and ran into some difficulties. If I just try to upload, it fails and says I need to contact somebody in the trustees group to be added to the Uploaders group. If I try to upload a package candidate instead, it says Forbidden, No access for this resource.

You need a Hackage account for both candidate upload and final release.

...

Also, I have a Hackage account and I can get to the account management page, and generate an auth key, but I don't know what I can do with that.

It's a long time ago that I registered my account, but maybe your account must be added to a special group, the group Uploaders.

I do not need an auth key for uploading, just user name and password. I use 'cabal upload' for Hackage releases.

...

It seems the package candidate feature is the way to go, since direct uploads are irreversible and more difficult to manage.

right

You can watch and check the appearance of your package candidate at Hackage before publishing. You can even use the uploaded candidate temporarily in your project by adding its tarball URL to cabal.project.local or stack.yaml. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Hello Carter, I should have been more patient. I heard back from hackage-trustees@haskell.org and managed to publish my package https://hackage.haskell.org/package/mathlist Thanks, Dominick On Sat, May 13, 2023 at 12:03 PM Carter Schonwald < carter.schonwald@gmail.com> wrote:

What email address did you use?

On Thu, May 11, 2023 at 6:05 PM Dominick Samperi wrote:

...

There must be a backlog of requests for uploading rights as I have not heard back for some time.

On Mon, May 8, 2023 at 3:38 AM Merijn Verstraaten wrote:

...

If I recall correctly, the account creation page mentions needing to mail the hackage admins, but I don't know if there's any further reminders afterwards.

Cheers, Merijn

...

On 4 May 2023, at 17:32, Dominick Samperi wrote:

Thanks for the feedback. It might be helpful to add this requirement to the Package upload page, instead of only displaying it after a failed upload.

On Thu, May 4, 2023 at 4:23 AM Merijn Verstraaten < merijn@inconsistent.nl> wrote: Unlike the "long time ago", when everyone would immediately get upload rights upon account creation, you now need to be manually added to the Uploaders group by mailing the hackage admin address. This due to spammers abusing hackage and uploading packages consisting solely of linkspam/advertisements.

Cheers, Merijn

...

On 4 May 2023, at 08:23, Henning Thielemann < lemming@henning-thielemann.de> wrote:

On Thu, 4 May 2023, Dominick Samperi wrote:

...

I just tried to upload a new Haskell package and ran into some difficulties. If I just try to upload, it fails and says I need to contact somebody in the trustees group to be added to the Uploaders group. If I try to upload a package candidate instead, it says Forbidden, No access for this resource.

You need a Hackage account for both candidate upload and final release.

...

Also, I have a Hackage account and I can get to the account management page, and generate an auth key, but I don't know what I can do with that.

It's a long time ago that I registered my account, but maybe your account must be added to a special group, the group Uploaders.

I do not need an auth key for uploading, just user name and password. I use 'cabal upload' for Hackage releases.

...

It seems the package candidate feature is the way to go, since direct uploads are irreversible and more difficult to manage.

right

You can watch and check the appearance of your package candidate at Hackage before publishing. You can even use the uploaded candidate temporarily in your project by adding its tarball URL to cabal.project.local or stack.yaml. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.