Location

Cambio office, Drottninggatan 89, Stockholm

Physical Attendees

Planned Outcomes

Agenda Suggestions

Agenda

 

ProgrammeVirtual attendees
Thursday 11 Feb WhoActionsPPHFKADBIMSK
09:30 - 10:00Informal - get set up with Jira, screens, GTMAll       
10:00 - 10:30

Tooling

Git strategy / workflow

Review workflow - BN

All       
10:30 - 11:00

Documentation tooling update - show everyone how tooling is working at the moment; solicit suggestions for improvement.

MagicDraw?!

Thomas Beale       
11:00 - 11:30Global review
        
11:45 - 12:15ITS release strategyAll       
12:15 - 13:15LUNCH        
13:15 - 14:15ITS release strategy - Sebastian Iancu
  • does ITS continually accumulate mutually consistent sets of resources, e.g. XSDs, Java code etc etc? It should be the case that the ITS project has ITS for every other component that has something available at any time.
  • ITS specifics - RM 1.0.3 XSDs
Sebastian       
14:15 - 15:15Specifications Releases        
15:15 - 15:30C O F F E E        
15:30 - 16:30Specifications Releases
  • RM Release 1.1 - move most of Common to BASE
  • SM first release timetable
        
16:30 - 17:30ADL2 migration strategyTB       
17;30 - 18:00Cambio - GDL state of the artRong       
20:30 -Dinner        
          
Friday 12 Feb         
09:00 - 10:15TDS2        
10:15 - 10:30C O F F E E        
10:30 - 11:00REST APIs        
11:00 - 12:15REST APIs         
12:15 - 13:15LUNCH        
13:15 - 13:30AQL        
13:30 - 14:30AQL        
14:30 - 14:45         
14:45 - 16:00         
 drinks? :)        

Actions

Vagrant

Create list of instructions for vagrant provisioning script for documentation / publishing env. Sebastian to build and test.

MagicDraw

Do a test to see if MD XMI includes all model content including diagrams.

Do a test to transfer full model to another tool.

GDL

ROng - send TB XMI of GDL model.

Publishing / Workflow

Asciidoc or other generic small types - use a 'collector' CR on each release e.g. 'Correct Asciidoc syntax errors'.

Signficant CR-driven changes:

  1.  Changes is done one personal fork 
  2.  Pull request is sent to main repository 
  3. Owner of the specification will do the merge 
  4. Each commit must be assigned with a prefix for the JIRA item (e.q SPEC-RM-35)