20131125 - Meeting minutes, Tuesday, November 25th, 2013

OpenNCP Weekly Sprint Meeting

25nd November 09:30 to 11:00  CET

Work RoadMap - epSOS 2 Services

1º Sprint: 28Jan > 8 Fev (2 weeks) > Completed
2º Sprint: 11Fev > 22Fev (2 weeks) > Completed
3º Sprint: 25Fev > 8Mar (2 weeks) > Completed
4º Sprint: 11Mar > 22Mar (2 weeks) Completed
5º Sprint: 25Mar > 8Apr (2 weeks) Completed 
6º Sprint: 22Apr> 3May (2 weeks) > Completed 
7º Sprint: 6May> 17May (2 weeks)  > Completed
8º Sprint: 20May> 31May (2 weeks)  > Completed
9º Sprint: 3June> 14June (2 weeks)  > Completed
10º Sprint: 24June > 19July (4 weeks)  > Completed

  • Release OpenNCP 2.0.1 > 31 July, 2013 (Wednesday) 6th August
  • Release OpenNCP V2.0.2 > 2013-09-12   Transformation Manager + Emergency Scenario + Bug Fixing      

5ª PPT [completed]

  • [NOT] OpenNCP V2.0.3 (after PPT)   2013-10-16   OPERATION   Ready for: PAC + HCER epSOS 2 Services 

11º Sprint: 15Oct > 28Oct (2 weeks) > completed 

  • PPT Ready for: MRO (new epSOS 2 Service)
  • [√] OpenNCP V2.0.3 (after PPT)   2013-11-05   OPERATION   Ready for: PAC + HCER epSOS 2 Services

12º Sprint: 1Nov > 14Oct (2 weeks) [ in progress ]  

12º Sprint: 5Nov > 19Oct (2 weeks) [ in progress ] (delayed one week due to lack of resources to work in the 1st week)

  • PPT Ready for: CI Automated Testing Suite Enhancements > COMPLETED

  • OpenNCP V2.1.0 (PPT Ready)  2013-11-20  > MRO + CI Automated Testing Suite Enhancements [In Progress]


PPT/QA Stage [not a formal PPT but a more structured QA stage - coordinated by the OpenNCP Community]  

  • OpenNCP V2.1.1 (after PPT stage)   2013-12-18   OPERATION   Ready for: MRO + CI Automated Testing Suite Enhancements

AGENDA

a) Internal QA - Progress Monitoring

  • Internal QA activities progress monitoring and RESULTS
  • PN's QA Activities planning (25th November)
    • OpenNCP 2.1.0 Release Process (+ Notes)

b) Documentation preparing

c) Knowledge sharing


 

LOCATION

- Skype (sirLicman) + Jira Board + MeetingWords

 


PARTICIPANTS


Today's Meeting Participants:

Marcelo Fonseca <marcelo.fonseca@iuz.pt>,
Licinio Mano <licinio.mano@iuz.pt>,
Stéphane Spahni <stephane.spahni@hcuge.ch>,
Juergen Wehnert <juergen.wehnert@gematik.de>,
Ivo Pinheiro <ivo.pinheiro@iuz.pt>,


Invited Members List:

Konstantin Hypponen <konstantin.hypponen@kela.fi>,
Marcello Melgara <Marcello.Melgara@cnt.lispa.it>,
Per Loubjerg <consult@loubjerg.dk>,
Aarne Roosi <Aarne.Roosi@affecto.com>, 
Alexander Berler <a.berler@gnomon.com.gr>, 
Arnaud Gaudinat <arnaud.gaudinat@hesge.ch>,
Belani Hrvoje <Hrvoje.Belani@hzzo.hr>,
Gergely Heja <heja.gergely@eski.hu>,
Giorgio Cangioli <giorgio.cangioli@gmail.com>,
Ljubi Igor <Igor.Ljubi@hzzo.hr>,
Oskari Kettinen <oskari.kettinen@kela.fi>,
Jussi Lemmetty <jussi.lemmetty@kela.fi>,
Kostas Karkaletsis <k.karkaletsis@gnomon.com.gr>, 
Mate Beštek <mate.bestek@gmail.com>,
Milada Kovarova <Milada.Kovarova@posam.sk>,
Mika Myllyvirta <mika.myllyvirta@kela.fi>, 
Mindaugas Ajauskas <mindaugas.ajauskas@lispa.it>, 
Norbert Repas <norbert.repas@elga.gv.at>,
Patrick Ruch <Patrick.Ruch@unige.ch>,
Tomaz Cebular <Tomaz.Cebular@ivz-rs.si>,
Steen Manniche <steen@manniche.net>, 
Annika Sonne Hansen <ash@carecom.eu>,

 

MEETING NOTES

