Virtual FSweekend Hackathon 2020: Difference between revisions

Jump to navigation Jump to search
(8 intermediate revisions by 2 users not shown)
Line 12: Line 12:
=Sign up=
=Sign up=


To register your participation, please contact Stuart either on the forum post, or via the -devel list.  You can also list your attendance here.
To register your participation, please contact Stuart either on the forum post, or via the -devel list.   


Confirmed participants (in no particular order):
Confirmed participants (in no particular order):
Line 25: Line 25:
* Henning Stahlke
* Henning Stahlke
* Pat Callahan
* Pat Callahan
* Isaak Dieleman


=Ahead of the Hackathon=
=Ahead of the Hackathon=
Line 39: Line 40:


James and Stuart will pull together (and improve) the wiki resources to make this easier.
James and Stuart will pull together (and improve) the wiki resources to make this easier.
Ideally, we would have a couple of weeks upfront to identify articles that would be useful to provide rough guidance, either to update these or rewrite/merge them with other articles.
Candidate articles are currently being put into a dedicated [[:Category:Hackathon Materials]]
If we can agree on a set of articles that seem useful (to walk people through the process of patching FlightGear to add self-contained functionality), it might make sense to reach out to the community to help with reviewing/proof-reading and possibly translate such articles. Also, encouraging people to contribute artworks might be a good idea (screen shots, images, diagrams/drawings etc).


==Logistics==
==Logistics==
Line 46: Line 52:


==Ideation==
==Ideation==
The core of the Hackathon!  Ideas of what you want to work on.  The aim here is to pitch your idea to the group, and hopefully encourage people to work with you on it.
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 [[Template:Hackathon Proposal]] and your idea will appear magically in the category page linked below:
 
[[:Category:Hackathon_2020_Ideas]]
 
Not got an idea?  No problem!  Have a look at the ideas above, comment in the Discussion section, and add yourself as an Interested Party for those you might consider working on during the Hackathon.  There's no commitment until Friday evening.


== Materials ==
== Materials ==
Line 58: Line 70:
==Friday 13th November 2000-2200 UTC.  Kick-off==
==Friday 13th November 2000-2200 UTC.  Kick-off==


General welcome, introductions and team formation.
* General welcome
* Introductions
* Hack pitches
* Team formation


Participants with ideas can give a 5 minute pitch to the group to recruit people to their teamAt the end of the pitches, people can decide which team they want to join/formTo gain maximum benefit, it's best to be in a team of at least two :).
This is the point at which participants will decide which Hacks they want to work on.  The sponsors of each of the Hacks proposed head of time will be invited to give a 5 minutes pitch to the group, with some questions from the audienceSlides/screenshots optional.
 
After all the Hacks have been pitched, we'll 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 droppedThis 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's more sociable!


==Sunday 15th November 2000-2200 UTC.  Wrap-up and demos==
==Sunday 15th November 2000-2200 UTC.  Wrap-up and demos==


At the end of the hackathon we'll have a get together and have each team present the results of their hack.  Hopefully in the form of a working demo. We may have some voting for the best hack.
At the end of the hackathon we'll 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've learned, and what their next steps are.
 
We'll finish with voting for the best hack of the weekend.


=FAQ=
=FAQ=

Navigation menu