On pondělí 14. srpna 2017 17:31:00 CEST Greg Sutcliffe wrote:
> Hi all,
>
> This went fairly quiet, but we all seem largely in agreement. I'll
> draft something up for the website and send a PR tomorrow. I had a few
> side questions though:
>
> On Wed, 2017-07-19 at 10:13 +0200, Marek Hulán wrote
Thanks Shim, it looks very promising. Couple of thoughts for future. I
think it'd be great if it was checking community-templates PRs. I wonder if
we should integrate it with core or rather foreman_templates (or merge
templates to core). Since it should probably be interactive and users
should
+1 on infra being unintuitive.
I'd also add that containers might not be obvious. I'd expect at least a
few because nobody runs just 1 container. Something like [1] or [2] is
more like what I'd expect, but at least 3 neatly stacked boxes IMHO.
Another this that overlaps a lot is Configure and
In my opinion, the infrastructure icon looks unintuitive. How about some kind
of treeview?
The rest looks good and straightforward to me.
Timo
> On 14. Aug 2017, at 21:10, Roxanne Hoover wrote:
>
> Visual Design took a pass at the icons in vertical nav. Anyone have any
> thoughts? They seem s
Visual Design took a pass at the icons in vertical nav. Anyone have any
thoughts? They seem straightforward to me, some were unaltered from the
original chosen.
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and
Hi all,
This went fairly quiet, but we all seem largely in agreement. I'll
draft something up for the website and send a PR tomorrow. I had a few
side questions though:
On Wed, 2017-07-19 at 10:13 +0200, Marek Hulán wrote:
> In general +1. I'm not sure if official policy changes anything,
> prob
On Mon, Aug 14, 2017 at 04:29:01AM -0700, ssht...@redhat.com wrote:
TL;DR: I have developed a way to scan any template and see if there are
suspicious/incorrect code patterns in them, so the templates will remain
valid even after foreman code changes.
Recently I have started to think about user
TL;DR: I have developed a way to scan any template and see if there are
suspicious/incorrect code patterns in them, so the templates will remain
valid even after foreman code changes.
Recently I have started to think about user created templates and foreman
upgrades.
When user upgrades foreman
