may'18 dev week sessions suggestion ground

[phritz]

• (juan) What it's like to work on an open-source crypto project
• dev retrospective
• full architectural walk-through / whiteboard

[mishmosh]

Paper Reading Group: people arrive having read the Filecoin paper at least once. Take an hour to answer any questions/explain areas of confusion. (requested by @frrist)

[dignifiedquire]

• VM in Filecoin now and its future
  (aiming for smaller group to discuss/draft, then make sure it's written down for people read, feedback, understand)

[ZenGround0]

1. Discussion of attacks that have guided / are guiding design decisions and their mitigations*
2. Overview of plans for in-house security testing, and maybe a quick demo of the afl or its golang analog go-fuzz

*1 might benefit from preliminary EC / PoST deep dives

[porcuquine]

Product Dartboard -- a team-assessment tool developed by a C5 PM. Details here: https://protocollabs.slack.com/archives/G7XUR2TU2/p1524773662000416

[phritz]

• decide how we want to start using filecoin as soon as we have alpha
  brainstorm ways to start using filecoin #334

[phritz]

• finish ipfs release process flowchart
• talk about dht stuff

[frrist]

• discuss testnet producing "metric blocks"

[phritz]

• how things change: repo format, protocol messages, etc

[phritz]

• REQUIRED: agree on a process that delivers a usable spec by testnet

[nicola]

• (nicola) Proof-of-Replication/Proof-of-Spacetime implementation

[phritz]

@jbenet has proposed two talks, basically grouped into :

1. filecoin protocol deep dive
2. filecoin implementation & process

https://docs.google.com/document/d/1mSM665SLiDQyl09M0hVG8qFJKUeo_QPANEWIW4XVe6M/edit?ts=5aeb5ba4

[mishmosh]

This list grew by a LOT in the past 24 hours. I've grouped them into Fundamentals and Other Sessions applying a fairly strict filter.

I suggest doing Fundamentals on Day 1, at least #1-3. At the end of Day 1, take 15 minutes as a group to discuss how you want to prioritize other sessions vs. hacking time. Currently, it is not possible to cover all topics nominated and also have any open hacking time. It will help if the Other sessions are opt-in — unless you want to join, or a teammate requests you to join, go talk or pair or take a walk.

Things expand to fill all available space. I highly recommend scheduling structured things back-to-back, rather than one at a time followed by open time (which is more likely to disappear).

Fundamental Sessions

The 4 Fundamental Sessions build shared understanding; everyone should attend. I would expect #1-2 to be ~90 mins each with healthy Q&A, and #3-4 to be 60 minutes each.

1. Deep Dive 1: Filecoin Protocol (@jbenet volunteered | outline)
2. Deep Dive 2: Filecoin Implementation & Process (@whyrusleeping volunteered | outline)
3. Dev Retrospective (@phritz can you facilitate? | stickies format)
4. Product Dartboard team-assessment activity (@clkunzang proposed & volunteered | details)

Other Sessions / Conversations

• Paper Discussion: people arrive having read the Filecoin paper at least once. Take an hour to answer any questions, explain areas of confusion, and discuss. (requested by @frrist + many +1s in dev meeting; need to confirm an explainer, likely @nicola @jbenet)
• VM now and its future (@dignifiedquire): aiming for smaller group to discuss/draft, then make sure it's written down for people read, feedback, understand
• Discussion of attacks that guide design decisions and their mitigations (after preliminary EC / PoST deep dives) (@ZenGround0)
• Overview of plans for in-house security testing, and maybe quick demo of the afl or its golang analog go-fuzz (@ZenGround0)
• What it's like to work on an open-source crypto project
• Decide how we want to start using filecoin as soon as we have alpha (@phritz)
• Finish ipfs release process flowchart (@phritz)
• Talk about dht stuff (@phritz)
• Discuss testnet producing "metric blocks" (@FRRRST)
• How things change: repo format, protocol messages, etc (@phritz)
• REQUIRED: agree on a process that delivers a usable spec by testnet (@phritz)
• Proof-of-Replication/Proof-of-Spacetime implementation (@nicola)

Space, Time, and People Hacks

The first 2 minutes of each day are critical to the energy and focus of the group. That means as little lag time as possible: the space is set up beforehand, and host is ready to emcee on time. If recording, test the setup beforehand.

• Describe what's planned that day. It doesn't need to be fancy, but it needs to be clear.
• Written timetable helps: whiteboard should be fine for this, don't need printouts.
• For conversations or talks, set up the room so that (1) extension cords go in a corner so it's possible but not easy to charge your devices while using them and (2) people are not behind tables.
• To start the day or regroup after meals, use quick games like "A Strong Wind Blows" or "Soundball" if you need help to get people physically moving and mentally present. Two other game ideas (suggested because this team mostly doesn't know each other well): how much do you use and worst job.
• It is surprisingly difficult to both play timekeeper and fully engage in the conversation. Outsource timekeeping to an alarm.

[whyrusleeping]

When scheduling please keep in mind that I want the majority of our time to be spent hacking together, *not* in meetings and presentations. (i prefer majority == 66%, but could be pressed into 51% because blockchain) Thanks, Why

…

On May 4, 2018, 1:50 PM +0900, Michelle Lee ***@***.***>, wrote: This list grew by a LOT in the past 24 hours. I've grouped them into Fundamentals and Other Sessions applying a fairly strict filter. I suggest scheduling the Fundamental sessions on Day 1, at least #1-3. At the end of Day 1, take 15 minutes as a group to discuss how you want to prioritize other sessions vs. hacking time. Currently, it is not possible to cover all topics nominated and also have any open hacking time. It will help if the Other sessions are opt-in — unless you want to join, or a teammate requests you to join, go talk or pair or take a walk. Things expand to fill all available space. I highly recommend scheduling structured things back-to-back, rather than one at a time followed by open time (which is more likely to disappear). Fundamental Sessions The 4 Fundamental Sessions build shared understanding; everyone should attend. I would expect #1-2 to be ~90 mins each with healthy Q&A, and #3-4 to be 60 minutes each. 1. Deep Dive 1: Filecoin Protocol ***@***.*** volunteered | outline) 2. Deep Dive 2: Filecoin Implementation & Process ***@***.*** volunteered | outline) 3. Dev Retrospective ***@***.*** can you facilitate? | stickies format) 4. Product Dartboard team-assessment activity ***@***.*** proposed & volunteered | details) Other Sessions • Paper Discussion: people arrive having read the Filecoin paper at least once. Take an hour to answer any questions, explain areas of confusion, and discuss. (requested by @frrist + many +1s in dev meeting; need to confirm an explainer, likely @nicola @jbenet) • VM now and its future ***@***.***): aiming for smaller group to discuss/draft, then make sure it's written down for people read, feedback, understand • Discussion of attacks that guide design decisions and their mitigations (after preliminary EC / PoST deep dives) • Overview of plans for in-house security testing, and maybe quick demo of the afl or its golang analog go-fuzz • What it's like to work on an open-source crypto project • Decide how we want to start using filecoin as soon as we have alpha • Finish ipfs release process flowchart • Talk about dht stuff • Discuss testnet producing "metric blocks" • How things change: repo format, protocol messages, etc ***@***.***) • REQUIRED: agree on a process that delivers a usable spec by testnet ***@***.***) • Proof-of-Replication/Proof-of-Spacetime implementation ***@***.***) Space, Time, and People Hacks The first 2 minutes of each day are critical to the energy and focus of the group. That means as little lag time as possible: the space is set up beforehand, and host is ready to emcee on time. If recording, test the setup beforehand. • Describe what's planned that day. It doesn't need to be fancy, but it needs to be clear. • Written timetable helps: whiteboard should be fine for this, don't need printouts. • For conversations or talks, set up the room so that (1) extension cords go in a corner so it's possible but not easy to charge your devices while using them and (2) people are not behind tables. • To start the day or regroup after meals, use quick games like "A Strong Wind Blows" or "Soundball" if you need help to get people physically moving and mentally present. Two other game ideas (suggested because this team mostly doesn't know each other well): how much do you use and worst job. • It is surprisingly difficult to both play timekeeper and fully engage in the conversation. Outsource timekeeping to an alarm. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.