13 patches has been pushed / reviewed / rebased

Feedback from the event:

- "if we want to add many more tests to OST, and I think we do, we need to do some change there to allow that. Current framework is simply not scalable enough"

- not joining the hackathon because "I'd be like an elephant in a porcelain shop"

- "I'm not sure I'm OK with the flood of suites that we have - the more we have, the harder it is to sync and maintain but more importantly - to run."

- invite wasn't clear enough. I found people on #ovirt on Freenode and on Red Hat IRC servers and redirected them to OFTC IRC server (my fault, hopefully managed to workaround it by talking to people)

Lessons learned:

- Calendar invites to mailing lists doesn't work well, need a different way to track mailing list members joining the events.

- Invites needs to be pedantic on how to join the event, not leaving space for interpretation and misunderstanding.

- We need a contribution guide to ovirt-system-test: we need to make people comfortable in trying to add a new test and we need to ensure that we won't reject a day of work because the patch doesn't match core contributors plannings on number of suites, resources and so on

- The ovirt-system-tests check patch script is not good enough. It triggers too many sequential suites on every single patch pushed, and fails due to timeout taking more than 6 hours to complete.

- The way ovirt-system-test collects rpms from defined repos is not smart enough: it doesn't take the latest version of a given package, just the first found in sequential order of the repos,

Thanks everyone who participated to the event! if you have time please continue improving ovirt-system-test even if today event is almost completed!