Hi @kentaro! 👋

Thank you for building toon_ex

The Vision

As TOON grows, I'm establishing official implementations under the toon-format organization for each major language. We recently kicked off this effort with Python and other languages, and I'd love to extend the same approach to Elixir.

Unlike Python, Elixir doesn't have competing implementations to consolidate. You've already done the work. So this is simpler: I'd like to invite you to migrate toon_ex to become the official toon-format/toon-elixir implementation, with you as the primary maintainer.

What "Official" Means

Here's what we're aiming for across all language implementations:

• ✅ Spec compliance: Passes the full SPEC.md test suite
• ✅ Quality: Comprehensive tests, handles edge cases
• ✅ Documentation: Clear examples, idiomatic for the language
• ✅ Maintenance: Stays in sync with spec updates
• ✅ Community: A clear "blessed" path for Elixir users

From what I've seen, toon_ex already checks most of these boxes (except spec v2 compatibility). The main benefit of moving it under the organization is visibility, shared infrastructure, and alignment with the broader TOON ecosystem.

What You'd Get

Maintainer ownership:

• Full commit access to the official repo
• Decision-making authority on Elixir-specific design choices

Community benefits:

• Listed on the main TOON repository as the official Elixir implementation
• Easier discoverability for Elixir developers

The Migration

If you're interested, here's what I'm thinking:

1. Migrate to toon-format/toon-elixir and transfer your repo
2. You remain the primary maintainer – this is your work, I'm just providing the organizational home
3. Optional adjustments:
   • Rename package to toon_format or toon-format on Hex.pm (what is best practice here?) to keep it semantically close to the other language's package names
   • Add compliance tests against the official spec fixtures v2
   • Align documentation with the standardized structure we're using across languages
4. Ongoing collaboration: Stay in sync with spec updates, share learnings with other language maintainers

All of this would be async – no pressure, no rush. You keep full control over the Elixir implementation's architecture and design.

Next Steps

No pressure if you prefer to keep toon_ex independent – I respect that. But if you're interested in collaborating:

1. Are you open to migrating toon_ex to the organization?
2. What would you need from me? (CI setup, documentation help, etc.)
3. Any concerns or questions about how this would work?

Looking forward to hearing your thoughts!