ASAM OpenSCENARIO V1.x

3. OpenSCENARIO Alignment & Looking Forward

A first outline of the plan for OpenSCENARIO looking into the mid to long term: What is ASAM doing to ensure the two development pipelines of 1.x and 2.0 converge in the future

6. Contribution Workflow

• Some insights into how to contribute to the project proposal
• Getting setup with git and a text editor
• How to submit changes to the project proposal

7. Runtime Improvements

A proposal for improving the runtime model of the next version of OpenSCENARIO 1.x. Andreas Hege will prepare a writeup for the Project Proposal

8. Review and categorization of current Bugzilla items

• Review of the current list of Bugs and feature requests on the OpenSCENARIO issue tracker
• Bugs were categorised according to the three proposed working groups:
  • Actions and controllers
  • Parametrization and complex conditions
  • Runtime improvements and system boundaries
• This is intended to be the foundation of features, fixes and improvements intended for the next version of OpenSCENARIO V1.x
• Once the list is published on the new ASAM system, it will be open to all to allow all members of the public to submit further features for the development pipeline

9. Discussion Panels

(based on Bugzilla items)

Goal: Prioritization of topics for a V1.1.0 release in Q1 2021

9.1. Discussion Summary: Actions & Controllers

Ludwig Friedmann (BWM)

Recording
(5:03)

Recording
(5:10)

To enroll in the project, enter your details and resource committments (we recommend 25 man-days per company) in 3-2_committed_resources.adoc 

10.2. Nomination project lead

A project leader will be elected in the final proposal meeting end of April. 

Tasks of the project leader (support by ASAM office):

• Coordination of the project group (meetings, technical content, milestone management)

• Interface between project and ASAM TSC (status updates, releases)

• (optional) Interface between project and ASAM Coordination Group:Simulation (alignment with other standards and activities). This can also be fulfilled by another project representative

Submit of your candidacy for project lead by Apr 17, 2020:

• Email a short summary of your profile (1-2 slides) to benjamin.engel(at)asam.net (profile will be shared with the public for voting of the project lead)
• Each company committing resources has one vote (outliers that have significantly more or less commitment than others will be weighted accordingly - the details of this will be shared prior to the vote)
• The project will not be able to start until a project lead is defined.

10.3. Change Control Board (CCB)

CCB members are effectively repository moderators with the necessary permissions on the OpenSCENARIO repository to:

• Push content to the protected project branches
• Accept merge requests from other project members

To nominate yourself as a moderator, please enter your details in Table 2 of 3-2_committed_resources.adoc
(Note: A minimum of two volunteers are expected to be named in the project proposal. The volunteers can change over the project runtime but 2 are always required.)

10.4. Next Meetings

1. Full proposal group meeting to finalize the project proposal end of April (Date TBD and will be shared over ASAM Channels and with all registered participants of this workshop)
   -  Final resource commitments are expected by this meeting
   -  Voting on repository administrators
   -  Voting on Project Lead
2. Individual Workgroup meetings to continue refining list of issues in the coming 2-3 weeks (Actions&Controllers, Runtime, Parametrization&Conditions)
   → These meetings will be shared with all as soon as they are created (early next week)