Ookii Dialogs

1.   General Information

Project Name: Ookii Dialogs

License: BSD 3-Clause "New" or "Revised" License

Contributor (Company, Organization or individual name(s)): @augustoproiete, Sven Groot

Existing OSS Project? (Yes/No): Yes

Source Code URL: https://github.com/ookii-dialogs

Project Homepage URL (if different):

Project Transfer Signatories:
Will submit via email

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:

Ookii Dialogs is a class library for WPF and Windows Forms applications providing several common dialogs. Included are classes for task dialogs, credential dialog, progress dialog, and common file dialogs, and more. Some dialogs are simple wrappers around existing Windows APIs that are not (yet) exposed to WPF/Windows Forms, and others are custom dialogs that provide utility for Windows Desktop apps.

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

Awesome dialogs for Windows Desktop applications built with Microsoft .NET (WPF & WinForms). Includes task dialogs, credential dialog, progress dialog, common file dialogs, and more.

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: C. Augusto Proiete
Email: (Will submit via email)
GitHub Profile URL: https://github.com/augustoproiete

Committers:

@augustoproiete - contributions are not on behalf of an employer

Governance Model:

@augustoproiete has been the maintainer of the project for the last 4 years, and all changes require sign-off from him through pull-requests proposed by contributors.

CLA

There is no CLA at this time.

CLA Notification Alias
Will submit via email

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.

• Yes
• No

• The project produces source code for distribution to the public at no charge.

• Yes
• No

• The project's code is easily discoverable and publicly accessible (preferably on GitHub).

• 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).

• Yes
• No

• When applicable, project must use reproducible build settings in its toolchain.

• Yes
• No

• The project uses Source Link.

• Yes
• No

• The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).

• Yes
• No

• The project code signs their artifacts as appropriate.

• Yes
• No

• The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.

• Yes
• 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).

• 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.

• Yes
• No

• The copyright ownership of everything that the project produces is clearly defined and documented.

• Yes
• No

• The project has a public issue tracker where the status of any defect can be easily obtained.

• Yes
• No

• The project has a published Security Policy.

• Yes
• No

• The project has a home page which provides high level information about its status and purpose.

• Yes
• No

• The project has a public communication channel where community members can engage with maintainers.

• Yes
• No

• The project has a publicly available location where members can review and contribute to documentation.

• Yes
• No

6.   PR Plan

Please summarize the public relations plan for the announcement when joining the foundation (and releasing as open source if appropriate). What is the main story we wish to promote, through what channels, what issues should we be aware of?  For significant news events then please also work with your .NET Foundation contact to ensure a full PR plan is developed.

7.   Infrastructure Requirements

Please describe any infrastructure requirements for the project. For example, how will build servers be operated? Any web hosting or service hosting requirements? Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases?

Code signing certificates for NuGet/Authenticode will be needed.

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.