Issue: New .NET Foundation Project Application - dotnet-fba-templates #470
Description
Project Name
FbaTemplates
License
MIT
Contributor
Jung Hyun, Nam
Existing OSS Project?
No
Source Code URL
https://github.com/rkttu/dotnet-fba-templates
Project Homepage URL
No response
Project Transfer Signatories
- Jung Hyun, Nam rkttu@rkttu.com
Description
A collection of .NET project templates for creating File-based Applications (FBA) - simple C# console applications that can be executed directly without traditional project files using the dotnet command-line interface.
What are you hoping from the foundation
I would like my project to join the .NET Foundation so that I can contribute more effectively to the global .NET ecosystem, including communities in Korea where adoption is still growing. By joining the Foundation, I hope to gain support and resources that will allow me to deliver professional training, workshops, and educational activities. With the Foundation’s credibility and network, I believe I can expand the reach of this project and help more developers benefit from high-quality tools and learning opportunities.
Name
Jung Hyun, Nam
GitHub Profile URL
Committers
No response
Discord Ids
No response
Governance Model
All code changes are proposed through GitHub pull requests. Each pull request is reviewed for code quality, consistency, and alignment with the project’s goals. Decisions to accept changes are made after at least one review and open discussion when needed, with me as the project maintainer responsible for the final approval.
New committers are identified based on consistent contributions, demonstrated technical quality, and positive collaboration within the community. When a contributor has shown sustained involvement and responsibility, I appoint them as a committer to recognize their role and expand the project’s stewardship.
CLA
- If already an OSS project, was a Contribution License Agreement in place for contributions accepted?
How does the project check who has signed one?
Currently, as an individual-led project, contributors are limited and changes are primarily managed by me. For now, I verify contributor intent and agreement through GitHub pull requests and contributor communication. Once the project is accepted into the .NET Foundation, I plan to adopt the Foundation’s CLA system so that all contributors are automatically checked and validated through the official CLA bot. This will ensure transparency and consistency in tracking who has signed a CLA.
CLA Notification Alias
No response
Select the Project Transfer Agreement model
Contribution
Repository Layout
This project is still in its early stage, so the repository layout may not be pixel-perfect with the .NET Foundation’s guidance yet. However, the structure is already simple and clean, and it can be easily aligned with the recommended standards. I plan to add or adjust elements such as documentation, governance notes, and licensing files as needed, so that the repository fully matches the Foundation’s hosting guidance without significant effort.
Eligibility Criteria
- The project is built on the .NET platform and/or creates value within the .NET ecosystem.
- The project produces source code for distribution to the public at no charge.
- The project's code is easily discoverable and publicly accessible (preferably on GitHub).
- The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
- When applicable, project must use reproducible build settings in its toolchain.
- The project uses Source Link.
- The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
- The project code signs their artifacts as appropriate.
- The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
- Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
- Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
- The copyright ownership of everything that the project produces is clearly defined and documented.
- The project has a public issue tracker where the status of any defect can be easily obtained.
- The project has a published Security Policy.
- The project has a home page which provides high level information about its status and purpose.
- The project has a public communication channel where community members can engage with maintainers.
- The project has a publicly available location where members can review and contribute to documentation.
Describe why you are applying for Project Membership.
I am applying to add my project to the .NET Foundation because I want to contribute to the broader adoption of .NET technology, including in regions like Korea where the ecosystem is still developing. By joining the Foundation, I hope to gain support, visibility, and governance that will help this early-stage project mature into a reliable and well-recognized resource for the community.
My goal is to use this project not only as a technical tool, but also as a foundation for delivering professional training, workshops, and educational activities that promote .NET worldwide. Being part of the .NET Foundation will provide the credibility and infrastructure needed to grow the project responsibly, attract contributors, and ensure it continues to create long-term value within the .NET ecosystem.
Infrastructure Requirements Summary
This project does not require any dedicated infrastructure beyond standard GitHub hosting. All functionality will be delivered through packages published to NuGet.org, so no separate build servers, web hosting, or SSL/certificate management are necessary. The existing GitHub Actions CI/CD pipeline is sufficient to build and validate the project, and no additional infrastructure from the .NET Foundation is required at this stage.
Additional Notes
This project is one of the first open-source initiatives focused on the new File-based App (FBA) model introduced in .NET 10. While there are many existing templates for .NET, this project is unique in that it demonstrates how developers can leverage the latest single-file and AOT-style patterns in a practical and accessible way. It helps lower the learning curve for adopting modern .NET features and provides a foundation for both experimentation and professional use.
As the project is still in its early stage, I anticipate that support from the .NET Foundation will be valuable in areas such as documentation, community outreach, and increasing visibility so that more developers can benefit from it. I also see this project being used not only as a technical resource but also as an educational tool in professional training and workshops, where the Foundation’s support would greatly amplify its impact.