From Fedora Project Wiki
(→Event Report: Picture of our Booth) |
|||
| Line 53: | Line 53: | ||
---- | ---- | ||
[[Category:Events]] | [[Category:Events]] | ||
[[File:OpenRheinRuhr2017.jpg|200px|Picture of our Booth]] | |||
Revision as of 17:45, 6 November 2017
OpenRheinRuhr 2017
Dates/Location
- Saturday and Sunday, the 4th and 5th of November 2017
- Rheinisches Industriemuseum, Oberhausen in NRW, Germany OpenStreetMap
- About 900 visitors according to organizer's count after the event.
Event Description
OpenRheinRuhr is a free software trade show with conference and exhibition in the Rhine-Ruhr region, the largest metropolitan area in Germany. For more information please visit the OpenRheinRuhr website (German).
Event Owners
Fedora Representatives
- Raphael Groner
- Till Maas (On Saturday)
- Silvia Sanchez
Event Schedule
Booth staffing was handled ad hoc, there were no Fedora talks.
Ideas/Brainstorming
- Just show a little bit of presence
- Maybe provide writing Fedora images to USB drives
- Maybe show Fedora on a notebook
Important Deadlines
- 15 Octobre 2017: Deadline for participation (registering booths and proposing contributions)
Ideas for Talks
Raphael Groner maybe something about Python3+Java in Fedora, progress report about my new project PyVxml if wished.
Tickets
Event Budget
Fedora sponsored an uncounted amount of swag.
Travel Subsidy Requests
None /TBD
Event Report
Event Report
Please use this section to document and report about the event. Nice things to see in this section are blog posts about the event, pictures from the event, and anything else that might be valuable to showing the success of our participation in the event. If there were any "lessons learned" or problems that others might benefit from seeing please do include those here too. Some general information about report expectations can be found on the Event Reports page.
Please use this section to document and report about the event. Nice things to see in this section are blog posts about the event, pictures from the event, and anything else that might be valuable to showing the success of our participation in the event. If there were any "lessons learned" or problems that others might benefit from seeing please do include those here too. Some general information about report expectations can be found on the Event Reports page.
