I'd join regularly, after few years for which I receive all notifications
from redmine, I can confirm there are bugs without much attention.
If we won't have representatives from all areas, we might need some tooling
to ping people in redmine tickets. Again, after few years, I can tell that
me
On Wed, Nov 8, 2017 at 1:55 PM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
> On Wed, Nov 08, 2017 at 11:49:55AM -0500, Eric D Helms wrote:
>
>> The work for this transition has completed. All packages have been moved
>> at
>> this point, and katello-packaging fully deprecated
On Wed, Nov 08, 2017 at 11:49:55AM -0500, Eric D Helms wrote:
The work for this transition has completed. All packages have been moved at
this point, and katello-packaging fully deprecated. The packaging PR
testing on foreman-packaging has been updated to account for these new
packages as well as
On Wed, Nov 8, 2017 at 2:42 PM, Greg Sutcliffe wrote:
> Apparently my arguments aren't coming out coherently - I think we've
> misunderstood each other on a couple of points...
>
>> I'm afraid the amount of time waiting doesn't have any influence on
>> the feeling if something is big bang or not.
The work for this transition has completed. All packages have been moved at
this point, and katello-packaging fully deprecated. The packaging PR
testing on foreman-packaging has been updated to account for these new
packages as well as the rubygem-katello, katello-installer and
hammer_cli_katello n
I partially suggested in light of the concerns I heard on IRC and how the
Katello plugin has dealt with similar issues by having a weekly triage.
We've been doing this for quite a while and I think it works quite well to
address every issue. What follows is a run down of how we manage that
process.
So on IRC the idea of a regular issue triage for core issues in redmine
came up, and I think it's a pretty good idea.
I think we'd want to do this on a public stream (but recorded, I think),
and then anyone interested can join. We'd need a minimum number of
people involved to make it work, I guess
On 08/11/17 11:12, Ewoud Kohl van Wijngaarden wrote:
> +1 on just marking it in README and in the github description.
+1 from me too. I can make those changes as an Org owner if need be.
Greg
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To u
On Wed, Nov 8, 2017 at 3:42 PM, Greg Sutcliffe
wrote:
> On 08/11/17 12:35, Eric D Helms wrote:
> > All,
> >
> > I brought this idea up in a separate thread, but want to formalize it
> into
> > it's own direct proposal. As of today, the Jenkins Job (JJB)
> configurations
> > live buried inside the
On 08/11/17 12:35, Eric D Helms wrote:
> All,
>
> I brought this idea up in a separate thread, but want to formalize it into
> it's own direct proposal. As of today, the Jenkins Job (JJB) configurations
> live buried inside the foreman-infra repository. I believe this makes them
> hard to discover
Apparently my arguments aren't coming out coherently - I think we've
misunderstood each other on a couple of points...
> I'm afraid the amount of time waiting doesn't have any influence on
> the feeling if something is big bang or not.
Sure, that's not what I was trying to say, I was just trying
All,
I brought this idea up in a separate thread, but want to formalize it into
it's own direct proposal. As of today, the Jenkins Job (JJB) configurations
live buried inside the foreman-infra repository. I believe this makes them
hard to discover [1] and awkward to work with being inside a puppet
+1 on just marking it in README and in the github description.
On Wed, Nov 08, 2017 at 12:07:43PM +0100, Ivan Necas wrote:
+1 of marking as unmaintained, but keeping around
-- Ivan
On Wed, Nov 8, 2017 at 12:04 PM, Timo Goebel wrote:
... i would not remove it from the github org. There are ev
+1 of marking as unmaintained, but keeping around
-- Ivan
On Wed, Nov 8, 2017 at 12:04 PM, Timo Goebel wrote:
> ... i would not remove it from the github org. There are even more abandoned
> plugins there. I would not delete the code, maybe somebody wants to start
> work on them again.
>
> I w
... i would not remove it from the github org. There are even more abandoned
plugins there. I would not delete the code, maybe somebody wants to start work
on them again.
I would mark them as unmaintained in the repo description, remove the jenkins
jobs and remove them from packaging.
Timo
--
Just a quick update on threading, since that's causing the most pain...
On 05/11/17 18:51, Martin Bačovský wrote:
> - for some reason the threads are not kept together in my Gmail and the
> messages from one thread are split into multiple threads even if they seem
> to have same subject. I'm not
Thank you all! Especially for the encouraging words.
-Ursprüngliche Nachricht-
> Von:Eric D Helms
> Gesendet: Mittwoch 1 November 2017 20:29
> An: foreman-dev
> Betreff: Re: [foreman-dev] Merge permission for
> theforemen/foreman-ansible-modules
>
> +1 from me as well (Ill aim to add y
17 matches
Mail list logo
