Workshop Template
Created by Adrian Cole, last modified on Nov 07, 2018
delete things in blue italics
replace examples in red
The goal should be clear, and outcome oriented though not necessarily code oriented. For example, a goal could be to achieve insight into a site's concerns. It could also be work-related, like completing X or coming to an agreement on Y. Finally, a goal can be determined later. For example, an expert could lead us through unexplored areas, and our goal is to decide where we fit into that.
Important to note the days and which timezone (specifically UTC offset)
29 Oct - 30 Oct 2018 during working hours in JST (UTC +9)
Provide the most specific location, but most appropriate for anonymous viewing. It is no problem to be vague like a town name. It is also fine to mention details are distributed offline.
LINE HQ JR Shinjuku Miraina Tower, 23rd Floor
Folks attending will need to coordinate offline
We will add notes at the bottom of this document including links to things discussed and any takeaways.
Mention what's expected. Workshops are not the same as meetups: Almost always intimate knowledge is required of at least Zipkin or a contributing topic. Meetups are often completely open, yet also have room for many more. Highly resist any workshop with over 12 especially approaching 20 people as they can be very unproductive in practice.
The scope of this workshop assumes attendees are intimately familiar with Zipkin and X, as we have to discuss details of UI design.
Being physically present is welcome, but on location constrained. Remote folks can join via Gitter and attend a TBD video call.
Note who is present and who they associate themselves with (if anything). Leave association to the person. Remove their name if they can't make it for any reason so that they aren't falsely attributed. Mention the maximum space constraints
-
Max people onsite are 8!
List anything here that will help people not have to spend time rehashing. For example, wikis, github issues, papers, alternative tech
Please review the following before the meeting
Start early as appropriate for the site. Always start with intros and conclude with a round-table. This Don't forget to carve time for meals. Remember many are volunteers so try to keep it fun also, but don't assume everyone drinks (though they might.. ask!). Finally, it is better to have a workshop document sparsely made vs no document!
If any segment is in bold, it will be firmly coordinated for remote folks. Other segments may be lax or completely open ended.
| 2:00pm | introductions |
| 2:30pm | Overview zipkin's current UI |
| 4:00pm | Overview's internal UI and motivation |
| 5:30pm | Overview of dependency work |
| 10:00am | UI hacking |
| 1:00pm | Vinay on haystack-ui bluejeans |
| 3:00pm | Discussion on shared spans and impact to UI |
| 5:30pm | round up |
| 6:00pm | Beers at the watering hole, Shinjuku |
Add outcomes categories as appropriate, such as planning, social, code or doc improvements.
Notes should be kept at least daily, better as things occur. Note who asks questions and who provided answers, as it helps later.
Notes will run below here as the day progresses. Please don't write anything that shouldn't be publicly visible!
Screen Shot 2018-11-01 at 2.37.49 PM.png (image/png)
Screen Shot 2018-11-01 at 2.00.44 PM.png (image/png)
Screen Shot 2018-11-01 at 2.00.52 PM.png (image/png)
Screen Shot 2018-11-01 at 2.41.40 PM.png (image/png)
Document generated by Confluence on Jun 18, 2019 18:50