XtermBlazor .NET Foundation Project Application

[BattlefieldDuck]

Project Name

XtermBlazor

License

MIT

Contributor

@BattlefieldDuck

Existing OSS Project?

Yes

Source Code URL

https://github.com/BattlefieldDuck/XtermBlazor

Project Homepage URL

https://xtermblazor.pages.dev

Project Transfer Signatories

• Pui Tat Tse contact@tatlead.com

Description

Blazor library that integrates the xterm.js terminal emulator into Blazor applications.

Name

BattlefieldDuck

Email

contact@tatlead.com

GitHub Profile URL

https://github.com/BattlefieldDuck

Committers

@BattlefieldDuck

Discord Ids

348921660361146380

Governance Model

https://github.com/BattlefieldDuck/XtermBlazor/blob/main/CONTRIBUTING.md

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?

No response

CLA Notification Alias

contact@tatlead.com

Select the Project Transfer Agreement model

Contribution

Repository Layout

• Project Structure: The repository contains several projects, including XtermBlazor.Demo.Server (Blazor Server), XtermBlazor.Demo.Wasm (Blazor WebAssembly), and the main XtermBlazor library.
• Installation Guide: It provides detailed instructions for installation, such as adding the package via NuGet, updating _Imports.razor, and adding CSS & JS references to the HTML files.
• Usage Instructions: The page includes examples of basic usage and how to work with addons, demonstrating how to integrate the xterm.js terminal emulator into Blazor applications.
• Contribution and License: Contributions are encouraged, and the project is licensed under the MIT License, promoting open-source collaboration.

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.

PR Plan Summary

The foundation offers support and resources

Infrastructure Requirements Summary

No response

Additional Notes

No response

[sbwalker]

Thank you for your application. The Project Committee reviewed the application at a recent meeting based on the criteria outlined in the Charter (https://github.com/dotnet-foundation/projects?tab=readme-ov-file#criteria). Based on the current Activity metrics, the project does not yet meet the Activity requirements for becoming a Member project. However, the Project Committee is interested in getting a better understanding of the specific benefits or services you were hoping to receive by joining the .NET Foundation. If you are able to provide this additional context, we will be able to provide guidance on next steps.

[BattlefieldDuck]

I am keen on leveraging the technical expertise and resources offered by the .NET Foundation to enhance the quality of my project. I believe this access could provide invaluable support in overcoming technical challenges and improving our practices. Additionally, I am excited about the prospect of engaging with a larger community of developers and contributors. This interaction could lead to increased visibility for the project, fostering a more vibrant community around it, and potentially attracting more contributors.