dotnet-foundation / dotnet-foundation/projects

Issue: New .NET Foundation Project Application - signalr-client-swift

Open
#429 1 comment 0 reactions 2 assignees View on GitHub

@sbwalker is already working on this.

Since Feb 18, 2025.

project application project support
Dominant language
No language data
Stars
157
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Project Name

signalr-client-swift

License

MIT

Contributor

Microsoft, Chenyang Liu (chenyl@microsoft.com), Binjie Qian(biqian@microsoft.com)

Existing OSS Project?

Yes

Source Code URL

https://github.com/dotnet/signalr-client-swift

Project Homepage URL

No response

Project Transfer Signatories
  • Chenyang Liu chenyl@microsoft.com
  • Binjie Qian biqian@microsoft.com
Description

The Swift client library for SignalR and Azure Signalr Service.

Name

Chenyang Liu

Email

chenyl@microsoft.com

GitHub Profile URL

https://github.com/zackliu

Committers
  • Chenyang Liu chenyl@microsoft.com Microsoft
  • Binjie Qian biqian@microsoft.com Microsoft
Discord Ids

No response

Governance Model

Contributer uses Pull Request to propose changes, and the core maintainer will review and approve the pull requests.

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

chenyl@microsoft.com, biqian@microsoft.com

Select the Project Transfer Agreement model

Assignment

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.
Describe why you are applying for Project Membership.

As SignalR and all SignalR client libraries are in the Foundation, swift client should also be a part of it.

Infrastructure Requirements Summary

No response

Additional Notes

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.