NanUI for WinForms

[XuanchenLin]

1.   General Information

Project Name: NanUI

License: MIT

Contributor (Company, Organization or individual name(s)): Xuanchen Lin

Existing OSS Project? (Yes/No): Yes

Source Code URL: https://github.com/NetDimension/NanUI

Project Homepage URL (if different): https://github.com/NetDimension/NanUI

Project Transfer Signatories: Xuanchen Lin, xuanchenlin@msn.com

2.   Description

Please provide a brief statement about your project in terms that are understandable to the target consumer of the library or project, i.e. an elevator pitch for the project:

NanUI is an open source user interface framework for .NET / .NET Core Windows Form Applications. It's based on Chromium Embedded Framework. Mordern web front-end technologies can be used to build the application's user interface. It allows you to experience the combination of front-end frameworks such as React / Vue / Blazor / Angular and WinForms. And The JavaScript Bridge can easily and concisely relize the communication and data exchanges between the browser and .NET enviroment. Using NanUI framework will bring unlimited possibilities to your design of Windows Form Applications.

Please provide a 1 sentence (<140 character) summary of your project to help users when searching the .NET Foundation projects

NanUI is an open source .NET project for .NET / .NET Core developers who want to use front-end technologies such as HTML5 / CSS3 to build user interfaces for Windows Form applications.

3.   Project Governance

Please complete this section about who will be maintaining the open source project and how it will run. Project Lead: (Who is the primary contact point for the community and the .NET Foundation when discussing governance of the project.)

Name: Xuanchen Lin Email: xuanchenlin@msn.com GitHub Profile URL: https://github.com/XuanchenLin

Governance Model:

Please describe how new code changes are proposed to the project, how those changes are reviewed and how a decision is made to accept proposed changes. Also describe the process for identifying and appointing new committers.

Changes are proposed via GitHub issues.

CLA

No

CLA Notification Alias Provide an email address that will receive CLA related notifications from the .NET Foundation CLA automation

N/A

Assignment Model. Under the .NET Foundation assignment model, project ownership and other intellectual property is assigned to the .NET Foundation and the .NET Foundation agrees to grantback a license to the contributor(s).

Contribution Model. Under the .NET Foundation contribution model, a project retains ownership of the project, but grants the .NET Foundation a broad license to the project’s code and other intellectual property. The project also confirms that the project’s submissions to .NET Foundation are its own original work (there are also instructions for any third party materials that might be included).

4.   Repository Layout

The .NET Foundation host guidance for new projects and details on recommended structure here: https://github.com/dotnet/home/tree/master/guidance

Note that the open source repository should be the master where changes are made by the core development team using the same PR process that is used for non-committer contributions.

Please define below any changes you would want to make to your repositories as part of the process of joining the .NET Foundation

5. Eligibility Criteria

Please complete the following for your project

• The project is built on the .NET platform and/or creates value within the .NET ecosystem.
• [x] Yes
• [ ] No
• The project produces source code for distribution to the public at no charge.
• [x] Yes
• [ ] No
• The project's code is easily discoverable and publicly accessible (preferably on GitHub).
• [x] Yes
• [ ] No
• 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).
• [x] Yes
• [ ] No
• When applicable, project must use reproducible build settings in its toolchain.
• [x] Yes
• [ ] No
• The project uses Source Link.
• [x] Yes
• [ ] No
• The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
• [x] Yes
• [ ] No
• The project code signs their artifacts as appropriate.
• [ ] Yes
• [x] No
• The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
• [ ] Yes
• [x] No
• 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).
• [x] Yes
• [ ] No
• 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.
• [x] Yes
• [ ] No
• The copyright ownership of everything that the project produces is clearly defined and documented.
• [x] Yes
• [ ] No
• The project has a public issue tracker where the status of any defect can be easily obtained.
• [x] Yes
• [ ] No
• The project has a published Security Policy.
• [x] Yes
• [ ] No
• The project has a home page which provides high level information about its status and purpose.
• [x] Yes
• [ ] No
• The project has a public communication channel where community members can engage with maintainers.
• [x] Yes
• [ ] No
• The project has a publicly available location where members can review and contribute to documentation.
• [x] Yes
• [ ] No

6.   PR Plan

Not yet.

7.   Infrastructure Requirements

Only for Windows. Can't cross platform.

8.   Additional Notes

Please provide any additional information required or use this area for notes during the onboarding process. If this open source project has similarities with any other projects in this space then please detail them and why this project is different. If there are any potential issues that you feel the project might need help with early on then also state them here and discuss with your .NET Foundation Contact.

[clairernovotny]

Hi,

As a head's up, the Foundation does not currently permit restrictive licenses like LGPL. We require permissive licenses, such as MIT or Apache 2.0.

[XuanchenLin]

Hi,

As a head's up, the Foundation does not currently permit restrictive licenses like LGPL. We require permissive licenses, such as MIT or Apache 2.0.

OK, I'll change it to MIT soon

[XuanchenLin]

Hi,

I have changed the project's license to MIT, and republished the NuGet packages.