Template:Hackathon Preparations

From FlightGear wiki
Jump to navigation Jump to search

There are a couple of key activities ahead of the weekend in 2020.

Getting started

So we can hit the ground running, we really want everyone participating to already have:

  • SourceForge credentials
  • A working build environment with OSG, PLIB etc.
  • A Git checkout of simgear/flightgear (cf. FlightGear_Git)
  • A Git checkout of fgdata
  • Some experience with Git :)

At the very least you should be able to work with a nightly version of FlightGear.

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 being put into the dedicated Hackathon Materials category.

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

Being completely remote, we need the ability to collaborate in teams as well as video conference as a group.

There will be a Mattermost server for the weekend. We'll be using that for organization, discussion and collaboration.

We'll be using a Jitsi Server for video conferencing and demos.

To use the server, please start the Jitsi calls from within Mattermost (click on that power plug symbol in the top bar next to the search). Preferably use an app or Chrome/Chromium.

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.

Check out the Hackathon no year Ideas category page for a how-to as well as links to existing proposals.

You can also take a look at proposals from the previous year.

Not having 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 the start of the Hackathon on Friday evening.

Materials

No description.

Template parameters

ParameterDescriptionTypeStatus
Yearyear

year of the hackathon

Default
2020
Example
year=2021
Auto value
2021
Numbersuggested