2011-02-24 Developer Meeting

Unknown macro: {composition-setup}

Date

24/February/2011

How to Join

Unknown macro: {toggle-cloak}

Click here for information about joining the meeting in person or remotely.

Unknown macro: {cloak}

Unable to render {include} The included page could not be found.

Unknown macro: {cloak}

In Attendance

You

Agenda

Quickly review previous meeting minutes (5 min)
1.8 update (unscheduled)
Web Services update - Saptarshi (30 mins)
- Enhanced Web Services (Design Page)
- Webservices.cxf Module
Summer of Code 2011 (30 min)
After-action review & next week's agenda (5 min)

Minutes

real-time collaborative notes

1.8 Update - Wyclif (1 hr)

Tickets are mostly done
Waiting on feedback from HaPIHmish, AMPATH,
We have about one more week for testing (according to schedule)
Jeremy: AMPATH has one more week before they can test
TODO: Ben says TRUNK-2016 needs to be investigated. Ben fixed part of it but James reporting slow to find patients in search boxes. The general consensus was that this can be deferred to 1.8.1 (Darius has created a JIRA project version for this).
Wyclif feels there are too many duplicate bug reports (i.e., reports for things already fixed). Many times these have been fixed in the nightly builds but aren't visible in the beta.
- TODO: Michael to write up publicize list of apps using server resources
  - http://openmrs.atlassian.net/wiki/display/RES/OpenMRS.org+Infrastructure
- TODO: Michael write dev list about why or why not nightly.openmrs.org is feasible and why
  - Michael: Separate from hardware constraints, having people test against an installation we control is not a sustainable/correct QA strategy for the project. We need to make it easier for people to download and test nightly releases.
RC1 target date - 10 March
Darius: Is our release process dependency on end-user testing unrealistic/unsustainable?
Roger: Can our user community abosorb our speed of development?
Darius: Many implementations have too many modules to make testing an easy process
Jeremy: We need more participation in the testing environment. "If you want real world testing, you have to wait for the real world to have time to do it."
Questions raised generally by the group:
- Can the core group take ownership of new feature functional/usability testing?
- Who can do testing of modules against new releases?
- Should implementations be just responsible for testing against their own data?
Roger: Can we get new implementers into a kind of testing group in exchange for additional assistance?
Darius: If someone is a reference implementation, they should commit to doing beta testing.
- Michael: Are these references implementations too big, or too complex to be useful?
TODO: We should "consider the possibility" of helping AMPATH with their testing (Darius Dawn). Discuss during next week's leadership team meeting.
TODO: Wyclif to follow-up with James to ensure real users have tested 1.8 at HAS Haiti. If so, then we are ready for RC1.

Web Services (45 min)

Overview from Saptarshi
- http://openmrs.atlassian.net/wiki/display/projects/Enhanced+Web+services+(Design+Page)
- http://openmrs.atlassian.net/wiki/display/projects/Webservices.cxf+Module
TODO: Darius will add some of his thoughts to the wiki's design page and start a discussion on the dev list.
TODO: Saptarshi to write dev list with open questions around WS-Security and possible annotations for modules

Summer of Code (5 min)

http://go.openmrs.org/soc2011
We will be applying at the end of the month (next week)
Mentors still needed/wanted
Project ideas needed
TODO: By next week: Mentors will contact any of their high-quality students about participating as mentors this year. People will also bring summary lists of potential projects.

Resources