---
published: true
layout: post
title: Weekly Public API Governance Office Hours Each Thursday at 12:00 PM EST
tags:
  - Office Hours
  - Governance
  - Meetings
image: >-
  https://kinlane-productions2.s3.amazonaws.com/algorotoscope-master/bf-skinner-san-francisco-wharf-clock.jpg
---
I have been planning on adding weekly public office hours to help drive a discussion around the API governance needs of the community since the beginning of the year. I was struggling getting some customers to agree on participating in a public discussion versus paid private sessions, but we’ll just go ahead and get things rolling while they work things out. With this in mind, I am officially adding to the weekly schedule, **API Evangelist API Governance Office Hours each Thursday at 12:00 PM EST**. I don’t want to inject too much into the agenda, and would prefer hearing from the community, but to kick things off, I propose the following.

- **Specs** - Discuss OpenAPI, AsyncAPI, JSON Schema, as well as Spectral and Vacuum rules.
- **Operations** - Talk about governance at design, development, pipelines, and gateway layers.
- **People** - Discussion around what is needed by people when it comes to API governance work.
- **What Else?** What could we be talking about that is needed across the API community?

This is a public event and will be recorded. Let’s avoid pitching products and services--I understand it is impossible to avoid references to what each of our products and services offer, but let’s try to keep it based upon what the community needs and not just selling to each other. Everyone I have talked with has agreed that 12:00 PM EST would allow the west coast US to join first thing in the morning while still giving Europe a chance to join in on the discussion.

The goal of these office hours is to better understand what the API community is needing when it comes to API governance, giving product and engineering stakeholders a place to share their needs, ask questions, while also providing API service providers and the wider community a chance to share their knowledge, and experience. I think that API governance is the top issue the community is facing and look forward to hear what people are needing.

<h1 class="fs-3 mb-5" id="rule-name-header">Register</h1>
<p>You can register for the office hours by emailing me <a href="info@apievangelist.com">info@apievangelist.com</a> and I will add you to the list, or you can use the form below.</p>
<form action="https://formspree.io/f/mblrpwra" method="POST" name="contact" style="padding: 5px;"> 
  
<label for="role">Your Name</label>
<input type="text" class="form-control" id="name" name="name" placeholder="" style="width: 100%;">
  
<label for="email">Your Email</label>
<input type="email" class="form-control" id="email" name="email" placeholder="name@example.com" style="width: 100%;">
      
<label for="role">Your Role</label>
<input type="text" class="form-control" id="role" name="role" placeholder="" style="width: 100%;">
        
<label for="company">Your Company</label>
<input type="text" class="form-control" id="company" name="company" placeholder="" style="width: 100%;">
              
<label for="other">Other Questions</label>
<textarea id="other" class="form-control" name="other" rows="4" style="width: 100%;"></textarea>

<a href="#" onclick="document.contact.submit();"><button type="button" class="btn btn-primary">Submit</button></a>
</form>