Brig Dev Meeting, Feb 5th 2019

gistfile1.txt

Agenda

- Brigade 1.0
    - https://github.com/Azure/brigade/projects/1
    - decide on features to bump to 1.1
    
- `brigadecore` GitHub Org
    - CLA bot?
    - Brigade CI for the org
    - anything else keeping us from migrating everything there?

- Brigade Utils library to reuse pipelines
    - https://github.com/brigadecore/brigade-utils

- community repo
- new GitHub Gateway
https://github.com/Azure/brigade/projects/1


Notes:

Working towards 1.0

What can we bump to 1.1?
 - Configurable sidecar #340
    May need some sort of watch component
 - Limiting the number of concurrent builds #172
    Possible to quickly configure Brigade-wide (let's check if we can bring into 1.0)
    if per Project, a work queue per project, gets trickier/more design needed (most likely post-1.0)

What is minimally needed for transition from Azure to brigadecore org?
  - string changes in repos
  - CLA bot
  - CI
  - (postpone Docker registr(ies) changes)
  
 BYU Capstone team (Thanks for attending!)
  - (Michael and Derek filling us in)
  - Finished planning, setting up Dev environment
  - Still setting up queues/components (Kafka)
  - January represented migration to Docker containers/K8s cluster
  - February: Working on Kafka-Brigade Gateway (looking at the GH gateway as a template) - OSS
  
 Governance model (looking at Helm)
  - Check in with Matt Butcher (out this week)