Issue: New .NET Foundation Project Application

[kwhinnery-openai]

Project Name

OpenAI .NET

License

MIT

Contributor

OpenAI, Microsoft

Existing OSS Project?

Yes

Source Code URL

https://github.com/openai/openai-dotnet

Project Homepage URL

No response

Project Transfer Signatories

• Kevin Whinnery [email protected]

Description

Official .NET API client for the OpenAI platform.

Name

Jose Arriaga Maldonado

Email

[email protected]

GitHub Profile URL

https://github.com/joseharriaga

Committers

Various contributors from Microsoft and OpenAI

Discord Ids

No response

Governance Model

The project is developed in the open, but primarily maintained by Microsoft and OpenAI employees. Pull requests are considered and reviewed on an ad hoc basis,

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.

Describe why you are applying for Project Membership.

Membership in the foundation will make it easier for users in the .NET ecosystem to build AI into their applications running on Azure and elsewhere. OpenAI will continue to benefit from Microsoft's partnership in building a developer experience that matches what the community needs and expects from us.

Infrastructure Requirements Summary

As a part of membership, a key benefit will be automating the code signing process. We expect this to be implemented in CI using https://github.com/dotnet/sign. I do no believe we will need any additional support with hosting.

Additional Notes

It does appear that this repository lacks a Contributor License Agreement, as it has been primarily built and maintained by Microsoft and OpenAI employees. If that is a blocker, let me know!

[kwhinnery-openai]

Applying as advised / discussed with Arun Sekhar ([email protected]) - thanks!

[glennawatson]

Hi

The project committee meets once per month to discuss eligibility and also suitability of projects once per month. The January meeting has already happened and it will be discussed during the February meeting.

We will update you after that meeting

Thanks
Glenn

[kwhinnery-openai]

Sounds great, thank you!

[achandmsft]

@glennawatson (cc @ChrisSfanos FYI), Please let us know if you needed any more information around this.