---
# System prepended metadata

title: PyMC Labs 17 May 2021

---

# PyMC Labs 17 May 2021

Should document this in the docs.

- Repo: working on private repository per project to help with code review
- Pull request practice: When clients have their own code, we don't need a fork of their repo. 
- Code review: Encourage reviews for the following reasons:
	1. Backup - in case lead has to drop off.
	2. Ensure rigour in projects.

Code review:

- Finding the right person for reviewing -- always be open to bringing in the right person.

## Hackathons

- TW: Valuable and fun. Good to push us to do those. Any other thoughts?
- AS/AA: Agreed.
- (ZeroSumNormal -- new name for CenteredNormal)
    - We will have one hackathon on this tomorrow.


## Working on PyMC3 & ArviZ

- EM: Question - war chest for funding PyMC development?
- AS: 2 weeks dedicated, let clients know that it is reserved.
- AA: Good for marketing
- Financially, paid flat rate equal for all of us involved. ($50/mo)
- Broader goals:
    - Upstream improvements
    - Upstream new features that we have learned from client work
- Proposal:
    - Lisbon
    - Central
    - Weather is good in fall
    - Close to ocean
    - Cheap

## Client projects

We didn't talk about it today.

AA: We probably want something where if the model requires more than just surigcal changes, we should sell a much better model. We would want 

TW: When clients insist, we just play along. Definitely there were things we didn't really know.
