Skip to content
GitLab

Autonomy Software WG Meeting 2020/10/06

Agenda

  • Previous Meeting Minutes
  • A Toast to AVP Success!
  • AVP Demo Overview
  • AVP Hack-a-thon Overview
  • AVP ODD Development Cycle Retrospective
  • Short discussion regarding Gitlab/Github
    • Gitlab CI is better
    • ROS users (probably git users in-general) are more familiar with Github
    • In ROS2, developers resorted to other applications outside of Github for project management (Waffle)
    • (opinion) Gitlab is hands-down a better management tool than Github, unfortunately, Github has the userbase

The Great

  • Participation immediately before the demo
  • Slack was a good communcation tool and works well for quick back-and-forth
  • Localization worked near-perfectly on the real vehicle (luck)
  • The patience and understanding shown by all paricipants was excellent

The Good

  • A lot of thought put into initial development of the code but maybe not structure
  • Having simulation for most development was very helpful
  • The hack-a-thon was not a priority so nothing critical was lost by it not being a huge success
  • Given all of the bumps along the way, the end result came together well
  • Contributor's guide was very helpful, especially the fork-and-pull model document
  • Having milestone-based boards was nice
  • Being able to create dependencies in issues is useful
  • Facilitating Google Meet meetings outside of Gitlab was very useful

The Bad (room for improvement)

  • Creating excitement about the project to get participation during the normal development cycle
  • Missing singl-soure-of-truth for running simulation
  • autowarefoundation/autoware.auto/AutowareAuto#668 (closed) Motion folder seems to contain too much
  • autowarefoundation/autoware.auto/AutowareAuto#671 (closed) Need description of what each folder should contain
  • Would be helpful to have a way to transfer conversation from Slack to Gitlab
  • Much development was blocked by LGSVL fixes/changes
  • Many differences between real vehicle and LGSVL (more than anticipated)
  • Need to test in real vehicle much earlier
  • Need more realistic (and just more) rosbag2 data
  • Have someone other than the System Architect work on the hack-a-thon
  • Need to have a clear discussion with the developer of each feature about expectations for the feature and how it's output will be used as well as the limitations of what will be provided
  • Have leader for groups of components (e.g. planners, localization components, etc.)
  • autowarefoundation/autoware.auto/AutowareAuto#672 (closed) A few sources of documentation that need to be consolidated (documentation repository, design folder, etc.)
  • autowarefoundation/autoware.auto/AutowareAuto#670 (closed) Need guidelines for where to put docs (add to contributor's guide)
  • autowarefoundation/autoware.auto/AutowareAuto#665 Have an easier, more consolidated way for users to run all tests that run on CI
  • Using doxygen for generating non-API documentation is not great (move to RTD?)
  • Sometimes when the conversation in Gitlab gets long, it's hard to follow and find important information
  • Could do better about diseminating information created during Google Meet meetings
  • Try to form topic- or feature-specific groups within the development community to discuss those topics/features during development

The Ugly

  • Slack has essentially no history
  • Hack-a-thon was a disaster

Action Items

Edited by Joshua Whitley
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information