Issue: New .NET Foundation Project Application - Query Builder

[nithyav2017]

Project Name

Query Builder

License

MIT

Contributor

Nithya

Existing OSS Project?

No

Source Code URL

https://github.com/nithyav2017/nithya-devhub/tree/master

Project Homepage URL

Project Transfer Signatories

Name : Nithya Venkatakrishnan
Email Address: nithya.venkatakrishnan2017@gmail.com

Description

Dynamic Query Composition in .NET: Introducing QueryBuilder Tool

Overview:
Entity Framework Core Query builder is a lightweight utility that simplifies building dynamic LINQ
queries for Entity Framework Core.

Motivation:

• Many applications need filterable/searchable API endpoints
• This tool standardizes the filtering/pagination logic.

Goals:

• Provide a fluent API to build queries dynamically.
• Support Where, OrderBy, Skip, Take out of the box.
• Allow JSON- based query definition, making it easy for frontends to send filter objects.
• Keep lightweight , dependency-free , and EF core friendly.
  Non-goals:
• No complex joins or groupings , sending JSON filter objects from the front end in first release(future version may add).

What are you hoping from the foundation

As a first time contributor , I'm hoping the .NET foundation can provide guidance as I enhance my project . I am eager to connect with others who value reusable utilities and collaborative learning. I'm especially interested in learning how to manage issues, triage feedback , and maintain a healthy release cadence. I'd appreciate mentorship and resources that help me evolve Querybuilder into a reliable tool for the community.

Name

Nithya

Email

nithya.venkatakrishnan2017@gmail.com

GitHub Profile URL

No response

Committers

No response

Discord Ids

No response

Governance Model

• All changes are proposed via pull requests to the "master" branch.
• PRs are reviewed for clarity, correctness and alignment with project goals.
• The "master" branch is kept stable - no direct pushes.

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.

Describe why you are applying for Project Membership.

I'm applying for Project Membership to grow QueryBuilder into a reliable open source tool with community support and best practices from the .NET Foundation

Infrastructure Requirements Summary

No response

Additional Notes

No response

[glennawatson]

Hi,

There is no license file I can find the in repository which means it doesn't meet the requirements.

[nithyav2017]

Thank you for taking time to review my project. I've now added a MIT License file specifically for the QueryBuilder module to ensure it meets the permissive licensing requirements. Please let me know if any further clarification is needed. For your reference, here is the license file:
https://github.com/nithyav2017/nithya-devhub/blob/master/LICENSE

[glennawatson]

Just a heads up.

Normally membership is associated with larger established projects.

The help you need from the foundation might be worth jumping on our discord server and asking for help around maintaining our projects area of the server. It's not something at the moment we offer with either seed or full membership.

If you're still keen to go ahead with the submission the project committee meets once a month. We already had our meeting this month so would be included in the November round.

[nithyav2017]

Thank you for the feedback. I've taken some time to reflect on the feedback and wanted to share a bit more about my intention: QueryBuilder is part of a startup initiative focused on building reusable , contributor-friendly modules for the .NET ecosystem. My goal is to make it discoverable and valuable to other developers and maintainers. I'm currently refining its architecture and onboarding clarity, and I'll be engage on Discord server to align QueryBuilder with contributor-friendly best practices. I appreciate any guidance on what makes a project more discoverable or contributor-friendly.