Purpose: Review Features list and discuss wh=
at implementations sites need from the software

=20

=20

=20

Meeting Min=
utes

=20

Annual Leadership Meeting

=20

=20

Save the Date: March 8-9th

=20

Location: New York

=20

=20

=20

Hosting at Columbia=20

=20

Andy will get a hold of the key stakeholders in the department and see =
if there are commitments to present collaborative ideas for OpenMRS=20

=20

Paul: We definitely want to make time to meet face to face with the Col=
umbia team

=20

Andy: It's a great way to set up more collaborative work

=20

Andy: OpenMRS can present and ppl can show 5min the work that they do a=
nd find ways to collaborate from there

=20

=20

=20

=20

2012 Road Map

=20

=20

Darius: We need to develop the strategy: How we define the road map and=
how to reach out to groups with developers

=20

Darius: We need to make the OpenMRS Road Map more than just releases of=
the core platform=20

=20

Paul: That's fundamental that we reach out to different audiences, and =
that the road map is truly driven by the implementers

=20

Darius: We need to figure out how to group and prioritize those feature=
s=20

=20

Darius: Who are the groups with developers we want to reach out to?=20

=20

Jembi, PIH, AMPATH, MVP,etc.

=20

=20

=20

=20

Paul: Once we have a list, how do we decide what to do and scope the pr=
oject?

=20

Darius: Do we still want to think about 3 releases per year, and why do=
we want that? Do we want 3 releases per year or show that we're being resp=
onsive=20

=20

Burke: There's no science saying you must do "x" releases per year, but=
if we are only releasing every 6mths or more, the project feels stagnent=
li>=20

Darius: A pain point is testing

=20

=20

Darius: What if there is a release that is so awesome that you upgrade =
everyone to that and we also move to a world where the core changes are muc=
h smaller between releases.....would PIH upgrade more often or no?=20

=20

Mike: The way we have release in Rwanda, it may be reasonable to do 1 O=
penMRS upgrade per year...possibly 2

=20

=20

Darius: We want to be more in sync with the implementations supporting =
OpenMRS

=20

=20

=20

Process:=20

=20

Reach out to the implementers and say "here's what you sent" and expoun=
d on that

=20

Any items that are voiced by more than one implementation site gets pri=
ority

=20

Next we scope the road map

=20

=20

=20

Follow up on BWH & OpenMRS Licensing Agreement

=
=20

=20

Darius: BWH wants to assign this code over to OpenMRS. The copyright go=
es to OpenMRS and OpenMRS grants BWH perpetual use of that material.=20

=20

Paul: I want to see language of what's in the license

=20

Andy: It's a little different. BWH is giving us something, but they sti=
ll want rights to it to do what they want. If the open source license was r=
estrictive, it doesn't apply to BWH