- give credit to user for good runs, throw out bad runs - capability for red hat to override whether or not a system is certified
(In reply to comment #0) > - give credit to user for good runs, throw out bad runs All proper runs will be put into the database passed or failed. As long as they are sane. If a run does not contain proper sanity such as a INFO test, it will be skipped and only the ones that are proper will be put in. Does this need to be more intelligent than that? > - capability for red hat to override whether or not a system is certified This should already happen since the cert is a bug report and we can change the status of the bug to reflect how we feel about the cert. Plus it is not considered public til we uncheck the groups regardless if it is certified or not.
Adding Rob to the cc: to talk about issue #1. (To me that sounds good enough)
I'm making an executive decision, let's do it as you say.
So reading back through the comments I made and others, doesn't sound like anything needs to be changed from the current system. Reopen this if you can think of anything else that needs addressing.