On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
The first stage of this has been completed, with the code
switching to
forklift. The next two stages would be:
Rename the repository
Transfer to theforeman github organization
I am of the opinion those two should be done at the same time,
with 1
week
pre-warning to users and developers to allow for update
preparation to
their usage, scripts and automation so that they do it once and not
twice.
I’ll leave this idea open for comment for a few days and then plan
for
the
one week cycle.
I believe that Github will redirect, at least on transfer.
Nice - in that case I’ll bump up the time table.
–
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
This task has been finalized with Forklift moving to theforeman Github
organization proper. All issues and PRs have been moved and Github should
properly redirect.
Eric
···
On Mon, Jan 23, 2017 at 3:01 PM, Eric D Helms wrote:
In one weeks time, I’d like to officially move Forklift to the Foreman
organization. If there are any objections or concerns, speak now or
forever
hold your peace.
+1000 for moving.
– Ivan
The following developers currently have write access and thus I’d like
to
request a team setup to ensure we keep access:
The katello-deploy repository has been officially renamed to
‘forklift’ in
concert with the code updates. The next step is to move this
officially
into theforeman organization on Github.
On Wed, May 25, 2016 at 11:36 AM, Eric D Helms ericdhelms@gmail.com >> >>> wrote:
On Wed, May 25, 2016 at 10:14 AM, Ewoud Kohl van Wijngaarden < >> >>>> ewoud@kohlvanwijngaarden.nl> wrote:
On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
The first stage of this has been completed, with the code
switching to
forklift. The next two stages would be:
Rename the repository
Transfer to theforeman github organization
I am of the opinion those two should be done at the same time,
with 1
week
pre-warning to users and developers to allow for update
preparation to
their usage, scripts and automation so that they do it once and
not
twice.
I’ll leave this idea open for comment for a few days and then
plan for
the
one week cycle.
I believe that Github will redirect, at least on transfer.
Looks like the "Forklift" maintainers team does not have the necessary
rights to manage the repository. Could this team please be given the
requisite permission updates?
···
On Thu, Feb 16, 2017 at 11:15 AM, Eric D Helms wrote:
This task has been finalized with Forklift moving to theforeman Github
organization proper. All issues and PRs have been moved and Github should
properly redirect.
On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
The first stage of this has been completed, with the code
switching to
forklift. The next two stages would be:
Rename the repository
Transfer to theforeman github organization
I am of the opinion those two should be done at the same time,
with 1
week
pre-warning to users and developers to allow for update
preparation to
their usage, scripts and automation so that they do it once and
not
twice.
I’ll leave this idea open for comment for a few days and then
plan for
the
one week cycle.
I believe that Github will redirect, at least on transfer.
Nice - in that case I’ll bump up the time table.
–
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
