Repository navigation
Transfer out: icalevents #486
Description
The existing icalevents repository has moved to eigenmannmartin/icalevents. The November 3 PyPI registry confirms eigenmannmartin and eigenmannmartin2 as Owners, alongside Irgang and jazzband. hultner is a Maintainer. Martin's RTD access was verified before the move. RTD now uses his repository and homepage. Build 35396658 passed, and the hosted pages were verified with existing users and defaults unchanged. The release workflow still requires Jazzband. Publishing PR #181 replaces it with package builds and a separate tag-only PyPI publishing job under the pypi environment. Local wheel and sdist builds passed. The updated PR preserves Martin's two original commits from #180. At e923d21, all 12 test-matrix jobs and the package build passed. PyPI publishing was skipped for this pull request. Martin's review and merge, the protected environment, configuration of the matching PyPI Trusted Publisher and the next planned maintainer-approved release remain pending. Publishing remains unverified. Hultner and ndw's current collaborator permissions are not visible to Jannis. Keep the remaining service access, upload credential and website entry until the receiving setup works.
People
- Project leads: @eigenmannmartin.
jezdez: arrange Jazzband's ownership changes and remove obsolete access after the handoff.
TODOs
- Give @eigenmannmartin Admin access to prepare the handoff. The repository has now moved to his account.
- Confirm current authority and agreement. Martin is the website and GitHub project lead, confirmed by the onboarding and lead-request history.
- Agree eigenmannmartin as the receiving owner. Preserve Hultner and ndw as Write collaborators.
- Confirm accepted PyPI Owner access for eigenmannmartin and eigenmannmartin2, and Read the Docs access for eigenmannmartin.
- Verify the known fork conflict is resolved. Martin deleted the fork, and both paths and the upstream fork list confirm its removal.
- Transfer the existing repository to eigenmannmartin/icalevents. Its repository ID and Jazzband redirect are preserved.
- Martin: confirm Hultner and ndw retain collaborator access. Jannis cannot inspect their current permissions.
- Update RTD's repository and homepage to eigenmannmartin/icalevents. Build 35396658 and the published pages are verified. Existing users and defaults are unchanged.
- Prepare and open publishing PR #181 to replace the Jazzband-only release job. Static workflow checks passed.
- Verify package builds from the proposed workflow. Local wheel and sdist builds passed.
- Martin: review and merge publishing PR #181. At e923d21, all 12 test-matrix jobs and the package build passed. PyPI publishing was skipped for this pull request. Publishing remains unverified.
- Configure and verify a protected GitHub environment named pypi and the matching PyPI Trusted Publisher: owner eigenmannmartin, repository icalevents, workflow release.yml, environment pypi. The environment is not configured. The November 5 authenticated PyPI check found no publisher configured. Confirm release reviewers, allowed release tags and required checks under the receiving owner before publishing.
- Verify a maintainer-approved release from the destination. Keep publishing verification pending until that has happened.
- Update contribution guidance, security and conduct contacts, project links and the Jazzband badge.
- Remove the unattached icalevents-leads and icalevents teams. Organization membership, website records, upload credentials, PyPI and RTD access are unchanged. Hultner and ndw's collaborator roles still need verification.
- Remove obsolete Jazzband credentials and integrations after their replacements work, update the Jazzband directory, and link the completion evidence.
If retirement is agreed, replace the transfer steps with the archive, package ownership and service-retirement checks. Silence does not count as agreement.
Project details
- Repository: https://github.com/eigenmannmartin/icalevents
- Destination: eigenmannmartin (repository and docs verified, publishing and closeout pending)
- Jazzband wind-down board
- Jazzband wind-down plan
- Onboarding: Implement Jazzband guidelines for icalevents eigenmannmartin/icalevents#82
Activity
eigenmannmartin commentedon Oct 13, 2026
Hi Jezdez
I can take ownership personallyfor the project.
cheers
Martin
jezdez commentedon Oct 13, 2026
Thanks, Martin. Could you confirm that
eigenmannmartinis the GitHub account to receive the repo, and share your PyPI and Read the Docs usernames? @Hultner, would you like to stay involved?PyPI currently lists
Irgangas Owner. @eigenmannmartin, could you arrange an Owner invitation with them so you can manage publishing after the move?eigenmannmartin commentedon Oct 14, 2026
sure
eigenmannmartineigenmannmartineigenmannmartin2uff! that is not ideal - Irgang seems to have deleted the user on github. Is there any other way?
thank you for your time and support!
jezdez commentedon Oct 14, 2026
@eigenmannmartin, if Irgang doesn't reply at the published contact address, could you open a PyPI support request for Owner access as
eigenmannmartin2? Link this discussion and include your attempts to reach them. I can add the Jazzband context there. Your Read the Docs invitation is still pending.eigenmannmartin commentedon Oct 16, 2026
@jezdez I found Irgang on linkedin - I am owner now and have accepted the read the docs invite.
jezdez commentedon Oct 19, 2026
@eigenmannmartin, you now have repo admin access. I've also verified your PyPI Owner and RTD access. Could you prepare publishing from your account? RTD will need its repository URL updated after the move. Hultner's access stays unchanged while we wait for their reply. We'll keep Jazzband's service access until publishing and docs are verified.
Hultner commentedon Oct 19, 2026
@jezdez @eigenmannmartin Thank you for reaching out. I've not been particular active in the project lately as my bandwidth for volunteer work has been quite full. I do still use the library in some of my personal projects and if I do encounter any issues I'll patch it, however that's probably as far as I'll stretch my participation at this moment.
With that in mind, I'd say that it's up to you @eigenmannmartin if you want to keep me on as a maintainer considering that you are taking over as the formal lead for this project now. For me either way is fine. What's your assessment of the current state of the project? I do remember that there were some for me quite critical issues early on which we've resolved by now and from my perspective it's been fairly stable without too much ongoing work. Maybe that's to be discussed on the project board itself and outside the scope of this discussion?
jezdez commentedon Oct 19, 2026
@eigenmannmartin, your existing fork still blocks transferring the repository to your account. How would you prefer to handle that while preserving any work you want to keep?
eigenmannmartin commentedon Oct 21, 2026
Hi @jezdez I renamed the fork - so it should work now I think.
I leave it to @Hultner - for simplicity I would still keep @Hultner as contributer/admin in case I am unresponsive.
Thanks!
jezdez commentedon Oct 23, 2026
Thanks @eigenmannmartin. The renamed fork is still in the same network, so it still blocks the transfer. Could you move that fork to another account you control, or ask GitHub Support about detaching it while preserving your work? It has a child fork, which rules out the self-service option. Hultner's existing Write access can stay.
eigenmannmartin commentedon Oct 23, 2026
@jezdez the fork is deleted now :)
jezdez commentedon Oct 23, 2026
Thanks @eigenmannmartin, the fork blocker is cleared and the transfer checks are done. You can transfer the repo to your account from Settings with your existing Admin access. GitHub requires you to initiate this move. Keep Hultner and ndw as collaborators. Afterward, the release workflow needs to publish from your account and RTD needs the new repository URL. Please keep Jazzband's service access until publishing and docs are verified.
jezdez commentedon Oct 25, 2026
@eigenmannmartin, RTD now points to your repository and homepage. The build passed and the published docs work. I kept existing access unchanged. The remaining release work is to replace the Jazzband-only workflow and verify publishing from your account. Jazzband's credential and website entry will stay until the remaining checks pass.
jezdez commentedon Oct 27, 2026
I've removed the two unused Jazzband teams. Organization membership and service access are unchanged. Publishing and Hultner and ndw's access still need verification.
jezdez commentedon Nov 2, 2026
@eigenmannmartin, I've opened #181 to replace the Jazzband upload job with Trusted Publishing from your repository. Local wheel and sdist builds passed. The existing Python 3.9 CI job failed while installing Poetry, before project tests. I see #180 already removes Python 3.9. Could you review the publishing change alongside #180?
Before the next planned release, the protected GitHub environment and PyPI publisher need to match:
eigenmannmartin/icalevents,release.yml, environmentpypi. I'll keep Jazzband's credential and service access until receiving publishing and the remaining handoff checks are verified.jezdez commentedon Nov 3, 2026
@eigenmannmartin, #181 now includes your original cleanup commits from #180. All 12 test jobs and the package build pass. Could you review and merge it when you're happy with it?
Before your next planned release, please configure the protected
pypienvironment with the agreed reviewers and release tags, and confirm the PyPI publisher matcheseigenmannmartin/icalevents,release.yml, environmentpypi. I'll keep Jazzband's credential and service access until publishing and the remaining handoff checks are verified.