Can we get @takluyver and @neutrinoceros's Anaconda.org user names to add them?

I am takluyver on anaconda.org as well

Please have a member of the h5py team complete the missing items from the checklist to get started.

• Create an account on Anaconda.org
• Reply here with the link to your account (https://anaconda.org/tacaswell, https://anaconda.org/takluyver)
• Make a new Anaconda Cloud API token with permissions described in https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects

• Save the API token as a repo GitHub Actions secret named ANACONDA_ORG_UPLOAD_TOKEN
• Direct @scientific-python/nightly-wheels-developers to a h5py nightly wheel for us to upload to create the package in the registry
• Verify that we have added you to the h5py team "Group" on https://anaconda.org/scientific-python-nightly-wheels
• Verify that we have added the package scientific-python-nightly-wheels/h5py to the h5py team "Group"

If you'd also like to use the scientific/upload-nightly-action GitHub Action please check out the action repo's README. If you need to collect wheels from different CI jobs, consider creating a new GitHub Actions workflow with logic similar to matplotlib's or Awkward's.

If you have any questions please just ask here!

@tacaswell We already have done this before. c.f. Issue #77 The group already exists and h5py has been previously added.

The issue is just that h5py hasn't uploaded any wheel for more than 30 days and so it got automatically cleaned up (removed). Just upload a wheel again and you're good to go.

I've added @takluyver to the maintainers group. Let me know if you have any questions, but if not, I'll close this out.

I just registered at anaconda.org under neutrinoceros

@neutrinoceros Added you.

Now @tacaswell, @takluyver, and @neutrinoceros can have their Anaconda cloud account be the one who uploads the files in a CI/CD workflow.

Fixed by @takluyver in h5py/h5py#2563. 🚀