OpenMI Association Technical Committee meeting no
...
12
Date: December 10 - 12, 2007
Venue: Wallingford Software, Howbery Park, Oxfordshire OX10 8BA, Wallingford, UK
OpenMI Association Technical Committee meeting no 8
Date: October 22 - 24, 2007
Venue: WL|Delft Hydraulics, The Netherlands
Participants:
Jan Gregersen, LICTEK DHI / LicTek (gregersen@lictek.dk) (chairman of the meeting)
Peter Sinding Unknown User (psi@dhigroup.com), DHI - Water & Environment (psi@dhipsi@dhigroup.dkcom)
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, WL | Delft Hydraulics (stef.hummel@wldelft.nl) ~don (Gena), WL | Delft Hydraulics (gennadii.donchyts@wldelft
Apologies:
Rob Knapen, Alterra (Rob.Knapen@wur.nl)
~onnoroos Unknown User (onnoroos), Alterra (Onno.Roosenschoon@wur.nl)
Peter Gijsbers Unknown User (don) (Gena), WL | Delft Hydraulics (Petergennadii.Gijsbers@wldelftdonchyts@wldelft.nl)
Rob Knapen, Alterra (Rob.Knapen@wur Peter Gijsbers, WL | Delft Hydraulics (Peter.Gijsbers@wldelft.nl) - Tuesday afternoon + WednesdayApologies:
Wiktoria Daniels, Wallingford software (wiktoriad@wallingfordsoftware.com
Jon Goodall, Univ South Carolina (goodall@engr.sc.edu)
Objective:
OpenMI 1.4 release
OpenMI version 2.0
Documents:
http://www.openmi.org/
http://sourceforge.net/projects/openmi
Agenda
...
& Minutes:
1. Minutes from last meeting
The minutes were accepted
2.
...
3. Feature requests
See feature requests on sourceForge
...
OpenMI 1.4.0.0 release
2.1 Review OpenMI 1.4 Tasks on sourceForge
...
Most tasks were completed and thus closed.
*We decided to have a beta2 release and to postpone the final 1.4.0.0 release a few days.
See
...
the updated release plan here. Tasks according the new release plan were added to the 1.4.0.0 task list on source Forge.*
2.2 Other tasks on source forge
There is a task for enabling the configuration editor (preferably version 1.4.1.0) to run models en separate processes. The priority of this task was change to "high".
3 Reported bugs
GOTO SourceForge bug tracker for OpenMI
There are only two bugs reported, both will be fixed with the 1.4.1.0 release.
4 . Feature requests
GOTO sourceForge feature request tracker
All feature requests currently listed relates to the OpenMI 1.4.1.0 or later release. We will address these at out next AOTC meeting in February 2008.
5. OpenMI 2.0
...
Issues
This meeting only focused on finishing the OpenMI 1.4.0.0 release, and no
...
OpenMI version 2.0 roadmap
We need to make an updated version 2 roadmap.issues were discussed.
5.1 Review of OpenMI 2.0 tasks on sourceForge
This meeting only focused on finishing the OpenMI 1.4.0.0 release, and no version 2.0 issues were discussed.
5.2 Use cases
This meeting only focused on finishing the OpenMI We worked on the use cases. Since everyone at the moment is busy with the 1.4.0.0 release not changes to the interfaces was made.
6. OpenMI Java and OpenMI .net synchronization
The new OpenMI standard definition: Personally I am not in favor of making the standard language (implementation) specific. However, looking forward, how will this 1.4 version be updated / modified so that the 2.0 version includes both a .NET and a Java implementation? (Rob)
, and no version 2.0 issues were discussed.
5.3 OpenMI 2.0 architecture
This meeting only focused on finishing the OpenMI 1.4.0.0 release, and no version 2.0 issues were discussed.
5.4 OpenMI 2.0 architecture
This meeting only focused on finishing the OpenMI 1.4.0.0 release, and no version 2.0 issues were discussed.
5.5 Development and release roadmap
This meeting only focused on finishing the OpenMI We decided to include Java in the standard. So there will be both OpenMI.Standard 1.4.0.0 release, and no version 2.0 issues were discussed.
6. OpenMI Java and OpenMI .net synchronization
This meeting only focused on finishing the OpenMI Standard 1.4.0.0 .Netrelease, and no version 2.0 issues were discussed.
7.
...
Meeting plan for 2008
From Jan: We should make a list with new dates for OATC meeting for 2008. My suggestion is to make the meeting less frequent (e.g. use a two months interval rather than a six weeks interval.) Also I think we should schedule more frequent web conferences (e.g. weekly or every second week). See proposed dates
The dates on the proposed meeting plan were accepted.
8. Tasks and unresolved issues
Moved to source forge
From Jan: I was getting a bit frustrated over managing all the tasks and unresolved issues. I have therefore moved these to https://sourceforge.net/projects/openmi/. Hope that this helps.
We need to review these tasks and update status for these.
The new approach with taking more advantage of the SourceForge feature were reviewed and accepted as the way to do it from now on.
OATC Procedures
Review and update the OATC procedures (GOTO OATC procedures)
This meeting only focused on finishing the OpenMI 1.4.0.0 release, and no version 2.0 issues were discussed.
8. OpenMI WIKI
*The URL wiki.OpenMI.org now points to the OpenMI WIKI.
9. Miscellaneous issues
Matters arising from visit of Jon Goodall.
- The multiple instances problem. (we already have a task about this, but we also need a time schedule for when this is to be done). We will make a release schedule for OpenMI SDK 1.4.1.0 at our next OATC meeting, this will also include a list of features that must be included.
10. Tasks and unresolved issues
11
...