Issue: New .NET Foundation Project Application - OpenSSH-GUI

[frequency403]

Project Name

OpenSSH-GUI

License

MIT

Contributor

Oliver Schantz, domportera

Existing OSS Project?

Yes

Source Code URL

https://github.com/frequency403/OpenSSH-GUI

Project Homepage URL

No response

Project Transfer Signatories

• Oliver Schantz frequency403@gmail.com

Description

OpenSSH-GUI is a cross-platform .NET tool providing an intuitive, user-friendly interface for managing OpenSSH connections and settings.

Name

Oliver Schantz

Email

frequency403@gmail.com

GitHub Profile URL

https://github.com/frequency403

Committers

No response

Discord Ids

No response

Governance Model

1. Project Leadership

The OpenSSH-GUI project will be led by a Project Maintainer, responsible for setting the project’s overall direction, release planning, and major architectural decisions. The Project Maintainer also facilitates community discussions and ensures alignment with the .NET Foundation’s standards.

2. Contributors

Contributors are any community members who contribute code, documentation, or other resources. Contributors gain their status by having pull requests merged by maintainers. Contributions are welcomed from any community member, subject to the project's Contribution Guidelines, which outline coding standards, testing requirements, and documentation practices.

3. Core Committers

Core Committers are contributors who have shown consistent, high-quality contributions. They are granted commit rights and may review and merge contributions. Core Committers are selected by the Project Maintainer based on the quality, frequency, and impact of their contributions.

4. Decision-Making Process

Minor Decisions: Day-to-day decisions, including bug fixes and minor improvements, are made by Core Committers and Contributors, with final review by the Project Maintainer.
Major Decisions: Significant changes, such as new features or design shifts, are discussed in GitHub Issues or the project’s community forum. The Project Maintainer facilitates consensus and may call for a community vote if needed.
5. Code of Conduct

The project follows the .NET Foundation’s Code of Conduct to ensure a respectful, inclusive, and welcoming environment for all participants.

6. Community Engagement

The OpenSSH-GUI project encourages community involvement through GitHub discussions, periodic surveys, and community meetings, allowing all contributors to provide feedback and influence project development.

7. Licensing

OpenSSH-GUI will adopt the MIT License, aligning with .NET Foundation recommendations for open-source projects. This license encourages broad usage, collaboration, and contribution from the community.

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

Assignment

Repository Layout

Adding a Documentation and a Contributing.md

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.

Joining the .NET Foundation would provide OpenSSH-GUI with invaluable support, ensuring its sustainability, accessibility, and impact across the developer community. As part of the Foundation, OpenSSH-GUI can benefit from additional guidance on best practices in open-source software development, including licensing, community governance, and code quality standards. Moreover, the Foundation’s resources would help bolster OpenSSH-GUI's adoption, visibility, and credibility as a reliable tool within the .NET ecosystem.

Infrastructure Requirements Summary

No response

Additional Notes

No response

[sbwalker]

@frequency403 thank you for submitting a project application to the .NET Foundation. The Eligibility Criteria is outlined on the main page of this repo (https://github.com/dotnet-foundation/projects?tab=readme-ov-file#eligibility-criteria) and includes the following item:

Licenses and Copyright

• The code is offered under a standard, permissive open source license which has been approved by the .NET Foundation.

Your project is licensed under the GPLv3 which is not considered to be a permissive license (https://en.wikipedia.org/wiki/Category:Permissive_software_licenses). Therefore at this time based on the eligibility criteria, the Project Committee will need to place your application on hold. If anything changes which would make your project eligible for membership in the future, the Committee will review your application once more.

[frequency403]

Thats my bad, i thought that - if the commitee approves the application - i can change the license then.

I changed it now - so it can be reviewed again :)

[sbwalker]

The Project Committee reviewed your application yesterday, and based on the Activity Metrics (https://github.com/dotnet-foundation/projects?tab=readme-ov-file#activity-criteria) it was recommended that your project could be added to the Seed category (https://github.com/dotnet-foundation/projects?tab=readme-ov-file#project-levels)