Re: [foreman-dev] Propsing a move from Google Groups to Discourse

That's indeed one of my aims. One common piece of Discourse wisdom is not to have too many categories, so I don't for see one per plugin - but the system also has tags which would work well in the Support category (I.e. foreman-users) A category for Infra might well make sense separate from dev

Re: [foreman-dev] Propsing a move from Google Groups to Discourse

I skimmed the site over, played with configuration, clicked and tried to play with various part of it. There are parts I'll have to get used to, and there are parts I wish were done slightly different but overall I like the advanced power behind it. Thinking a loud, it seems like this might allow

Re: [foreman-dev] Merge permission for theforemen/foreman-ansible-modules

+1 from me as well (I'll aim to add you in the requisite 5 more days depending on the further outcome) On Wed, Nov 1, 2017 at 3:24 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > +1 while I haven't looked at his ansible work that closely I have seen > that he's already

Re: [foreman-dev] Propsing a move from Google Groups to Discourse

The site will be made public if/when we go live with it. I assume Google will index it then, I don't think it does any robots.txt stuff - certainly I'm using google to look up configuration questions on meta.discourse.org :) -- Sent from my Android device with K-9 Mail. Please excuse my

Re: [foreman-dev] Merge permission for theforemen/foreman-ansible-modules

+1 while I haven't looked at his ansible work that closely I have seen that he's already behaving like an excellent maintainer: good reviews, active and generally a good and friendly person to have around. On Mon, Oct 30, 2017 at 11:46:34AM -0400, Andrew Kofink wrote: +1 from me! We have

Re: [foreman-dev] Propsing a move from Google Groups to Discourse

I admit, I skimmed the prior emails (they were tl). I just wanted to ask if discourse is searchable/is indexed from the wider internet. I've often found relevant mailing list discussions by searching from Google, and I really value that. - Andrew On Wed, Nov 1, 2017 at 12:04 PM, Greg Sutcliffe

[foreman-dev] Building a Rails 5.1 SCL

In a previous thread [1], we discussed building an SCL vs. vendorizing gems and the general consensus was to build an SCL. This thread is to outline a starting plan for how to build and maintain a Rails 5.1 SCL. I invite and appreciate comments towards this design. I'll begin by laying out some

Re: [foreman-dev] Propsing a move from Google Groups to Discourse

One more point, we're currently on a free tier of our SMTP provider, which is limited to 6k emails / month & 200 mails / day. I'm seeing if I can negotiate a free higher tier for a FOSS project, but for now, go easy on the mail testing :D Greg -- You received this message because you are

Re: [foreman-dev] Propsing a move from Google Groups to Discourse

OK, some questions I expect to come up: * Will the mailing list import be kept up to date? Yes, I plan to update it every day or two. Happily it's incremental (no 7 hour import) but sadly it's not something that's easy to automate. It's also why I've not renamed the categories yet, or fixed

Re: [foreman-dev] Foreman instrumenting analysis

> Does Prometheus only not work in a multi-process Rails web server? Does it > work for a single process multi-threaded web server? This is an interesting > roadblock given you'd expect this to affect lots of webserver across > multiple languages out there. Any Rails app that has multiple

[foreman-dev] Propsing a move from Google Groups to Discourse

Hi all, As ever from me, this is long. Sorry about that, it's a habit. Here's the TL;DR: * What: move Google Groups -> Discourse * Why: https://blog.discourse.org/category/use-cases/ * Can I try? - Scroll to the end for login details So, as some of you know, I'm a big fan of the Discourse[1]

Re: [foreman-dev] Foreman instrumenting analysis

On Wed, Nov 1, 2017 at 3:51 AM, Lukas Zapletal wrote: > Statsd can be configured for remote transport, meaning that the > collecting agent (or aggregating process if you like) can run on > remote server (or container). It is recommended to run it either on > localhost or at

Re: [foreman-dev] Merge permissions for Katello/katello

At last! Thanks Justin. On Tuesday, October 31, 2017 at 9:48:03 PM UTC-4, Justin Sherrill wrote: > > Given its been a number of days with no -1's, I've now granted you access! > > Congrats! > > Justin > > On Tue, Oct 31, 2017 at 9:37 PM, Eric D Helms > wrote: > >> +1 >> >>

Re: [foreman-dev] FactoryGirl renamed to FactoryBot - plugin maintainer action needed

On středa 1. listopadu 2017 10:19:08 CET Tomer Brisker wrote: > Hello, > This has now been merged in Foreman core. > All plugins should make sure that their respective PRs pass tests and > merge them now. If you need assistance making this change in your > plugin, please reach out to us and we

Re: [foreman-dev] Merge Permissions for Katello/katello

Thanks everyone! On Tue, Oct 31, 2017 at 9:47 PM, Justin Sherrill wrote: > Given its been a number of days with no -1's, I've now granted you access! > > Congrats! > > Justin > > On Tue, Oct 31, 2017 at 9:36 PM, Eric D Helms > wrote: > >> +1 >> >>

Re: [foreman-dev] FactoryGirl renamed to FactoryBot - plugin maintainer action needed

Hello, This has now been merged in Foreman core. All plugins should make sure that their respective PRs pass tests and merge them now. If you need assistance making this change in your plugin, please reach out to us and we would be happy to help. Keep in mind that any PRs that include test

Re: [foreman-dev] Foreman instrumenting analysis

Statsd can be configured for remote transport, meaning that the collecting agent (or aggregating process if you like) can run on remote server (or container). It is recommended to run it either on localhost or at least LAN, it is not a good idea to route the UDP packets through complex