Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shotgun.API .NET Foundation Project Application #382

Open
14 of 18 tasks
Freysi21 opened this issue Jun 23, 2024 · 0 comments
Open
14 of 18 tasks

Shotgun.API .NET Foundation Project Application #382

Freysi21 opened this issue Jun 23, 2024 · 0 comments
Assignees
Labels
project application project support Use this label to request support for an existing .NET Foundation project

Comments

@Freysi21
Copy link

Freysi21 commented Jun 23, 2024

Project Name

Shotgun.API

License

MIT

Contributor

Árni Freyr Þorsteinsson

Existing OSS Project?

No

Source Code URL

https://github.com/Freysi21/Shotgun

Project Homepage URL

No response

Project Transfer Signatories

Description

Current status

Abstract classes to quickly create ASP.NET webapi controller that support the following:

  • CRUD
  • Filtering
  • Paging
  • Exporting

for any given dbSet within a EntityFramewok dbContext.

Future features

I aim to create dotnet cli commands that uses these classes to extend dotnet ef scaffold command. Further development ideas are to have the new dotnet shotgun cli command create two projects from a database string. One for the webapi controller and the other for a dotnet maui project that creates basic Fluent UI designed app with common UI features for a table/view.

Name

Árni Freyr Þorsteinsson

Email

[email protected]

GitHub Profile URL

https://github.com/freysi21

Committers

freysi21

Discord Ids

freysi21

Governance Model

Árni Freyr Þorsteinsson will review everything in the beginning. Core functionality has been defined for the current abstract classes. Changes that will be accept are either optimization for existing core functionality or missing implementations for existing definitions. With time I will nominate new co owners that will be able to accept 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

No response

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.

PR Plan Summary

I want to connect with more dotnet developers

Infrastructure Requirements Summary

I think nuget and github have everything covered

Additional Notes

No response

@Freysi21 Freysi21 added project application project support Use this label to request support for an existing .NET Foundation project labels Jun 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project application project support Use this label to request support for an existing .NET Foundation project
Projects
None yet
Development

No branches or pull requests

3 participants