Issue: New .NET Foundation Project Application: Dev Proxy

[waldekmastykarz]

Project Name

Dev Proxy

License

MIT

Contributor

Waldek Mastykarz, Garry Trinder, and others

Existing OSS Project?

Yes

Source Code URL

https://github.com/microsoft/dev-proxy

Project Homepage URL

https://aka.ms/devproxy

Project Transfer Signatories

Waldek Mastykarz [email protected]
Garry Trinder [email protected]

Description

Dev Proxy is an API simulator that helps you effortlessly test your app beyond the happy path.

Name

Waldek Mastykarz

Email

[email protected]

GitHub Profile URL

https://github.com/waldekmastykarz

Committers

@waldekmastykarz
@garrytrinder
@gavinbarron
@sebastienlevert
@MIchaelMainer

Discord Ids

798256584857747497
482535457796915210

Governance Model

The project uses GitHub issues to discuss new ideas for the project. When reviewing ideas, the project team considers the project's direction, existing feature set and project's mission. Discussion and decisions are made in the open, involving the contributors and providing them with a rationale behind the decision.

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?

Project is in the Microsoft org and uses the standard Microsoft CLA bot

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.

We'd appreciate help to build the project into an active community. Additionally, we hope to simplify acquisition thanks to foundation's help with signing our distributables.

Infrastructure Requirements Summary

We use GitHub Actions to build the project
We publish documentation on Microsoft Learn
Yes, we'll need a code-sign certificate.

Additional Notes

No response

[sbwalker]

Your application will be reviewed at the monthly Project Committee meeting today

[waldekmastykarz]

Thank you for the update. Looking forward to hearing your decision.

[glennawatson]

The committee did meet today and discussed the application. We are putting DevProxy forward for consideration by the board.