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 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 gospel. Unforeseen circumstances might drag a feature out 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 |
|---|---|---|---|---|
| @upadhyeammit | 5 mins | Introductions | ||
| @jeremylenz | 5 mins | New host details - ‘System purpose’ card | 35078 | Katello 4.6 |
| @atazhiba | 5 mins | Clearing the search link and standardizing CV empty states | 35027 & 34472 | Katello 4.6 |
| @nofaralfasi | 3 mins | Adding validation for root_pass on provisioning settings | 32925 | Foreman 3.4 |
| @iballou | 3 min | Alternate Content Source Refresh cron job | 34898 | Katello 4.6 |
| @partha | 10 min | Syncable yum-format repository exports | 34861 | Katello 4.6 |
Foreman developer-focused demos
| Speaker | Time | Topic | Redmine issue | Expected in version |
|---|---|---|---|---|
| @nofaralfasi | 5 mins | Adding a development installation guide for Foreman | 35160 | Foreman 3.4 |