Pull request for "Unarchive py-multiaddr and establish new active maintainership team"

[seetadev]

@pacrob , @acul71 , @dhuseby , @arcinston

Wish to share the pull request that we should submit in the coming week. Please let me know your feedback and thoughts. Happy to make changes if needed.

PR Title:

Unarchive py-multiaddr and establish new active maintainership team

📝 PR Description:

This is in reference to our discussion on Slack — thank you so much for your kind consideration and thoughtful guidance regarding the future of Python projects within the multiformats organization. As part of that conversation (tagging @rvagg and @dhuseby), we’re submitting this pull request to formally request unarchiving of the py-multiaddr repository, with the intent to actively maintain and grow it as a key library for Python developers in the IPFS, libp2p, and Filecoin ecosystems.

🔧 Proposed Changes:

• Set archived: false for py-multiaddr
• Populate the project entry to follow the minimal structure used by actively maintained projects (e.g. js-blake2)
• Lay the groundwork for reviving additional Python multiformats libraries (py-multibase, py-multicodec, etc.)
• Add maintainers temporarily as individuals, pending revival of the Python Team

📚 Context & Intentions:

We’ve recently resolved long-standing type errors and other issues in pymultiaddr, and are committed to rebuilding it with a strong emphasis on sustainability and open contribution.

Our goals are to:

• Keep the library actively maintained and versioned
• Ensure good triage practices, timely PR reviews, and meaningful issue response times
• Provide CI coverage, test maintenance, and contributor documentation
• Encourage ecosystem collaboration and new contributors

Our roadmap includes:

• A refreshed README.md with updated usage, scope, and development intentions
• Realistic maintenance practices (CI coverage, issue triage, release cadence)
• Structured response timelines for issues and pull requests
• Active coordination with the broader IPFS, libp2p, and Filecoin ecosystems

We also recognize the importance of long-term ownership and are designing this as a community-first project with a responsible governance structure, rather than as a one-off fix.

🙋 Request for Maintainership:

We are currently an active group from the py-libp2p project, and we’d like to request maintainership responsibilities as a team:

• @acul71
• @arcinston
• @dhuseby
• @pacrob
• @seetadev

Instead of listing individual maintainers in each repo config, we’d love to follow your suggestion and revive the existing Python Team in the multiformats org. This will allow consistent governance and smoother onboarding/offboarding across all py-* repos. We're happy to help coordinate this transition and manage the team collaboratively.

To streamline this effort across all Python repos, we’d also like to help revive and generalize the Python team within the org, so maintainers can be tracked and coordinated more effectively across the py-* projects.

📌 Next Steps:

• After this PR, we’ll open similar requests for other py-* libraries (py-multibase, py-multicodec, etc.)
• We’ll also submit a roadmap/README update for py-multiaddr to clarify goals, scope, and contribution guidelines
• We’re happy to draft a proposal for reactivating the Python Team structure, and will follow up in Discussions or Slack, Discord.

Thank you again for the opportunity to help support and grow this critical part of the multiformats ecosystem. We appreciate your feedback, mentorship, and trust — we’re excited to collaborate and rebuild a healthy, contributor-friendly multiformats stack for Python developers.

With appreciation,
Py-libp2p Maintainers and OG Contributors

[seetadev]

@dhuseby : Thank you so much for making introductions with @rvagg. Very helpful indeed.

[varun-r-mallya]

I found a difference between what the docs say and what the library actually does, so I think I'd like to fix that with a PR. By when can I expect to be able to PR into it?

[acul71]

We're submitting PRs to this forked repository:
https://github.com/acul71/py-multiaddr-fork/tree/master
(actually to this branch: https://github.com/acul71/py-multiaddr-fork/tree/fix/typecheck)
until the original repository is unarchived.

I suggest waiting a bit (a few days?) to ensure everything is set up properly.

Things are changing quickly, so you might otherwise end up looking at outdated code.

[varun-r-mallya]

Certainly. I'll start work on this in a while then!

[pacrob]

Looks good, @seetadev! Nothing to add, thanks for putting this together.

[arcinston]

Looks awesome @seetadev , thanks for taking the initiative!!

[acul71]

Great step @seetadev , you're a great communicator and coordinator.

[seetadev]

Thank you so much for the warm support and thoughtful feedback on this effort! 🙏 Appreciate it.

@pacrob, @arcinston, @acul71, @rvagg, @dhuseby, @varun-r-mallya — your encouragement and kind words truly mean a lot. It’s been a privilege to help coordinate this first step toward reviving pymultiaddrs and setting the stage for sustainable Python support across the multiformats and libp2p ecosystem.

I’ve now posted PR #126 in the multiformats/github-mgmt repository proposing the unarchiving and initial stewardship plan for pymultiaddrs. It builds on our shared discussions and the model we’ve seen with similar revivals, while clearly communicating that this is not a reference implementation, but one of potentially several Python multiformats implementations.

Thanks again for the trust and community spirit. Very much looking forward to what we build together from here! 🚀