[foreman-dev] Prprocessor Moved
All, The prprocessor has been moved off of Openshift V2 onto the same box that contains our Redmine instance and now has a permanent DNS. All repositories that used the prprocessor have been updated. The new site is: http://prprocessor.theforeman.org/status If you encounter any issues, such as not seeing labels or theforeman bot commenting on pull requests please let us know here so that we can investigate. -- 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.
[foreman-dev] [Event] Foreman Community Demo Items - Thu 04 Jan 3pm [BST]
First demo of 2018! I'm sending an early reminder before the holidays so everyone has time to plan ahead and add to the agenda. As always, have a think for items which have been completed since the last demo on 2017-12-07. There is a query that will show you items completed (i.e. marked as closed) since the last demo [2]. Please add demo items following the instructions on the agenda page [3]. If you can't be present but have something to show, add it to the agenda and let me know - I'll be happy to talk about the feature in your absence. Please do leave me enough time to familiarize myself with the content though :) [1] https://www.youtube.com/watch?v=BVTiwSEMcyw [2] http://tinyurl.com/ycpqnew3 [3] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information -- Ori IRC: orabin -- 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] Introducing #theforeman-dev-ui, an experiment
On Sat, Dec 16, 2017 at 2:38 AM, Greg Sutcliffe wrote: > On 14/12/17 16:04, Walden Raines wrote: > > The UX team is playing with the idea of forking UI discussions out > > into a separate channel. We will do a month long experiment and see > > how it goes. > > > > *Background:* The irc channel #theforeman-dev is very busy and > > there are often times multiple conversations taking place > > simultaneously. > > Whilst I'm generally against fragmentation of similar discussion types > (i.e dev chat in this case), I can see why you want to test this out. > Will be interested in seeing your results. > > BTW I can add it to the Matrix Foreman community if you OP me on the > channel. > ping me on the channel once you logged in and I'll op you. > > > *Hypothesis:* By using the irc channel #theforeman-dev-ui > > conversations will be more relevant to those who are concerned > > mainly with UI topics. Having a smaller channel will also facilitate > > more conversation because of this focus. > > Facilitate, yes. Also could potentially exclude people too, especially > if they don't see this thread. If this channel persists after your poll, > please do send PRs to the website etc so that *new* people to the chat > community know where to find discussions. > > Greg > > -- > 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: Re: [foreman-dev] Proposal: Let's make notifications optional
On 12/20, Walden Raines wrote: > I also added an item to the Team UX backlog to make the notifications use > websockets (or similar) instead of the polling. The polling annoys me as > well. Definitely the way to go, I've been experimenting with ActionCable and it's not only cleaner (way less code, check out our polling code) but more efficient. https://github.com/dlobatog/foreman/tree/actioncable The biggest limitation is https://github.com/phusion/passenger/issues/1202 - which I'm able to circumvent with mod_proxy_wstunnel, http://anycable.io/ as Ohad mentioned on IRC the other day looks like a feasible suggestion (if a bit more involved) > > Cheers, > Walden > > On Wed, Dec 20, 2017 at 5:02 AM, Tomas Strachota > wrote: > > > On Wed, Dec 20, 2017 at 9:09 AM, Ohad Levy wrote: > > > > > > > > > On Wed, Dec 20, 2017 at 10:07 AM, Lukas Zapletal > > wrote: > > >> > > >> Hello, > > >> > > >> while I agree that notifications is useful feature to our users, its > > >> one second polling mechanism is killing me during development, it > > >> makes watching logs or debugging sessions a nightmare. > > >> > > >> I propose an Administer - Setting option to completely turn it off - > > >> no notification bell icon, no polling. If there is someone who things > > >> users should not be given this option, let's make this an > > >> environmental variable. > > >> > > >> Opinions? > > > > > > 1. a Global setting, followed by a user setting sounds sane to me. > > > 2. do you know that there is a global env already? just run: > > > > > > NOTIFICATIONS_POLLING=100 foreman start > > > > Great, I didn't know that. > > > > Polling annoys me in development as well, but this env variable is > > enough for me. Thanks! > > > > > > > >> > > >> -- > > >> Later, > > >> Lukas @lzap Zapletal > > >> > > >> -- > > >> 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. > > > > -- > 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. -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=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. signature.asc Description: PGP signature