Skip to content
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

Technical decision about: how to structure the repo that will contain the TestApp #291

Open
sebastianpfischer opened this issue May 5, 2023 · 0 comments
Labels
documentation Improvements or additions to documentation feature New feature or request size L Complexity of the ticket

Comments

@sebastianpfischer
Copy link
Contributor

In order to support many different versions of the TestApp (for Rust, C, C++&FreeRTOS)
we want to define the right repository structure.

Capabilities

  • it should be easy to understand what are the pre-requisite per TestApp implementation
  • it should be easy to compile the TestApp for a specific platform (as a lib for example)
  • it should be relative easy to provide the needed interface for the TestApp to work
  • a clear documentation, well build should enable the user to select the right manual for the right TestApp (confusions should not be there!)

Acceptance Criteria
AC1: Decision taken

@sebastianpfischer sebastianpfischer added documentation Improvements or additions to documentation feature New feature or request size L Complexity of the ticket labels May 5, 2023
@sebastianpfischer sebastianpfischer added this to the TestApp Contribution milestone May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation feature New feature or request size L Complexity of the ticket
Projects
None yet
Development

No branches or pull requests

1 participant