githubEdit

6.1 Development

govstack-cfr-development 2.0.0

#1 All application source code and comments are clear and maintainable, written in English. (REQUIRED EXTENSIBLE)

All application source code and comments are written clearly in English and structured for readability and maintainability. Code must follow a consistent style guide, naming conventions, and folder structure.

#2 EOL SHOULD be at Least 5 Years (RECOMMENDED REPLACEABLE)

No languages, frameworks, or dependencies should be used in a building block where that component has an EOL of less than 5 years.

Building block includes unit and integration tests to validate functionality and facilitate regression testing.

Audits can be run across code and dependencies using automated tools such as SonarQube or Snyk.

#5 Preference for the top 25 languages listed in either the TIOBE Index or any of the three IEEE Spectrum rankings (RECOMMENDED REPLACEABLE)

See https://www.tiobe.com/tiobe-index/arrow-up-right, https://spectrum.ieee.org/top-programming-languagesarrow-up-right

Where possible, building blocks SHOULD be written using commonly used languages to ensure ongoing maintenance and support are as easy as possible. Building blocks MAY leverage less common languages, such as shell scripting where needed.

See https://standard.publiccode.net/arrow-up-right and practices outlined here:

#7 All application source code uses version control (e.g. Git). Database schema changes are managed with migration scripts. (RECOMMENDED EXTENSIBLE)

All source code is version controlled (e.g., Git), and database schema changes are managed through migration scripts.

All software developed includes a clear open-source license.

Last updated

Was this helpful?