|
|
| Line 1: |
Line 1: |
| This is the landing page for the '''Virtual FSweekend Hackathon 2021'''.
| | {{Hackathon |
|
| |
|
| Normally in mid-November a group of FlightGear enthusiasts participate in [[FSWeekend]] in [https://www.aviodrome.nl/ Aviodrome] at the [https://www.lelystadairport.nl/ Lelystad Airport] in the Netherlands. Over the years this has been a focal point for both finishing existing development/releases and a catalyst for new ideas in FlightGear, as well as an opportunity for FlightGear enthusiasts to share a beer. Like in 2020, FSweekend 2021 was unfortunately cancelled due to COVID-19 uncertainties (it will maybe take place in March 2022).
| | |year=2022 |
|
| |
|
| To keep the spirit alive and repeat the successful execution of the [[Virtual_FSweekend_Hackathon_2020|Virtual FSweekend Hackathon 2020]], we are planning to hold another Virtual FSweekend Hackathon on the weekend of 5/6/7 November 2021 (in {{days from now|2021|11|5}}).
| |
|
| |
|
| == Hackathon? ==
| | }} |
| {{Hackathon Intro}}
| |
| | |
| == Only Core Development? ==
| |
| While the core of the hackathon incl. support previously has been dedicated to development in the very core of FlightGear (mostly C++, [[Nasal_scripting_language|Nasal]] and xml), you are also welcome to participate if you are developing stuff, which contributes to the general FlightGear ecosystem (e.g. [[Addon]], visual artwork or [[Osm2city.py|osm2city]]). However, in that case you might need to provide your own support.
| |
| | |
| == Sign up ==
| |
| {{Note|There is space for many participants, so don't be shy. Rick is happy for people to register right up to the Friday night, but we will not be able to help out with getting builds and git working if you leave it that late!}}
| |
| | |
| To register your participation, please contact Rick either on the {{forum link|t=39793|text=forum post}}, by PM on the [https://discord.gg/rzuV2DR FlightGear Discord server] or via the [https://sourceforge.net/p/flightgear/mailman/message/37358418/ devel list].
| |
| | |
| Confirmed participants (in alphabetical particular order):
| |
| {| class="wikitable"
| |
| |-
| |
| ! Name
| |
| ! aka.
| |
| ! Role
| |
| ! Remarks
| |
| |-
| |
| |Fernando García Liñán
| |
| |{{Usr|Icecode}}
| |
| |Mentor (core dev)
| |
| |Can provide help regarding core development and graphics (OSG, [[Compositor]] and shaders)
| |
| |-
| |
| |Julian Smith
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=19719 cgdae]
| |
| |Mentor (core dev)
| |
| |Can help with thread-safe properties, recording/replay, [[CompositeViewer Support|CompositeViewer]], multiplayer
| |
| |-
| |
| |Lars Toenning
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=22241 Lars], LarsT on FG Discord
| |
| |Participant
| |
| |
| |
| |-
| |
| |Marc Eberhard
| |
| |
| |
| |Participant
| |
| |
| |
| |-
| |
| |
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=25958 MariuszXC], MariuszXC on FG Discord
| |
| |Participant
| |
| |
| |
| |-
| |
| |
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21618 merspieler]
| |
| |Participant/Infrastructure
| |
| |Hit me up if you've got trouble with mattermost or jitsi.
| |
| |-
| |
| |Pat Callahan
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=14816 callahanp]
| |
| |Participant
| |
| |
| |
| |-
| |
| |Rick Gruber-Riemer
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9140 vanosten], HB-VANO on FG Discord
| |
| |Organiser/mentor
| |
| |Can coach osm2city and OSM data processing
| |
| |-
| |
| |Roman Ludwicki
| |
| |PlayeRom on FG Discord
| |
| |Participant
| |
| |-
| |
| |
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=26150 SDeAstis]
| |
| |Participant
| |
| |
| |
| |-
| |
| |Stuart Buchanan
| |
| |[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9 stuart]
| |
| |Mentor (core dev)
| |
| |As well as WS3.0, he can provide advices on a wide range of the codebase, as he has touched lots of different parts over the years
| |
| |}
| |
| | |
| == Ahead of the Hackathon ==
| |
| | |
| {{Hackathon Preparations|year=2021}}
| |
| | |
| == Schedule ==
| |
| With (hopefully) a world-wide group of participants, and varying real life constraints, at any given time over the weekend there will hopefully be a couple of people active.
| |
| | |
| We will have two big get-togethers:
| |
| | |
| === Friday 5th November 2000-2200 UTC. Kick-off ===
| |
| * General welcome
| |
| * Introductions
| |
| * Hack pitches
| |
| * Team formation
| |
| | |
| This is the point at which participants will decide, which Hacks they want to work on. The sponsors of each of the Hacks proposed ahead of time will be invited to give a 5 minutes pitch to the group, with some questions from the audience. Slides/screenshots optional.
| |
| | |
| After all the Hacks have been pitched, we will have a little break for people to chat and work out which Hack they want to work on.
| |
| | |
| If a Hack ends up with fewer than 2 people wanting to work on it (including the sponsor), then it will normally be dropped. This is to encourage people to work in groups - larger teams can get more done in the time, and have more opportunities to learn from each other, plus it is more sociable!
| |
| | |
| === Sunday 7th November 2000-2200 UTC. Wrap up and demos ===
| |
| At the end of the hackathon we will have a get together and have each team present the results of their hack.
| |
| | |
| Depending on the number of hacks, each team will have 5-15 minutes to demonstrate their hack, describe what they have learned, and what their next steps are.
| |
| | |
| We will finish with voting for the best hack of the weekend.
| |
| | |
| == FAQ ==
| |
| {{Hackathon FAQ}}
| |
| | |
| == References ==
| |
| {{Appendix}}
| |
| | |
| [[Category:Hackathon Materials]]
| |
| [[Category:Hackathons]]
| |