Page Comparison

...

1. Use HuBoard and accept the strange labels
   1. Pros
      1. One spot to see all of the issues
      2. Does not stop other parties from working on issues
   2. Cons
      1. Weird labels
2. Use ZenHub
   1. When we due sprint planning, create mirror issues in the maintenance repository linking to the issues we wish to close
   2. Pros
      1. ZenHub has some better PR association functionality (supports blocking)
   3. Cons
      1. We need to create and maintain mirror issues
3. Create a Github Project board in the Samvera Organization
   1. Should have access to the the repositories we need to add
   2. Adding a repository alone still requires that one manually add tickets to columns
   3. Can request Product Owners to add issues to a Project
   4. Appeared that there was a 5 repository limit for a Project
   5. We might also avoid linking to repositories, and just populating the Projects with issues

Samvera-Labs

We don't need to be concerned with this as a separate Organization

If we needed to promote a component, we could just create mirror issues

Or, we could simply maintain two separate boards