The first stage of this has been completed, with the code switching to forklift. The next two stages would be:
1) Rename the repository 2) 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. Eric On Sat, May 21, 2016 at 10:00 AM, Eric D Helms <[email protected]> wrote: > Thank you all for the input and votes! The winner appears to be Forklift > and thus I will begin (contributions welcome as well) to rename the > libraries within to reflect this name change and clean up a few bits and > pieces before requesting moving to theforeman organization. > > > Eric > > On Thu, May 12, 2016 at 3:36 PM, Eric D Helms <[email protected]> > wrote: > >> Coming back around to this, the suggestions I saw were narrowed down to: >> >> * Forklift >> * foreman-deploy >> * foremanize >> * oh-my-foreman >> >> I created a doodle to capture votes easier, I am not sure if the name >> field is actually required but it can be anonymous if does: >> >> http://doodle.com/poll/wye83srdqdifd7cg >> >> >> On Thu, Apr 28, 2016 at 7:41 AM, Ivan Necas <[email protected]> wrote: >> >>> 9) foremanize >>> >>> On Tue, Apr 26, 2016 at 11:23 PM, Ivan Necas <[email protected]> wrote: >>> >>>> +1 for foreman-deploy. >>>> >>>> 8) oh-my-foreman :) >>>> >>>> -- Ivan >>>> >>>> On Wed, Apr 13, 2016 at 4:57 PM, Tomas Strachota <[email protected] >>>> > wrote: >>>> >>>>> On 04/13/2016 04:55 PM, Tomas Strachota wrote: >>>>> >>>>>> On 04/05/2016 01:54 PM, Eric D Helms wrote: >>>>>> >>>>>>> To move this away from being Katello centric, the first thing would >>>>>>> be, >>>>>>> I assume, to rename the repository and thus the internals. >>>>>>> Suggestions >>>>>>> welcome, throwing out a few ideas: >>>>>>> >>>>>>> 1) foreman-deploy >>>>>>> 2) foreman-dev-tools >>>>>>> 3) foreman-dev >>>>>>> 4) foreman-devel >>>>>>> 5) foreman-tools >>>>>>> 6) Forklift >>>>>>> 7) Taisun (strongest crane in existence) >>>>>>> 8) ??? >>>>>>> >>>>>>> >>>>>> foreman-deploy sounds ok to me. >>>>>> >>>>> >>>>> Ehm, taking back. It might easily get confused with >>>>> foreman-deployments. >>>>> So, forklift would be my second choice. >>>>> >>>>> >>>>> >>>>>> T. >>>>>> >>>>>> >>>>>>> >>>>>>> Eric >>>>>>> >>>>>>> On Tue, Mar 29, 2016 at 4:13 AM, Tomas Strachota < >>>>>>> [email protected] >>>>>>> <mailto:[email protected]>> wrote: >>>>>>> >>>>>>> On 03/23/2016 11:14 PM, Eric D Helms wrote: >>>>>>> >>>>>>> All, >>>>>>> >>>>>>> I believe there is a fair chunk of developers that are >>>>>>> familiar >>>>>>> with the >>>>>>> katello-deploy repository [1]. The repository started to >>>>>>> house >>>>>>> our bats >>>>>>> tests inspired by foreman-bats and has grown to represent a >>>>>>> set of >>>>>>> tools, tasks and functionality for developers. To date, it >>>>>>> can >>>>>>> do things >>>>>>> like: >>>>>>> >>>>>>> * Spin up Foreman nightly and 1.11 via Vagrant >>>>>>> * Spin up Katello nightly and 3.0 via Vagrant >>>>>>> * Spin up a development environment that follows common >>>>>>> practices and >>>>>>> configurations >>>>>>> * Run installations with koji scratch builds >>>>>>> * Run installations pointed at puppet module PRs >>>>>>> * Install from koji-repos >>>>>>> * Docker containers for some common tasks >>>>>>> - Katello client containers for registration/package >>>>>>> install testing >>>>>>> - Jenkins Job Builder environment runtime >>>>>>> - Redmine container for testing updates (still in PR >>>>>>> phase) >>>>>>> >>>>>>> When we switched the installer over to scenarios, we moved >>>>>>> katello-deploy to be more Foreman centric with respect to >>>>>>> being >>>>>>> able to >>>>>>> spin up Foreman directly (and not just Katello+Foreman). >>>>>>> >>>>>>> >>>>>>> I would like to propose moving katello-deploy from its >>>>>>> current >>>>>>> state and >>>>>>> home to be centered in the community as a suite of >>>>>>> development >>>>>>> tools and >>>>>>> runtime environments. The goal being to not only allow >>>>>>> developers to be >>>>>>> more efficient when they need a particular environment for >>>>>>> development >>>>>>> or testing but as an entry point to lower the barrier for >>>>>>> users >>>>>>> as well. >>>>>>> >>>>>>> >>>>>>> katello-deploy has proved to be very helpful. +1 for making it an >>>>>>> official tool for test/devel setups of the Foreman. >>>>>>> >>>>>>> >>>>>>> If this sounds like something the community would want and >>>>>>> benefit from >>>>>>> then I would like to: >>>>>>> >>>>>>> a) identify any changes that should be made before >>>>>>> centralizing it >>>>>>> (e.g. changing the repo name and ownership) >>>>>>> b) tackle any code related issues identified from this >>>>>>> discussion >>>>>>> c) gather a list of personal developer repositories for >>>>>>> development >>>>>>> tasks and tooling and triage them for inclusion in this repo >>>>>>> with their >>>>>>> permission >>>>>>> >>>>>>> >>>>>>> [1] https://github.com/Katello/katello-deploy >>>>>>> >>>>>>> -- >>>>>>> Eric D. Helms >>>>>>> Red Hat Engineering >>>>>>> Ph.D. Student - North Carolina State University >>>>>>> >>>>>>> -- >>>>>>> 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 [email protected] >>>>>>> <mailto:foreman-dev%[email protected]> >>>>>>> <mailto:[email protected] >>>>>>> <mailto:foreman-dev%[email protected]>>. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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 [email protected] >>>>>>> <mailto:foreman-dev%[email protected]>. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Eric D. Helms >>>>>>> Red Hat Engineering >>>>>>> Ph.D. Student - North Carolina State University >>>>>>> >>>>>>> -- >>>>>>> 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 [email protected] >>>>>>> <mailto:[email protected]>. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>> -- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Eric D. Helms >> Red Hat Engineering >> Ph.D. Student - North Carolina State University >> > > > > -- > Eric D. Helms > Red Hat Engineering > Ph.D. Student - North Carolina State University > -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
