search

NESCent / hip_hack_howto

Hackathon guidance from NESCent's Hackathons, Interoperability, Phylogenies working group.
1 stars 1 forks source link

add graphic illustrating typical day 1 schedule #18

Closed arlin closed 7 years ago

rvosa commented 9 years ago

Do we feel like we have a canonical description of the day 1 schedule or is this the moment to flesh that out? The manuscript outlines:

epontell commented 9 years ago

Sounds right to me. Looking at the schedule of the events, some cases saw technical presentations being made after pitches (I guess to facilitate selecting topics relevant to the projects).

Enrico

College of Arts & Sciences New Mexico State University Las Cruces, NM 88003

On Mar 30, 2015, at 1:10 AM, Rutger Vos notifications@github.com wrote:

Do we feel like we have a canonical description of the day 1 schedule or is this the moment to flesh that out? The manuscript outlines:

Welcome and introductions ("brief") Technical presentations ("90min - several hours") Open discussion ("The appropriate time to end the discussion is when participants are ready to proceed to the next stage") Initial pitches and feedback (how long? number of pitches * X minutes) Team formation and pitch refinement (how long?) Solidification of team plans (optional) — Reply to this email directly or view it on GitHub https://github.com/arlin/hip_hack_howto/issues/18#issuecomment-87575074.

arlin commented 9 years ago

ok, getting this to work in github now. Here are some graphical ideas for anyone who wants to try this (don't assume that the times are right). We could do a timeline with braces, or with trapezoidal blocks.

graphic

arlin commented 9 years ago

I think the last action for the day is "teams report out", i.e., teams stand up and present their revised plan and their roster.

As I recall, we sometimes had multiple bouts of discussion, ideas and technical talks.

With respect to the exact timeline, here are my suggestions:

hlapp commented 9 years ago

Technical presentations - 60 to 150 min

I would normally refer to this block of time as "stage-setting talks". Usually these would be presented by users (helping to drive home pain points), and/or some big picture talk that brings everyone on the same page with regard to context and scope.

Is this what you mean by "Technical Presentations"? When I see "Technical presentations" I think bootcamps, but presumably you mean something else?

rvosa commented 7 years ago

Are we still doing this? In the manuscript we're not referencing a figure like this. Maybe this is not necessary?

hlapp commented 7 years ago

I think it would be very useful to have from a reader's perspective.

rvosa commented 7 years ago

Ok, I can work on this.

rvosa commented 7 years ago

I've added a figure (named fig4.pdf) to the stash on overleaf.

hlapp commented 7 years ago

I assume the figure caption will explain what the tick marks stand for?

fig4.pdf

rvosa commented 7 years ago

Time. Minor tick marks 15 minutes, then 30, then 60. Op Thu, 8 Dec 2016 om 16:16 schreef Hilmar Lapp notifications@github.com

I assume the figure caption will explain what the tick marks stand for?

fig4.pdf https://github.com/NESCent/hip_hack_howto/files/639798/fig4.pdf

— You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub https://github.com/NESCent/hip_hack_howto/issues/18#issuecomment-265764781, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGf-nh3m25SAjSjdh3yam1eVFqoJ3yYks5rGB9IgaJpZM4D19WF .