Welcome Team!

[johannschopplich]

Hi @ghost1face and @0xZunia! 👋

Following our discussion, the official .NET implementation repo is now ready. Both of you have been invited as maintainers.

What's Ready

This Repository

You now have full access to toon-format/toon-dotnet. This is where you can build the official .NET implementation together.

The repository includes:

• ✅ Basic project structure (targeting .NET 8.0 & 9.0)
• ✅ NuGet package configuration (Toon.Format)
• ✅ Test project setup with xUnit
• ✅ GitHub Actions CI/CD pipeline
• ✅ Trusted Publishing configured for NuGet

NuGet Package Reservation

I've requested the Toon.Format namespace on NuGet. Once approved, we can use Trusted Publishing to automatically publish releases without managing API keys. Does that sound good to you?

Language-Agnostic Tests

The spec repository includes language-agnostic test fixtures that all implementations can use:

• Encoding tests: JSON → TOON conversion (tests/fixtures/encode/)
• Decoding tests: TOON → JSON parsing (tests/fixtures/decode/)
• Error cases: Validation and strict mode checks
• Edge cases: All specification corner cases

These JSON fixtures ensure consistency across all language implementations and make it easy to validate spec compliance.

Next Steps

Here's how to move forward:

1. Technical Planning (async via issues):
   • Propose architecture and API design
   • Discuss serialization approach (System.Text.Json integration, source generators, etc.)
   • Plan testing strategy using the spec fixtures
   • Define milestones and deliverables

Note

You can touch every file in this repo – I've set it up with minimal .NET knowledge. Feel free to challenge everything!

2. Initial Implementation:

   • Finalize project structure and conventions
   • Integrate the spec repo's test fixtures
   • Implement core encoder/decoder functionality
   • Set up code analyzers and formatting rules

3. Collaborate:

   • Use issues and PRs for design discussions
   • Work async across timezones
   • Equal ownership and decision-making

Key Priorities

Here's what we should aim for:

• ✅ Full SPEC.md compliance using the language-agnostic tests
• ✅ Support for .NET 8.0 and 9.0
• ✅ Nullable reference types and modern C# features
• ✅ High test coverage with spec compliance validation
• ✅ CI with GitHub Actions validating spec compliance
• ✅ Clean, idiomatic .NET API design
• ✅ XML documentation for IntelliSense
• ✅ Source Link support for debugging

Team Work

Please be kind to each other. If something is off or you experience troubles in the team, please DM me and we'll get this sorted out.

Let's Get Started

Feel free to open issues to kick off discussions about:

• API design and architecture decisions
• How to integrate the spec test fixtures
• Project structure and tooling (analyzers, formatting, etc.)
• Performance considerations and benchmarking strategy

Thank you both for stepping up to collaborate on this. Looking forward to what you're going to build! 🎉

---

P.S. – Trusted Publishing is configured for NuGet. Once the Toon.Format namespace is approved, I'll set up the trust policy on NuGet.org.

[ghost1face]

Sounds great, thank you. @0xZunia let's sync up, I see we've had a pull request already which is great, but we should determine any guidelines and architecture before we accept any changes

[nsx07]

can you guys create a new topic after defined the guidelines for this repo? I would like so much to collaborate with it.

[ghost1face]

For sure, I'm going to start a discussion

[michsco]

@ghost1face -- came across this library while looking for Toon serialization support for C#. Any interest in adding another member to the team? I'd love to help push this library forward.

[ghost1face]

Hey @michsco glad to meet you. I'm not against adding any new members but do want to bring some order to things. I'll hold off for now but will likely be looking for more as we re-evaluate all members for the upcoming year.

@johannschopplich you are the original creator so I do want to get your feedback as well here. I'd also like to request higher access to get this library from a crawl to a run within the next week or so

[johannschopplich]

I'm also all in to new team members. It's best if you, @ghost1face, and the current team members decide collactively.

Which higher access to you require specifically? What do you mean by "crawl to a run"?

[michsco]

Makes sense. Was hoping to utilize the downtime during the holidays to give some contributions. Let me know once you figure out how you want to move forward.