Every few weeks we host a Community Demo to showcase new & interesting developments from the Foreman community. We encourage participation from any member of the community (although you do need a Google account), so if you’ve been working on something cool, please do come to show it off.
This post is a wiki, so if you have something to show, add yourself to this table!
Expected In
We’ve added a new column to indicate the release in which community members might expect the feature that is being demoed to appear. This column should be taken as a guide rather than a gospel. Unforeseen circumstances might drag a feature out of a release or two. The best way to know for sure what is in a release is to check out the release announcement! 
If you have any feedback about the change to the format, feel free to comment here
Depending on where it would be a better fit, please add yourself to one of the following tables:
Foreman user-focused demos
| Speaker | Time | Topic | Redmine Issue | Expected in Version |
|---|---|---|---|---|
| @nofaralfasi | 5 mins | Introductions | ||
| @nofaralfasi | 5 mins | Community Demos: Topic Ideas and Contributor Participation | Community Demos: Topic Ideas and Contributor Participation | |
| @ladislavvasina1 | 5 min | All hosts Manage notifications - Feature presentation | Feature #39181: All hosts- Add action – Configure Notifications - Foreman | Foreman 3.19 |
| @aneta-petrova | 5 mins | Documentation updates: New procedures for MCP use cases | ||
| @iballou | 10 mins | New content credentials details page | 39197 | Katello 4.21 |
| @nofaralfasi | 2 mins | Fix hosts pagination when filtering by report origin | 39197 | Foreman 3.19 |
Foreman developer-focused demos
| Speaker | Time | Topic | Redmine issue | Expected in version |
|---|---|---|---|---|