Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Communication: fix the bugs that we found first or do we make the announcement now?
There are 4 issues to be fixed, ideally we should wait for those issues to be fixed
Timeline? Maybe 2 weeks, it looks quick to fix but see if we include: openncp 92 (S), UTIL 17 (S), AM 25 and 26 + new ones still to be created
we should add those issues to OpenNCP affected version 2.4.0 & tag them as "Connectathon issues"
Cache mechanism
All the properties are currently stored in the db
Idea was to remove db and store properties in properties file. Then properties stored in hashmap (singleton). If key absent, trigger the query or TSL synchronizer. This would prevent redundant mysql call
if we agree, we could push the idea to the SMP task force this Friday
Heiko Zimmermann: some of the properties are sometimes updated.; Will they be updated in the properties file? Need a restart?
TSL syncro updating the properties file
either TSL synchro to notify or let it fail (url not longer valid), then check to reconnect and db query
Update task force meetings and tasks forces to relaunch
Security task force will be relaunched as soon as we start component per component testing, which should start very soon.
We will communicate the process and tools used
Release management task force will also be relaunched to improve and reduce release time
eSENS meeting in Brussels: non-repudiation, eID level 3 and SMP/SML: the willingness to pilot again was expressed in order to show the evidence that OpenNCP is able to work with eSENS BB (non-repudiation and eID). The idea is to simulate an encounter with the doctor
eID - ongoing discussion with technical and legal
For the time being this topic is handled by eSENS WP 5.2, if OpenNCP need to support, Massi and Joao will do the liaison with OpenNCP