I am ready to move them when you give the green light.

My inclination for permissions and team setup would be to maintain all
individual maintership on the modules to date. Further, to take the katello
installer team and add them to a similar installer team on theforeman
organization.

On Thu, Nov 2, 2017 at 12:38 PM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:

> Hello all,
>
> Previously this has been discussed in various threads but now we're ready
> to make it a reality. All modules should be ready to use a single
> modulesync repository and a pull request has been opened.
> https://github.com/theforeman/foreman-installer-modulesync/pull/78
> lists all tasks that need to be completed.
>
> Some important things to note:
>
> * We invite users to submit redmine issues to the foreman installer
> project. Previously we only pointed them to Redmine without specific
> directions.
> * We will continue to publish modules on the puppet forge under the
> katello user. Moving modules there requires a bit more effort for  little
> benefit.
> * This does (not yet) include merging the installers. For now
> foreman-installer won't ship the katello modules.
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to