GenevaERS

https://github.com/genevaers

we have governance and contribution documentation to track changes along with mailing list, a slack channel and using GIT's issues Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.

we will provide interim versions using git branches

we are using git Repository on GitHub, which uses git. git is distributed.

we will use semantic versioning

will use git tags

we will have a CHANGELOG with all changes for the release

if we are made aware of any CVE will document it

https://github.com/generaers/

we have mailing list,

We track individual issues in GitHub for each repository.

Will respond to meet this criteria

Will respond to meet this criteria

https://githib.com/genevaers/archive

https://github.com/openmainframeproject/GenevaERS/issues

GenevaERS-private@lists.openmainframeproject.org 

tracked via Issues

Will provide a work system e.g. a convenience build and document so users may replicate on their systems

1. on z/OS we use High Level Assembler, Enterprise Cobol and Java
2. does require licenses for the above software except for High Level Assembler but needs HLASM Toolkit licenses if needed
3. all other builds not on z/OS can use FLOSS tools such as gradle

a. we need to use structured macros provided by HLASM Toolkit on z/OS (license needed) - no alternative s it is built on z/OS b. WorkBench and Test Framework will use FLOSS tooling such as GRADLE

We have the Test FrameWork repo for this along with use of Gradle

Will be invoked by GRADLE and written in JAVA

it does

will be followed

will be followed

will track changes to test suite and document addition of new tests, via issues

will document test policy

Will use SONAR LINT and CodeScan Toolkit

all warnings are investigated

will do so

We have such a person

We have a number of staff able to handle this

We do not use communication protocols for remote access

Does not have a need to use cryptography

Does not have a need to use cryptography

Does not have a need to use cryptography

Does not have a need to use cryptography

Does not have a need to use cryptography

Does not have a need to use cryptography except with password storage

Will adhere to OWASP requirements

Does not have a need to use cryptography

This is not a web based application is is a 1:1 application as it is an Eclipse IDE application.

This is not a web based application is is a 1:1 application as it is an Eclipse IDE application.

Will endeavor to do so but we use ECLIPSE IDE which itself may have flaws which is outside our control

Will endeavor to do so but we use ECLIPSE IDE which itself may have flaws which is outside our control

We do supply a ADMIN password for a possible first time use

sonar lint and codescan toolkit and possibly Dependency Checker

sonar lint

Will endeavor to do so but we use ECLIPSE IDE which itself may have flaws which is outside our control

Will deploy GitLab CI/CD,

no C or C++

As most of the product runs on z/OS this is not feasible. The Java portion on the Eclipse IDE maybe possible