Skip to content

sarahseewhy/meeting-tracker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 

Repository files navigation

meeting-tracker

Contents

Introduction

This spike uses the Google Api to develop metrics on calendar events.

It seeks to answer the following questions:

  • How many meetings exist in a given calendar?
  • How many events are created with an agenda?
  • Who organises meetings?
  • How long do meetings last?

This is achieved by creating a standard meeting title format based on the Karma Commit Convention.

Build

This project is not yet in a buildable stage.

If you clone the project you won't be able to build it due to credential authorization and configuration.

I recommend following the tutorials I mention in my Approach section.

Watch this space for updates.

Context

Meetings can be pain but they don't have to be. I recently wrote about it here.

I wanted to create a way to start measuring how my team was investing their collaboration energy. Through measuring we could begin to make improvements.

We've been experimenting with using the Karma Commit Convention (<type>(scope):<subject>) on my team's meeting invites which creates a standard meeting format, one that's a lot easier to query and measure.

Right now for example, we have the following:

meet(graphite): Develop SLIs
retro(team): Last iteration
huddle(slackbot-spike): How to productionise?
1-1(sarah): Discuss meeting-tracker project

We're still working on allowed type values.

Hopefully this will generate some interesting information and conversations.

Approach

I'm following a few resources to get this spike working:

About

Project to run metrics on Google Calendar

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages