Technical Roles & Leads

A project is made successful by the amazing people involved. This page documents some of the major roles that make up the OpenVox project and the people in these roles.

Some roles are not currently filled, and for those we invite you to learn about the application process.

Role	Responsibilities	Lead	SIG
Social Media Lead	Attract contributors to the project		SIG
Security Team Lead	Oversee security response protocol		SIG
Release Engineering Lead	Manage & operate build pipelines		SIG
Infrastructure Team Lead	Manage & coordinate infra needs	Gene Liverman	SIG
OpenVox Core Framework Lead	Maintain core ruby project
OpenVox Server Lead	Maintain Clojure server project
OpenVox Database Lead	Maintain openvoxdb
Facter Team Lead	Coordinate the Facter fork	Romain Tartière	SIG
OpenVox SDK Team Lead	Coordinate the SDK development.	Jason Straw	SIG
Bolt Team Lead	Coordinate the Bolt fork

---

Evangelists and Social Media

One of our big challenges is and will continue to be awareness and attracting participation. People looking at an open source project don't always understand that they're actively invited to participate and that whatever skillset they have will be happily welcomed. The role of evangelism here is to attract these people and to help get them contributing.

This role will benefit from technical expertise, but does not require it. For example having hacked on Puppet core or extensions might help you connect with developers you're trying to engage. Far more important is the ability to connect with people and to write reasonably well.

Duties:

• Outreach according to your time and skills. This could include things like:
  • social media engagement
  • speaking at conferences
  • coordinating meetups
  • hosting a podcast or twitch stream
  • writing press releases
• Onboarding materials and processes
• Tutorials and other developer enablement
• Documentation on wiki & web
• Own this and the application wiki pages ;-)

Security Team Lead

In order to ensure the security of our users, we will need a more robust security response protocol. The person in this role will oversee and maintain this protocol. That doesn't mean 24x7 availability to respond personally to every security report. It means coordinating a team that can make that guarantee.

Duties:

• Oversee the security response protocol
• Update and improve protocol as needed
• Evaluate CVEs in dependencies for applicability to OpenVox
• Notify engineering leads of CVEs in dependencies

Release Engineering Lead

Nick's been doing a bang-up job, but it's time for someone else to take over.

Duties:

• Maintain and evolve the OpenVox build system ** Vanagon, Ezbake, GitHub actions
• Maintain system for signing packages
• Perform releases of openvox-agent, openvox-server, and openvoxdb as needed

Infrastructure Team Lead

A project of this magnitude has a lot of moving parts in our infrastructure. We've got mirrors, and CI hardware, and webhooks, and mail, and more. Someone's got to keep track of it all!

Duties include (but not limited to):

• Maintain the GitHub OpenVoxProject org
• Work with OSU OSL on maintaining the S3 buckets
• Maintain testing infrastructure (VMs, cloud hosts)
• Work with mirror providers
• Ensure proper backups of all important bits

OpenVox Core Framework Lead

This person is responsible for leading the development of core OpenVox features. Because of the way Puppet was originally architected, agent and compiler and server features are all commingled into the single puppet repository.

Duties:

• Ruby development
• OpenVox agent/compiler architect when we want to add new features
• PR reviews
• Preparing openvox-agent for release before handing off to RE lead
• Participate in language steering committee

OpenVox Server Lead

This person is responsible for leading the development of OpenVox Server features. Because of the way Puppet was originally architected, is commingled into the single puppet repository and the openvox-server project wraps around it.

Duties:

• Ruby, JRuby, and Clojure development
• JVM maintenance
• OpenVox server architect when we want to add new features
• PR reviews
• Preparing openvox-server for release before handing off to RE lead
• Participate in language steering committee (somewhat optional)

OpenVox Database Lead

This person is responsible for leading the development of OpenVoxDB features.

Duties:

• Clojure development
• JVM maintenance
• OpenVoxDB architect when we want to add new features
• PR reviews
• Preparing openvoxdb for release before handing off to RE lead