MiniExcel .NET Foundation Project Application

[shps951023]

Project Name

MiniExcel

License

Apache-2.0

Contributor

Wei Lin, mini-software team

Existing OSS Project?

Yes

Source Code URL

https://github.com/mini-software/MiniExcel

Project Homepage URL

No response

Project Transfer Signatories

Wei Lin shps951002@gmail.com

Description

MiniExcel is simple and efficient to avoid OOM's .NET processing Excel tool.

At present, most popular frameworks need to load all the data into the memory to facilitate operation, but it will cause memory consumption problems. MiniExcel tries to use algorithm from a stream to reduce the original 1000 MB occupation to a few MB to avoid OOM(out of memory).

Name

Wei Lin

Email

shps951002@gmail.com

GitHub Profile URL

https://github.com/shps951023

Committers

No response

Discord Ids

No response

Governance Model

Maintainers

• Responsible for one or more components within the project.
• Review and merge pull requests related to their components.
• Address issues and bugs related to their components.

Pull Requests

• All changes to the project must be made through PRs.
• PRs must be reviewed by at least one core contributor before merging.
• Contributors should follow the project's coding standards and guidelines.

Issue Tracking

• All bugs, feature requests, and enhancements must be tracked using Issues.
• Community members are encouraged to report issues and suggest improvements.

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

Open source project to make better .NET community.

Infrastructure Requirements Summary

No response

Additional Notes

No response

[sbwalker]

The Project Committee reviewed your application and will recommend the project for consideration of Member status at the next Board of Directors meeting. The project will require a majority Board vote to proceed.