rbehjati

Thanks for yesterday's meeting. The following is my summary of the discussions, referring heavily to the following suggestion from @laurentsimon: ```yaml uses: path/to/builder with: output-folder: ./some/folder/ image: gcr.io/oak-builder@sha256:xxx configuration: ./path/config.toml...

> > I don't think baking the command in the docker image scales well; for instance, in Oak, we want to use the same docker image, but run different commands...

Notes for review: - I am not sure if the `development.md` is the right place for this `how-to`. Let me know if you can think of a better place. -...

> This sounds like it can be a very useful workflow. Any progress on it? Doesn't look like it has been picked yet. Here is the top-level tracking issue: https://github.com/project-oak/transparent-release/issues/145...

My idea was to pose these questions to people and let them guess, and encourage in a discussion. I am not sure having the answer right there in the slides...

@mgeisler I added **short** answers. Can you take another look? :)

Is a deep knowledge of Rust concurrency required for understanding the use of `Send` in Bare Metal? If not, I agree that including a single slide to briefly introduce `Send`...

I agree with you @mgeisler. The process is complicated and not very well described. I had to look at GitHub actions to figure out how to generate the exercises. The...

I see different opinions about including all files in the slides :) I think if it is clear that those files are for just reference, then it is perhaps fine...

@mauvealerts Can you also update the list of required APIs in the description of the exercise? In particular this line: https://github.com/google/comprehensive-rust/blob/c0138a424fdd4ebf108544363791295a067ce93b/src/exercises/concurrency/chat-app.md?plain=1#L32 Instead of `BufReader::read_line()`, we want the API for [Lines::next_line()](https://docs.rs/tokio/latest/tokio/io/struct.Lines.html#method.next_line).