Contributing

Document Control

TODO:

  • Overall structure.
  • Initial draft complete
  • Testing
  • Ready

Contributions not yet open

The framework is still under development, and things are very likely to change. Once the baseline roles and structure is created and running under CI/CD, along with playbooks for integration testing running on Cloud / VMs, contributions will be open.

Development model:

  • Roles are developed individually, and published on Github, tested with TravisCI and pushed to Ansible Galaxy.
  • Playbooks are created for specific scenarios, and tested at regular intervals.
  • Specific releases are build from versioned roles.
  • Roles follow the gitflow guidelines.

Chat Group

  • Slack, IRC or Discord? Not yet decided.

How to contribute

  • Pull requests

Supported Versions

Ensure that all roles and playbooks are tested using:

  • Python ⅔
  • Ansible 2.4, 2.8, 2.9
  • OS: RHEL ⅞, CentOS ⅞, Fedora 30/31, Ubuntu 18.04, Debian 10

This should be captured in the tox / travisci test matrix

Coding Standards

Apply the coding standards and best practices described in the Ansible Best Practices section.

All contributions should be tested using ansible-lint, yamllint and molecule and follow the cookiecutter template.

Where to contribute

  • Testing:
  • Documentation:
  • New Roles:
  • New Playbooks:

Hackathons

The following hackathons / workshops have been set up:

- Dublin, …

Last update: 2020-02-15