Issue: New .NET Foundation Project Application: Ursa.Avalonia

[rabbitism]

Project Name

Ursa

License

MIT

Contributor

IRIHI Technology

Existing OSS Project?

Yes

Source Code URL

https://github.com/irihitech/Ursa.Avalonia

Project Homepage URL

No response

Project Transfer Signatories

@rabbitism [email protected]
@zdpcdt [email protected]

Description

Ursa is a UI library for building cross-platform UIs with Avalonia UI. Ursa provides more than 50 controls, and is designed with look-less philosophy, enabling full styling customization. Ursa also provides a concrete dialoging system to accelerate multi-window style application.

Name

Dong Bin

Email

[email protected]

GitHub Profile URL

https://github.com/rabbitism

Committers

@rabbitism
@zdpcdt

Discord Ids

No response

Governance Model

For project maintainers, we follow regular PR and review process for adding new features and bug fixes. branches are maintained in main repo. For open-source contributors, they need to fork and submit changes via PR. The PR is then reviewed by maintainers and other contributors who evaluate the changes for quality. Reviews may include feedback, and contributors may need to address comments before the PR is accepted, or maintainer may make last step change if contributors agree.

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

No response

Select the Project Transfer Agreement model

Contribution

Repository Layout

No response

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

Ursa itself is a well-polished Avalonia control library, it is welcomed by many Avalonia developers. It also strictly follows the best Avalonia development practices. It is a good resource to learn how to build a highly reusable control.

Infrastructure Requirements Summary

• To provide NativeAOT sample for different platforms, we might need different build server infra.
• We need code/pack signing help.

Additional Notes

No response

[nicoleabuhakmeh]

Hi @rabbitism
In your PR answer, you didn't state the reason for joining, please reply this this question as part of your application process.

What is the main reason you wish to join the Foundation?

[rabbitism]

Hi @rabbitism In your PR answer, you didn't state the reason for joining, please reply this this question as part of your application process.

What is the main reason you wish to join the Foundation?

Thanks for reminding. I don't know why this session is displayed as PR Plan Summary. My answer:

Joining the .NET Foundation will benefit both Ursa project and .NET developers.

Joining the .NET Foundation will increase visibility and credibility of Ursa project within open-source community. .NET Foundation also provides resources that Ursa anticipates, including security and legal advices, digital signing, CLA support and so on. We also hope to learn more about managing open-source project and open-source community.

Ursa itself is a well-polished Avalonia control library, it is welcomed by many Avalonia developers. It also strictly follows the best Avalonia development practices. It is a good resource to learn how to build a highly reusable control.

[sbwalker]

@rabbitism thank you for submitting a project application to the .NET Foundation. Your project was reviewed at the Project Committee meeting today, however there were not enough members present at the meeting to make a recommendation to the Board of Directors. We will review the project once again at our next meeting in December.

[sbwalker]

The Project Committee met yesterday and unanimously agreed that it should be submitted to the Board of Directors for consideration as an official Member project (the final step in the process).

[rabbitism]

Hello Team, any further action from our side?

[glennawatson]

Next board meeting will be in February.