On Thu, Jun 21, 2018 at 8:51 AM Petr Pisar <ppisar@redhat.com> wrote:
On 2018-06-21, Stephen Gallagher <sgallagh@redhat.com> wrote:
> On Thu, Jun 21, 2018 at 5:17 AM Kevin Kofler <kevin.kofler@chello.at> wrote:
>> Will the repositories be enabled or disabled by default?
>>
>
> Enabled by default. Packaging policy will require that modules with a
> default stream may not override packages in the standard repo.
>
How are packagers supposed to implement a seamless move from a bare package to
a module not to disrupt users?

Example: I have a gscan2pdf package that I want to move to a module.
According to the policy firtst I have to remove the package from
a repository. Now the user cannot install the package. Then the module
review will be approved and the module built. And finally package is
available to users again.

I don't think this is a great user experience.

I oversimplified that last statement, sorry. I shouldn't post before breakfast. What you're requesting is permissible; if you are the maintainer of a package and want to move it into a module with a default stream to replace the version in the standard repos, that's fine.

My statement was more about protecting against "I have Node.js 8.x in the traditional repos, but 10.x in the default module stream, which overrides it, thus resulting in a different experience with and without the modular repos enabled." If you decide to replace a package with a module default stream, it will need to follow the stable updates policy for the current Fedora release. (So if I wanted to move from Node.js 8.x bare RPMs to a module, then the 8.x module stream would have to be the default, not 10.x).