Devan Goodwin wrote:
I'm not really worried about what happens if the thesis fails, I'm worried about what happens if it succeeds. My concern is that we don't end up in a situation where someone spends 1.5+ years working on an open source project, succeeds (in that the code works), submits that work to the project and we're left scrambling to determine if the code passes review, we can accept the added burden of maintaining and testing a third schema, etc.
Just maintaining. We test (in terms beyond acceptance testing only code which is part of RHN Satellite). And it can be easily part of Spacewalk and not part of Satellite.
And I really have no fear that no one will maintain it.
Basically it boils down to: do we know whether or not we can accept this work (if it is successful or partially successful) and if the answer is no, is this communicated clearly up front. If those questions are answered, or Matej is content to spend years working on code that may never be used even if it's successful, then my concerns are satisfied.
The possibility of rejecting is for every patch/submission. For long terms projects it is little higher, but I suppose that both parties count with this risk.
-- Miroslav Suchy RHN Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
