Learn more about these different git repos.
In the traditional model, packages are built out of release branches (i.e. f28, f29, ...) directly by submitting package builds.
There is just one person owning the package and building it.
With Modularity, packages are being built indirectly by submitting a module build which automatically spins package builds for all package stream branches the module includes.
One module can include multiple packages, and one package can be included in multiple modules.
How do we deal with ownership?
I think the proposal should be reworded to be:
Package stream branches don't have explicit owners. The ownership is defined implicitly by the following:
@james I think the FPC should probably review this ticket
@langdon Thanks! I've changed the proposal to include your edit which is much better than what I wrote!
well, this has been put in the way that only modular version exists, however there might be package which is built traditionally and in a module.
@ignatenkobrain Are you referring to the potential use of stream branches for ursine builds? I don't think that's currently the case anywhere or am I wrong?
Not sure if this is an FPC matter but I think an ack from FESCo would be welcome. I'll file the ticket.
we'll discuss this one with FESCo
to comment on this ticket.