Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-27 Thread Eric D Helms 
The work to transfer tool_belt officially to theforeman for use is now
complete. The foreman configs have been moved into the repository, the old
repository deleted and the original transferred. I have created a team to
manage the repository based on the top code committers to date. If you'd
like to be a part of the team and contribute please reach out.

If anyone would like more information around what it can or how it can help
with your own release please let us know and I'd be happy to write
something up or do a small deep dive.


Eric

On Thu, Oct 26, 2017 at 10:37 AM, Eric D Helms  wrote:

> I've began this process by capturing what I believe is everything from [1]
> as an PR to the mainline tool_belt repository:
>
> https://github.com/ehelms/tool_belt/pull/58
>
> Once this is approved, I will do the delete and transfer dance.
>
>
> [1] https://github.com/theforeman/tool_belt
>
> On Mon, Oct 23, 2017 at 9:08 AM, Andrew Kofink  wrote:
>
>> +1 I guess the foreman and katello config files will still live
>> separately (i.e. katello_35.yaml and foreman_16.yaml) but in the same repo.
>>
>> On Mon, Oct 23, 2017 at 5:59 AM, Daniel Lobato Garcia <
>> elobat...@gmail.com> wrote:
>>
>>> On 10/20, Eric D Helms wrote:
>>> > For quite a few releases now, we've been using a little tool named
>>> > tool_belt as a CLI to perform release tasks such as finding cherry
>>> picks,
>>> > or building koji configurations. The larger idea of the repository is
>>> you
>>> > define a release via a configuration file and perform various release
>>> > actions based on the data within the config file. The original
>>> repository
>>> > lives on my personal Github account [1]. At some point, this was
>>> forked to
>>> > theforeman organization and configurations for just Foreman stored in
>>> it.
>>> > Meanwhile, in the original repository are configs for Katello releases.
>>> >
>>> > I would like to propose merging the configuration files from
>>> theforeman to
>>> > my original repository, deleting thetheforeman fork and then
>>> transferring
>>> > my repository to theforeman to serve as the single shared repository.
>>> If
>>> > you have any concerns, objections or questions please raise them here.
>>> >
>>> > If there are no objections, I will perform this next Wednesday or
>>> Thursday.
>>> >
>>> >
>>> > [1] https://github.com/ehelms/tool_belt
>>> > [2] https://github.com/theforeman/tool_belt
>>> >
>>> > --
>>> > 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.
>>>
>>> +1, I would also like to merge https://github.com/dlobatog/fo
>>> reman_release
>>> into that repository, making each of the scripts a subcommand of
>>> tool_belt
>>>
>>> --
>>> Daniel Lobato Garcia
>>>
>>> @dLobatog
>>> blog.daniellobato.me
>>> daniellobato.me
>>>
>>> GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30
>>> Keybase: https://keybase.io/elobato
>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> Andrew Kofink
>> akof...@redhat.com
>> IRC: akofink
>> Software Engineer
>> Red Hat Satellite
>>
>> --
>> 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
>



-- 
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.

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-26 Thread Eric D Helms 
I've began this process by capturing what I believe is everything from [1]
as an PR to the mainline tool_belt repository:

https://github.com/ehelms/tool_belt/pull/58

Once this is approved, I will do the delete and transfer dance.


[1] https://github.com/theforeman/tool_belt

On Mon, Oct 23, 2017 at 9:08 AM, Andrew Kofink  wrote:

