---
# System prepended metadata

title: Collaboration Tools Discussion
tags: [better-collaboration]

---

---
title: Collaboration Tools Discussion
tags: better-collaboration
---
# Collaboration Tools Discussion

[TOC]

# Backlog and Roadmap


## Goals
1. Make our prioritization and progress easily visible to the community.
2. Allow collaboration with the community.
3. Do not create more overhead.

## Constraints

- Our repos are in the [`vmware-tanzu` Github org](https://github.com/vmware-tanzu/)

## Concerns

- We write (tiny) stories that are shapped differently than what people typically see as Issues in Github.
  - This might be confusing
  - It's a bad look when there are 100+ issues

## Options

- Pivotal Tracker
- Github Projects
- Zenhub (TL;DR. GitHub Projects + Tracker-ish features)
  - Velocity
  - Epics
- Zube

## Proposals

### Zenhub Façade

- Continue to use Tracker as we have.
- Use Zenhub as a public/community view.
  - For each _epic_ in Tracker, create 1:1 an epic in Zenhub.
  - When progress is made, we figure out how to efficiently reflect that progress in the Zenhub epic.

### GitHub Org-wide Project

- Create "backlog" repo in GitHub
  - move items from Track to this repo
- Create a org-scoped Github project
  - link all Carvel repos

# Shared Documents

- Google Docs
- hackmd.io
- Microsoft OneNote
- Confluence
