-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discuss the format of Autoware's design documents #9
Comments
I agree, It'd be a lot more cleaner this way. and we could directly track the changes based on the source text of the documentation. But documentation should have versioning. |
chore: sync upstream
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
The result of https://gitlab.com/autowarefoundation/autoware.auto/AutowareAuto/-/issues/1421 was added by #48. We have to keep discussing this. |
This pull request has been automatically marked as stale because it has not had recent activity. |
Before writing design documents in #10, we have to discuss the format.
I feel Tier IV's proposal could be the base, but it should be refined a bit more.
The comments in #10 (comment) should be addressed as well.
The text was updated successfully, but these errors were encountered: