Description: Short-term approaches to identifying technical debt; how to apply new development practices now; Common shared upstream branch

Leads: Darius

Rapporteur/Notetaker: Rich

Notes from Session:

Intro

In this session, we start to decide which practices to follow, and how to handle technical debt.

What are the implications for countries between now and 2.0 master? (Not addressed in discussion)

Tasks: (Owner is in brackets)

Need to pick a CI: "travis", based on github permissions. Most orgs currently use Jenkins

Public expectations between organizations, who has privilege to commit to master trunk?

VillageReach doesn't need to do all of the above tasks. Govern & Tech tracks should review and decide. Tomorrow, decide Tech WG members.

Should have some upfront feature review so project knows ahead of time if a feature belongs to core or not, to set expectations and avoid surprises. Product design should occur beforehand.
How is a feature, ready to be merged, defined as Done? Any requirements around documentation, testing, etc.
- Question arising from doc concern: If code is merged into dev/master, what is the Done criteria? If feature is gradually built and constantly merged in, when is that feature "done"? Needs to at least be Done by the next release tag.