Virtual FSweekend Hackathon 2020: Difference between revisions

Jump to navigation Jump to search
(+ References section)
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This is the landing page for the '''Virtual FSWeekend Hackathon 2020'''.
This is the landing page for the '''Virtual FSweekend Hackathon 2020'''.


Normally in mid-November a group of FlightGear enthusiasts participate in FSWeekend at 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.  FSWeekend 2020 was cancelled, so to keep the spirit alive, we are planning to hold a Virtual FSWeekend Hackathon on the weekend of 14/15 November.
Normally in mid-November a group of FlightGear enthusiasts participate in FSweekend at 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.  FSweekend 2020 was cancelled, so to keep the spirit alive, we are planning to hold a Virtual FSweekend Hackathon on the weekend of 14/15 November.


== Hackathon? ==
== Hackathon? ==
For those who have not participated in a hackathon before, the broad idea is to get people from a wide variety of experience and backgrounds together to solve problems over a short period of time - typically 24 or 48 hours. Details vary, but typically at the start of the event, people pitch ideas and groups form organically based on what people are interested in. The groups then work together intensively, often fueled by pizza and caffeine etc. At the end of the hackathon the groups present their work and there are often prizes for the best hacks.
For those who have not participated in a hackathon before, the broad idea is to get people from a wide variety of experience and backgrounds together to solve problems over a short period of time - typically 24 or 48 hours. Details vary, but typically at the start of the event, people pitch ideas and groups form organically based on what people are interested in. The groups then work together intensively, often fueled by pizza and caffeine etc. At the end of the hackathon the groups present their work and there are often prizes for the best hacks.


The idea of the virtual FSWeekend hackathon would be to encourage existing and new contributors to collaborate over the course of the weekend to create new and exciting features for FlightGear in the broadest sense. James and I would particularly like to use it as an opportunity to encourage people to get their hands dirty in the core code, so we will be primarily there to help people rather than hacking ourselves, but anything is possible :)
The idea of the virtual FSweekend hackathon would be to encourage existing and new contributors to collaborate over the course of the weekend to create new and exciting features for FlightGear in the broadest sense. James and I would particularly like to use it as an opportunity to encourage people to get their hands dirty in the core code, so we will be primarily there to help people rather than hacking ourselves, but anything is possible :)


No prior development experience is necessary - we will try to run some education sessions ahead of the weekend so people can hit the ground running. Also, do not feel you have to commit to coding the entire weekend to the exclusion of all else. I think participants will still get real value if they can just commit to one day and some late evenings.  
No prior development experience is necessary - we will try to run some education sessions ahead of the weekend so people can hit the ground running. Also, do not feel you have to commit to coding the entire weekend to the exclusion of all else. I think participants will still get real value if they can just commit to one day and some late evenings.  


== Sign up ==
== Sign up ==
{{Note|If you've not received Stuart's mail but are interested in taking part please drop him an email. While we now have 15 participants registered, there still
{{Note|If you've not received Stuart's mail but are interested in taking part please drop him an email. While we now have 20 participants registered, there still is space for plenty more, so don't be shy. Stuart 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!<ref>https://sourceforge.net/p/flightgear/mailman/message/37129832/</ref>}}
space for plenty more, so don't be shy. Stuart 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!<ref>https://sourceforge.net/p/flightgear/mailman/message/37129832/</ref>}}


To register your participation, please contact Stuart either on the {{forum link|t=38071|text=forum post}}, or via the [https://sourceforge.net/p/flightgear/mailman/message/37125347/ -devel list].   
To register your participation, please contact Stuart either on the {{forum link|t=38071|text=forum post}}, or via the [https://sourceforge.net/p/flightgear/mailman/message/37125347/ -devel list].   
Line 29: Line 28:
* Isaak Dieleman
* Isaak Dieleman
* Michael Filhol
* Michael Filhol
* Nik Brucker
* Patrick Trottier
* Patrick Trottier
* Mark Joseph
* Mark Joseph
* CaptB
* CaptB
* Brendan Black
* Guenter Alzinger
* Chris Frey
* Bertrand Coconnier


== Ahead of the Hackathon ==
== Ahead of the Hackathon ==
Line 55: Line 59:
Being completely remote, we need the ability to collaborate in teams as well as video conference as a group.
Being completely remote, we need the ability to collaborate in teams as well as video conference as a group.


We will try to have some sort of video conference running permanently for people to drop into, as well as some collaboration tool that can be used both by individual teams as well as the whole group for general support.
Merspieler has set up a mattermost server for the weekend.  We'll be using that for organization, discussion and collaboration.
 
We'll be using a private Jitsi Server sponsored by [https://ellyserver.de Uniki] for video conferencing and demos.
 
To use the server, plase start the Jitsi calls from within mattermost (click on that power plug symbol in the top bar next to the search).


=== Ideation ===
=== Ideation ===
The core of the Hackathon!  These are the projects, idea and problems that participants will be working on during the weekend.  In the weeks before the hackathon itself, participants can, and should, propose things to work on.  Simply create a wiki page describing your idea, and encourage people to contribute and get interested.
The core of the Hackathon!  These are the projects, idea and problems that participants will be working on during the weekend.  In the weeks before the hackathon itself, participants can, and should, propose things to work on.  Simply create a wiki page describing your idea, and encourage people to contribute and get interested.


Simply use the {{tl|Hackathon Proposal}} template and your idea will magically appear on the [[:Category:Hackathon_2020_Ideas|Hackathon_2020_Ideas]] category page.  
Simply use the {{tl|Hackathon Proposal}} template and your idea will magically appear on the [[:Category:Hackathon 2020 Ideas|Hackathon 2020 Ideas]] category page.  


Not got an idea?  No problem!  Have a look at the ideas above, leave a comment on the Discussion page, and add yourself as an Interested Party for those you might consider working on during the Hackathon.  There is no commitment until Friday evening.
Not got an idea?  No problem!  Have a look at the ideas above, leave a comment on the Discussion page, and add yourself as an Interested Party for those you might consider working on during the Hackathon.  There is no commitment until Friday evening.

Navigation menu