Development   RFCs


Topic Replies Activity
About the RFCs category 2 January 16, 2019
RFC: Storing reported data / Compute Resource Data as source for facts 8 October 15, 2019
Upcoming changes to Dynflow 21 October 10, 2019
RFC: Moving Foreman Proxy, Installer and NodeJS to SCLs 10 October 7, 2019
Client repository for Debian / Ubuntu 5 October 2, 2019
RFC: Optimized reports storage 13 September 30, 2019
RFC: Changing how we handle Webpack Building 90 September 26, 2019
Deprecating katello-remove 8 September 3, 2019
Sunsetting foreman_cockpit 4 September 3, 2019
Modularizing Foreman - High-level features 12 August 11, 2019
RFC: Dropping support for MySQL 18 July 29, 2019
Changing the default from static to dynamic query for REX 2 July 22, 2019
Defaulting Puppet to off in the Katello Scenario 6 July 17, 2019
Foreman Landfill (aka "tools" or "extras") repository 6 July 10, 2019
Move GCE to a plugin 15 June 12, 2019
Ansible implementation switch to ansible-runner 8 June 4, 2019
Drop "stable" link in Deb repos 7 May 15, 2019
Presenter pattern to abstract Compute Resources UI 3 May 6, 2019
Provisioning Templates / Testing & Separate Repository 11 April 30, 2019
Clicks, Clicks Everywhere 3 April 23, 2019
Redesigning the javascript stack 5 April 21, 2019
Testing more plugins together regularly 8 April 11, 2019
RFC: Deprecate foreman-debug in favor of sosreport 13 April 3, 2019
Rethinking host groups 18 March 22, 2019
RFC: Add puma as the default smart-proxy server 37 March 19, 2019
Dropping ARM packages 10 March 15, 2019
Dropping Puppet 4 support in our installer 7 March 13, 2019
RFC: Expandable Component Architecture 20 March 10, 2019
RFC: Make Foreman easy to deploy and maintain 16 February 20, 2019
Consolidating The Console 29 February 19, 2019