MethodicConfigurator

Compliance

ArduPilot Methodic Configurator adheres to multiple compliance standards and best practices:

Usability

• Wizard like interface, allows user to concentrate in one task at a time
• All GUI elements contain mouse over tooltips explaining their function
• Relevant documentation opens automatically in a browser window
• Uses What you see is what gets changed paradigm. No parameters are changed without the users’s knowledge
• Translated into multiple languages
• No visible menus, no hidden menus.

Code Quality

• Follows PEP 8 Python code style guidelines
• Maintains high code quality through automated linting (static code analysis), all using strict settings:
  • Pylint automated workflow,
  • Ruff automated workflow,
  • mypy automated workflow and
  • pyright automated workflow
• Uses PEP 484 type hints
  • Enforces type checking with MyPy and pyright type checkers
• Automated code formatting using ruff for consistency
• Code and documentation are spell checked and english grammar checked
  • markdown-lint automated workflow and
  • markdown-link-check automated workflow
• Follows object-oriented design principles and clean code practices
• Implements comprehensive error handling and logging, with 5 verbosity levels
• Implements PEP 621 project metadata standards
• Adheres to Keep a Changelog format
• Complies with Python Packaging Authority guidelines

Software Development

• Implements continuous integration/continuous deployment (CI/CD) practices
• Maintains comprehensive assertion-based test coverage through pytest
• Uses semantic versioning for releases
• Follows git-flow branching model
• Implements automated security scanning and vulnerability checks
• Implements git pre-commit hooks to ensure code quality and compliance on every commit
• Implements reproducible builds with locked dependencies
• Uses containerized CI/CD environments for consistency
• Uses automated changelog generation
• Implements automated dependency updates and security patches using renovate and dependabot

Open Source

• Complies with OpenSSF Best Practices for open source projects
• Uses REUSE specification for license compliance
  • Uses CI job to ensure compliance
  • Uses SPDX license identifiers
• Maintains comprehensive (more than 5000 lines) documentation
• Implements inclusive community guidelines
• Provides clear contribution procedures

Security

• Regular security audits through Snyk, codacy, black duck and other tools
• Follows OpenSSF Security Scorecard best practices
• Uses gitleaks pre-commit hook to ensure no secrets are leaked
• Implements secure coding practices, runs anti-virus in CI
• Maintains security policy and vulnerability reporting process

This site is open source. Improve this page.