FINOS Financial Objects Project Activation

Description

This issue has been created to encapsulate materials provided by the Financial Objects project team to directly drive the FINOS Financial Objects project to an Active state.

Steps to Complete

For each criteria listed below, the Financial Objects team must provide evidence that describes the project's maturity to progress the project state from an Incubating Project to an Active Project.

The supporting evidence and commentary should be provided in the comments of this issue prior to any further discussion and deciding vote.

FINOS Activation Criteria

https://finosfoundation.atlassian.net/wiki/spaces/FINOS/pages/75530376/Activation

Activation	(promotion to Active State)
What it means for consumers?	The Project is high quality, mature from a codebase and community dynamics perspective. The Project produces valuable releases to solve a useful business problem for our Community.
What it means for the Project Team?	Increased visibility and positioning in FINOS web resources, marketing and Community building efforts like meetups, blog posts, etc.
QUALITY & SECURITY
Development Process	The Project adopts best-of-breed standards of distributed software development, including but not limited to: semantic versioning tagging / branch protection continuous integration ("CI") and continuous delivery ("CD") where applicable If Project Team choses not to use the FINOS provided Open Developer Platform (ODP), a comparable SDLC should be adopted and made available.
Build & Release	The Project code/documentation release process automated or at lest well documented. If code is published, publicly redistributed release binaries should be listed or referred to in the documentation (e.g. under the FINOS namespace in an artefact repository or package manager, e.g. NPM, Maven Central, etc.)
Security	No OWASP Top 10 warnings are present in the code No long-standing medium or higher vulnerabilities (2+ months) and proper security disclosure processes Any cryptographic functions and key lengths used within the software should be identified and vetted with Foundation's legal counsel in order to request compliance with U.S. Export policy. Read more about FINOS Security vulnerabilities responsible disclosure and how to automate scanning with WhiteSource.
Documentation	The README.md must include or reference up to date: end user docs, including a description of the software, feature overview, installation & configuration instructions developer docs, including links to other external systems (further docs, wiki, CI & validation tools, artefact repository, change log / history, etc.) where possible badges (e.g. from shields.io) are encouraged sample code explaining how to use the project, library, standard, SDK, etc.
DIVERSITY & VIABILITY
Community	Project has active participation from 2+ independent individuals and/or organizations; Ideally Project Team members who make contributions in connection with their employment are doing do as part of their regular job duties.
Project Team	Project Team has/have demonstrated active involvement in PMC and have demonstrated commitment to furthering overall Program goals
License	Project must not have dependencies which effectively restrict how the project may be distributed or deployed and must not depend on any proprietary third-party components for their core functionality.
Trademark	Community is using a different established Project name or original contribution trademark is owned by FINOS. All Project related websites and assets are owned and hosted by FINOS.
ROADMAP & RESOURCES
Progress	Project has progressed against its public roadmap during incubation; roadmap is aligned with, and where applicable incorporated into, the overall program roadmap or backlog
Versioning	Project software is production grade and ready for large scale consumption. 1.0.0 version was released and announced it to the announce@ mailing list.
Roadmap	Projects share and work to a public roadmap, aligned with the overall program roadmap.
FINOS Support	Project Team is largely self-sufficient, requiring minimal operational support from FINOS to govern the maintain the project. FINOS support switches to strategic growth of the Project in the Community.
GROWTH & ADOPTION
Usefulness	The Project demonstrably solves a real life use case in the Community. Evidence of adoption beyond the contributing individuals or firms (e.g., in the form of download statistics, listing known deployments or implementations, etc.)
Status Badging	Project Team commits to adopt the FINOS Active badge in the README.md once PMC approves activation properly signal adopters the new state of the Project
HYGIENE & OPERATIONS
Compliance	The appropriate license text is included in each source file's header. See details and template
Community Inquiries	Community inquiries on the project channels (mailing lists, issues and pull requests, etc) are generally promptly answered
Meeting Hygiene	If the project meets regularly on-line, the Project Team has demonstrated a track record of publishing and distributing agenda no less than 24 hours before the meeting, and publishes meeting minutes after calls.
Transparency	Project Team has adopted a transparent governance model(*) consistent with FINOS Community governance. Work for new contributors is organized into issues within a public issue tracking system, as appropriate, tagged as "Good First Issues"