COPR

[Toshio Kuratomi]

On Tue, Sep 3, 2013 at 11:54 PM, Miroslav Suchý <msuchy at redhat.com> wrote:
> On 09/03/2013 03:41 PM, Frankie Onuonga wrote:
>>
>> I mean we have a really sharp crew here.
>> Why not?
>
>
> We have sharp crew, but they have a lot of other work to do. So thinking
> about how to offload some developer work with others make IMO sense.
>

Note: Our sysadmin limitations are a lot more severe than our
developer constraints.  With that in mind, I'd say if you're looking
to run this in Fedora Infrastructure (as opposed to making it a RH
service), OBS is not going to happen.  There's too much additional
burden in running it.

Getting things merged into koji is better.  If mikem is willing to
build the necessary features into koji then it is more desirable to
run a second instance of koji than to run an entirely new system using
an entirely new language stack.  In the past we were a bit leary of
building on top of koji as it is designed to do something quite
different than what we need for implementing coprs.  koji makes many
demands in order to be able to track and make (at least theoretically)
reproducible what has been built on it in the past.  Coprs doesn't
need this and in some cases (being able to build against arbitrary
third-party repos at arbitrary points in time) is at odds with koji's
goal of reproducability.  Talking to mikem at flock, though, he seems
interested in the use-cases so adding the necessary features and the
ability to turn some features off may be doable for a separate koji
instance that we run to implement coprs.

-Toshio