a) Dev Sprint Monitoring 

 

  • QA Internal STAGE  Planning;
  • MRO Service + CI Enhancements
    • INTERNAL QA > 19 to 22 Nov > OpenNCP V2.1.0 (Release Candidate); (Fine tune first approach with provided information and incorporate final tasks)
      • Implemented  automated validation of transaction messages for XCPD and XD* in IS,  PS, ED, OS, HCER, MRO and PAC services, both on client and server side;
      • Implemented  automated validation of audit messages messages for IS, PS, ED, OS,  HCER, MRO and PAC, both on client and server side;
      • Implemented  automated validation of CDA documents for PS, ED, OS, HCER and MRO  services, both on client and server side - for pivot and friendly  versions;
        • Improved  naming of validation report file (Example:  20131122150923528_XCA-QUERY-RESPONSE_EPSOS-2_FETCHDOCUMENTSERVICE_QUERY_-_RESPONSE_FAILED.xml);
      • Attached the parse result of validation reports bellow each integration test, Example:
INFO ][ClientGenericIT.testFailScenario    ][106]: ✔ PT_CLIENT_XCA_PS_#3
[INFO ][ValidationReport.write               ][123]: ↳Validation result
[INFO ][ValidationReport.write               ][130]:  ├─XCA-QUERY-REQUEST [VALIDATOR: EPSOS-2-FETCHDOCUMENTSERVICE-QUERY---REQUEST, STATUS: PASSED]
[INFO ][ValidationReport.write               ][130]:  ├─XCA-QUERY-RESPONSE [VALIDATOR: EPSOS-2-FETCHDOCUMENTSERVICE-QUERY---RESPONSE, STATUS: FAILED]
[INFO ][ValidationReport.write               ][128]:  └─AUDIT [VALIDATOR: EPSOS-2---HCP-ASSURANCE-AUDIT, STATUS: FAILED]
    • Integration from the CI Server (Jenkins) with the Jira Development Board.
    • [ToDo] Prepare "How To Use  the New CI Automated Tests Suite"  Manual
    • [ToDo: NiceToHave] Store report files in Jenkins Job and present links in console output, Example:
[INFO ][ClientGenericIT.testFailScenario    ][106]: ✔ PT_CLIENT_XCA_PS_#3
[INFO ][ValidationReport.write               ][123]: ↳Validation result
[INFO ][ValidationReport.write               ][130]:  ├─XCA-QUERY-REQUEST [VALIDATOR: EPSOS-2-FETCHDOCUMENTSERVICE-QUERY---REQUEST, STATUS: PASSED ]
[INFO ][ValidationReport.write               ][130]:  ├─XCA-QUERY-RESPONSE [VALIDATOR: EPSOS-2-FETCHDOCUMENTSERVICE-QUERY---RESPONSE, STATUS: FAILED]
[INFO ][ValidationReport.write               ][128]:  ├─AUDIT [VALIDATOR: EPSOS-2---HCP-ASSURANCE-AUDIT, STATUS: FAILED]
  • GOLD (FINAL) Release - OpenNCP V2.1.0 (Gold Release)
    • Release Process:  9 to 13Dec
    • Support Countries Updating: 16 to 20Dec;

b) Documentation preparing

  • [LKM] epSOS Technical Aspects review, in order to include OpenNCP references:
  • [Gareth] OpenNCP General Presentation
  • [Gareth] Review Work;
  • [ToDo] OpenNCP Installation Manual Overview
  • OpenNCP Installation Overview
  • [LKM] epSOS D 3.B.2 document
  • Articulate with MM, but without;


c) Knowledge sharing

  • Knowledge sharing & Collaborative Design
  • [LKM] Value Proposition and Relevant questions have been made. How to find answers?
  • [JW] Recommend "Forward Thinking" maybe apart from TPM forum.
  • [LKM] Think how we can involve other "Stakeholders" besides epSOS TPM and other foruns, in order to give visibility on issues that need to be addressed concerning openNCP Community Sustainability.
  • [JW]  The OpenNCP Wiki Page could be presented to EC in the review milestone from epSOS.


d) Central Support Services (migration)

  • It was agreed to have a first import test (of Redmine data into Jira);
  • Empirica was contacted to provide assistance on that task - requested information and configuration was provided for first test import;
  • While testing the import again an error has occured and was lighlty investigated - probable cause: incompatible Redmine version;
  • Error: Cannot login to Redmine site: org.json.JSONException: A JSONObject text must begin with '{' at character 1
  • Empirica was contacted again and anwsered (with some delay) with version information - the version is compatible with import tool of Jira;
  • Supported versions: 1.3.0+, 2.0+, Central Support Redmine version: 2.3.2.stable;
Probable future actions:
  • Perform deeper investigation of the returned error;
  • Try to orchestrate the resolution of this problem together with Empirica (despite the delay in e-mail requests and anwsers);
  • [ToDo] Open an issue to reflect the current work and needed tasks;
  • [MF] Try another contact with empirica
  • [JW] Try to create a positive emotion towards this issue and migration effort, from Empirica;
[LKM] Think on a B plan
- What if we can't have the migration in place? How will be the future for this services?


e) OpenNCP Support Activities

  • From now on every activity (improvements, task, bugs) should be reported to the Support Board.
  • The Development Board is Officialy closed, until further "scope" and "conditions" concerning development;
  • Let's try to have a minimum "task force" 

 

NEXT STEPS (include previous meeting actions needing monitoring)