[Toaster] please help me review Toaster presentation

[Reyna, David]

Hi Alex,

Here are some small comments, based on the slides and from hearing your presentation in person.

1) I think that how you spoke to how Toaster got designed via customer and client interviews is a very strong story.

2) I think that you should add content around how scalable and extendible Toaster it, because I think that this reflects the strength and foresight of your architecture. I am glad someone in the audience asked the question in the QA, and I think that it is worth mentioning in your slides.

Speaking of that, both you and I got questions on how Toaster will interact with buildbot and Jenkins (though interestingly from opposite points of view), so that may be worth a preemptive line in your slides.

3) In Slide #5 you spoke to how the content in black was in the present release, and how the content in gold was planned for future releases. I think that you should go ahead and add that comment at the bottom or that slide for those you may see your presentation separate from your speaking.

4) I think that in Slide #6 you should absolutely use a picture of the Toaster interface and _not_ that of a unrelated financial chart. I think that the Toaster home page is an excellent entre to the intended scope of the Toaster interface, and would be a fine candidate.

5) In your live demo, you ‘unfortunately’ had perfect builds :-). It would be good if you had a failed build, even if you have to manually introduce the error into the codebase, so that you can use that to explicitly demonstrate how Toaster directly allows you to trace back to the error state and guide you to where to debug, to really drive your point home.

6) In Slide #16, you have the statement “Targeted at finding low-hanging fruits for optimization”. Do we have any specific examples on how we would apply that idea? I ask because I expect that all of the Yocto-provided packages are already optimized, so I am not sure what in this circumstance Toaster could teach us.

Perhaps you could do one build with no parallelism, one with jobs/packages at level 2, and one with jobs/packages at level 4. Then you could use Toaster to show the relative build speeds to prove how these Yocto Project configuration tools help speed optimization. It could also help show diminishing returns for a high number, where for example “4” is not fully twice as faster as at “2”. I think that solid numbers like this can help convince skeptics.

7) On Slide #18 you mention “Targeting Web-based editors for configuration and recipes”. The phrase “Web-based editor” threw me, because as written it sounded like we were perhaps trying to incorporate existing web-based VI/Emacs/Notepad editors on the web or something. Perhaps “Toaster-based Project Configuration Wizards” is more indicative to what we are trying to convey?

8) Similarly on Slide #19 you use the phrase “the Web interface”. I think it should be something like “the Toaster Web interface”, to underline that this is Toaster’s web interface. Other than that small note I like what you wrote on Slide #19.

Good luck in your presentation!
David


From: toaster-bounces at yoctoproject.org [mailto:toaster-bounces at yoctoproject.org] On Behalf Of Damian, Alexandru
Sent: Thursday, April 03, 2014 4:38 AM
To: toaster at yoctoproject.org
Subject: [Toaster] please help me review Toaster presentation

Hello,
I am about to give a Toaster presentation at the Intel OTC conference.

Can you please help me by reviewing the attached slides and come back with suggestions for improvement ?

Thank you,
Alex

--
Alex Damian
Yocto Project
SSG / OTC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20140422/3a5d8cdb/attachment.html>