Gridify

1. General Information

Project Name: Gridify

License: MIT

Contributor (Company, Organization or individual name(s)): Alireza Sabouri (@alirezanet)

Existing OSS Project? (Yes/No): Yes

Source Code URL: https://github.com/alirezanet/Gridify

Project Homepage URL (if different): Documentation Site

Project Transfer Signatories: Alireza Sabouri Zadeh (@alirezanet) alirezanet@outlook.com

2. Description

Gridify is a dynamic LINQ library that simplifies the process of converting strings to LINQ queries. With exceptional performance and ease-of-use, Gridify makes it effortless to apply filtering, sorting, and pagination using text-based data.

Consider Gridify 𝖺 𝗌𝗂𝗆𝗉𝗅𝖾𝗋/faster 𝖺𝗅𝗍𝖾𝗋𝗇𝖺𝗍𝗂𝗏𝖾 𝗍𝗈 𝗚𝗿𝗮𝗽𝗵𝗤𝗟/𝗢𝗗𝗮𝘁𝗮. 𝖨𝗍 𝖺𝗅𝗅𝗈𝗐𝗌 𝗍𝗁𝖾 𝖿𝗋𝗈𝗇𝗍-𝖾𝗇𝖽 𝗍𝗈 𝗌𝖾𝗅𝖾𝖼𝗍𝗂𝗏𝖾𝗅𝗒 𝖿𝗂𝗅𝗍𝖾𝗋 𝗋𝖾𝗌𝗈𝗎𝗋𝖼𝖾𝗌 𝖺𝗇𝖽 𝗋𝖾𝗊𝗎𝖾𝗌𝗍 𝗈𝗇𝗅𝗒 𝗍𝗁𝖾 𝗇𝖾𝖼𝖾𝗌𝗌𝖺𝗋𝗒 𝗋𝖾𝖼𝗈𝗋𝖽𝗌.

3. Project Governance

Project Lead:

Name: Alireza Sabouri
Email: alirezanet@outlook.com
GitHub Profile URL: https://github.com/alirezanet

Committers:

@alirezanet

Governance Model:

No Governance Model developed So-Far. I usually do it myself.

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

CLA Notification Alias
Provide an email address that will receive CLA related notifications from the .NET Foundation CLA automation

n/a

Assignment Model. Under the .NET Foundation assignment model, project ownership and other intellectual property is assigned to the .NET Foundation and the .NET Foundation agrees to grantback a license to the contributor(s).

Contribution Model. Under the .NET Foundation contribution model, a project retains ownership of the copyright, but grants the .NET Foundation a broad license to the project’s code and other intellectual property. The project also confirms that the project’s submissions to .NET Foundation are its own original work (there are also instructions for any third party materials that might be included).

I am ok with both also not sure which one I should choose. probably it's better if you choose the one that is more suitable for .NET Foundation.

4. Repository Layout

The .NET Foundation host guidance for new projects and details on recommended structure here:
https://github.com/dotnet/home/tree/master/guidance

Note that the open source repository should be the master where changes are made by the core development team using the same PR process that is used for non-committer contributions.

Please define below any changes you would want to make to your repositories as part of the process of joining the .NET Foundation

5. Eligibility Criteria

Please complete the following for your project

• The project is built on the .NET platform and/or creates value within the .NET ecosystem.

• Yes
• No

• The project produces source code for distribution to the public at no charge.

• Yes
• No

• The project's code is easily discoverable and publicly accessible (preferably on GitHub).

• Yes
• No

• 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).

• Yes
• No

• When applicable, project must use reproducible build settings in its toolchain.

• Yes
• No

• The project uses Source Link.

• Yes
• No

• The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).

• Yes
• No

• The project code signs their artifacts as appropriate.

• Yes
• No

• The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.

• Yes
• No

• 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).

• Yes
• No

• 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.

• Yes
• No

• The copyright ownership of everything that the project produces is clearly defined and documented.

• Yes
• No

• The project has a public issue tracker where the status of any defect can be easily obtained.

• Yes
• No

• The project has a published Security Policy.

• Yes
• No

• The project has a home page which provides high level information about its status and purpose.

• Yes
• No

• The project has a public communication channel where community members can engage with maintainers.

• Yes
• No

• The project has a publicly available location where members can review and contribute to documentation.

• Yes
• No

6. PR Plan

Please summarize the public relations plan for the announcement when joining the foundation (and releasing as open source if appropriate). What is the main story we wish to promote, through what channels, what issues should we be aware of? For significant news events then please also work with your .NET Foundation contact to ensure a full PR plan is developed.

7. Infrastructure Requirements

Please describe any infrastructure requirements for the project. For example, how will build servers be operated? Any web hosting or service hosting requirements? Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases?

none

8. Additional Notes

Please provide any additional information required or use this area for notes during the onboarding process. If this open source project has similarities with any other projects in this space then please detail them and why this project is different. If there are any potential issues that you feel the project might need help with early on then also state them here and discuss with your .NET Foundation Contact.

I hope this project can help me to join this great community and learn from professionals, also can help others to solve their problems.

thank you