> +1 I guess the foreman and katello config files will still live separately
> (i.e. katello_35.yaml and foreman_16.yaml) but in the same repo.
>
> On Mon, Oct 23, 2017 at 5:59 AM, Daniel Lobato Garcia  > wrote:
>
>> On 10/20, Eric D Helms wrote:
>> > For quite a few releases now, we've been using a little tool named
>> > tool_belt as a CLI to perform release tasks such as finding cherry
>> picks,
>> > or building koji configurations. The larger idea of the repository is
>> you
>> > define a release via a configuration file and perform various release
>> > actions based on the data within the config file. The original
>> repository
>> > lives on my personal Github account [1]. At some point, this was forked
>> to
>> > theforeman organization and configurations for just Foreman stored in
>> it.
>> > Meanwhile, in the original repository are configs for Katello releases.
>> >
>> > I would like to propose merging the configuration files from theforeman
>> to
>> > my original repository, deleting thetheforeman fork and then
>> transferring
>> > my repository to theforeman to serve as the single shared repository. If
>> > you have any concerns, objections or questions please raise them here.
>> >
>> > If there are no objections, I will perform this next Wednesday or
>> Thursday.
>> >
>> >
>> > [1] https://github.com/ehelms/tool_belt
>> > [2] https://github.com/theforeman/tool_belt
>> >
>> > --
>> > 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.
>>
>> +1, I would also like to merge https://github.com/dlobatog/fo
>> reman_release
>> into that repository, making each of the scripts a subcommand of tool_belt
>>
>> --
>> Daniel Lobato Garcia
>>
>> @dLobatog
>> blog.daniellobato.me
>> daniellobato.me
>>
>> GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30
>> Keybase: https://keybase.io/elobato
>>
>> --
>> 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.
>>
>
>
>
> --
> Andrew Kofink
> akof...@redhat.com
> IRC: akofink
> Software Engineer
> Red Hat Satellite
>
> --
> 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.

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-23 Thread Andrew Kofink 
+1 I guess the foreman and katello config files will still live separately
(i.e. katello_35.yaml and foreman_16.yaml) but in the same repo.

On Mon, Oct 23, 2017 at 5:59 AM, Daniel Lobato Garcia 
wrote:

> On 10/20, Eric D Helms wrote:
> > For quite a few releases now, we've been using a little tool named
> > tool_belt as a CLI to perform release tasks such as finding cherry picks,
> > or building koji configurations. The larger idea of the repository is you
> > define a release via a configuration file and perform various release
> > actions based on the data within the config file. The original repository
> > lives on my personal Github account [1]. At some point, this was forked
> to
> > theforeman organization and configurations for just Foreman stored in it.
> > Meanwhile, in the original repository are configs for Katello releases.
> >
> > I would like to propose merging the configuration files from theforeman
> to
> > my original repository, deleting thetheforeman fork and then transferring
> > my repository to theforeman to serve as the single shared repository. If
> > you have any concerns, objections or questions please raise them here.
> >
> > If there are no objections, I will perform this next Wednesday or
> Thursday.
> >
> >
> > [1] https://github.com/ehelms/tool_belt
> > [2] https://github.com/theforeman/tool_belt
> >
> > --
> > 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.
>
> +1, I would also like to merge https://github.com/dlobatog/foreman_release
> into that repository, making each of the scripts a subcommand of tool_belt
>
> --
> Daniel Lobato Garcia
>
> @dLobatog
> blog.daniellobato.me
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30
> Keybase: https://keybase.io/elobato
>
> --
> 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.
>



-- 
Andrew Kofink
akof...@redhat.com
IRC: akofink
Software Engineer
Red Hat Satellite

-- 
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.

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-23 Thread Greg Sutcliffe 
On Fri, 2017-10-20 at 16:59 -0400, Eric D Helms wrote:
> 
> If there are no objections, I will perform this next Wednesday or
> Thursday.

+1
-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

-- 
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.

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-22 Thread Ewoud Kohl van Wijngaarden 

On Fri, Oct 20, 2017 at 04:59:33PM -0400, Eric D Helms wrote:

For quite a few releases now, we've been using a little tool named
tool_belt as a CLI to perform release tasks such as finding cherry picks,
or building koji configurations. The larger idea of the repository is you
define a release via a configuration file and perform various release
actions based on the data within the config file. The original repository
lives on my personal Github account [1]. At some point, this was forked to
theforeman organization and configurations for just Foreman stored in it.
Meanwhile, in the original repository are configs for Katello releases.

I would like to propose merging the configuration files from theforeman to
my original repository, deleting thetheforeman fork and then transferring
my repository to theforeman to serve as the single shared repository. If
you have any concerns, objections or questions please raise them here.

If there are no objections, I will perform this next Wednesday or Thursday.


[1] https://github.com/ehelms/tool_belt
[2] https://github.com/theforeman/tool_belt


Sounds like a good idea

--
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.