-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add documentation regarding code generation guidelines - Stint 1 #90
Comments
Nice idea @mfussi66 👍🏻 However, the goal is to publish everything, including these aspects related to the policies, on our website; so, in this sense, it's very much related to: Now that we're in a good position with the development of the architectural models, we can think of addressing the public documentation from the ground up. Probably, we should put this on the bill for the next facility increment. |
Well, we haven't covered the proper Software Architectures yet... |
/remind May 06 |
⏰ Reminder |
Great! Agreed F2F that we eventually aim to develop the website. |
At the moment I am at the Code generation part of the model configuration parameters: https://github.com/mfussi66/icub-firmware-models/blob/devel/boards/docs/The%20Techie's%20guide%20to%20code%20generation.md#code-generation |
In this commit, I think I concluded the draft for the Configuration Parameters window: https://github.com/mfussi66/icub-firmware-models/tree/acc4d9da907b1f4e47e525eedcf1c9d03629a18c There is also a small section that talks about code replacement libraries with a link to the official docs. |
Well done 👍🏻 |
No problem! Just posting regular updates to show progress on the task. |
Given the scope of the task, maybe it will be useful to swtich this issue to a first stint? cc @pattacini |
Good point 👍🏻 I've turned #13 into an Epic and thus associated this issue with that Epic. |
Closing in favour of follow up #93. |
I updated the open post with a checklist of topics addressed in this first sprint @andreaderito . |
Now that we have achieved some sort of expertise regarding code generation for an embedded board, it might be nice to create a .md document that highlights the best practices and settings to apply for an effective and flexible process.
For example, it could contain:
05/07/2024 Update:
Adding a checklist of the points addressed in this Stint 1
The text was updated successfully, but these errors were encountered: