On 08/14/2013 12:22 PM, Miroslav Suchý wrote:
as I started working on COPR I gathered dozens requirements, which does
not fit into current COPR architecture and I make little step back and
thought about COPR and what we can have.
This is current options:
1) Continue with current code.
Pros: We can have working (and public) solution very fast (aprox. ETA +1
Cons: It will be very simply. I will probably have very few time for
coding RFE so implementation of all RFE will take ages
imo, copr's is implementation looks fairly complete for it's supported
use-cases. please keep it simple.
Folks that want more, can explore their own alternatives, including koji