EPAM Glue

Development Process

The current contributor(s) commit to adopt a development process suitable for distributed development -- i.e., well established ways of working in successful open source projects, like automated builds, CI/CD and maintaining a public backlog of issues. Access and support for the FINOS Open Developer Platform (ODP) is offered free of charge to all Project Teams for this purpose.

Build & Release

If pre-existing software is contributed and there is a build process required to make software work, that build should work successfully as documented using publicly available artefacts.

No build process, it’s a set of scripts

Security

No high or critical vulnerabilities are discovered by scanning systems during FINOS contribution due diligence or they are resolved before the code base is brought into FINOS. Read more about FINOS Security vulnerabilities responsible disclosure and how to automate scanning with WhiteSource.

Per no issue was found.

Documentation

The README.md must include a description of the idea or how to use and build any pre-existing contributed software

Documentation available in README.md

Community

The Project Team seeks more contributions, as well as wider adoption and feedback; the Project has a good idea of tasks (e.g. "good first issue) for new contributors to work on.

Maintainers are actively seeking new contributors, including hosting a virtual meetup, a blog post, and community@ socialization email.

Project Team

One or more initial contributors, agree to form the initial Project Team (with a named Lead Maintainer) and are able to further maintain the code base and work with prospective contributors.

3 Maintainers have been identified from EPAM (see github team) and (Github ID: yasenfingarov) is the Lead Maintainer.

License

Project is Apache v2 licensed or one of the Category A licenses. If your Project uses another license please get in touch with the FINOS Legal team.

Per , license validation passed.

Trademark

Contributors choose a different name for the contributed Project or commit to transfer to FINOS the original contribution trademark and all related assets (web domains, websites, etc).N

The contributing team does not own or has registered a trademark for the project. FINOS will not immediately seek to register a trademark as naming is very broad, but team and FINOS agree that in the future they might look for a new mark in case need arises to register it.

Progress

New Projects might involve existing code, but can also be an idea or proof of concept which gets developed and accelerate in the Open.

Existing code was contributed to validate the project concept at

Versioning

Projects releases versions below 1.0.0 (or equivalent based on existing number scheme used in project).

There’s no current release from the project and the guidance to use semantic versioning has been shared.

Roadmap

The Project Team commits to building and working towards a public roadmap, aligned with the overall program Roadmap.

Issues are being worked directly on Github and will become the base for a milestone / roadmap plan.

FINOS Support

The Project Team can work with FINOS to identify areas where they may need further help and support form the Community and the FINOS team

Team has engaged directly with . Support is planned to ramp down post contribution as currently Glue is not a QFP.

Usefulness

The contributed code or idea has the potential to be useful to end users and organizations in the financial industry (even if the code base / project is not necessarily finance-specific)

The idea has been thoroughly socialized and has the potential to benefit a large and important part of our Community, the buy side, so it fits the bill in terms of usefulness.

Status Badging

Project Team is ready to adopt the FINOS Incubating badge in the README.md once contribution is approved

Badge is in the README.md.

Compliance

Before or during contribution, Project should work with the FINOS team to comply with the FINOS contribution compliance requirements, including LICENSE, NOTICE and CONTRIBUTING files are present and correct.

Validated in

Community Inquiries

The project team commits to answer to Community inquiries on the project channels (mailing lists, issues and pull requests, etc)

Team will interact via Github issues If further channels are needed (e.g. chat, mailing list, etc.) please reach out to help@finos.org

Meeting Hygiene

If the Project holds meetings, the Project Team commits to preparing and distributing agenda and as meeting minutes in accordance to guidelines to run good meetings.

The project is not currently planning to hold meetings.

Transparency

Project Team commits to work with FINOS to implement a transparent governance model(*) and publish a roadmap for the project towards activation.

Roadmap currently being worked on in Github