Issue: New .NET Foundation Project Application

[pournasserian]

Project Name

FluentCMS

License

MIT

Contributor

Momentaj Inc

Existing OSS Project?

Yes

Source Code URL

https://github.com/fluentcms/FluentCMS

Project Homepage URL

https://fluentcms.com/

Project Transfer Signatories

• Amir Pournasserian [email protected]
• Hadi Ahmadi [email protected]

Description

FluenCMS is an open source AI Driven ASP.NET Core Blazor Content Management System (CMS) supporting headless CMS features.

Name

Amir Pournasserian

Email

[email protected]

GitHub Profile URL

https://github.com/pournasserian

Committers

• Amir Pournasserian (https://github.com/pournasserian) - founder/owner
• Hadi Ahmadi (https://github.com/TheHadiAhmadi) - employee
• Afshar Mohebbi (https://github.com/afsharm) - employee

The employer is Momentaj Inc.

Discord Ids

• pournasserian
• thehadiahmadi

Governance Model

Governance Model for FluentCMS

FluentCMS follows a transparent and collaborative governance model designed to encourage community participation and maintain high code quality.

Proposal and Review Process

1. Proposing Changes: New code changes, including features, bug fixes, and documentation improvements, are proposed via GitHub pull requests (PRs). Contributors are encouraged to follow the contribution guidelines provided in the project's repository.

2. Review Process:

   • Initial Review: All pull requests are subject to an initial review by the core maintainers. This review checks for adherence to coding standards, project guidelines, and overall code quality.
   • Community Feedback: Once the initial review is passed, the PR is open for community feedback. Community members can comment, suggest changes, or approve the PR.
   • Core Maintainers Approval: After incorporating feedback from the community, the PR must receive final approval from at least two core maintainers.

3. Acceptance: Once a pull request receives the necessary approvals, it is merged into the main branch. Automated tests and continuous integration processes ensure the stability of the codebase.

Identifying and Appointing New Committers

• Active Contributors: Contributors who consistently provide high-quality contributions, participate in code reviews, and engage positively with the community are considered for committer status.
• Nomination: Existing committers or core maintainers can nominate active contributors for committer status. The nomination is discussed within the core team.
• Decision: The decision to appoint a new committer is made by consensus among the core maintainers. Once a decision is reached, the new committer is granted appropriate access and permissions.

Core Maintainers

The core maintainers are responsible for the overall direction of the project, ensuring code quality, and fostering a welcoming and productive community environment. The maintainers list is public and regularly updated in the project's documentation.

By adhering to this governance model, FluentCMS aims to build a sustainable and thriving open-source community, continuously improving through collaboration and shared responsibility.

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

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.

PR Plan Summary

Main Reason for Joining the .NET Foundation

The primary reason for FluentCMS seeking to join the .NET Foundation is to leverage the Foundation's resources, support, and community to enhance the project's visibility, credibility, and growth. By joining the .NET Foundation, we aim to:

1. Increase Visibility and Adoption: Being part of the .NET Foundation will increase the visibility of FluentCMS within the .NET developer community and beyond, encouraging more developers to adopt and contribute to the project.

2. Ensure Long-Term Sustainability: The support and governance provided by the .NET Foundation will help ensure the long-term sustainability and health of the FluentCMS project, providing a stable foundation for future development.

3. Enhance Community Collaboration: The .NET Foundation’s collaborative environment will foster greater community engagement and collaboration, attracting new contributors and maintaining a high level of activity within the project.

4. Access to Best Practices and Resources: Joining the .NET Foundation will give us access to a wealth of best practices, resources, and tools that can help improve our development processes, project management, and overall code quality.

5. Legal and Operational Support: The Foundation’s legal and operational support will help manage intellectual property concerns and streamline contributions, ensuring a robust and legally sound contribution process.

By joining the .NET Foundation, FluentCMS aims to grow its community, enhance its development practices, and ensure its continued success and relevance within the .NET ecosystem.

Infrastructure Requirements Summary

Infrastructure Requirements Summary

Build Servers:

• Continuous Integration (CI): FluentCMS utilizes GitHub Actions for continuous integration. Build servers are required to run automated tests and build processes for each pull request and commit to the main branch.
• Continuous Deployment (CD): Deployment pipelines are set up to automate the deployment process to our hosting environment.

Hosting and SSL:
We don't provide hosting and developers should host their own instance (an use their own SSL).

Additional Notes

No response

[sbwalker]

Project will be reviewed today at the Project Committee Monthly Meeting

[sbwalker]

The Project Committee Charter (https://github.com/dotnet-foundation/projects) contains activity criteria which is used to evaluate project applications. At our most recent meeting, it was agreed by the Committee that this project does not currently exhibit activity or adoption metrics at a level which would allow for an application approval- however based on the broad applicability, it will be included in the Seed category for consideration as a Member project in the future.