Re: [foreman-dev] Nominating cfouant for write access to hammer-cli-katello

2017-12-01 Thread Eric D Helms
+1 -- even though this appears to be done already -- welcome to CLI team
Christine!

On Fri, Dec 1, 2017 at 8:31 AM, Walden Raines  wrote:

> +1
>
> On Thu, Nov 30, 2017 at 5:26 PM, Tom McKay  wrote:
>
>> +1
>>
>> On Tue, Nov 21, 2017 at 11:55 AM, Chris Roberts 
>> wrote:
>>
>>> +1 from me
>>>
>>> On Tuesday, November 21, 2017 at 11:40:48 AM UTC-5, Andrew Kofink wrote:

 I hereby nominate Christine Fouant to gain commit access to
 hammer-cli-katello. She currently has 12 merged PRs
 
  and
 has helped to review 11 merged PRs
 
 .

 Let the +/-1's begin!

 --
 Andrew Kofink
 ako...@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.
>>>
>>
>> --
>> 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.
>>
>
> --
> 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] Nominating cfouant for write access to hammer-cli-katello

2017-12-01 Thread Walden Raines
+1

On Thu, Nov 30, 2017 at 5:26 PM, Tom McKay  wrote:

> +1
>
> On Tue, Nov 21, 2017 at 11:55 AM, Chris Roberts 
> wrote:
>
>> +1 from me
>>
>> On Tuesday, November 21, 2017 at 11:40:48 AM UTC-5, Andrew Kofink wrote:
>>>
>>> I hereby nominate Christine Fouant to gain commit access to
>>> hammer-cli-katello. She currently has 12 merged PRs
>>> 
>>>  and
>>> has helped to review 11 merged PRs
>>> 
>>> .
>>>
>>> Let the +/-1's begin!
>>>
>>> --
>>> Andrew Kofink
>>> ako...@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.
>>
>
> --
> 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.
>

-- 
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] The road to Rails 5.1

2017-12-01 Thread Michael Moll
Hi,

On Thu, Nov 30, 2017 at 08:47:12PM -0500, Eric D Helms wrote:
> Good find! I know this will likely break nightlies on the RPM side given
> JSON is only at 2+ in Ruby 2.4. However, based on your previous email it
> sounds like we are going to have to bite the bullet on some length of time
> where RPMs are broken? The question then is how long do we allow that
> period to be based upon how much time we give plugins to switch to Rails 5?

At the end of the day plugin development is independent from core. Today
all the major plugins are compatible with Rails 4.2 and 5.0. Initially I
thought of one week having core using 5.0, but even now plugin authors
can start working on opening PRs aginst plugins that will fix all the
remaining 5.0 deprecations (breaking 4.2).

Regards
-- 
Michael Moll

-- 
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] Kanban tools and redmine

2017-12-01 Thread Ewoud Kohl van Wijngaarden

On Thu, Nov 30, 2017 at 10:27:40AM +0100, Marek Hulán wrote:

Dne středa 29. listopadu 2017 9:05:28 CET, Lukas Zapletal napsal(a):

Can you elaborate on why something does not make sense to track in
RedMine? I am not following, RedMine is a generic ticketing system and
you can create as many tickets as you want, e.g. Buy milk. It will
work. This is a dogma I do not take as an argument. What's relevant is
if you need to create private work items, but we do have a private
feature in RedMine and we use it from time to time. And frankly, we
don't need these very often (mostly security issues).


Sorry for answering someone else question, but from my experience, redmine is
great for tracking dev stuff, including back traces, links to PR, BZ, release
that includes the fix etc. Stuff like buy milk that does not hopefully have a
backtrace is easier to track in some board as it's easier to manipulate. More
realistically, things like "review PR $number" is easier to add and track in
more lightweight system. I think these are simply two different use cases and
I'm fine using two different tools for them.

So for me, I'd prefer to keep using what I need, redmine and some board and
not trying to combine both together.


This mirrors my experience. It's also easier to keep downstream issues 
out of upstream but still track them.



If you look to the past, various scrum teams tried dozens off tools.
But hey, you know what is still here? RedMine (and RHBZ of course :-)
- those systems survived. My sole opinion is let's ditch RedMine and
use RHBZ for everything, many open source projects do this. But I
understand many people cannot live with Bugzilla, that's fine. OK!
Let's just stick to RedMine then. If people want to try RedMine
plugins, I totally do support that. What I really like is to have
everything in one place - no copies.

Historically, there have been problems with RedMine plugins for scrum,
it was overloading the server when whole team was moving tickets. But
we might upgraded to better hosting how, if infrateam approves I am
all for trying anything that is a RedMine plugin and works with
regular issues.

This could be a chance to setup "staging" redmine, since we still have
some knowledge from the migration. There we can test it on our current
data and vote how we like it.

LZ

On Wed, Nov 29, 2017 at 8:00 AM, Ivan Necas  wrote:
> My uderstanding of kanban is, that moving the cards manually on the signal
> board is actually part of the kanban way of doing things. Another thing,
> that is integrated part of the kanban process is
> WIP limits, that I don't even see on the redmine plugin. Another reason
> for
> actually not using
> redmine for this is the rasks, that don't make sense to actually track in
> redmine.
>
> I have a pr to nice Marek's tooling around automating some common actions
> around
> Kanboard https://github.com/ares/kansync/pull/5 and so far, I'm happy with
> this.
>
> -- Ivan
>
> út 28. 11. 2017 v 22:37 odesílatel Andrew Kofink 
>
> napsal:
>> I'm open to using other kanban style tools. To me it doesn't really
>> matter
>> that much how we plan - it's the same information just in a different
>> format. So, if people have reasons, then I'm fine with switching.
>>
>> On Tue, Nov 28, 2017 at 4:29 PM, Walden Raines 

wrote:

>>> Hey,
>>>
>>> With several teams moving to kanban style tools for the visualization of
>>> tasks I'm wondering if anyone has tried redmine's PluginKanban [1].
>>>
>>> I really like the idea of a trello/kanboard like tool but I hate having
>>> to update tasks in multiple places.  Another idea I had was to switch
>>> (back) to using GH issues and use GH projects [2] as well.
>>>
>>> Any other thoughts on how to make these kanban boards work better with
>>> redmine?
>>>
>>> Cheers,
>>> Walden
>>>
>>> [1] http://www.redmine.org/projects/redmine/wiki/PluginKanban
>>> [2] https://help.github.com/articles/about-project-boards/


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