Contributing

DevOpsTribe is looking for contributors in two main areas:

  • writing technical articles
  • contributing to the development of our tools.

Below are some details:

Writing Technical Articles

DevOpsTribe covers topics in the following areas, listed in order of priority:

  1. DevOps, GitOps, DevSecOps, Platform Engineering
  2. Tools sponsored by the Cloud Native Computing Foundation
  3. Software development

To participate, we offer the opportunity to become authors for our blog. In return, we provide training and access to the necessary hardware resources for various tests.

The workflow is as follows:

  • Propose articles via email to luckysideburn [at] gmail [dot] com
  • Wait for confirmation of the article topic acceptance
  • Optionally, we will provide hardware resources and supporting material (at the expense of DevOpsTribe)
  • Article review
  • Publication

Contributing to Tools in Development

Kubeinvaders

GitHub Repo: https://github.com/lucky-sideburn/kubeinvaders

Required skills: LUA, Kubernetes, Javascript, CSS, HTML, Python, Nginx, Prometheus

  1. Testing on various Kubernetes distributions (RKE, K3S, GKE, AKS, EKS, OKE)
  2. Improving the graphical interface
  3. Developing a report to certify the resilience of a Kubernetes cluster

TrainingShells

GitHub Repo: https://github.com/DevOpsTribe/training-shells

Required skills: Congruit, Jenkins, Linux, Kubernetes, Tmux

It is crucial to understand how https://github.com/DevOpsTribe/congruit works.

  1. Review https://github.com/DevOpsTribe/training-shells
  2. Select the stockroom you want to contribute to
  3. Write “places,” for example: https://github.com/DevOpsTribe/training-shells/tree/main/stockrooms/create_tmux_session_bash_training/places
  4. Write “works,” for example: https://github.com/DevOpsTribe/training-shells/tree/main/stockrooms/create_tmux_session_bash_training/places
  5. Write “workplaces,” for example: https://github.com/DevOpsTribe/training-shells/tree/main/stockrooms/create_tmux_session_bash_training/workplaces
  6. Request access to https://ci.devopstribe.it/
  7. Write the Jenkins Job
  8. Test the training session

SFComet

GitHub Repo: https://github.com/lucky-sideburn/sfcomet

Required skills: Hashicorp Vault, Ansible, Golang, Vagrant

It is crucial to review the repository: https://github.com/lucky-sideburn/sfcomet

  1. Clone https://github.com/lucky-sideburn/sfcomet
  2. Configure an OORT Panel using the Vagrantfile
  3. Understand the functioning of comets and associated fencing mechanisms
  4. Write new features to automatically detect files to observe checksums
  5. Resolve any latency issues… the system is fast in detecting checksum mismatches and proceeding with the fencing mechanism?

If you are interested in contributing in any of these areas, please feel free to contact us at luckysideburn [at] gmail [dot] com. Thank you for your attention and interest in DevOpsTribe!