Greetings Linaro-dev, I have joined the mailing list today and as a newbie Codethink(er) I am looking at contributing around the Linaro Validation area, especially Lava. My background is as a programme manager, generally around embedded mobile and have just completed a significant webkit based development project. First up on Linaro I have been digesting blueprints to get a feel for the Lava project scope and produce a system use-case (or story) list. The blueprints are not really giving me a system level picture that pulls together all the threads at the moment. Once I get this I can then spot some gaps where we can add value. Typical questions I am trying to answer are:
What Mechanism is used by the community member to trigger/request an evaluation run? What needs to be provided by the community member in the evaluation package? What is the minimum? What will be present on the boards? Will the test run content be configurable by the evaluation requester? To this end, is there a Lava system-level requirement/scope? I have come across Linaro burn-down graphs, so maybe there is a Scrum type requirements backlog I can pick up on. Regards, Paul paul.mi...@codethink.co.uk _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
