Rationale: Scripts are a key part of the quality we want to achieve. So, we need to organize how we develop and use arsenal, to avoid people being bottlenecks in the process or only one person or another to be responsible for all the structure, which doesn't scale.
Define maintenance schema for reports being used to track bugs that the teams are working on (including but not limited to: http://status.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html).
Goal: Have a defined process on how to contribute to arsenal (code reviews, mailing list discussions prior to implementation). Communication improved among people involved with arsenal. Not having scripts failing for days or unexpectedly due to changes known to a few.