-
Notifications
You must be signed in to change notification settings - Fork 10
Teleconference 30.3.2020
- Introduction of the new gitHub area for TDCF
- Discussion on machine-readable format requirements
- Items for next fast track
Enrico made an introduction on gitHub and how the TDCF Team has been setup to manage the three repositories:
- GRIB-2
- BUFR-4
- Common Code Tables The work of the team will be based on the project board on the three repositories
- GRIB-2 project board
- BUFR-4 project board
- Common Code Tables project board
In each project board the following lanes are defined:
- Submitted. This is the stage of a proposal that has been submitted and not yet examined by the team. From this stage the proposal can go to: In progress or In validation.
- In progress. Some team members are working on an acceptable solution. External domain experts can contribute at this stage, mainly to support the work of the member in the subject area.
- In validation. In this stage, an acceptable solution has been provided and at least two Centres with independent decoders have to encode and decode sample messages and validate the proposal. At this stage, a branch has to be produced to allow other team members to validate the solution.
- In review. The proposal has been sent to Focal Points or PRs or to the Technical Commission for review, before being endorsed for adoption.
- Operational. The proposal is fully operational an is released on the community.wmo.int web site.
The team discussed the opportunity to work in asynchronously (experts to work independently from each other at their how time and exchanging ideas in gitHub) or synchronously with a teleconference or a meeting to have a discussion on an issue or topic and take moderated decisions. The tool provides the option to use both modality and teleconferences or face to face meetings will be preceded by asynchronous work to prepare the proposals to be mature enough to be discussed for decision by the team.
The need of all the machine to machine legacy formats, included the XML format have been discussed. The team consider a requirement to have the XML format. The csv format will be used as master version of the tables and the XML format will be produced by a script before final publication or whenever is necessary for validation purposes. Enrico asked for support by the team members to provide a python tool to convert from csv to XML and Marian said that he is available to help with the task. The converter will be needed by October to convert the new approved fast track to the XML format before publication.
A proposal has been made to provide templates for the issues so that the procedure is better governed based on the type of amendment requested and all the required information is reported in the issue. There will be some member and Enrico working on trying to provide issue templates.
A timeline was decided to be able to produce on time the next fast track.
- Provide the proposals by 25 April 2020
- Decide which proposals can make the fast track. Teleconference beginning of May.
- Finalise fast track. Teleconference end May/beginning June
- Send to National Focal Points beginning of July. End of consultation beginning of September.
- Operational end of November.