Re: [foreman-dev] Moving katello puppet modules to the foreman github namespace

2017-11-03 Thread Eric D Helms
All repositories have been transfered to theforeman Github organization. A new team has been created named 'Katello Installer' that contains all puppet modules and users from the same team in the Katello github organization. On Fri, Nov 3, 2017 at 9:50 AM, Ewoud Kohl van Wijngaarden <

Re: [foreman-dev] Moving katello puppet modules to the foreman github namespace

2017-11-03 Thread Ewoud Kohl van Wijngaarden
Not sure if I understand what you mean. Are you saying to create a katello installer team in theforeman org to match it with the katello org one? That was similar to what I was thinking. It's the easiest in the short term and we can easily iterate from there. On Thu, Nov 02, 2017 at

Re: [foreman-dev] Moving katello puppet modules to the foreman github namespace

2017-11-02 Thread Eric D Helms
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,

[foreman-dev] Moving katello puppet modules to the foreman github namespace

2017-11-02 Thread Ewoud Kohl van Wijngaarden
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