Working group meeting 20200611
Doorstop missing features
- Mapless have produced a document listing the features we need or desire that are missing from Doorstop
- The first priority is probably closing the workflow loop with GitHub/GitLab.
- OpenFastTrace is produced by Elektrobit
- Doorstop takes a document-centric approach with requirements in one place, whereas OpenFastTrace allows requirements to live anywhere, even in places like in the source code.
- The Doorstop approach makes things more transparent and easier to maintain (especially regarding managing and understanding the life of a requirement), but there are benefits to the OpenFastTrace approach as well.
- OpenFastTrace is just a tracing tool. You need to do work with the output to produce a readable requirements report from it.
- Rather than investigating other tools and spending time on them, it seems that working on Doorstop to improve it for our needs is a better use of our time. We have enough evidence to make a decision to use Doorstop.
Change in meeting schedule
To avoid a clash with the Manipulation Working Group’s monthly meeting, this working group will change it schedule from “every two weeks” to “first and third Thursday of the month”. The next meeting will still take place as originally scheduled, but the new schedule will be put in place from the following meeting. Please see the ROS Events Calendar for the schedule of meetings.
- Geoff will begin putting together a proposal for changes to REP 2004 to identify what we need to make possible before we can make it required by REP 2004.
- Geoff to ask Apex.AI if they have any learnings and best practices about design documentation that they can make open for the ROS community to learn from.
- Mapless/Geoff to look into defining what content to capture from GitLab (e.g. comment history for MR, and associated Issue)
- Florian/Ternaris willing to help with implementation of synching Doorstop requirements with GitLab labels