Technical Committee Sessions Read-Outs/Group Discussion (Plenary)

Description: Informal summary of key outcomes from each session, with time for Q&A from the larger group

Leads: Leads from Each Technical Session

To Join Remotely:

Join the call: https://www.uberconference.com/info3285

Optional dial-in number: 716-293-6106

PIN: 63498

Rapporteur/Notetaker: Sarah

Notes from Session:

Where is the code at right now? What should the next implementation do?

Next implementation needs a stable code base to start from
Current "2.0" code base is really more of a development branch: not release tag
Need to: clean up code, remove some code, etc. – a whole set of short-term activities that are targeted for completion by the end of 2015

Architecture

Architecture Proposal

Proof-of-Concept Proposal

Comments from larger group

Re-Architecture Planning Considerations

Technical Working Group Definition (link to page)

Who: Elias (JSI), Jeff (TW), Josh (VR)

Characteristics of Membership: Actively engaged in the work going forward

Duties & Privileges:

Arbitrate technical disputes
Have the final say in major arch. decisions
Tech review for new projects
Owns github.org
Defines coding standards and contribution process
Regular review of architecture for roadmap and tech debt
Tool selection
Account for community input
Accountable to the community
Meets bi-weekly
Review membership and approves new ones in collaboration with community leadership group

Timeline

Q4 2015: Shared upstream branch; Shared Infrastructure for Devs; Tech Committee Calls; Code Clean-Up; Coding Standards v1; Tech Committee Meeting; Research Spike

Q1 2016: Start enforcing v1 standards; Contribution Guide v1; Evolved code standards; Some code clean-up; Shared demo and demo db; Automate required new standards; Decide on re-architecture path; Shared issue tracker; Public community/implementation forum

Q3: New implementations can write to extensions (what does this mean from a business perspective?)

What do we want 1 year from now

link to page

Key Open Questions

How would upgrades to new version be funded?

Need to know how long the re-architecture would take, and how much it would cost.

What is the sustainability plan for countries on the current version? For example OpenMRS supports the last 3 versions.

Should additional implementation start? probably yes – needs to be transparent.

Action Items

Technical committee to raise trade-offs and present alternatives to product team - product team to verify and analyze how alternatives meet business goals

Product and Technical committees to work together to define how we will measure success

Is it possible to set-up linked issues between different Jira's?