Skip to content

Hackathon (Sep. 2017)

Jump to bottom
Jonathan Schmidt edited this page Aug 24, 2017 · 19 revisions

Template: https://wiki.autodesk.com/display/MELearn/Hackathon+Organization+Kit

(TODO SEB) The event at a Glance section in which you will define:

https://wiki.autodesk.com/pages/viewpage.action?pageId=332940392

Event Stingray Interactive hackathon – for M&E

Overview Through this hackathon, participants will get exposure to Stingray’s interactive framework/engine and will learn about the complete pipeline of developing components and plugins, and making them available to users through our store.

Audience Shotgun, Forge, Stringray, Maya and anyone else interested – this is opened to all (note that a rerun of this hackathon will be done in January after AU, for the Live/3dsmax teams)

Length 2 days – Sept 12-13

Location Montreal

Remote participation allowed? Yes

Subject matter experts Sebastien Phaneuf, Jonathan Schmidt, and perhaps a few more, tbd.

Preferred Team size 4 To be formed between Sept 7-11

Important dates and events

Aug 23-24: announce & registration opens Aug 31: registration ends Sept 1 (14h30-16h): getting started 90 minutes’ session (recorded) – hackathon wiki site launch Sept 1-12: teams’ creation and ideation phase Sept 12-13 (9h-17h): hackathon days, with kickoff in the am Sept 15 (16h-17h): hackathon popcorn and beer showcase Voting live by audience + online Sept 18: hackathon winners announced

(TODO JO) Getting Started section in which you will define:

https://github.com/AutodeskGames/stingray-plugin#step-1-install-prerequisites

The machine and environment setup and requirements, i.e. step by step instructions of everything your users must install on their machine to participate. Information about licenses they need to obtain, where applicable

TODO: Faire un build developer de 1.9 et mettre sur dropbox

Information about how to request access to source code or systems, where applicable

If you want to build your own version of Stingray https://git.autodesk.com/gameware/stingray/tree/1.9.1494.0

instructions on video recording software, if you are expecting a video and not a live pitch. If a live pitch is requested, you can also provide a template, to ensure consistency in the presentations

TODO: Find link used for Forge hackothon

(TODO SEB) Technology Overview section, in which you will:

describe the product, technology or API you want participants to use provide some context ; how does it fit in the Autodesk echo-system? what is it used for?

http://help.autodesk.com/view/Stingray/ENU/?guid=__sdk_help_introduction_html

Sample Applications

in which you will provide 'documented' source code for 2-3 (min) applications. Those will serve as starting point for participants and will speed up their on-boarding process. You can also provide templates, where applicable.

  • (TODO JO) Giphy

TODO: Mettre lien GitHub de la solution fonctionnel sur 1.9

  • (TODO SEB) Thunderstorm

(TODO SEB) Use Cases and Ideas

section for participants to better understand the different customers or internal workflows for your product. Since many participants have a hard time finding an idea or project to work on, a small list will serve as a source of inspiration

TODO: Mettre des iédes de plugins

(TODO SEB) Participants & Teams section, in which you will define:

the target audience for your event the skills or knowledge requirements your participants must have, eg: programming or scripting languages, coding experience, ... the recommended team size (often ~4 people) and composition (if you need a mix of skills or profiles)

(TODO SEB) Getting Ready

  • C++ sites
  • JavaScript sites
  • Lua cheat sheet
  • Tutorials
  • Stingray Lua API

for your Event section in which you can list all the tasks participants must do prior to participant, for instance: setting up your environment listening to a video attending an online training or presentation reading sections B and C above forming their teams (if they need to be formed before the event) finding their ideas (if they need to find them before the event) connecting to a source repository (eg GitHub) + instructions of what to do with their code at the end? should it be kept local, shared, ....

(TODO JO) Subject Matter Experts & Getting Support section in which you will:

  • Slack channel?

  • Contact info

  • Jonathan Schmidt

  • Sebastien Phaneuf

  • Karine Roy

  • Carlos ou Andrew

  • Robb

list the name of the SMEs that will assist the participants during the event instructions on how to reach them (will they be onsite or on a slack channel? if so, provide the URL to it) their schedule during the day

(TODO JO) FAQ section in which you will answer what you believe will be the most common questions. For instance:

what if i don't have a team or an idea? can i participate alone?

do i need working code at the end?

Yes

what if i am not an engineer, can i still participate?

If you can find an engineer to work it.

if i am remote, can i still participate?

Yes, but support might be harder to get.

Clone this wiki locally