There are technical requirements: https://github.com/FOSDEM/stands-website (basically it uses Hugo just like our main site, and we provide only the content, the style will use FOSDEM branding).
As is usually the case with FOSDEM, we get provided the infrastructure (usually a table to put your things on, a wifi network and a power plug; this year an empty website and chartoom) and what we make of it is up to us.
Here is the email they sent us:
Congratulations on your stand at FOSDEM 2021. Now the “real” work starts
We realise we left you very little time to prepare, and we apologise for it; FOSDEM 2021 is a new experience and our tried-and-tested recipes don’t work as well in the virtual world.
Nevertheless, to recap what we already stated, this is certainly what you will get from us:
I’ll explain in reverse order.
You’ll get a chatroom at chat.fosdem.org (with a lot of help from the amazing Matrix people) for your stand, to manage as you wish. We propose that you create some kind of schedule (can be public, can be private) of when an interesting person will be at your stand, so interested visitors can have a chat.
We’ll make sure your primary stands page links to the chatroom.
In a way that still has to be developed (or at least worked out), you’ll be able to upload (or rsync/sftp) some prerecorded video’s (showcases, interviews, demo’s, etc.) to a folder under video.fosdem.org.
We’ll also make sure that there is a link from the stands page.
There will be a website called stands.fosdem.org which will list under /stands/ all stands at FOSDEM 2021; organised per theme. Each “stand” has a primary (index) page with some generated content. All other pages are up to you: you can put everything on the primary page, create subpages or do something else. The website is generated with Hugo, and every stand is a directory (with _index.md) under content/stands. Your pages are thus content pages (HTML and MD), which means you don’t have to care about how it looks (we’ll put it in the FOSDEM theme) or how it exactly is configured; we deal with all that.
You can add static content (images, etc.) to be used on your pages.
We’ll fetch all your content once per hour (when the site is up - sometime next week) with git. Therefore, in the acceptance mail, we asked you to provide us with two git repositories; one for the content files (you don’t have to provide the rest of the Hugo scaffolding) and one for the static files. Make sure we can pull without authentication.
As soon as the site is up, well provide you with the link so you can check how everything will look. You can also clone our git repo and check for yourself (see the Hugo documentation for more details on how - the command is hugo serve).
I think the idea is to give the following information:
- A short overview of what is Haiku, covering the frequently asked questions: our goal is writing a modern and well-integrated desktop operating system, we have a BeOS compatibility layer, etc.
- A “what’s new since last year” (can be based on the beta2 release notes) and maybe “what’s coming up next”
- A “get involved”/“how to help” page as well as a way to submit donations (this is an event mostly targetted to people already well into the free software thing, mostly developers)
- Usually we also give a demo of Haiku showing (I think this would be best done as a video in this year format):
- extended attributes: live queries (editing a people file and showing how tracker immediately adds or removes it from search result), stored queries, how to use a stored query as a MediaPlayer playlist, querying for bookmarks (possibly including a mention of Googlefs showing how this could in theory extend to files that are on the web)
- Media support: running multiple MediaPlayer instances, showing Cortex with all the media nodes, maybe using that demo where you can have multiple videos coming from different apps shown on a spinnnig cube, sometimes I also added a MIDI keyboard. This year I guess we would instead showcase Medo?
- User interface: stack and tile, “X-Ray menus” showing how you can right click a directory in Tracker and easily navigate inside it, worskpaces,…