|Timestamp||How did the course meet your learning objectives?||How was the duration of the course?||Comments and suggestions||Comments and suggestions||How useful was the lecture document?||Comments and suggestions||Will you recommend this document to others?||Comments and suggestions||If you have Linux / Android project opportunities, will you use this document again in the future?||Comments and suggestions||How knowledgeable was the instructor?||Comments and suggestions||Did instructor oral explanations add value to the lecture materials?||Comments||How much value did the instructor add to lecture materials?||Suggestions and comments||Was the instructor helpful with practical labs?||Comments and suggestions||How do you rate the training equipment (mainly computers)?||Comments and suggestions||How well was the course organized (program, registration, schedule...)?||Comments and suggestions||How much did you learn?||Comments and suggestions||How useful should this course be in your daily job?||Comments and suggestions||Would you recommend this course to others?||Comments and suggestions||Overall rating||Comments and suggestions||Further training needs?||Comments||How did the course meet your learning objectives?||What part(s) of the course did you like most?||Comments||What part(s) of the course did you like least?||What reasons prompted you to choose Free Electrons?||How did you first learn about Free Electrons?||Interested in other types of embedded Linux / Android engineering services?||Comments and expectations||Comments and suggestions||How do you rate training conditions (room size, equipment, environment)?||How useful were the training labs?||Comments and suggestions||Comments and suggestions||How difficult were the training labs?||Was enough time dedicated to practical labs?||Comments and suggestions||How far do you come from?|
|11/5/2015 16:45:46||3||4||5||5||5||5||5||3||3||6||3||4||Trainer||Free Electrons chosen by my management||Not interested||5||3||3||3||From less than 100 km / 60 miles|
|11/5/2015 16:53:23||2||everything fine||5||5||5||5||5||5||5||4||7||3||5||interest in own topics||Access to full feedback from participants to previous sessions||Free Electrons chosen by my management||Technology and architecture consulting||5||5||4||5||From less than 100 km / 60 miles|
|11/5/2015 16:54:53||3||5||5||5||5||The beaglebone board is a nice board for the labs and was very useful for the "real-life" experience with buildroot.||5||We used our computer, so it was ok. The advise to use SSDs was very helpful.||5||5||We used buildroot at our company, but now we really understand its potential. Before the course we used it only to build the sysroot without realizing that we could use it to include our software in the process.||5||7||5||Android and kernel development.||5||Integration and management of company applications within he buildroot process.|
Debugging with buildroot and integration of created toolchains in Eclipse.
|The technical internals of buildroot - quiet interesting but at the moment we plan only to use buildroot. Perhaps later we are able to give active support so this part was ok and should not be missing.||Trainer||Course recommended by previous participants||Not interested||5||5||3||3||From a foreign country|
|11/5/2015 16:58:05||4||The training has a little high pace, which imho could be adjusted for the participants.||5||Also useful/usable without the training itselfq2||5||Could answer all questions pretty accurately and fully.||5||Since he mostly wrote the training materials himself, he complemented pretty well with it. There was no big need for additional notes, since most important stuff is already contained in the slides.||5||Some noise outside, people murmuring in the back. Nothing the trainer could have prevented.||5||Our own equipment was definitely sufficient, and the hardware provided for the practical lab (beagleboard, wii nunchuck, ...) was prepared for all eventualities (ethernet -> usb adapter, usb hub, card reader, ...).||2||I have no insight into the organization, but the trainer was accidentally given a wrong time to start at the first day, and some of our participants arrived too late some days, which sucked.||4||I definitely learned a lot, but couldn't process it all since it was a little dry sometimes. I have no idea though how it could have been avoided.||5||We use buildroot systems quite regularly.||7||4||5||Flexibility and openness of the trainer. Some participants were trying to set up buildroots for custom hardware and he was quite a support.||Availability for on-site sessions, Trainer, Open training materials that can be checked in advance, Not applicable - My management made the decision||Technical resources on the Free Electrons website||Maybe later, when there is tangible demand ;)||The open source materials rock, also on other topics. Also the publicly available talk recordings are pretty valuable to me. Keep it up! :)||Spotted all problems which I couldn't figure out by myself.||3||4||Through the (subjective) high pace, at some few points it was mainly copying the materials, but most of the time there were still some realization-effects included.||3||2||From less than 100 km / 60 miles|
|11/5/2015 17:12:00||3||Great presentation, great knowledge, great speaking, easy to follow.||5||Listen, see, reproduce ... and you got 90% of the stuff. Great!||5||5||5||Well, these have been provided by our company. So the instructor has to answer this ;)||5||Well, these, too, have been provided by our company. So the instructor has to answer this ;)||5||4||5||7||5||5||Trainer, Earlier training session||Choosen by colleague||Linux board support package development, Build environment support||Many thanks!||5||5||3||3||From a foreign country|
|11/5/2015 17:17:39||3||4||5||4||4||4||5||4||4||6||3||5||- The integration of own software packages into the existing buildroot system. |
- Strategy to set up different targets for one buildroot solution.
- integration of legal info
- strategy to update the buildroot without configuring the own software packages.
|The internal functionality of buildroot was not so important, because as a software developer in a company I want to use buildroot and customize it on a higher level.||Trainer, Not applicable - My management made the decision||Presentations in conferences||Build environment support, Not interested||4||4||2||3||From less than 100 km / 60 miles|
|11/5/2015 17:27:48||5||Two days would have been enough.||3||The Lab Book is often too vague with the instructions and the expected results. What is the approximate output of a command if I did everything correctly?|
The number of re-flashings could be lower.
BR2_EXTERNAL should be introduced in the beginning, not in the end.
The trainer could have provided correct solutions for reference.
|5||4||3||The room is too small, but that is not your fault.||5||3||I would have preferred a written schedule with lecture and labs times.||5||3||6||The grey-on-white text on this form is hard to read.||3||5||Not applicable - My management made the decision||Presentations in conferences||Not interested||The sections in the Lab Book should be numbered and the instructor should state very clearly which section(s) we should work on and how much time we have for that. He should show the correct solution for each section or ask a participant to show theirs to the others.||4||4||Good, but could be improved (see above).||Often you have to guess or Google small things. The Lab Book should be more explicit with details.|
Example: When we need to reference a Github site, there should be a reminder for the syntax ($(call github,name,project,ref)).
|5||3||From a foreign country|