Call for do-a-thon proposals for Aarhus-2019 workshop

The do-a-thon concept was a great success at the Zurich workshop, so this year we are going to continue the format and spice it up a bit: the coordinators of the do-a-thons that receive the most positive votes in the forum get direct access to the workshop.

What: As to what do-a-thons are, and what they could be, I quote from @timtroendle and @stefan.pfenninger :

  • Hackathons, write-a-thons, or document-a-thons, are obvious examples of do-a-thons.
  • But why not a teach-a-thon? While we are not organising a separate tutorial day this time, you might want to teach a method or a visualisation tool to others.
  • If you were thinking of giving a talk, but don’t want to present it as a poster, perhaps you could turn it into an interactive discuss-a-thon to take your ideas and jointly develop them further?
  • How about closing some Pyomo issues?
  • How about drafting a position paper?
  • How about prototyping a tool?
  • How about creating an energy specific Software-Carpentry-style lesson?
  • How about polishing and redistributing a certain dataset?

How to propose a do-a-thon: open a new topic and tag it with “do-a-thon” and “aarhus-2019” so it can be easily found.

Concrete outputs: per @tom_brown’s suggestion, in your proposal please specify what the expected outputs are. It could be a list of models discussed, a list of sources for certain data, everybody learns how to use your library or a best-practice guideline.

How to vote: Click the “Like” botton of the proposal.

How many votes does one do-a-thon need to make it happen:
We aim to keep the do-a-thon sessions small to be effective, which means a high number of do-a-thons will be accepted. When the deadline comes, the ones with the most votes will be selected to fill the rooms and time slots.

Deadline for proposals: March 1st (preliminary).

List of proposed do-a-thons: Do-a-thon list, or search for “do-a-thon” and “aarhus-2019”.

Contact: PM @Hailiang_Liu


It might be worth requiring that people specify concrete “outputs” for their do-a-thons e.g.

  • a wiki guideline
  • everybody learns Python
  • position paper
  • a prototype for a new tool

Otherwise everyone will just chat and enjoy themselves too much :grinning:. Workshop means work! :sweat:

Text and images licensed under CC BY 4.0Data licensed under CC0 1.0Code licensed under MITSite terms of serviceOpenmod mailing list.