-
Notifications
You must be signed in to change notification settings - Fork 24
Hackathon (Sep. 2017)
the event goal the theme, if there is one, and the kinds of ideas you are expecting instructions and links to sign up its length and schedule how the ideas will be evaluated/judged (incl. evaluation criteria) the reward for participation, if any
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 Information about how to request access to source code or systems, where applicable 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
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?
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.
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
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)
Getting Ready 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, ....
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
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? what if i am not an engineer, can i still participate? if i am remote, can i still participate?