-
Notifications
You must be signed in to change notification settings - Fork 86
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs(hackathon): make this a bit more official than a slack message
- Loading branch information
Showing
2 changed files
with
72 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
# Rumathon I | ||
|
||
June 17th to 20th, Basel, Switzerland (Adobe Office) | ||
|
||
--- | ||
|
||
(See the [Hackathon Archive](./README.md) for past Operations Workshops and Hackathons) | ||
|
||
### Rumathon??? | ||
|
||
This is a more or less spontanous workshop to ge the team together and work on things | ||
that have come up, discuss ideas and generally have a good time. We are modeling this | ||
after the Helix Hackathons, but due to the short notice, everything will be a bit more | ||
bare-bones than usual. We are also meeting in the Basel office, but I'd ask you to | ||
keep the number of sidetracks reasonable. | ||
|
||
### Agenda | ||
|
||
> I hear this is an rumathon workshop, are you going to taste RUM all day? | ||
Trying to get as much of the virtual team together, the goal is to have high-bandwidth exchanges on the current state and next steps of RUM. We will try to keep it hands-on, so instead | ||
of presentations, we will rely on code settling arguments, this means we won't be hacking all the time, there will also be plenty | ||
of programming and coding. | ||
|
||
The main purpose of the hackathon is social: allow the team to reconnect, meet new team members for the first time, and work on | ||
stuff that won't fit neatly into a 45-minute Teams meeting. | ||
|
||
| Time | Monday | Tuesday | Wednesday | Thursday | Friday | | ||
| --------: | ------------------------------------------------------ | ------- | --------- | -------- | ------- | | ||
| Morning | Noon: Kickoff, Introductions, Architecture | Hacking | Hacking | Hacking | - | | ||
| Afternoon | Hacking | Hacking | Hacking | Demos | - | | ||
| Evening | Social | Social | Social | - | - | | ||
|
||
### Location | ||
|
||
> Where is this going to happen? Do you have a windowless conference room blocked out? | ||
In the Basel office. We don't have a room yet, but it will likely have windows. | ||
|
||
#### Travel | ||
|
||
BSL. You are either there already, or you know the drill. | ||
|
||
### Goals | ||
|
||
> What are you planning to show at the end of the week? | ||
Put down the topic and the people that would like to discuss it: | ||
|
||
The theme of this offsite is .... | ||
|
||
#### Ideas / Suggestions / Topics Collection | ||
|
||
### Attendees | ||
|
||
> Who is going to be there? Can I come? | ||
If you had your hands on RUM code in the past year, you are welcome to join us. Put your name on the list, so that planning is a bit easier | ||
|
||
2. @trieloff | ||
|
||
|
||
### Preparation | ||
|
||
> What can I do to prepare for the Hackathon? | ||
1. Join `#rum-explorers` on Slack | ||
|
||
### Demos |