ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A answers.ros.org

Autoware working group: Call for participation

Following on from the announcement about working groups for the Autoware Foundation and the announcement of the reference platform working group, I am announcing the Autoware Working Group.

This working group will be led by myself and the incredible @esteve. The purpose of the working group is likely to change to account for the operation of other working groups and what we learn that we need over time, but to begin with the working group’s purpose will be:

  • Manage general development of Autoware.AI and Autoware.Auto
  • Coordinate activities between the two so we don’t duplicate work
  • Coordinate cross-functionality infrastructure and Autoware-wide functionality
    • Release process
    • Documentation
    • Docker
    • CI
  • Coordinate the overall architecture of Autoware.Auto
  • Ensure that function-specific working groups are not working at cross-purposes
  • Provide a place for cross-working group discussions (e.g. perception and planning when they need to talk) on an as-needed basis

We will begin by meeting every two weeks. The first meeting time is Tuesday, July 16, 2019 1:00 PM TZ (see below for the meeting information).

The regular time is to be decided based on who wants to participate in the working group, so if you are interested then speak up here even if you can’t join the first meeting!

Most of our coordination will be via GitLab. The teleconferences will mainly be used to catch up on progress overviews and discuss tricky issues that are hard to do via text.

I encourage anyone who is interested in seeing Autoware progress and contributing to that to join the working group. We are open to all, no matter your affiliation or skill set. Even if you can’t program, if you can use a keyboard then we always need more people to write or review documentation!


Autoware Foundation: Autoware working group
Tuesday, July 16, 2019 1:00 PM TZ

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/677305637

You can also dial in using your phone.
United States: +1 (571) 317-3116

Access Code: 677-305-637

More phone numbers
Australia: +61 2 9091 7603
Austria: +43 7 2081 5337
Belgium: +32 28 93 7002
Canada: +1 (647) 497-9373
Denmark: +45 32 72 03 69
Finland: +358 923 17 0556
France: +33 187 210 241
Germany: +49 692 5736 7300
Ireland: +353 15 360 756
Italy: +39 0 230 57 81 80
Netherlands: +31 207 941 375
New Zealand: +64 9 282 9510
Norway: +47 21 93 37 37
Spain: +34 932 75 1230
Sweden: +46 853 527 818
Switzerland: +41 225 4599 60
United Kingdom: +44 20 3713 5011

New to GoToMeeting? Get the app now and be ready when your first meeting starts:
https://global.gotomeeting.com/install/677305637

1 Like

Attendees

  • Geoffrey Biggs (Tier IV)
  • Esteve Fernandez (Apex.AI)
  • Liyou Zhou (Arm)
  • Eliot (Arm)
  • Luxiang Zhou (AutoCore)
  • Ryohsuke Mitsudome (Tier IV)
  • Stephane Strahm (Kalray)
  • Akihiko Tsukuba (eSOL)

Minutes

Working group backround and goals

  • Manage general development of Autoware.AI and Autoware.Auto
  • Coordinate activities between the two so we don’t duplicate work
  • Coordinate cross-functionality infrastructure and Autoware-wide functionality
    • Release process
    • Documentation
    • Docker
    • CI
  • Coordinate the overall architecture of Autoware.Auto
  • Ensure that function-specific working groups are not working at cross-purposes
  • Provide a place for cross-working group discussions (e.g. perception and planning when they need to talk) on an as-needed basis

Autoware specification proposal

Discussion

  • [Kalray] Add a document to define the overall structure of Autoware.
  • [eSOL] How does the specification fit with Autoware.AI?
    • It will not be forcefully aligned with the specification because it is due to be gradually phased out. We may need to alter Autoware.AI to match the specification in places to make the bridge work, but we want to keep these to a minimum because any resources put into Autoware.AI development are resources taken from Autoware.Auto development.
  • [Arm] Can Autoware.Auto have multiple implementations of a specific functionality, even though it is a reference implementation?
    • Yes. This will aid in it being a reference, because it will show multiple ways to implement the specification.
  • [Kalray] The Autoware working group will need to define target applications/use cases, particularly if we aim to go for certification in the future.
    • As a starting point we have the [existing five milestones for Autoware.Auto development]. These need to be fleshed out to be detailed use cases that can drive the specififcation’s development.
  • [Arm] Next step should be to define the use cases for the specification.
  • [eSOL] Will Autoware support ISO 26262, other than writing the document specification? For example, test coverage data.
    • This question applies more to Autoware.Auto (the reference implementation) than the specification itself. Currently the Autoware Foundation is not aiming to certify Autoware.Auto, due to the difficulty of certifying an open-source project. However we do aim to be high-quality (as close to production quality as possible), so we already support various useful things such as generating a coverage report in the documentation, thanks to work done by Apex.AI.
  • [Arm] What’s the process from now?
    1. Make the proposal to the TSC this week
    2. Define a formal process proposal over the next few weeks
    3. Propose the process in the August TSC meeting
    4. Once the process is accepted begin moving forward with proposing and accepting draft specification documents.
    • All work will be done via GitLab using MRs so that proposed changes and discussions are recorded.
  • [Tier IV] If the documents will be separated into various documents, who will do the documents that don’t currently have a working group?
    • For cross-functionality ones, such as introspection interfaces, this working group should be responsible.
    • For functionality-specific ones, such as perception, new working groups will need to be created.

Autoware.Auto

I would like to join the WG - are there dates for next meetings set?

Sorry for being late to setting the next meeting date. Here’s a poll, everyone please answer it quickly!

The next working group meeting has been set.