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.
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.
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 < ewoud@kohlvanwijngaarden.nl> wrote:
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 01:42:31PM -0400, Eric D Helms wrote:
>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 < >ewoud@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.
> 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.
Yes, thanks for clarifying. Essentially, just port the existing team over
and we can then go from there towards future integrations between
repositories and teams. All the modulesync PRs are merged. I'll create the
team and then transfer each module if you are ready?
···
On Fri, Nov 3, 2017 at 9:03 AM, Ewoud Kohl van Wijngaarden < ewoud@kohlvanwijngaarden.nl> wrote:
On Thu, Nov 02, 2017 at 01:42:31PM -0400, Eric D Helms wrote:
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 < >> ewoud@kohlvanwijngaarden.nl> wrote:
>
>> 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.
>
>
>Yes, thanks for clarifying. Essentially, just port the existing team over
>and we can then go from there towards future integrations between
>repositories and teams. All the modulesync PRs are merged. I'll create the
>team and then transfer each module if you are ready?
I'm ready.
···
On Fri, Nov 03, 2017 at 09:28:18AM -0400, Eric D Helms wrote:
>On Fri, Nov 3, 2017 at 9:03 AM, Ewoud Kohl van Wijngaarden < >ewoud@kohlvanwijngaarden.nl> wrote:
On Thu, Nov 02, 2017 at 01:42:31PM -0400, Eric D Helms wrote:
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 < >>> ewoud@kohlvanwijngaarden.nl> wrote:
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 < ewoud@kohlvanwijngaarden.nl> wrote:
On Fri, Nov 03, 2017 at 09:28:18AM -0400, Eric D Helms wrote:
On Fri, Nov 3, 2017 at 9:03 AM, Ewoud Kohl van Wijngaarden < >> ewoud@kohlvanwijngaarden.nl> wrote:
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.
Yes, thanks for clarifying. Essentially, just port the existing team over
and we can then go from there towards future integrations between
repositories and teams. All the modulesync PRs are merged. I’ll create the
team and then transfer each module if you are ready?
I’m ready.
On Thu, Nov 02, 2017 at 01:42:31PM -0400, Eric D Helms wrote:
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 < >>>> ewoud@kohlvanwijngaarden.nl> wrote:
