---
# System prepended metadata

title: QHub Project Management
tags: [qhub, quansight]

---

# QHub Project Management
###### tags: `qhub` `quansight`

## Goals

The goals should drive the project mangement around QHub meaning that plans will adapt to goals.

 - Keep Dharhas informed about the weekly progress of QHub and how we are tracking with goals to enable him to talk with clients about QHub developments
 - Set expectations on available hours to help prioritize which issues will be addressed in the week
 - Conversations during meetings are tracked and captured
 - Meetings will have agendas
 - Everyones time is important meetings should stick to times
 - Clients are happy with their QHub experience
 - New qhub users are happy with responsiveness
 - Onboard and upskill people on team
 - Demonstrate Quansight's expertise

## Meetings

 - virtual standups via [standup and prosper](https://standup.teaminator.io/) not necessarily every day (I think Tuesday and Thursday make sense before meetings)
     - put available hours into standup response

 - start the idea of pair programming negotiation, explain the purpose [1]


    

   - Tuesday
     - announcements
     - Who's taking notes?
     - determine who has bandwidth to interact with community 
     - how are we progressing towards long term goals
     - prioritize issues for week
     - ending early is good
     - breakout into technical discussion outside of meeting
     - open floor to pair programming

   - Thursday meeting
     - announcements
     - issue grooming
       - define target audience
       - define success on every issue
     - open floor to pair programming

 - monthly
   - High level Strategy Meeting
     - next release what will happen
     - critial issues for high level success
     - important issues 
         - IE discuss how/when to implement backups and simplified qhub-config.yaml

 - quarterly
   - Purpose of QHub (Include high level stake holders)
     - marketing goals
     - company goals
     - overall vision

 - semi-anually
    - community roadmap discussion

# HackMD

Used to capture meeting notes and document project structure where it does not fit in repository. See this [discussion](https://discuss.quansight.dev/t/taking-notes-during-project-meetings/293) for how to take meeting notes.
 
# GitHub
 
## Labels
  - `client-funded` :: features that a funded by clients
  - `needs-discussion` :: needs discussion beforce deciding what needs to be done
  - `enhancement` :: features added to QHub
  - `bug` :: bug in QHub that need to be fixed
  - `documentation` :: documentation to help
  - `good-first-issue` :: issues that are good first issues for people new to the project
  - 
  - `stale`

## Milestones
  - milestones are used to associate issues with a given release

## Project Columns
 - new issues :: issues that have not been categorized
 - icebox :: issues that are not within a month of being implemented
 - backlog :: next issues to work on in coming month
 - in progress :: reflects the current issues being worked on by team
 - needs review :: signifies a PR/documentation is ready for review
 - closed :: once issue has been resolved
 
# Community Engagement Responsibilities

Periodically check:
 - [github discussions](https://github.com/Quansight/qhub/discussions)
 - #qhub-dev slack channel
 - #qhub-open slack channel

Respond to issue/discusion/ 

(respond to community and open/reference issues as needed) time is bounded

- some response same day, more detailed 24 hrs

 
# Actions

 - mechanism to communicate immediate client qhub issues (that require development) e.g. john communicates AES needs X
    - for example look at clearml, prefect, how do we link issues 
 - start 3/6 month roadmap (or involve community)
 - talk with him before the meeting and get buy in from him with the plan
 - introduce everything to team probably as it comes up
 - document long terms goals and store somewhere
 - document audiences
 - meeting notes https://discuss.quansight.dev/t/taking-notes-during-project-meetings/293 how to take