Over a week ago, @lzap published an RFC about removing the term blacklist from Foreman templates. A short discussion about this took place on the related Pull Request. With a wider discussion taking place in the tech, open source, and academic worlds (please see Further Information at the bottom of this post for some links), the community management team wants to take a moment to outline our thoughts on this in the context of the Foreman community. While normally RFCs and PRs go through a longer process, we think it is important to address this specific RFC and outline some action items.
The upstream versions of the Foreman and Katello projects become, among other downstream projects, the Atix’s Orcarhino and the Red Hat Satellite of tomorrow. The discussions and contributions that take place in the vibrant upstream community shape the code base. The code base begins upstream and moves downstream. Until now, the Satellite documentation did not follow the same journey. In this blog, I will outline what has been happening with Satellite documentation over the last year and how this benefits both the Foreman community and Red Hat Satellite users.
You’ve probably heard already me talking about how you can automate Foreman using Ansible and our Foreman Ansible Modules. And if you did, I have great news for you: we just released v1.0.0 - the first officially stable release!