Happily, we haven’t really had to change any of our practices - we were already pretty good at respecting our community! The only notable change is that we have enabled the IP anonymization in Google Analytics, which really should have been done earlier. The rest is all aggregate statistics and public data (such as forum posts, bug reports, and git commits).
If you do have any concerns, you are welcome to reach out to me to discuss them. We’ll be keeping the policy updated in the future, and significant changes will be notified in the Announcements list and here.
Foreman at OpenSourceCamp.de
In just 2 weeks, Foreman will be taking part in the OpenSourceCamp.de event. We’re teaming up with Graylog to bring you a day of infrastructure management talks, and it’s right after OSDC so you can get two conferences for your travel budget! We’ve got a great speaker line-up for you, and a booth where you can come chat with us in the breaks. See you there!
Foreman 1.17.1 released
Just 2 days ago Ondřej released 1.17.1 containing a bunch of important fixes for issues found in the 1.17 release. Packages are out, so get your upgrade hat on!
You can find details on the bugs fixed in the release announcement, and thank you to everyone that reported the issues and worked on the fixes. As always bugs can be reported on issue tracker - thanks!
Katello 3.5.2 is out
The next release in the Katello 3.5 stream was released earlier this month, containing 20 fixes in Katello alone, and more in subpackages. This is suitable for Foreman 1.16, and you can check the announcement for more details. As ever, many thanks to those who contributed to the release, and further reports of bugs is always appreciated.
Plugin Maintainers wanted!
Many of our plugins suffer compatibility issues and/or changes in the projects they integrate with over time - when Foreman changes, or (for example) Salt released a new version, plugins can be affected. Sadly, several plugins hit by this have not been maintained, and are now facing being retired from the plugin repository.
If you’re interesting in helping contribute to the community by helping to fix a plugin you rely on, please get in touch! Currently we’d love some help with:
RFCs needing attention
I’m going to start highlighting open RFCs that might benefit from more eyeballs. Here’s this month’s selection:
The Foreman Community has now fully embraced Discourse as the source of its
event data - if you’ve been using the old
/events/all.ics in your own
calendar, you’ll need to head over to the forum
calendar and hit the Subscribe
button (which will give you an ICS link). You can also use the Add To Calendar
on specific events if you don’t wish to import the whole thing.
Future community demos will now be created much further in advance, so you should be able to keep up with upcoming demos there (currently I’ve created topics out to August :P)
This was largely an event roundup from Red Hat Summit & RossConf, and a discussion of potential future work on community stuff from me.
John Mitsch gave us a look at how to start developing on foreman-maintain.
- foreman_expire_hosts updated to 5.1.0
- foreman_xen updated to 0.6.1
- foreman_remote_executionto 1.5.2
- foreman_salt updated to 10.0.0
- foreman_bootdisk updated to 12.0.0
- foreman_snapshot_management updated to 1.5.0
- foreman_column_view updated to 0.4.0
- foreman_templates updated to 6.0.1
- foreman_ansible updated to 2.1.2
- foreman_virt_who_configure updated to 0.2.1
- foreman_default_hostgroup updated to 5.0.0
- smart_proxy_ansible updated to 2.0.3
- smart_proxy_salt updated to 2.1.9
- hammer_cli updated to 0.13.0
- hammer_cli_csv updated to 2.3.1
- smart_proxy_dhcp_device42 now has DEBs
- foreman_snapshot (unmaintained)
- foreman_param_lookup (unmaintained)
- foreman_reserve (unmaintained)
Thanks to everyone who contributes to the Foreman community - patches, plugins, testing, bug reports, translations, interviews, presentations, meetups and everything else. Your efforts are very much appreciated!